Accessibility statement for Annex
Yakup Efe Çalışkan is committed to making Annex accessible, in line with Directive (EU) 2019/882 (the European Accessibility Act).
What this service is
Annex is a website about the accessibility obligations that came into force with the European Accessibility Act, and a subscription service for agencies that need to keep client sites in order under it. The public pages explain WCAG 2.2 success criteria in the terms of an online shop, list the national law that transposed the directive in each of the 27 member states, and explain how enforcement is structured. A free tool checks the markup of a single page. The paid service scans a portfolio of client sites on a schedule, publishes an accessibility statement for each one, and keeps a dated record of the scans.
How the service works
Every public page is plain HTML with no JavaScript required to read it: navigation, tables and text all work with scripting switched off. The exception is the free scan tool. Its rule engine runs in your own browser in both of its modes, so the scanning itself never happens on a server. If you paste a page source, nothing you paste leaves your browser at all. If you instead give it an address, that address is sent to our server, which fetches the page and passes the HTML back for your browser to check; we do not store the address or the page, and the tool says so at the point where you enter it. Results appear in a region marked as a live region so that assistive technology is told when they arrive. Colours follow the light or dark theme your system asks for. There is no account, no sign-in and no cookie banner, because the site sets no cookies and runs no analytics or tracking scripts of any kind.
How the accessibility requirements are met
This service is assessed against EN 301 549 V3.2.1, which references WCAG 2.2 Level AA. Its current status is partially conformant. The status is stated as partial for one reason: this site has never been tested with a screen reader. Everything that can be checked without a person has been checked and passes, but automated checking is not the same as knowing, and claiming full conformance on the strength of it would be exactly the overstatement this product exists to argue against. The record of scans below starts on 3 September 2026, which is when the record itself started rather than when the work did.
Known limitations
- The site has never been tested with a screen reader. Why: It is built and maintained by one person, and no assistive technology testing has been done. Automated checks and a keyboard pass cannot stand in for hearing how a page is actually announced. Planned: A manual pass over the home page, one criterion page and the free scan tool, using NVDA and VoiceOver, before this statement is next reviewed.
- When the free scan tool finds many issues, the entire result block is announced at once. Why: Results are written into a single polite live region. That is correct in the sense that the arrival of results is announced, but a long list announced in one go is tiring to listen to and gives no way to skip ahead. Planned: Announce a short summary in the live region and move the detailed findings outside it, so the count is spoken and the list can be navigated by heading.
- Findings from the free scan tool quote the failing markup as unwrapped code, which can be long. Why: The quoted source is what makes a finding actionable, so it is not abbreviated. Long lines are made scrollable rather than truncated, and a horizontal scroll region is harder to operate than flowing text. Planned: Under review. Truncating the evidence would make findings less useful, so any change has to keep the full source reachable.
- The scan tool judges markup only, and several requirements are outside what it can see at all. Why: It reads the HTML a server returns. It does not run JavaScript and does not render the page, so colour contrast, keyboard operation, focus visibility and anything built after page load are invisible to it. Planned: Not a defect to be fixed but a limit to be stated. Every result names these criteria as needing human review rather than reporting them as passed.
How this was assessed
Three kinds of check. First, every page is scanned by Annex's own rule engine on every build, and a single error-level finding stops the build; the most recent run covered 80 pages with no errors and no warnings. Second, because colour contrast cannot be judged from static HTML, the site's colour palette is checked separately against the WCAG contrast formula in the automated test suite: 13 text and background combinations, in both the light and the dark theme, all at or above the 4.5:1 threshold for normal text. Third, a manual keyboard pass was carried out in a browser on 3 September 2026, which confirmed that the skip link is first in the tab order and becomes visible when focused, that there are no focusable elements hidden off-screen acting as keyboard traps, that a visible focus indicator is applied, and that the heading structure has one first-level heading and no skipped levels. No screen reader testing has been carried out, and no third party has audited the site.
This statement was last reviewed on 2026-09-03.
Record of automated scans
This service is scanned on a schedule. Each scan is kept so that progress over time can be shown. Automated scanning does not cover every requirement — see the limits noted below.
| Date | Pages | Errors | Warnings |
|---|---|---|---|
| 2026-09-03 | 80 | 0 | 0 |
Getting this information in other formats
Everything on this page can be provided in spoken form at no cost. Write to the address below and it will be explained by email, or a voice or video call will be arranged at a time that suits you and the contents read out and discussed. No telephone number is published because the service is run by one person and a published number could not be answered reliably; arranging a call by email means the call actually happens.
Contact
Yakup Efe Çalışkan — yakupefecaliskann@gmail.com
Feedback and complaints
Not required by Annex V. A feedback mechanism and an enforcement procedure are required of public sector bodies under Directive (EU) 2016/2102, not of private service providers under the European Accessibility Act. This section is included as good practice.
If you encounter a barrier using this service, write to yakupefecaliskann@gmail.com. We aim to reply within 5 working days.
Annex is not one of the e-commerce services the European Accessibility Act covers, and as a microenterprise it is exempt in any case, so there is no market surveillance authority to escalate to over this particular site. That cuts both ways: there is no external body obliging a reply, which is why the commitment above is stated plainly and why every limitation known at the time of writing is listed rather than summarised.
About this statement
This statement is published voluntarily. Annex is run by one person and is a microenterprise as defined in Article 3, point (23) of the directive, so under Article 4(5) it is exempt from the accessibility requirements for services and from the obligations that go with them. It follows the structure of the information obligation in Annex V of Directive (EU) 2019/882 because that is the useful shape for the information, not because it is owed here.
National transpositions differ, and this page is not legal advice.
Statement generated and hosted by Annex, which scans this service on a schedule and keeps the record above. Annex does not certify compliance and cannot; automated testing covers only part of the applicable requirements.