WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [EXTERNAL] Accessibility: ARIA trees obviously not accessible with NVDa/JAWS screenreader and Firefox/Chrome on Windows

for

From: Brooks Newton
Date: Jan 27, 2021 11:37AM

I have four questions related to the tree view widget and other common
widgets not currently supported through semantically meaningful HTML markup:

- Is it the W3C or WHATWG that is in charge of determining when new
widget markup is added to the HTML specification?
- How long does a widget have to be used in the wild before a standards
body is required to create markup that supports easy accessible
implementations of such widgets?
- Are user agent manufacturers, authoring tool manufacturers and
assistive technology manufacturers required to adopt new HTML markup
standards so that the new widget markup implemented by content authors will
work for users?
- How are individual site owners and content authors supposed to keep up
with the business need for implementing new accessible widgets without
strong support from standards bodies, user agent manufacturers, assistive
technology manufacturers and authoring tools manufacturers?


Thanks,

Brooks Newton

On Wed, Jan 27, 2021 at 12:10 PM Jonathan Avila < <EMAIL REMOVED> >
wrote:

> One reason why trees and other widgets may not be navigable with browse
> mode is that they require knowing the focused element. In browse mode JAWS
> and NVDA (no longer) sets focus to the elements on navigation with arrow
> keys. Focus setting would need to occur - but this has potential side
> effects that would need to be handled. It's likely something that could
> be addressed but my guess is that it's tricky.
>
> Jonathan
>
>