Please wait while this page is prepared.
Accessibility
MapAble is designed toward WCAG 2.2 AA across its web interfaces, with formal testing pending before any compliance claim is made. ATAG guides Places authoring; UAAG informs display preferences as design guidance only — not conformance claims.
Send accessibility feedbackDetails
Clear information, without overstated claims.
The public website uses semantic HTML, keyboard-focus styles, responsive layouts and accessible loading/error states. Formal WCAG 2.2 AA testing has not yet been completed, so MapAble does not claim conformance at this stage. MapAble likewise does not claim ATAG 2.0 or UAAG 2.0 conformance, and does not claim to be a user agent.
The W3C Web Accessibility Initiative describes accessible experiences as the combination of accessible content, authoring tools, and user agents. MapAble’s design targets map as follows (design targets only — not conformance claims):
Internal mapping for contributors: docs/accessibility/WAI-GUIDELINES-MAP.md.
Map, dashboard and workflow-heavy screens require additional assistive technology testing, manual keyboard checks and user-centred accessibility review before production launch. Places authoring needs continued ATAG Part A/B evaluation (including accessible content output). Display preferences need continued keyboard, screen reader, zoom, reduced-motion, and persistence testing alongside WCAG for the panel UI itself.
If a page is difficult to use with a screen reader, keyboard, switch control, magnification, captions, colour settings or another access technology, contact MapAble so the issue can be recorded and prioritised.
