How to test for accessibility for users with disabilities

An accessible website ensures that everyone can find what they need, including people with visual, hearing, motor or cognitive disabilities. In this comprehensive article, you will learn in simple language how to check whether your site is accessible. We will discuss manual checks, automatic tools, guidelines from the WCAG and practical examples. This way, you can make your website more accessible for all visitors step by step.

1. What is web accessibility?

Web accessibility means that people with various disabilities can use your website without problems. Think of:

• Blind and partially sighted people who use a screen reader
• Deaf or hard of hearing people who watch videos without sound
• People with motor disabilities who only use the keyboard
• People with cognitive disabilities who need clearly structured content

2. Why accessibility is important

• Social responsibility: everyone deserves equal access to information.
• Legal obligations: many countries have laws such as the Nederlandse Toegangkelijkheidswet.
• Reach and conversion: an accessible site reaches more people and can increase conversion.
• SEO advantage: search engines value good structure and semantics, which goes hand in hand with accessibility.

3. The WCAG guidelines in brief

The international Web Content Accessibility Guidelines (WCAG) help you step by step. They consist of four principles:

1. Perceivable: content must be visible or audible.
2. Operable: navigation and operation must work with keyboard and other tools.
3. Understandable: text and operation must be clear and predictable.
4. Robust: content must work with different browsers and tools.

Read more on the official site: WCAG 2.1.

4. Automatic accessibility tools

A quick first check can be done with automatic scanners. They provide immediate feedback on technical errors.

• WAVE Web Accessibility Tool – shows errors and warnings.
• Accessibility Insights – Microsoft’s tool for Windows and the web.

Run a scan on every important page, note the errors and prioritize them by severity.

5. Manual checks

In addition to tools, manual testing is indispensable. Here’s how to check:

5.1 Keyboard navigation

Try navigating your site without a mouse:

• Can you reach all links and buttons with Tab, Shift+Tab, and Enter?
• Is the focus clearly visible (for example, with a border or background color)?

5.2 Test screen reader

Use a free screen reader such as:

• NVDA (Windows)
  • nvaccess.org
• VoiceOver (macOS and iOS)
  • Enabled in System Preferences > Accessibility

Listen to see if your page is read logically, and if buttons and input fields are clearly labeled.

5.3 Measure Color Contrast

Sufficient contrast between text and background is essential. Use:

• Contrast Checker

WCAG requires a minimum contrast ratio of 4.5:1 for normal text.

5.4 Alt texts for images

Each <img> element must contain a descriptive alt="...":

<img src="gebouw.jpg" alt="Front view of office building with glass facade" />

Decorative images get an empty alt: alt="" to relieve screen readers.

5.5 Structure with headings

Use headings (<h1> to <h6>) for a logical hierarchy:

<h1>Our services</h1>
<h2>Web design</h2>
<h2>SEO optimization</h2>

5.6 Forms and labels

Make sure that each form field has a <label> has:

<label for="email">E-mailadres</label>
<input type="email" id="email" name="email" />

Labels help screen readers and enlarge click and touch areas.

6. Accessibility statement and roadmap

Publish an accessibility statement with your goals and backlogs. This shows that you are seriously working on improvements and that you meet legal requirements.

Example: “Our site complies with WCAG 2.1 level AA, with the exception of…”

7. Integrate into your development process

Make accessibility part of every release:

• Integrated part of code reviews
• Automatic checks in CI/CD pipelines (axe-core integrations)
• Regular manual testing with screen readers

8. Training and awareness

Make sure your team is familiar with accessibility principles:

• Organize internal workshops and knowledge sessions
• Use checklists in design and development

9. Monitoring and management

Keep monitoring your site:

• Use uptime monitoring with accessibility checks, such as AccessLint
• Keep track of user feedback, for example via a contact form
• Schedule periodic audits

10. Success story: making a municipal site accessible

A Dutch municipality rebuilt its site with a focus on WCAG 2.1 AA. By increasing contrast, simplifying navigation and adjusting forms, the accessibility score increased from 70% to 95%. Citizen support and satisfaction increased significantly.

Conclusion

Accessibility is not a one-time job, but a continuous process. With the right tools, manual checks, and following WCAG guidelines, you can make your website accessible to everyone. Start today with the steps in this guide and take an important step towards an inclusive online environment.

Did I help you well?

Your contribution enables me to write more articles.

I donate € 1,- now