Last updated: May 5, 2026
Our commitment
A1 RV Repair is committed to making this website usable by everyone, including RV owners with visual, hearing, mobility, or cognitive disabilities. We target compliance with the Web Content Accessibility Guidelines (WCAG) version 2.1, Level AA, and we test against that standard on every meaningful site update.
What we have done
This site uses semantic HTML throughout, includes descriptive alt text on every meaningful image, supports keyboard-only navigation including the mobile menu and the interactive service-area map, maintains WCAG AA color contrast (4.5:1 for body text, 3:1 for large text), uses focus indicators visible on every interactive element, and structures content with clear heading hierarchy that screen readers can navigate. All form fields are labeled. Animations respect prefers-reduced-motion.
Known limitations
The interactive US service-area map is best experienced visually. Each state element has a tooltip and is keyboard-focusable, and the same information (active service states and city links) is available as plain text in the footer and on the locations index page. If you find any other limitation, please tell us so we can fix it.
Requesting accessible service
Booking service does not require using the website. Call (866) 623-1340 Monday through Saturday 7 AM to 7 PM and we will dispatch a technician to your location. We will read invoices and warranty documents aloud, accept payment by phone, and arrange a sighted technician walk-through of completed work if helpful.
Reporting an issue
If you encounter a barrier on this site, please contact us so we can address it. We aim to respond within 5 business days.
- Email: [email protected]
- Phone: (866) 623-1340
- Mail: A1 RV Repair, Attention: Accessibility
Standards and audits
We test against WCAG 2.1 AA using automated scanning (axe-core) on every site deployment and a manual review by a sighted reviewer using a screen reader (NVDA on Windows, VoiceOver on Mac and iOS) before each major release. Issues are tracked publicly in our build log.