Screen Reader Testing: 7 Instant Checks for Perfect Accessibility

As a screen reader user, I experience daily which websites truly work and which make me despair after just seconds. The good news: With seven targeted instant checks, you can ensure your website functions optimally for NVDA, JAWS, and other screen readers. These tests are based on my years of experience and show you what really matters^[1].

Why Screen Reader Testing Is Essential

While automated tools like WAVE or Lighthouse identify important technical barriers, they capture only about 30% of the actual problems that screen reader users experience^[2][3][4]. A real screen reader test shows you how your website actually "sounds" and whether it's logically navigable. Especially since the German Accessibility Strengthening Act (BFSG) came into effect in June 2025, such tests are not only ethically appropriate but legally required^[5][6].

The reality is sobering: even large companies often fail basic screen reader requirements. A recent example from my own experience clearly shows the problem – when booking a flight with a major airline, I had to give up after a few minutes and request sighted assistance because the navigation was completely incomprehensible^[1].

Screen Reader Basics: The Most Important Programs Overview

Before we get to the concrete tests, a brief overview of the relevant screen readers. NVDA (NonVisual Desktop Access) is free and available for Windows – perfect for initial tests. JAWS (Job Access With Speech) is commercial but offers a 40-minute demo version. Both use similar keyboard shortcuts and are widely used in Germany^[5][7][8].

The most important keyboard shortcuts you should know: NVDA key + Down arrow reads everything, Tab key navigates between interactive elements, and H jumps to the next heading. With Escape you exit form mode and return to normal reading mode^[5][2][9].

The 7 Instant Checks for Screen Reader Compatibility

1. The Page Title Check: Perfect First Impression

The very first impression is crucial. When you open a website with NVDA and press Ctrl+Home, you hear the page title first. This must be descriptive and unique^[2][10]. Instead of "Homepage" it should say: "Online Shop for Sportswear - SportMax".

Instant Test: Open five different pages of your website and check the browser tabs. Each title should be specific and distinguishable. For screen reader users, this is like a table of contents – unclear titles immediately lead to confusion and early site abandonment^[10][11].

2. Heading Hierarchy: The Logical Structure That Holds Everything Together

Headings are like a navigation system for screen reader users. With the H key we jump rapidly between main sections. A correct hierarchy begins with exactly one H1 per page, followed by H2 headings for main sections and H3 for subsections^[5][2][10].

Instant Test: Press the H key repeatedly in NVDA and listen to the heading structure. The order must be logical – from H1 through H2 to H3, without jumps from H1 directly to H3. Common error: headings are only styled visually (large and bold) but not semantically marked as , , etc.^[10][12].

3. Alternative Texts: Images That Can Speak

Every informative image needs a descriptive alternative text. Decorative images get an empty alt attribute (alt="") so they're skipped^[5][2][6]. The alternative text should concisely describe the content and function, not the appearance.

Instant Test: Navigate through your page with the arrow keys and pay attention to image descriptions. NVDA says "graphic" and then the alternative text. If you only hear "graphic" without description, the alt text is missing. Especially critical: buttons and links with images that only say "graphic" – these are completely incomprehensible^[6][13].

4. Keyboard Navigation: The Path Through Your Website

All functions must be reachable via keyboard. With the Tab key, screen reader users navigate between links, buttons, and form elements. The focus must be clearly visible and in logical order^[5][2][11].

Instant Test: Start in the address bar and press Tab. You should be able to reach all important elements: navigation, main content, buttons, links. Ensure the order makes sense – top to bottom, left to right. With Shift+Tab you go backwards. If you can't reach an element or get "trapped," that's a critical error^[11][13].

5. Form Labels: Clear Labels for Every Input Field

Every form field needs a clear, understandable label that's also read when the field has focus. NVDA automatically switches to focus mode when you reach an input field^[5][2][11].

Instant Test: Navigate with Tab to each input field and listen to what NVDA reads. Instead of "text field" you should hear: "First name, edit" or "Email address, required, edit". If the label is missing or incomprehensible ("Field1"), users can't fill out the form. Also test error messages by leaving required fields empty^[11][13].

6. Links and Buttons: Descriptive Text Instead of "Click Here"

Screen reader users can list all links on a page (in NVDA with NVDA+F7). They hear only the link texts, without context. "Click here" or "Read more" are therefore completely useless^[2][14][12].

Instant Test: Press K for the next link or B for the next button. Each link should be understandable even without context: "iPhone 15 product details" instead of "Learn more". For buttons, it should be clear what happens: "Add to cart" instead of just "button". Especially important: links to external sites or PDF downloads should announce this^[13][15].

7. Dynamic Content: Changes That Arrive

Modern websites change content dynamically – through dropdown menus, notifications, or AJAX updates. Screen readers must be informed about these changes, otherwise they go unnoticed^[5][14][16].

Instant Test: Open dropdown menus, click accordion sections, or trigger other dynamic changes. NVDA should automatically read the new content or at least announce that something has changed. Critical: error messages that only appear visually, or confirmations that screen reader users never receive^[16][12].

Practical Implementation: Step-by-Step to Perfect Testing

Test Preparation

Install NVDA for free from nvaccess.org and configure it for testing^[17][18]. Important settings: reduce speech rate for better understanding, activate visual highlighting (under "Settings > Vision"), and set the NVDA key to Capslock for easier operation^[5][18][19].

The Systematic Test Process

Start with a "passive" walkthrough: open the test page, press NVDA+Down arrow and let all content be read. Pay attention to anomalies like missing alternative texts, incomprehensible labels, or technical terms^[5][3].

Then follow the "active" test: navigate with Tab through all interactive elements and check the order. Use quick navigation keys: H for headings, K for links, B for buttons, F for forms^[2][14][9].

Common Errors and Their Solutions

The Problem with Purely Visual Design

Many developers design elements only visually – large, bold text for headings, red text for error messages, or colored buttons for important actions. Screen readers don't recognize these visual cues^[10][12]. The solution: use semantic HTML (, , ``) and ARIA attributes for additional information.

Navigation Without Structure

Websites without clear heading hierarchy are like books without chapter titles for screen reader users. Navigation becomes a guessing game^[1]. The solution: develop a logical heading structure and test it with the H key. Each page should be structured like a well-organized document.

Incomplete Forms

Forms without labels are the most common cause of abandonment. Users can't guess what goes in a field when only "text field" is read^[11][13]. The solution: every input field gets a `` element, required fields are marked, and error messages are specific and helpful.

The Business Relevance of Perfect Screen Reader Compatibility

Screen reader-optimized websites are not only legally required but also economically sensible. Studies show that 38% of companies report revenue increases after implementing accessibility^[20][21]. A well-structured, screen reader-friendly website simultaneously improves SEO performance, as search engines rely on semantic structures similar to screen readers^[22][23][24].

The legal risks are considerable: fines up to 100,000 euros under BFSG (Germany), cease-and-desist letters from competitors, and reputational damage^[25][26][27]. Proactive screen reader testing protects against these risks and simultaneously opens up new target audiences.

From Theory to Practice: Your Next Steps

These seven instant checks are your starting point for screen reader-optimized websites. Begin with your most important page – usually the homepage – and work systematically forward. Plan about 30 minutes per page for a thorough test^[3][10].

Document your findings and prioritize corrections: critical problems like missing alternative texts or unusable navigation have highest priority. Less critical aspects like optimal heading text can be addressed in a second round.

Screen reader testing is not a one-time project but a continuous process. Every new feature, every update should be screen reader tested. This is the only way to ensure your website provides a great experience for all users – sighted and blind.

Digital accessibility begins with understanding how people with disabilities use the internet. These seven checks bring you a big step closer to this understanding and make your website a place where all visitors feel welcome.