I very much doubt this is possible. most such info is not processed at the
screen reader level, but instead is handled by the browser and what
information is provided to the screen reader. Obviously certain specific
properties are exposed, but even then, through mappings per the
accessibility API, so IA2 with Firefox and UIA/MSAA with IE, AFAIK.
Happy to be wrong, but I'd be curious about how that would even be
implemented.
President, Prime Access Consulting, Inc.
Twitter: @SinaBahram
Company Website: https://www.pac.bz
Personal Website: https://www.sinabahram.com
Blog: https://blog.SinaBahram.com
-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Travis Roth
Sent: Tuesday, July 18, 2017 9:11 AM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Disabling ARIA
Hi,
Anyone have suggestions for disabling ARIA processing on a website?
I use an app (QuickBooks Online) that uses ARIA incorrectly in places. As
you may imagine, this has worse consequences than if none were used. If I
could tell JAWS to ignore the ARIA markup the page would be more usable
under the circumstances.
Thoughts?
Thanks.
Travis Roth
__________o?=
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
__________�
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
