Accessibility statement

Conformance status

We are actively improving accessibility. Core flows — sign-in, property search, map browse, field audit submission, and Lens popup — support keyboard navigation, visible focus, and screen-reader labels.

Measures we take

• Semantic HTML landmarks and skip links
• Visible :focus-visible indicators on interactive controls
• Form labels and announced error messages
• Non-color trust tier labels on facts and badges
• Keyboard-accessible Lens controls on listing pages
• prefers-reduced-motion support in shared UI styles

Known limitations

• The interactive map relies on Leaflet; a keyboard property list is provided as an alternative.
• Some third-party booking sites may constrain how Lens overlays appear.

Feedback and contact

If you encounter an accessibility barrier, contact your node operator or open an issue in the WikiTraveler project repository. Please include the app (Lens, WikiTraveler Access, or Node), your browser, and any assistive technology you use.

Technical reference

Developer checklist and test commands are documented in docs/ACCESSIBILITY.md and the formal EN 301 549 report in docs/CONFORMANCE.md. Run pnpm test:a11y and pnpm lighthouse:ci for automated accessibility regression tests.