Skip to main content
WCAGrules
Quick navigation

Services · Testing types

Every Control on Your Site, Without a Mouse

For the team that wants every menu, modal, and form working for the people who never touch a mouse, which is more of your visitors than you think.

What We Keep Finding

Unplug your mouse and try your own site. Tab. Guess what is focused. Tab. Guess again. If you cannot tell where you are, you have met the invisible-focus problem, and it lives on every site that shipped a CSS reset without putting the outline back. Keyboard users are not a niche either. Screen reader users, people with tremor or repetitive strain injury, and plenty of power users all live on those keys.

We drive every interactive control, and we do mean every one. The carousel arrows, the date picker, the chat launcher, the cookie banner. Can you reach it, use it, and leave it? A trap fails the page it is on, and it fails it harder than most findings. The no-trap rule is one of only four in the whole standard that applies to everything on a page, whether or not you are claiming conformance for it. One trapping widget and the page conforms at no level at all.

The rule is also narrower than most teams test, and that matters because it stops us billing you for a finding that is not one. A widget needing something beyond Tab and the arrow keys to escape still conforms, as long as it tells the user how to get out. So a media player that says press Escape to leave the player passes, and the same player in silence fails. Silence is the failure. So is a focus order that jumps from the header to the footer and back in the middle of a form, which is a different rule and a real one.

What We Check

  • Tab through every audited page and log the order focus actually follows
  • Operate each control by keyboard alone, so menus, sliders, pickers, players
  • Hunt for traps, meaning widgets that hold focus without saying how to leave
  • Check the focus indicator stays visible on every stop, on every background
  • Test the escape routes, so close the modal, skip the menu, leave the widget

What You Get

Every service on this site runs the same three-pass engine: an automated scan, an expert review of all 55 WCAG 2.2 A and AA rules, and a hands-on session with a professional blind screen-reader user. You get one report with every finding screenshotted, ranked by user impact, and linked to its fix. Your team fixes, we verify: the re-audit is half price within 3 months.

The format is not a mystery either. Read the sample report before you spend anything.

The Honest Limit

One honest limit and one boundary in the rules. The limit is that our keyboard pass is desktop-based, the classic Tab and Enter experience. The good news rides along anyway, because switch access and most alternative inputs drive that same keyboard interface, so clearing this pass helps them too. The boundary is scope. An audit covers the pages you pick, 10 of them or 25, rather than every control on every page you have. What makes that go further than it sounds is that keyboard failures are nearly always template failures, so the menu we test is the menu on all of them.

What It Costs

Rapid Audit: $499, up to 10 pages you pick, report in 5 business days. Standard Audit: $1,499, up to 25 pages in 10 business days. Flat rates, no discovery calls, and a real blind screen-reader user on every engagement. Pick your pages. We bring the humans.

Worth Reading Next

Related on this site

Guides, checklists, tools, and terms that go with this service.

More in Testing types

Go somewhere useful

Find tools, resources and your workspace.

29 destinations