Common Accessibility Problems When Using a Screen Reader

Headings

Headings provide structure. When a document includes properly tagged headings, screen readers can list them and allow users to jump directly to each section. Without headings, users lose that structure and must read the document line by line.

When JAWS reads a heading, it announces its level and text, such as “Heading level one: The Evolution and Impact of Professional Wrestling.” This lets users understand where they are and how content is organized.

Best practices for headings:

• Tag each heading using consistent hierarchy (H1, H2, H3).

• Keep heading levels in order.

• Make each heading descriptive of its section.

Hyperlinks

Screen readers can detect and announce properly tagged links. When a link includes descriptive text, the user knows where it leads. For example, “Link: Traces its roots back to the 19th century, PDF.”

If a link is not tagged, a screen reader will not find it. Inaccessible links are invisible to users who rely on audio navigation. Users can list all links in a document by pressing Insert + F7 in JAWS.

Common problems with links:

• Full URLs read character by character, which is difficult to follow.

• Vague link text such as “click here” gives no context.

• Missing tags make links unreachable.

Best practices for links:

• Write clear, descriptive link text like “Download Accessibility Report (PDF).”

• Tag all hyperlinks properly.

• Keep link text short and meaningful.

Alternative Text

Screen readers use alternative text (alt text) to describe images. When an image includes alt text, the reader announces it clearly, such as “Graphic: The Undertaker. Rest in peace.”

If alt text is missing, the reader may announce meaningless metadata like “Graphic P24″ This confuses users and removes visual context.

Best practices for alt text:

• Use concise, specific descriptions under 125 characters.

• Omit phrases like “image of” or “picture of.”

• For decorative images, include empty alt text (alt=””).

Tables

Properly tagged tables allow screen readers to describe structure and read data accurately. JAWS announces “Table with two columns and ten rows” before reading the cells. When users move through the table, it identifies each cell and maintains context.

If a table is not tagged, data becomes jumbled or unreadable.

Best practices for tables:

• Use actual table elements rather than visual formatting.

• Include a header row and link data cells to headers.

• Avoid merged cells that disrupt order.

Lists

Lists help communicate sequence and organization. When properly formatted, screen readers announce the number of items and read them in order.

For example, a properly tagged list reads as:
“List of three items: 1. Stone Cold, 2. Undertaker, 3. Shawn Michaels.”

If list tags are missing, users lose this structure and cannot follow the sequence.

Best practices for lists:

• Use ordered or unordered list tags, not manual symbols.

• Keep the sequence logical.

• Avoid empty lines between list items.

Testing with Screen Readers

Screen readers interpret only tagged content. If something lacks structure, it might not be read at all. In many cases, inaccessible elements result in silence rather than errors, which prevents users from knowing content exists.

Testing regularly helps identify and correct these issues. The companion video demonstrates these steps in real time, showing how JAWS handles properly and improperly tagged elements.

Recommended tools:

• JAWS: Paid screen reader with advanced navigation features.

• NVDA: Free, open-source screen reader for Windows.

• VoiceOver: Built-in screen reader for Apple devices.

Useful shortcuts:

• JAWS: Insert + F6 for heading list, Insert + F7 for link list.

• NVDA: Insert + F7 for elements list.

Inclusion and Accessibility

Accessible design allows everyone to access digital content equally. Proper tagging, descriptive text, and regular testing create documents that screen readers can interpret accurately. Accessibility is both a technical practice and a commitment to inclusion.

Let me be your champion for inclusion. I offer tailored solutions (and self-paced courses!) to ensure your documents meet and exceed compliance expectations. For more detailed insights, tutorials, and in-depth discussions on accessibility and related topics, don’t forget to check out my YouTube channel: The Accessibility Guy on YouTube. Subscribe for regular updates!