Accessibility
Last reviewed
What this site does to stay usable however you read it, what has genuinely been tested, and what has not.
1.What this site aims for
This site is built to meet WCAG 2.2 level AA. That is the target, not a certification: it has not been audited by an independent accessibility specialist, and this page says what has actually been checked rather than what would sound reassuring.
2.What is in place
- A skip link to the main content, one landmark per region, and headings that descend in order without skipping a level.
- Everything interactive can be reached and operated from the keyboard alone, in a visible order, with a focus ring that never disappears. The mobile menu closes with Escape.
- Body text sits at 4.5:1 contrast or better against its background, and large text and interface borders at 3:1 or better. The lime accent is used on dark for text, and dark on lime for buttons, both of which pass.
- Every meaningful image has alternative text describing what the screenshot shows, not just that it is a screenshot. Decorative parts of the device frame are hidden from assistive technology.
- Touch targets are at least 44 by 44 pixels, including the navigation and the form controls.
- The form labels its field above the input, marks errors with text next to the field rather than colour alone, announces them, and moves focus back to what needs fixing.
- Sections rise a little as they scroll into view, on the browser's own scroll timeline, and the phone at the top cycles through three screens with a slow fade. Nothing is hidden until a script runs, and with reduced motion turned on neither animation runs and smooth scrolling is disabled as well.
- Text reflows without a horizontal scrollbar down to 320 pixels wide and at 200 percent zoom.
- Automated checks run against every page of the built site: axe-core with the WCAG 2.2 AA rule set reports no violations, and Lighthouse's accessibility audit passes. Automated checks find a minority of barriers, which is why the next section exists.
3.Known gaps
- No testing has been done with real screen reader users. Automated checks and keyboard testing are not a substitute for that.
- The screenshots of the app carry text inside the image. The alternative text describes what each one shows, but the text inside cannot be resized or read directly.
- The Veyrova app itself is covered by its own work and is not described by this page.
4.Reporting a barrier
If something here blocks you, write to ajdina750@gmail.com with the page and what happened. A barrier that stops someone using the site is treated as a defect, not a suggestion.