Wayne County Traffic School
Log in
Get started

Accessibility

A driver ordered to take a course does not get to choose the tool they take it with. Wayne County Traffic School is built so that a student using a screen reader, a keyboard alone, speech input, or a phone screen magnified to twice its size can register, work through every lesson, sit the quizzes and the final exam, and download their certificate of completion without help from anyone.

Last updated September 1, 2026.

The standard we aim at

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across the whole site: the public pages, the account pages, and everything inside a course. That is the target the Americans with Disabilities Act is read against in practice, and it is the one we hold ourselves to whether or not a particular page is required to.

We say “aim” rather than declaring the site finished. Conformance is a moving state: material changes, courses are added, and a page that passed last month can regress. What follows is how we keep it honest.

How the site is tested

  • Automated, on every push. axe-core runs in continuous integration against the pages a student actually walks: the home page, the catalogue, a course page, registration and sign-in, a lesson, a quiz, the dashboard, the certificate and the public verification page. A serious or critical finding fails the build, so it is fixed before it reaches anyone rather than after someone reports it.
  • By keyboard, before each release. A person walks registration, a lesson, a quiz and the certificate download using the Tab key and nothing else, checking that focus is always visible, that the skip link is the first thing the Tab key reaches on every page, and that nothing traps focus.
  • Structure, in the same automated run. Every page carries exactly one h1 and one main landmark, because those are what a screen reader user navigates by and an automated colour-contrast check would never notice they were missing.

We do not use an accessibility overlay

We do not use an accessibility overlay widget. Overlays change what a screen reader hears without changing the page, and they interfere with the assistive technology a student already has set up.

The work is done in the pages themselves instead. It is slower and it does not come with a badge, and it is the only version of this that helps the person it is meant for.

Known limitations

  • Captions on embedded video. Where a lesson embeds a video, the captions are served by the video host, so their presence and their quality are not entirely ours to control. Any lesson whose video is not captioned carries its full text on the same page as the transcript, so nothing in a course is only available as sound.
  • Third-party pages. Payment happens on a page hosted by Stripe. We chose a processor that takes accessibility seriously, but that page is theirs, not ours, and a problem on it is one we can report rather than fix.
  • Downloaded PDFs. A certificate of completion is a PDF. It carries real text rather than a picture of text, so a screen reader can read it, and every fact printed on it is also on the verification page on this site, which is a normal web page.

Reporting a problem

If any part of this site or any course on it is difficult or impossible for you to use, tell us and we will reply the next business day at the latest. Say which page you were on and what happened; if you know what you were using at the time, that helps, but you do not need to know.

A barrier you hit in the middle of a course is not your problem to work around. Write to us and we will get you through it while we fix the page, not after. See also the contact page and our terms.