Turkey’s Presidential accessibility circular (2025/10): who it covers, deadlines and the checklist.
Turkey’s Presidential Circular No. 2025/10, published in the Official Gazette on 21 June 2025, requires the websites and mobile applications of public institutions, and also of banks, private hospitals, private passenger carriers and service providers engaged in e-commerce, to comply with the Ministry’s level A checklist and WCAG 2.2.
This page explains what the circular says and what it means in practice. A warning up front: nothing here is legal advice. The scope of your obligation depends on your institution’s status and your contracts; a binding answer requires a lawyer. What follows is the technical frame.
What the circular says
The circular put the accessibility of public institutions’ websites and mobile applications on the agenda, pointing to WCAG 2.2 as the technical reference and level A as the conformance level. In other words, the circular ties conformance to an international standard and to a specific level of that standard.
That reference matters because it brings measurability. “An accessible site” is a debatable concept; “a site meeting the 31 success criteria of WCAG 2.2 level A” is not — it either meets them or it does not, and every criterion can be tested one by one.
Whom does the circular cover, and by when?
The circular splits the deadline into two groups but does not state a separate start date. Counted from its publication in the Official Gazette on 21 June 2025, the first group’s deadline passed in June 2026 and the e-commerce group’s runs out in June 2027. Check your own date against the official source and with your lawyer; this page is not legal advice.
- One year · public — public institutions and bodies, universities, municipalities, state economic enterprises, companies, businesses and affiliates owned by municipalities, and professional bodies with public-institution status.
- One year · private — banks, private hospitals, and private educational institutions licensed by the Ministry of National Education.
- One year · transport and tourism — road transport operators under Road Transport Law No. 4925, passenger ships, private companies carrying passengers by rail and air, and Group A travel agencies licensed by the Ministry of Culture and Tourism.
- One year · communications — electronic communications operators with more than 200,000 subscribers.
- Two years · e-commerce — service providers engaged in electronic commerce under Law No. 6563 on the Regulation of Electronic Commerce. The text sets no size threshold, and it makes no distinction between selling to consumers and selling to businesses.
What happens when the deadline passes?
The circular sets no sanction for when the deadline passes. What it sets up is a monitoring structure: a Monitoring Commission chaired by the Minister of Family and Social Services, an Advisory Commission that gives opinions, and a Review Commission that each monitored institution, body and legal entity sets up internally. The Review Commission examines its own site technically and reports to the Monitoring Commission; the Minister announces the result reports. The Ministry sets out how the commissions work.
The Ministry’s announcement of the circular goes a step further: it says that information on websites and mobile applications found not to meet the accessibility requirements within the deadline will be shared with the public. The first group’s deadline passed in June 2026; as of November 8, 2026, we found no published monitoring results.
Once monitoring is complete, the Ministry grants an institution or body found accessible the right to use the Accessibility Logo for two years; how to use the logo on a website is covered in the accessibility logo guide. Working out by measurement whether you are in scope, and what will go into the Review Commission’s report, is the first step of a web accessibility audit.
The Ministry checklist: 31 criteria, 126 questions
Following the circular, the Ministry of Family and Social Services published an assessment checklist. It takes the 31 success criteria of WCAG 2.2’s level A and expands them into 126 assessment questions, grouped under the four principles: perceivable, operable, understandable, robust.
The expansion from 31 to 126 is no accident. A success criterion usually covers more than one situation — the “non-text content” criterion, for example, concerns images, icons, charts, CAPTCHAs and decorative elements separately. By turning these situations into individual questions, the checklist removes subjectivity from the audit.
The list’s real value is that it ends the argument.
In practice, for a team entering a tender or an audit this means: preparation means producing a documentable answer to each of the 126 questions. Behind every “yes” there should be evidence saying “met on this screen, in this way.”
Whom it binds, whom it affects
The circular does not only cover public institutions; it directly covers the private organizations it names, too: banks, private hospitals, private educational institutions, private passenger carriers, Group A travel agencies, large electronic communications operators and service providers engaged in e-commerce. But its effect does not end there — and this is the point most private sector teams miss.
- Public institution, university, municipality, state economic enterprise and municipal company — directly in scope, deadline one year. Website and mobile application.
- Supplier selling software or sites to the public sector — indirectly in scope through the contract. The delivered product has to satisfy the buyer’s obligation.
- Software or design firm entering a public tender — should expect to see an accessibility clause in the technical specification.
- Private company selling to corporate buyers — if it takes orders online, it may fall under the e-commerce group (the circular makes no distinction between selling to consumers and to businesses); if not, the circular does not bind it, but the buyer’s supplier audits may.
- SME engaged in e-commerce — the circular sets no size threshold for this group; the deadline is two years. A promotional site that does not sell is in none of the named groups; even so, because the definition of “electronic commerce” in Law No. 6563 is broad, have your own situation confirmed by a lawyer.
So for you, the real question may be whether the circular binds your client. Delivering accessible work as a supplier is what gets the client through the audit, and that is increasingly turning into a sales argument.
Is level A enough
The circular references level A. But A is the floor: it covers the criteria whose absence makes content completely inaccessible for some users. For a usable experience it is generally not enough.
A concrete example: the contrast ratio does not appear at level A at all. 1.4.3 “Contrast (Minimum)” sits at AA. A site targeting only A could publish its body text at 2:1 contrast against its ground and count as technically conformant — yet that text is unreadable for someone with low visual acuity, and unreadable for everyone on a phone in the sun.
The same goes for the focus indicator: 2.4.7 “Focus Visible” is at AA. Level A requires keyboard access but does not require the focus to be visible — a site you can navigate by keyboard without ever seeing where you are can conform to A.
The practical advice is therefore: even though A satisfies the circular, set the target at AA. The items most often involved in moving from A to AA are contrast and visible focus; both are measurable, and both are solved at the lowest layer of the design — in color and component decisions. In Europe, EN 301 549, the standard referenced for web accessibility, also requires WCAG’s A and AA criteria together in its web section.
Preparation: a practical order
For a team preparing for an audit, there are four things to do before walking the checklist question by question. They close a large share of the questions in bulk.
- A keyboard tour — use the site end to end without a mouse. Most questions under the operable principle are answered here.
- Semantic cleanup — heading hierarchy, landmark structure, form labels. The foundation of the robust and understandable principles.
- An alternative text inventory — every image’s status must be decided: informative or decorative. The decorative one gets an EMPTY alternative, not an omission.
- An evidence file — for each question, not a screenshot but a repeatable measurement. When the audit is renewed, the same evidence must be reproducible.
The last item is the most skipped and the most expensive. A one-off accessibility fix silently decays within the next three deployments. If the evidence is tied to a reproducible measurement — an automated test, a check script — the decay shows immediately. If it is not, it is rediscovered at the next audit.
The circular does not require an accessibility statement; the model the EU applies to public-sector sites does. For an institution that wants to publish the result of its review, an accessibility statement is the readable summary of the evidence file.
What the 126 questions ask under the four principles
The checklist distributes its questions across the four principles, and the distribution shows where the audit puts its weight. Knowing it helps allocate preparation time correctly.
31 criteria, 126 questions
- 31level-A success criterion
- 126checklist question
- 4principles: perceivable · operable · understandable · robust
- Perceivable — alternatives for non-text content, transcripts for audio and video, information not carried by color or shape alone, text that can be resized.
- Operable — every function doable by keyboard, no focus traps, adjustable time limits, no flashing that could trigger seizures, meaningful page titles.
- Understandable — the page language declared, focus not causing unexpected context changes, errors identified, form fields labeled.
- Robust — markup interpretable by assistive technologies, interface components correctly reporting the name-role-value triple.
Note one thing: none of these principles carries the heading “visual design.” Level A is an almost entirely structural and semantic audit — it checks whether the HTML is written correctly. The visual items (contrast, focus visibility) begin at AA.
Which defects on the checklist are easy to fix?
The four defects below are asked about directly in the Ministry’s list — non-text content (criterion 1), info and relationships (criterion 5), language of page (criterion 24), labels or instructions (criterion 29) — and all four can be fixed with a few lines in the source.
Form labels. Text that looks like a label visually but is not programmatically tied to the field is the most frequent defect. The screen reader says “edit field” and cannot say which field. The fix is binding the label element to the field; placeholder text is no substitute for a label.
Image alternatives. Errors sit at both extremes: the informative image left without an alternative, and the decorative image labeled with a file name or a meaningless text like “image.” The correct alternative for a decorative image is EMPTY — so the screen reader skips it.
Heading hierarchy. Heading levels chosen for visual size (using h4 to make it look small) break the document structure. The screen reader user navigates the page by headings; a broken hierarchy breaks their table of contents.
Page language. A missing or wrong language declaration on the root element makes the screen reader mispronounce the text. Turkish content read by an English voice engine produces something unintelligible to the listener. A one-line fix, a large effect.
The relation to the European Accessibility Act
The circular in Türkiye does not stand alone; it is part of an international trend. Since 28 June 2025 the European Accessibility Act (Directive (EU) 2019/882) has imposed accessibility obligations on certain products and services offered to consumers in the EU, e-commerce included; microenterprises with fewer than ten employees and an annual turnover or balance sheet total not exceeding two million euros are exempt from the service obligations.
For a Turkish company selling online to consumers in the EU this has direct meaning: the directive defines the service provider as whoever provides the service on the EU market or offers it to consumers in the EU, and it does not require the company to be established there. An exporter that sells only to businesses is not covered directly; the effect comes through contract terms where the client has obligations of its own. For a manufacturer building a multilingual B2B site, accessibility is a question of market access.
The practical conclusion: taking AA as the floor covers the level A the circular in Türkiye asks for and meets the core of the web section of EN 301 549 on the EU side; the directive also requires the service’s accessibility information to be published in the general terms and conditions. Working to one standard instead of running two separate compliance efforts is markedly cheaper in the long run.
When the act covers a Turkish company — selling to consumers versus selling to businesses, the microenterprise exemption, Germany’s counterpart BFSG — we cover separately in the European Accessibility Act guide.
Keeping conformance continuous
The most expensive part of accessibility audits is a fix decaying after it has been made. A one-off improvement is silently undone within the next three deployments: a new component removes the focus ring, a new color lowers the contrast, a new image arrives without an alternative.
The only real solution is tying accessibility decisions to code rather than to human attention. If contrast ratios are computed in the palette file and bound to a test, the wrong color pair cannot reach deployment. If the focus ring is a token, it cannot be forgotten. If alternative text is a required field, it cannot stay empty.
Passing the audit takes a day; staying passed takes a system.
The concrete form of this approach: every accessibility decision gets a guard, and the guard runs on every deployment. When a defect appears, it shows in that deployment, not at the next audit, and fixing it takes minutes.
If you want to know whether your site meets these criteria, the web accessibility audit measures every template against WCAG 2.2 point by point, fixes problems at the source and documents the result.