Parkspot is committed to making parkspot.ai and the Parkspot mobile app accessible to people of all abilities. This statement explains the accessibility standard we target, what works today, what doesn’t, and how to reach us if you hit a barrier.
1. Standard we target
We target conformance with Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, the standard referenced by the EU Web Accessibility Directive, the European Accessibility Act, and the US Section 508 Refresh.
2. What conforms today
On parkspot.ai we have built the site with the following accessibility properties baked in:
- Semantic HTML5 (proper headings, landmarks, lists, buttons, and links);
- Keyboard navigation across all interactive elements;
- Visible focus rings on every focusable control;
- Color contrast meeting AA on all primary text and UI surfaces;
- Respect for the
prefers-reduced-motionsystem setting (we cut animations to near-zero); - Respect for the
prefers-color-schemesystem setting where applicable; - Alt text on informative images; decorative images marked as such;
- Form fields with associated labels and accessible error messages;
- Native form submission paths so the site is usable without JavaScript for core actions;
- Page titles, language attribute, and skip-to-content patterns where appropriate.
3. Known limitations
We are honest about where we’re not yet at AA. As of the effective date above:
- The Parkspot mobile appis in pre-launch development. We are building it against AA from day one, but a full audit will be published with the public launch in Q2 2026.
- Camera-feed thumbnails and live frames show street-level imagery without a per-frame text alternative. We provide spot counts and block-face descriptions as a non-visual alternative; a richer alt-text system is planned.
- Some hover and focus-visible interactionson the marketing site need polishing on touch devices — a known item on our backlog.
We audit accessibility quarterly with automated checks (axe-core, Lighthouse), keyboard-only walkthroughs of every primary flow, and screen-reader spot checks (VoiceOver on macOS/iOS, TalkBack on Android, NVDA on Windows). Findings are tracked and prioritized alongside other product work.
4. How to report a barrier
If you hit a barrier, need an alternative format, or have feedback on accessibility — please tell us:
- Email support@parkspot.ai with the URL or screen, what you were trying to do, the assistive technology you were using (if any), and what happened.
- We aim to acknowledge reports within 2 business days and to provide an alternative or a remediation timeline within 10 business days.
5. Enforcement procedures (EU users)
If you are in the European Union and you are not satisfied with our response to an accessibility complaint, you can contact your national enforcement body for the EU Web Accessibility Directive or the European Accessibility Act. For UK users, the equivalent is the Equality and Human Rights Commission (EHRC) and the Equality Commission for Northern Ireland.
6. Updates to this statement
We update this statement whenever our conformance status, audit findings, or processes change. The “Effective” date at the top reflects the current version.
7. Contact
Accessibility feedback and general support: support@parkspot.ai.