Skip to content
FAURITOR

Accessibility

A site designed to be usable, with testing still ongoing

FAURITOR treats accessibility as an engineering requirement. This statement records the implementation baseline without claiming a conformance certification.

Implementation baseline · review required before publication

What is built into this site

  • Semantic page landmarks, headings, labels and link text are used throughout the current routes.
  • Keyboard-visible focus styles, a skip link and keyboard-operable menus, form controls and interactive diagrams are included.
  • Form errors and status changes use labels, descriptions and live announcements where appropriate.
  • Motion has a complete static fallback and is disabled or reduced when `prefers-reduced-motion: reduce` is requested.
  • The layout uses responsive grids and minimum tap-target classes in the interactive controls.

Testing record

The repository runs automated axe checks over the homepage/header/footer tree (with color contrast excluded in jsdom because it has no layout engine), plus source-level tests for keyboard menu behavior, form semantics, reduced motion and responsive structure.

Real-browser inspection at all target viewports, screen-reader testing, zoom at 200%, text-spacing checks and manual contrast verification must still be completed on the deployed site. Passing automated checks alone does not establish WCAG 2.2 AA conformance.

Feedback and requests

If a page or interaction is difficult to use, email contact@fauritor.com with the route, device/browser and the barrier you encountered. Please do not send sensitive personal information in a first report.

Review status

This statement is an implementation baseline, not a declaration of legal accessibility compliance. Owner review and a real-browser accessibility pass are required before final publication.