Re: JAWS latest updates uses some post source

Next week we use my Zoom account!!! I have a full license.

Mike Paciello
Chief Accessibility Officer
michael.paciello@audioeye.com
+1.603.484.1938

[image: AudioEye Registered Trademark Logo]
[image: Follow us on LinkedIn for more accessibility tips!]
<https://www.linkedin.com/company/audioeye-inc/>


On Wed, Dec 10, 2025 at 3:08 PM Jason Taylor <jason@usablenet.com> wrote:

>
> This e-mail and any accompanying attachments are intended only to be read
> or used by the named addressee(s). It is confidential and contains legally
> privileged information. If you have received this message in error, please
> notify the sender immediately and delete this message.
>
> Sent from my iPhone
>
> Begin forwarded message:
>
> *From:* Jason Taylor <jason@usablenet.com>
> *Date:* December 3, 2025 at 3:22:30 PM EST
> *To:* Accessibility Edge <w3ca11yedge@gmail.com>
> *Subject:* *JAWS latest updates uses some post source*
>
>  Hi
>
> Example:
>
> the recent features announced by JAWS (the screen reader) represent
> improvements in how the screen reader handles web content, including
> leveraging “post-source”  to improve structured content (tables, ARIA
> roles, web controls, etc.).
>
>
> Here’s roughly how those improvements apply — and why they’re meaningful:
>
>
>
> ✅ What’s improved in JAWS lately (web & structure support)
>
>
>
>
>    - JAWS 2026 (and recent 2025 updates) introduced an integrated
>    AI-driven tool, FSCompanion, and a feature called AI Labeler / Page
>    Explorer, which helps by generating meaningful labels and a structural
>    summary of web pages. That helps when elements (buttons, links, form
>    fields) lack proper HTML labels — making navigation more reliable.
>    - JAWS now reads ARIA attributes, table headers, form controls, and
>    list structures more reliably. For example: column headers in ARIA grids,
>    proper announcement of table cells in relation to their headers, improved
>    handling of radio-button groups, checkboxes, combo boxes, and “separator”
>    elements.
>    - For Braille users (refreshable Braille displays), JAWS now supports
>    multi-line Braille output — meaning users can view multiple lines at once,
>    which preserves layout, paragraphs, tables, columns instead of forcing
>    constant panning line-by-line. This is especially helpful for structured
>    content (e.g. tables on a web page, or formatted docs).
>
>
>
>
> 🎯 Why that matters for “post-source / structural content”
>
>
>
> By “post-source,” we mean not just raw text scraping, but understanding
> the structure of a page: headings, tables, interactive controls, layout,
> semantics (ARIA labels), etc. The improvements listed above help JAWS more
> accurately reflect what a sighted user perceives (page structure,
> semantics, navigation cues), rather than just reading linear text. That
> makes web content more accessible, meaningful, and navigable — closer to a
> “real” representation of the page’s content and structure.
>
>
>
> ⚠️ But: Not everything is magically solved
>
>
>
>
>    - Even with AI Labeler and Page Explorer, their effectiveness depends
>    a lot on the underlying HTML/ARIA markup and how the page is built. Poorly
>    coded or dynamically generated content might still give sub-optimal results.
>    - For Braille: multi-line support depends on having a compatible
>    Braille display (like supported ones from specific manufacturers), and
>    correct firmware for those displays.
>    - The “AI-assisted” features may help with unlabeled controls or
>    images, but as with any automated approach — context, complexity, and
>    consistency vary.
>
>
>
>
>
>  the new features in JAWS represent  examples of  “post-source” support:
> better semantics, layout, and structure on websites. They won’t make every
> site fully accessible, but they significantly improve robustness and
> usability for many typical web pages.
>
>
> —-
>
>
>
> This e-mail and any accompanying attachments are intended only to be read
> or used by the named addressee(s). It is confidential and contains legally
> privileged information. If you have received this message in error, please
> notify the sender immediately and delete this message.
>
> Sent from my iPhone
>
>

-- 
The information in this communication is intended for the use of the 
individual or entity to which it is addressed, and may contain information 
that is PRIVILEGED, CONFIDENTIAL and/or exempt from disclosure under law. 
If you are not the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited.