[NFBCS] Anyone Know Why JAWS Does Not Just Ignore ARIA Attributes That Are Not Supported

Lewis Wood lewislwood at gmail.com
Fri Sep 15 13:16:04 UTC 2023


Sounds interesting, but if you develop on a non-standard quirk.  Won't that
break at a later date?

 

Lewis Wood

lewislwood at gmail.com

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Andy B. via NFBCS
Sent: Friday, September 15, 2023 6:29 AM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
Cc: sonfire11 at gmail.com
Subject: Re: [NFBCS] Anyone Know Why JAWS Does Not Just Ignore ARIA
Attributes That Are Not Supported

 

I can create a link with the aria-expanded attribute and create a
expandable/collapsible section of links, with a link itself. Sounds strange,
but it is entirely possible.

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On
Behalf Of Nicole Torcolini via NFBCS
Sent: Friday, September 15, 2023 1:54 AM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org
<mailto:nfbcs at nfbnet.org> >
Cc: Nicole Torcolini <torcolini at comcast.net <mailto:torcolini at comcast.net> >
Subject: [NFBCS] Anyone Know Why JAWS Does Not Just Ignore ARIA Attributes
That Are Not Supported

 

            I noticed something strange today when I was on a website. All
of the links in a particular area seemed to be expanded. Upon further
investigation, it turned out that the web developers had put aria-expanded
on the containing div-no ARIA role on the div-and, rather than just ignoring
the misplaced aria-expanded, JAWS was applying to the links inside of the
div. I checked both Firefox and NVDA-the developer tools do not show the
links as having aria-expanded in the accessibility tree, and NVDA does not
announce it-so a JAWS idiosyncrasy.

 

Nicole

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20230915/3f93da2f/attachment.html>


More information about the NFBCS mailing list