Appearance

Accessibility Statement ​

Effective Date: 2026-07-09 · Document ID: AS-MMA-001 · Contact: info@mapsted.com · Contact UsVersion: 1.0

Document ID: AS-MMA-001 Contact: info@mapsted.com · Contact UsRelated documents: Legal Hub · LA-MMA-001 · OSN-MMA-001

1. Our Commitment ​

Mapsted Corp. is committed to making the Mapsted Maps JavaScript API documentation site and its runtime surface accessible to the widest possible audience, including people with disabilities.

Mapsted Corp. publishes and reviews a Multi-Year Accessibility Plan under AODA O.Reg 191/11 s.14 where applicable; the current plan is available at mapsted.com/accessibility.

2. Conformance Target ​

Mapsted targets WCAG 2.2 Level AA conformance for the public API surface of the Mapsted Maps JavaScript API and the documentation site, validated through combined automated (axe-core) scanning and manual expert review.

Scoped surfaces:

  • This documentation site (docs.mapsted.com/maps-js-api), including all reference, guide, and tutorial pages.
  • The interactive sandbox pages embedded in the documentation.
  • The generated TypeDoc API reference. TypeDoc-generated HTML accessibility is reviewed as part of the formal audit scope; output produced by the TypeDoc version and theme in use at build time is included in the conformance target unless a version-specific carve-out is identified during audit.

The inner map iframe (maps.mapsted.com) is a rich, visually interactive surface. Screen-reader fidelity and keyboard navigability of the indoor map itself depends on the Licensee's use of the Mapsted Maps JavaScript API's accessibility APIs (e.g., setAccessibilityMode). See Section 4 for known limitations.

3. Current Conformance Status ​

At the time of this draft, the documentation site has been scanned with axe-core. The scan returned zero violations at the critical, serious, moderate, and minor severity levels across all surveyed pages.

Important limitation of automated scanning: axe-core is used as an automated scanning input and catches approximately 30–40% of WCAG success criteria. A full conformance claim requires manual auditor review, which is planned prior to public launch.

Automated scans do not constitute a conformance claim under AODA, the European Accessibility Act, or Section 508. A formal accessibility audit combining axe-core automated scanning and manual expert review is planned before or shortly after public launch at docs.mapsted.com/maps-js-api; the audit date and auditor will be recorded here upon completion.

Dark-mode contrast has not yet been independently verified. The VitePress theme used by this documentation site has known colour-contrast gaps in dark mode that may affect WCAG 2.1/2.2 Success Criterion 1.4.3 (Contrast, Minimum) and 1.4.6 (Contrast, Enhanced). Both light and dark themes will be included in the formal audit scope.

4. Known Limitations ​

ComponentLimitationWCAG SCMitigation
Indoor map iframeThe rendered indoor map is a content-rich, visually complex surface. Full screen-reader narration of all map entities is not guaranteed.1.1.1, 4.1.2setAccessibilityMode(true) configures default-route preferences to favour elevators and ramps over stairs and escalators for step-free wayfinding. It does not by itself expose additional ARIA surface for assistive technologies; a dedicated ARIA entity-list surface and formal screen-reader testing (JAWS, NVDA, VoiceOver) are included in the planned formal audit scope.
Indoor map canvas — keyboard trapKeyboard focus entering the map canvas may not be releasable by keyboard alone in certain interaction states.2.1.2Licensees implementing keyboard navigation must implement a documented keyboard escape path per WCAG 2.1.2. The Software does not currently expose a built-in compliant focus-release mechanism for all interaction states; this is a documented known gap targeted for resolution before public launch.
Indoor map iframeKeyboard-only navigation of the map canvas (pan, zoom) requires the Licensee to implement custom keyboard controls using the Mapsted Maps JavaScript API.2.1.1Documentation and sample code for keyboard accessibility integration is provided in the guide.
Documentation sandboxStatus messages within the interactive sandbox (e.g., map load state, route calculation results) may not be announced to assistive technologies if they are not exposed via ARIA live regions.4.1.3ARIA live regions (aria-live="polite" or aria-live="assertive") should be applied to all sandbox status message containers. This gap is targeted for resolution before public launch.
Video contentAny embedded tutorial videos must have captions to meet WCAG 2.2 Success Criterion 1.2.2.1.2.2All embedded videos will be captioned prior to public launch.
TypeDoc API referenceTypeDoc-generated HTML accessibility depends on the TypeDoc version and theme. Output has not been independently audited.MultipleTypeDoc output is included in the formal audit scope; version, theme, and any required carve-out will be confirmed as part of that audit.
Dark-mode contrastVitePress dark theme has known colour-contrast gaps. Dark-mode surfaces have not been independently scanned.1.4.3, 1.4.6Both light and dark themes must be scanned in any formal audit.

The limitations table above will be reviewed with the Maps engineering team for accuracy prior to publication.

5. Applicable Standards and Regulations ​

Mapsted Corp. designs to target the requirements of:

  • WCAG 2.2 Level AA — the international standard referenced by most accessibility regulations worldwide.
  • AODA (Ontario) — the Accessibility for Ontarians with Disabilities Act, 2005 and Integrated Accessibility Standards Regulation (O. Reg. 191/11). Mapsted Corp. will publish and review a Multi-Year Accessibility Plan (MYAP) under O. Reg. 191/11 s. 14; until the plan is published, Licensees and end users may request the current draft from info@mapsted.com. Enforcement contact: Accessibility Directorate of Ontario — ontario.ca/accessibility.
  • EN 301 549 — the European standard for ICT accessibility, referenced by the European Accessibility Act (EAA, Directive 2019/882), which is the binding instrument for commercial operators placing products or services on the EU/EEA market (effective June 2025). Note: the EU Web Accessibility Directive (Directive 2016/2102) applies to public-sector bodies only and is not the applicable instrument for Mapsted Corp.'s commercial operations. Enforcement contact: national market surveillance authorities in each EU/EEA member state where Mapsted products are made available.
  • Section 508 (US) — referenced for the benefit of US Federal Government Licensees. A Voluntary Product Accessibility Template (VPAT) / Accessibility Conformance Report (ACR) is available upon request from info@mapsted.com for US federal procurement engagements.

6. Feedback, Contact, and Enforcement ​

We welcome feedback on the accessibility of this site and the Software. If you encounter a barrier not addressed in Section 4, or if you need content in an alternative format:

We aim to acknowledge accessibility feedback within five (5) business days, consistent with Mapsted's Multi-Year Accessibility Plan (MYAP) commitments and O. Reg. 191/11 s. 14 obligations.

Enforcement (Ontario): If you are not satisfied with our response, you may contact the Accessibility Directorate of Ontario — ontario.ca/accessibility — or file a complaint with the Human Rights Tribunal of Ontario.

Enforcement (EU/EEA): If you are not satisfied with our response, you may contact the market surveillance authority in your EU/EEA member state responsible for EAA enforcement.

7. Review Cadence ​

This Accessibility Statement will be reviewed and updated:

  • Following any material change to the documentation site structure or the public API surface of the Mapsted Maps JavaScript API.
  • Following any formal accessibility audit.
  • At minimum annually.

Last review date will be inserted upon formal approval of this document.

  • Legal Hub
  • Licence Agreement: LA-MMA-001
  • Open Source Notices: OSN-MMA-001