This content originally appeared on TPGi and was authored by TPGi
Accessibility testing is only as accurate as the screen reader you test against. The September release aligns JAWS Inspect with the latest JAWS screen reader update and updates to ARIA handling which improves how content is announced on the web.
In addition, optional AI tools like FSCompanion now support testers in understanding how content is interpreted by the screen reader.
New to accessibility testing? Keep reading for a tip on how to get started.
JAWS Update Overview
Here are some of the updates to JAWS screen reader, and how it affects real-world testing:
- FSCompanion Updates: FSCompanion, the AI-powered assistant for JAWS, now responds faster and delivers clearer answers. It’s especially useful when interpreting what appears in JAWS Inspect reports. Try it at FSCompanion.ai.
- ARIA and Web Behavior Fixes: JAWS now announces ARIA table headers, labels, and form field states more consistently, redundant or unexpected output. These refinements are reflected in JAWS Inspect reports, helping testers catch subtle differences in how components are introduced and grouped.
Explore What’s New in JAWS to learn more.
How Testers Can Use FSCompanion with JAWS Inspect
If you’re new to accessibility testing, JAWS Inspect and FSCompanion can help you interpret screen reader output with confidence.
For example: If you’re running a report in JAWS Inspect and you see output like “heading level 2” or “link: Products” but aren’t sure why JAWS announces it that way. Then, open FSCompanion and ask: “Why does JAWS say ‘heading’ before some text?” or “What does JAWS use to detect a link?”
FSCompanion will explain how JAWS interprets roles, semantics, and accessible names, giving testers fast context for the speech output shown in JAWS Inspect reports. It’s not for learning how to use JAWS Inspect itself, but it’s a valuable companion when you’re trying to understand what you’re seeing and hearing.
And what does JAWS use to detect a link? According to FSCompanion:
JAWS detects a link on a web page by looking for specific HTML elements that are coded as links, such as the “A” (anchor) tag. When JAWS encounters a link, it announces “Link” and reads the link text. JAWS uses the following information to identify and speak about links:
-
-
- The visible text on the link (screen text).
- The HTML Title attribute, if present.
- Tooltip text from the “OnMouseOver” attribute, if available.
- ARIA roles and attributes that indicate a link.
-
By default, JAWS reads the screen text of the link, but you can change this in JAWS settings to use the Title or Tooltip if you prefer.
To quickly find and move to links on a web page, you can use the following keystrokes:
Press Tab or Shift+Tab to move between links.
Press Insert+F7 (JAWSKey+F7) to display a list of all links on the current page.
Together, this pairing offers a fast, accurate way to debug accessibility without needing to run JAWS directly.
Start Testing with JAWS Inspect
Ready to learn how screen reader users are experiencing your website? Schedule a demo now.
The post JAWS Inspect September 2025 Update appeared first on TPGi.
This content originally appeared on TPGi and was authored by TPGi