Accessibility

DriveEasier LLC aims for driveeasier.com to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We treat a barrier on the site as a bug, and we fix the ones that stop someone finishing a request first.

driveeasier.com partially conforms to WCAG 2.2 level AA: most of it meets the standard, and the parts that do not yet are listed below. This covers the home page, the request form at /start, and the privacy, service agreement and payment pages. The client portal at portal.driveeasier.com was not part of this review.

In the review of October 18, 2026, on the request form:

• Arrow keys move between answers without picking one. Space, Enter or a click picks, and only then does the form move to the next question.
• Each new question takes keyboard focus to its heading, so a screen reader announces it.
• The form's content is a main landmark, apart from the page header.
• The make and model lists are each one radio group: one Tab stop, arrow keys to move, Space or Enter to pick.
• The car on the details page turns with visible buttons on every screen size, not only by dragging, and announces the angle it shows.
• Hints and error messages are read with the box they belong to, and required contact boxes say they are required.
• The trim question is read as one labelled group while it waits for a year or loads.

And across the site:

• The home page headline's turning second line slides at full color instead of fading, so it keeps its contrast mid-turn; it still does not move if your device asks for reduced motion.
• The footer's small links are each at least 24 pixels tall.

• The car pictures come from an outside image service, and their text alternatives name the car (its make and model) but do not describe the picture itself, such as its color or angle.
• The request form has been used with VoiceOver, but not yet with NVDA or JAWS on Windows, and the rest of the site has had automated and keyboard checks only.
• The bot check on the last page is Cloudflare's. When it asks for a click, its accessibility is theirs, and we cannot change it. If it stops you, email us and we will take your request directly.

On October 18, 2026 we checked the site with automated tools (Lighthouse and axe), then by keyboard alone in Chrome, and by reading the page's accessibility tree: its landmarks, headings, labels, groups and what each control announces. We also checked the request form at phone width, and a person on our team went through it with VoiceOver and found nothing in the way.

If something on the site is hard or impossible to use, email support@driveeasier.com. Tell us the page, what you were trying to do and, if you like, the browser and assistive technology you use. We aim to reply within 2 business days, and we can take your car request by email or phone instead while we fix it.

Back to DriveEasier