Mapme Accessibility Conformance Reports
Voluntary Product Accessibility Template (VPAT) and Section 508 compliance information for Mapme’s web-based platform.
Overview
Mapme recognizes the importance of accessibility and our responsibility to make information and interactive experiences usable by people with a wide range of abilities. This page contains Mapme’s Accessibility Conformance Report (VPAT), describing how Mapme’s web-based SaaS platform aligns with accessibility standards and guidelines.
What is a VPAT? A Voluntary Product Accessibility Template (VPAT) documents how information and communication technology meets accessibility requirements such as the Revised Section 508 (U.S.), EN 301 549 (EU), and the WCAG success criteria. VPATs help public sector agencies and other organizations evaluate a product’s accessibility when considering procurement.
Other accessibility resources
Accessibility Conformance Report
Product Name: Mapme
Product Version: Continuously updated. Accessibility conformance statement reflects features available as of the Report Date below.
Report Date: September 11, 2025
Contact Information: accessibility@mapme.com
Evaluation Methods Used: Review of Mapme accessibility documentation, WCAG 2.1 AA criteria self-assessment, product feature analysis and internal testing with assistive technologies where applicable.
Applicable Standards / Guidelines:
- WCAG 2.1, Levels A and AA
- Revised Section 508 (U.S.)
- EN 301 549 (EU)
WCAG 2.1 Success Criteria Conformance
The tables below summarize conformance by principle and success criteria. Where we indicate Partially Supports or Not Applicable, the remarks explain limitations or creator responsibilities.
Principle 1: Perceivable
| Criteria | Conformance Level | Remarks & Explanations |
|---|---|---|
| 1.1.1 Non-text Content (A) | Supports | Map markers and images can include alternative text. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (A) | Not Applicable | Mapme does not natively provide prerecorded audio-only or video-only media. Accessibility of uploaded or embedded content (e.g., user-added audio/video) is the responsibility of the map creator.. |
| 1.2.2 Captions (Prerecorded) (A) | Not Applicable | Captions are not applicable unless creators embed video from third-party sources (responsibility of content creator). |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (A) | Not Applicable | Mapme does not provide prerecorded media. |
| 1.2.4 Captions (Live) (AA) | Not Applicable | Mapme does not provide live media. |
| 1.2.5 Audio Description (Prerecorded) (AA) | Not Applicable | Not applicable unless embedded video is used. |
| 1.3.1 Info and Relationships (A) | Supports | Map content is structured with semantic HTML where possible. Lists and markers maintain programmatic relationships. |
| 1.3.2 Meaningful Sequence (A) | Supports | Reading and navigation order is logical (map, list, details). |
| 1.3.3 Sensory Characteristics (A) | Supports | Instructions do not rely solely on shape, size, or color. |
| 1.4.1 Use of Color (A) | Supports | Color is used with labels/markers. High-contrast theme is available. |
| 1.4.2 Audio Control (A) | Support | Audio may autoplay when added to a map, but playback controls (play/pause) are always available to users, satisfying WCAG 2.1 requirements. |
| 1.4.3 Contrast (Minimum) (AA) | Partially Supports | Default templates meet WCAG 2.1 AA; creators must ensure chosen colors meet contrast requirements. |
| 1.4.4 Resize Text (AA) | Supports | Text can be resized with browser settings without loss of content/functionality. |
| 1.4.5 Images of Text (AA) | Supports | Mapme does not rely on images of text except in user-uploaded media. |
Principle 2: Operable
| Criteria | Conformance Level | Remarks & Explanations |
|---|---|---|
| 2.1.1 Keyboard (A) | Supports | Maps, lists, and markers are keyboard-navigable. |
| 2.1.2 No Keyboard Trap (A) | Supports | Users can tab in and out of map components. |
| 2.1.4 Character Key Shortcuts (A) | Not Applicable | No character key shortcuts are implemented. |
| 2.2.1 Timing Adjustable (A) | Not Applicable | No time limits apply to map interactions. |
| 2.2.2 Pause, Stop, Hide (A) | Supports | Animations or autoplay carousels can be paused/disabled. |
| 2.3.1 Three Flashes or Below Threshold (A) | Supports | Mapme content does not flash at rates likely to cause seizures. |
| 2.4.1 Bypass Blocks (A) | Supports | Page navigation can skip to main content; map UI uses structured navigation. |
| 2.4.2 Page Titled (A) | Supports | Pages have descriptive titles. |
| 2.4.3 Focus Order (A) | Supports | Logical tab order provided. |
| 2.4.4 Link Purpose (In Context) (A) | Supports | Links and markers are labeled clearly. |
| 2.4.5 Multiple Ways (AA) | Supports | Maps are accessible via multiple entry points (list view, map view). |
| 2.4.6 Headings and Labels (AA) | Supports | Headings and labels describe purpose. |
| 2.4.7 Focus Visible (AA) | Supports | Visible focus indicators are present. |
Principle 3: Understandable
| Criteria | Conformance Level | Remarks & Explanations |
|---|---|---|
| 3.1.1 Language of Page (A) | Supports | Language is programmatically defined. |
| 3.1.2 Language of Parts (AA) | Supports | Creators may set content in multiple languages. |
| 3.2.1 On Focus (A) | Supports | No unexpected context changes on focus. |
| 3.2.2 On Input (A) | Supports | Input changes do not trigger unexpected navigation. |
| 3.2.3 Consistent Navigation (AA) | Supports | Navigation order and controls remain consistent. |
| 3.2.4 Consistent Identification (AA) | Supports | Icons, controls, and markers are consistently identified. |
| 3.3.1 Error Identification (A) | Supports | Input fields identify errors (e.g., missing required fields). |
| 3.3.2 Labels or Instructions (A) | Supports | Fields and markers include labels/instructions. |
| 3.3.3 Error Suggestion (AA) | Not applicable | |
| 3.3.4 Error Prevention (Legal, Financial, Data) (AA) | Not Applicable | Mapme is not used for financial or legal transactions. |
Principle 4: Robust
| Criteria | Conformance Level | Remarks & Explanations |
|---|---|---|
| 4.1.1 Parsing (A) | Supports | HTML is valid and accessible. |
| 4.1.2 Name, Role, Value (A) | Supports | UI components expose role, state, and property information. |
| 4.1.3 Status Messages (AA) | Supports | Screen readers can announce status messages when map content updates. |
Notes, Exceptions & Creator Responsibilities
- Creator Responsibility: Many aspects of accessibility depend on map creators following Mapme’s best practices (for example, providing alternative text, descriptive titles for locations, and choosing high-contrast colour schemes). See our accessibility guide for step-by-step instructions and checklists.
- Third-Party Content: Accessibility of embedded or linked third-party media, widgets, or maps is the responsibility of the provider or content creator. Mapme cannot guarantee conformance for third-party items embedded by users.
- Customizations & Templates: Default Mapme templates are designed with accessibility in mind, but heavy customizations (custom fonts, external widgets, or third-party scripts) can affect conformance. Developers and creators should test custom maps with assistive technologies.
- Testing Scope: This report is based on documentation review, self-assessment against WCAG 2.1 A/AA and internal feature analysis as of the Report Date. Full independent testing with a range of assistive technologies, user testing with people with disabilities, or third-party audits are recommended for formal certification or procurement requirements.
- Known Limitations: Features that rely on user-uploaded media (video without captions, images without alt text) or external services may reduce conformance unless the content creator provides accessible alternatives.
How to request accessibility support or a tailored report
If you need additional technical information, a procurement-specific statement, or assistance to ensure a particular map meets an accessibility requirement, email accessibility@mapme.com with:
- The map URL or account ID
- A description of the required information or the procurement form you need filled out
- Any deadlines or formats required (for example, VPAT in a specific template)
Legal Disclaimer
This document is provided for informational purposes only and does not constitute a legally binding accessibility certification. Conformance statements are based on the features and documentation reviewed as of the Report Date and may change as the product evolves. For binding statements, refer to a signed procurement addendum or an independent third-party audit.