murattunalı.
Reading

@type
Service
@id
/en/services/web-accessibility-audit/#service
serviceType
Web Accessibility Audit
provider
/#org
areaServed
Istanbul Q406 · Turkey Q43 · Europe Q46
availableChannel
ServiceChannel · /en/contact/ · tr en de
hasOfferCatalog
OfferCatalog · 5 Offer
audience
Audience · audienceType
url
/en/services/web-accessibility-audit/

Web Accessibility Audit.

Accessibility is not a plugin added on top of a site; it is the code itself. We audit the site criterion by criterion against WCAG 2.2, fix the problems at the source and document the result — with proof of compliance if Turkey’s Presidential Circular or the European Accessibility Act applies to you.

DELIVERABLEShasOfferCatalog › Offer × 5in schema
  1. WCAG 2.2 AA audit: by template and critical flow
  2. Ministry checklist (level A): question by question
  3. Keyboard, screen reader and contrast testing — by hand
  4. Fixes at the source or a prioritized fix list
  5. Accessibility statement and regression checks
EVIDENCEObservation × 0not in schema · human only
Contrast on this site: body text 15.54:1, focus ring 7.66:1WCAG calculation from the color tokens · repeated on every build

source: css/tokens.css + css/base.css · WCAG ratio computed at build

WHO IT IS FORaudience.audienceTypein schema
Institutions and companies covered by Presidential Circular No. 2025/10 or the European Accessibility Act that have to document their conformance.
NOT FOR—not in schema · human only
We do not take on projects that want to cover the problem with an accessibility plugin or want a conformance statement without an audit; the statement is written after the measurement.

PROCESSHow does a web accessibility audit work?

  1. Inventory and scope

    The site’s templates, forms and critical flows (contact, quote, checkout) are listed, and which regulation applies to you is written down at the outset. The audit covers not every page but every template and every critical flow.

  2. Automated and manual testing

    Automated scans find only part of the problems. Full keyboard navigation, reading with a screen reader, contrast measurement and form error messages are tested by hand; each finding is recorded with its criterion and a screenshot.

  3. Fix at the source

    Problems are fixed in the template, the component and the content; no correction layer (overlay) is added on top of the page. If your team will make the fixes itself, the list is delivered in order of priority.

  4. Re-test and statement

    Fixes are re-tested with the same method. The result is a report showing how each criterion is met and a publishable accessibility statement; automated checks that catch regressions in later releases are part of the delivery too.

WHY THIS WAYWhy is an accessibility plugin not enough?

Why an accessibility plugin is not the fix

A fix-up script loaded on top of the page (an overlay) does not change the source code: the wrong heading hierarchy, the unlabeled form field and the menu that cannot be reached by keyboard stay exactly where they are. The script loads extra JavaScript on every visit and can clash with the tools screen reader users already rely on — which is why accessibility experts have signed a joint statement against overlays. The lasting fix is to correct the problem in the template where it originates.

Automated scanning is only part of the job

Automated tools find the issues a machine can decide, such as contrast or missing alternative text; they cannot tell whether an alternative text is accurate or whether the focus order makes sense. The limits of automated testing define the audit’s method: scanning is the starting point, manual testing is the result.

Accessibility is a deliverable

Every release of this site passes an automated accessibility audit and a suite of 1462 tests before it goes live; the focus ring, touch targets and contrast each have their own guard in that suite. The same logic is built into the site that is handed over: accessibility is not a job done once and left behind, but a contract measured again with every update.

Accessibility and search read the same structure

A meaningful heading structure, alternative text and links that make sense from their own text are the structure that a screen reader, a search engine and an answer engine all read. An accessible page is also more legible to machines — the very “two readers” principle of this site’s method.

SCOPEWhat does an accessibility audit include?

WCAG 2.2 AA audit

The audit’s yardstick is WCAG 2.2. The target level is AA: it is the technical reference of European regulation and the level most tender specifications require. Targeting AA also meets the level A the Circular requires; the difference is explained in the A, AA and AAA guide.

The Circular checklist: 2025/10

The checklist of the Ministry of Family and Social Services makes level A auditable question by question. The report is also delivered in that list’s order, so an institution entering the monitoring process can answer every question with a screenshot. More on the Circular: the Presidential Circular and its checklist.

Preparing for the European Accessibility Act (EAA)

If you sell online to consumers in the EU, the EAA may apply to you regardless of where your company is established. In that case the audit follows the web section of the European standard EN 301 549 and includes the pages in the target market’s language.

Accessibility statement

The statement says plainly which criteria the site meets, the known gaps and how to give feedback. It is not a claim but a summary of the measurement; that is why it is written after the audit, not before.

WHO IT APPLIES TO

The summary below is taken from the official texts and is not legal advice; consult a lawyer about your own obligations.

Turkey: Presidential Circular No. 2025/10

Published in the Official Gazette on 21 June 2025, the Circular requires websites and mobile applications to be brought into line with the Ministry’s level A checklist and WCAG 2.2. A one-year period was given to public institutions and organizations, universities, municipalities and municipal companies, banks, private hospitals, private education institutions opened with the permission of the Ministry of National Education, private passenger transport companies, Group A travel agencies and electronic communications operators with more than 200,000 subscribers. Service providers engaged in electronic commerce under Law No. 6563 were given two years.

Monitoring is carried out by commissions set up by the Ministry of Family and Social Services; an organization found accessible is granted the right to use the Accessibility Logo for two years.

European Union: the European Accessibility Act

EU Directive 2019/882 has applied since 28 June 2025. Its scope is products and services offered to consumers; e-commerce services through which contracts with consumers are concluded online are one of them. What matters is not where the company is established but whether the service is offered to consumers in the EU. Microenterprises with fewer than ten employees and an annual turnover or balance sheet total of no more than two million euros are exempt from the service obligations. Its German implementation is the Barrierefreiheitsstärkungsgesetz (BFSG).

Who it does not directly cover

A company website of a manufacturer that sells only to businesses does not appear to fall directly within either regulation. Even so, accessibility comes up in tenders, in large buyers’ supplier specifications and in the structure search engines read: accessibility and SEO.

LOCATION: ISTANBUL

Istanbul, TR — remote by default; on site when it matters.

Related

FREQUENTLY ASKED QUESTIONS

SOURCES