Accessibility

What works, what is tested and what still needs review.

BaziRoute aims for a readable, keyboard-accessible public site while documenting the accessibility work that automated checks cannot complete.

Current status

Partially conformant through automated and manual code review. This is not a claim of complete WCAG conformance or certification.

Implemented and tested

· Every page declares English language metadata and a meaningful title.
· A skip link moves keyboard users directly to the main content.
· Primary interactive controls receive a visible focus indicator.
· Reduced-motion preferences disable non-essential transitions and smooth scrolling.
· Public pages are built from semantic headings, lists, tables and landmarks.
· The CI audit checks duplicate IDs, empty links, image alternatives, iframe titles, positive tabindex and external-link safety.

Known limits

· No full manual screen-reader audit has been completed.
· Automated checks cannot prove every color-contrast combination.
· Third-party provider pages such as Creem checkout are outside BaziRoute’s markup.
· Generated PDFs use a basic text layout rather than a tagged accessible PDF workflow.
· Older browsers or assistive technologies may expose content differently.

Keyboard basics

Use Tab to move through interactive elements and Shift+Tab to move backward. The first Tab stop is a skip link to the main content. Forms retain visible labels and native controls.

Report an accessibility barrier

Include the page URL, device/browser, assistive technology if relevant, what you tried to do and where the barrier occurred.

[email protected]

Statement reviewed 27 October 2026. Accessibility is rechecked with every static build.