Steve Faulkner

the aria roles/states/properties are used as an abstraction of the various platform accessibility APIs see http://rawgit.com/w3c/html-api-map/master/index.html so there is no ARIA role/state/properties exposed via the DOM or in the browser...

From a [HTML-AAM](https://w3c.github.io/html-aam/) perspective there are already a number of elements that get their accessible name from child elements (when present [`caption`](https://w3c.github.io/html-aam/#el-caption) names `table`, [`figcaption`](https://w3c.github.io/html-aam/#el-figcaption) names `figure`). This could be...

@xi this is an interesting one. In Firefox/chrome/Edge on windows 10 the `hidden` attribute removes the input from the accessibility tree, so the name calculation is moot. In IE11 `hidden`...

I suggest it should **only** expose a menu button role for values of haspopup that have a high likelihood of displaying a menu.

@JAWS-test wrote: > but in my opinion not a violation of 2.4.7, because the elements do not get the focus when using the keyboard, but only when reading with the...

> Check > HTML Validation quick check (returns error 501) suggest remove > Check > W3C HTML Validator > all sub-options (return error 500) suggest remove > Check > Functional...

@patrickhlauke re FAE below is form code from the FAE site, the [fae.ws](https://github.com/ThePacielloGroup/WebAccessibilityToolbar/blob/master/wat/scripts/fae.ws) needs updating to send same info ``` URL Ruleset HTML5 and ARIA Techniques HTML4 Legacy Techniques ```

i will ping jon gunderson

> Or, to be blunt, it wouldn't be a big loss if FAE was removed. it probably makes sense to do a major cull of the toolbar features for future...

open aviewer app, in toolbar the ? button