Accessibility statement
We aim for WCAG 2.2 level AA on specoria.com. This page shows what we measured, how and when, the gaps we know about and how to report a barrier.
Target standard
Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, for the public site specoria.com in English and Turkish.
We don’t claim the site fully meets it. No independent audit has been done yet, and automated tests catch only part of the criteria.
Last measured: October 14, 2026. Statement updated: October 14, 2026.
What we measured and how
- Automated check: axe-core 4.14.0 with the WCAG 2.0, 2.1 and 2.2 A and AA rules, in Chromium at 1280 × 800 and at 375 × 812 (phone emulation), on a local build of the site. Pages: the list below, each in English and Turkish.
- Before this round of fixes (20 addresses): serious or critical issues on 20 of 20, across 7 rules and 150 elements. The main ones: language links whose spoken name didn’t contain the visible “TR” or “EN”, the phone menu button without a name, a focusable link inside an area hidden from screen readers, small text with low contrast and scrollable code boxes a keyboard couldn’t reach.
- After the fixes (24 addresses, both viewports): no serious or critical issues found by the automated check.
- Keyboard: on 11 English pages we pressed Tab through the first 60 focus stops. On every page the first stop is “Skip to content”. 1 field had no visible focus ring (the search box on the home page); we fixed it.
- Narrow screens: on October 13, 2026 we opened all 266 pages at 320, 375 and 768 px wide (browser emulation, not real devices). After the fixes no page scrolls sideways.
- The same automated check runs in our build pipeline (CI) on every change pushed to the code repository and marks the change as failed when it finds a serious or critical issue.
Pages in the automated check
Not measured yet
- Screen readers (VoiceOver, NVDA, TalkBack): not tested.
- Zoom to 200 percent and custom text spacing: not tested.
- Real phones and tablets: not tested. The narrow screen check above is browser emulation.
- Reduced motion: our style sheets switch animations off when your device asks for reduced motion. We haven’t tested this on devices.
- The customer panel (app.specoria.com), downloadable files and pages outside the list above: not measured in this round.
- Third party parts: the Cloudflare Turnstile check on forms and the Stripe checkout: not measured.
Known gaps
- An automated check doesn’t prove conformance. Criteria such as clear link text, reading order and meaningful headings need a person to review them.
Report a barrier
If something on the site is hard or impossible to use with your setup, write to contact@specoria.com. Please tell us the page address, what you tried to do, and your browser and assistive technology if you use one. We reply in writing.
Plan
- October 14, 2026 (done): The automated check runs in our build pipeline (CI) on every change pushed to the code repository.
- October 14, 2026 (done): Fix the three agent simulator issues found in the first measurement (stage label contrast, the pause checkbox name, a focusable control inside the animation window).
- By December 15, 2026: Test the pages above and the free test with screen readers (VoiceOver, NVDA); check 200 percent zoom and text spacing; run the automated check on the customer panel.
- By January 15, 2027: Review this statement with the new measurements.