Accessibility

Built to be usable, and tested that way

This site targets WCAG 2.2 level AA. Claims about accessibility are worth little without a way to check them, so this page explains what is tested, how, and where the limits are.

How it is tested

• Automated audit: axe-core was run against every page, at phone and desktop widths. The result was zero violations.
• Colour contrast: a script reads the real design tokens out of the stylesheet and asserts that every text and background pairing meets the AA ratios, rather than relying on the eye. Run it with npm run audit:contrast.
• Keyboard pass: every control is reachable and operable with the keyboard, in a sensible order, with a visible focus outline.
• Layout checks: page structure is measured in the browser at phone, tablet and desktop widths, including that no box is left orphaned and nothing overflows horizontally.

Things done deliberately

• A skip-to-content link is the first thing the keyboard reaches.
• The rotating front-page panel has a pause control, so content that moves on its own can be stopped (WCAG 2.2.2). Your choice is remembered as you move between pages.
• Reduced motion is respected. With it enabled the panel stops rotating entirely and page transitions are switched off.
• The product video has no audio track and a written transcript, so nothing depends on hearing it.
• Interactive targets are at least 24 by 24 pixels, most are far larger.
• The pointer embellishment is purely decorative and never replaces the real cursor, so the size and colour settings of your operating system keep working.
• Type is set in two self-hosted faces with generous line height, and no text is placed over busy imagery.

Known limitations

• Screenshots are images. Text inside a product screenshot is not readable by assistive technology. Every screenshot carries a caption describing what it shows, and the same information exists as real text elsewhere on the page.
• The site is English only.
• The AI guide is a third-party model. It is restricted to published facts, but a language model can still phrase something imperfectly. Treat its answers as a starting point and check the linked pages.
• Very old browsers without modern CSS support will see a simpler but still usable layout.

Tell me what is broken

If something here blocks you — a control you cannot reach, a contrast problem, a screen-reader name that makes no sense — emailabdurfreelance@gmail.com and describe what happened and what you were using. Fixes take priority over polish.