Accessibility Statement
Effective September 27, 2026 · TasLogic
Our commitment
TasLogic is committed to making MetroASAP accessible to people with disabilities. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA for the staff web application, citizen and external portals, public anonymous pages, and the MAUI mobile shell (WebView).
Each municipality remains responsible for city-authored content it publishes through the platform (for example welcome HTML, uploaded PDFs, and third-party embeds such as meeting streams). Cities should maintain their own accessibility statement or ADA transition plan when required and may override the default link in City Profile → Legal & trust.
Conformance status
MetroASAP partially conforms to WCAG 2.1 Level AA across the full multi-module product until specialty modules finish their remediation backlog. Partially conforms means that some parts of the content do not fully conform to the accessibility standard. We continuously improve accessibility based on automated checks, manual review, and user feedback.
MetroASAP runs a platform-wide WCAG 2.1 Level AA program for Tier 1 surfaces: staff shell, public anonymous pages, citizen/builder/FOIA portals, login, and mobile shell routes listed in the platform accessibility manifests (MetroASAP.E2E.Tests/data/platform-a11y-public-portal-manifest.json and platform-a11y-staff-manifest.json). Migration 1247_PlatformAccessibilityGoLiveGates.sql enforces trust links and accessibility options for all cities and adds PDF accessibility attestation on CityUxSettings. High-traffic resident-facing PDF exports set document title, creator, and Lang=en-US via AccessiblePdfDocumentFactory; cities attest letter templates after checklist review.
For City of Pearl, Mississippi go-live surfaces (additional Pearl route manifest and migration 1246_PearlAccessibilityGoLiveGates.sql), MetroASAP targets full WCAG 2.1 Level AA with documented known limitations for maps, designers, and city-authored content. See docs/pearl-accessibility-go-live.md and the VPAT Pearl section for the contracted-surface claim.
A summary of supported accommodations and known limitations is maintained for procurement and IT review (VPAT / ACR baseline). Contact [email protected] for the current summary for your contracted module set.
Accessibility features
The platform includes accommodations that users can enable:
• Large text, high contrast, and reduced motion — Account settings (/account/settings#accessibility) for signed-in users; guest quick toggles on portal layouts until sign-in.
• Skip links, semantic landmarks, and keyboard-focusable controls on primary staff and portal layouts.
• Screen-reader-oriented labels and status messaging on core workflows where implemented.
• Accessible PDF guidance for city letter templates used in correspondence.
Availability of a specific accommodation can vary by module; report gaps so we can prioritize fixes.
Technical specifications
Accessibility of MetroASAP relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:
• HTML
• WAI-ARIA
• CSS
• JavaScript
These technologies are relied upon for conformance with the accessibility standards used.
Limitations and alternatives
Despite our best efforts, some limitations may remain:
• City-authored rich HTML and uploaded documents may not meet WCAG if the city has not remediated them.
• Live meeting streams depend on captions and player accessibility provided by the city's YouTube, Vimeo, or similar channel.
• Some field mobile flows (for example barcode scan and certain camera workflows) may have incomplete VoiceOver / TalkBack coverage.
• Complex data grids and map interactions may offer equivalent text or list alternatives; if a path is blocked, contact us for an alternate format.
If you encounter content that is not accessible, please tell us and we will work with you on a reasonable alternative.
Feedback
We welcome your feedback on the accessibility of MetroASAP. Please contact us:
• Email: [email protected]
• Support: [email protected] or https://app.metroasap.com/support
Municipalities may also publish an Accessibility contact email on City Profile → Legal & trust so residents can report barriers for that city. We try to respond to accessibility feedback within five business days.
Assessment approach
TasLogic assessed the accessibility of MetroASAP using a combination of:
• Self-evaluation with automated axe-based checks in the end-to-end test suite
• Manual keyboard and screen-reader spot checks on primary staff and portal routes
• Ongoing remediation tracked against the WCAG 2.1 Level AA baseline
Effective date: September 27, 2026