Accessibility Statement

1.Our commitment

VoltaAMP aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Accessibility, responsive behaviour, right-to-left layout, and clear loading, empty, error, and offline states are treated as foundation requirements rather than later polish.

2.What is built in

• Every interactive control is reachable and operable with a keyboard, with a visible focus indicator.
• Interface text and controls carry accessible names, and dynamic results are announced through live regions.
• Colour is never the only way a status is communicated; verification, availability, and severity also carry text.
• Layouts reflow to small screens and to enlarged text without loss of content.
• Motion is reduced automatically when the operating system requests it.
• The interface is rendered in a dark theme with contrast ratios chosen to remain legible in daylight.

3.Arabic and right-to-left support

Arabic is a first-class language, not a translation layer. The interface mirrors correctly in right-to-left, uses logical rather than physical spacing so mirroring stays consistent, and loads the right-to-left text support needed for correctly shaped Arabic map labels.

Navigation direction icons are deliberately not mirrored, because a right turn is a right turn regardless of reading direction.

4.Known limitations

We would rather name these than imply the product is complete.

• The map itself is a canvas. Panning and zooming by keyboard is limited, and map features are not individually exposed to screen readers — the station directory is the accessible equivalent and carries the same records.
• Turn-by-turn guidance is visual and textual. There is no spoken voice output yet.
• Some station and EV service records originate from external sources and may carry inconsistent capitalisation or formatting that VoltaAMP has not yet normalised.
• Map labels are drawn from OpenStreetMap and their contrast cannot be fully controlled by VoltaAMP.

5.Assistive technology

VoltaAMP is tested against current versions of the major browsers on desktop and mobile, in both languages. If you use an assistive technology we have not covered and something does not work, please tell us — that report is more useful than any audit.

6.Feedback

Report an accessibility problem to the support address below or through the Contact page. Please include the page, what you were trying to do, your browser, and any assistive technology in use. We reply within two business days.

7.Review

This statement is reviewed whenever a significant feature ships, and at least once a year.