Accessibility

Porch Route (Vector UX LLC) is designed and built to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That covers the marketing website, the office app dispatchers use, drive mode on drivers’ phones, and the tracking pages delivery customers open from a text or email. We treat accessibility as part of quality, not a separate project: the same review that gates a screen’s design gates its accessibility.

• Contrast. Status colours used as words have darker text partners so they read at 4.5:1 or better on their tints, the page and grey rows, in light and dark mode. Estimated times are italic and marked “~”, not just a lighter grey.
• Meaning never by colour alone. Every status is a labelled badge; every time says whether it is actual, planned or estimated; estimated map lines are dashed as well as coloured.
• Keyboard and screen readers. Menus, sheets and dialogs are built on accessible primitives: focus moves in, is trapped, Escape closes, focus returns. Segmented controls are radio groups with arrow-key movement. Toasts announce through live regions. Every page has one h1, a logical heading outline and a skip link.
• Touch. Office controls are 40 px, 48 px on a phone; drive mode’s primary actions are 56 px and nothing there is smaller than 48 px.
• Motion. Entrance and pulse animations, the moving truck on the map and the header’s scroll effects all stop under “reduce motion”.
• Text first on tracking pages. A recipient’s progress is a text timeline; the live map adds to it rather than replacing it.
• Light, dark and system themes everywhere, including drivers’ phones and the tracking page.

We would rather tell you than have you find out:

• Maps. Dragging the map, and drawing or editing a delivery-zone polygon, are pointer interactions and are not fully operable from a keyboard. Everything a map shows is also available as text (stop lists, addresses, zone settings), and zones can be defined as a radius without drawing.
• Route manifest PDFs are generated as printable documents and are not yet tagged for screen readers. The same information is on the route screen in HTML.
• No third-party audit yet. Our checks are internal (automated checks in every review plus manual keyboard and screen-reader passes). A formal external audit is planned but not scheduled.
• Proof photos have generic alternative text (“delivery photo”), because a driver can’t be asked to describe each one at the door.

Porch Route is a web application. It relies on HTML, CSS, JavaScript and WAI-ARIA, and is tested in current versions of Chrome, Safari, Firefox and Edge, on iOS and Android phones, with VoiceOver and NVDA. Drive mode and tracking pages work in the phone’s browser without installing anything.

If something on Porch Route is hard or impossible for you to use, please tell us through the contact page or by email at [support email]. Say which page or screen, what you were trying to do and, if you can, the browser and assistive technology you use. We aim to respond within [accessibility response time] and to fix confirmed barriers as a priority. Postal address: Vector UX LLC, [postal address].