10 Free Manual Accessibility Tests You Can Run Right Now

Testing your app for accessibility isn't just about running expensive automated tools or hiring a consultant. Some of the most impactful checks you can do require nothing more than your own browser, keyboard, and a little patience. Here are the hands-on methods that catch real-world accessibility issues without a single paid plugin.

Start With Your Keyboard

The quickest accessibility test is to unplug your mouse or trackpad. Navigate your entire app using only the Tab, Shift+Tab, Enter, and Escape keys.

• Check focus visibility: As you tab through buttons, links, and form fields, can you always see where you are? If the focus ring is invisible or styled away, that's a problem for motor-impaired users who rely on keyboard navigation.
• Look for logical order: Does the tab order follow the visual layout? If you jump from a header to a footer to a sidebar, your page structure needs fixing.
• Test interactive elements: Can you open dropdowns, dismiss modals, and submit forms with the keyboard alone? If a menu stays stuck open or a button requires a click, you've found a blocker.

Use Your Browser's Built-In Zoom

Open your app and zoom in to 200% or 400%. This simulates how users with low vision might experience your interface.

• Watch for overlapping text: If buttons, sidebars, or labels overlap or get cut off, the layout isn't responsive enough.
• Check that content reflows: Text should wrap and resize without needing horizontal scrolling. A clean test is to zoom to 200% on a mobile-sized window and see if everything stays readable.
• Notice missing controls: If navigation menus disappear entirely when zoomed in, they're not designed for users who need larger text.

Toggle High Contrast Mode

Your operating system likely has a high contrast mode (Windows High Contrast, macOS Increase Contrast, Android Dark Mode with high contrast). Flip it on and browse your app.

• Look for invisible content: Text and icons that blend into backgrounds often become illegible in high contrast. If a button's label disappears, you're relying only on color, which fails for colorblind users.
• Check link differentiation: Links should have underlines or icons when in high contrast mode—color alone is insufficient.
• Test form field borders: Input fields with only a faint grey border can vanish entirely. Make sure they have a clear, dark outline.

Disable CSS

This one might sound extreme, but it's extremely revealing. Use your browser's developer tools (F12, disable all stylesheets) to view your app in raw HTML.

• Check content structure: Does the page still make sense as a linear reading order? Screen readers and text-only browsers see exactly this—no colors, no layouts.
• Spot missing alt text: Images with no alt attribute will appear as blank. Logos, icons, and decorative images should either have meaningful descriptions or be explicitly hidden from screen readers.
• Evaluate heading hierarchy: In plain HTML, you can instantly see if you're jumping from <h1> straight to <h4> or using random <div> tags as headings. Proper heading order is crucial for navigation.

Run a Manual Content Audit

Read your app's text out loud. Yes, literally.

• Check link text: Do you have "click here" or "learn more" as links? Screen reader users often tab through a list of links. "Click here" tells them nothing.
• Check button labels: A button with just an icon (like a trash can) should have a text label or an aria-label. Your manual read-aloud test will expose missing context.
• Identify complex language: If your UI uses jargon or unusual abbreviations, it can baffle users with cognitive disabilities. Simplify where you can.

Use the Browser's Accessibility Panel

Chrome and Firefox both have built-in accessibility inspectors. They're free and more insightful than most paid tools.

• Chrome DevTools: Go to the "Elements" tab, find the "Accessibility" pane. It shows computed roles, name, and state for any selected element. For example, you can see if a button is actually marked as a button or just a <div> with an event listener.
• Firefox Accessibility Inspector: Similar tool, but it also runs an automated check and tells you which elements have missing accessible names. It's particularly good at spotting images without alt text.

Get a Second Pair of Eyes

Ask someone who doesn't know your app to try these tests. Developers become blind to their own quirks. A fresh tester will spot the focus order that's off, the button that's unreachable, or the confusing label.

These manual techniques won't catch every possible issue—a true audit needs a screen reader and sometimes a disabilities consultant. But they'll catch the most common, most frustrating problems. And they cost exactly zero dollars.

Start with the keyboard test. That alone will reveal more than you expect.