MarioB

I like your idea Giacomo. First of all it is much better than using aria-roledescription. Through the latter the AT-user does not know which key shortcuts are valid for the...

By all these possible solutions we have to avoid introducing different text content for "on" and "off" values visually (CSS) and in the accessibility tree (possibly new HTML attributes of...

From all the discussions we've had so far and from what you've written Giacomo, it's actually just a dashboard card - whatever it may look like visually. Because in a...

If we allow to set a menu or menu group to "multiselectable", we have to offer a "close" menu option. Thou it could be possible to have "spacebar" for selecting...

Hi all people with good contacts to AT developers! Could you please try to convince them to improve the use of aria-flowto? It could be very useful tool e.g. for...

To have aria-relevant="value" would be important, then changing a value - as in the examle above, where an is a live region, is neither a text nor an dditional child...

###A trial of a suggestion 1. radiogroup role should not limit the "allowed child roles" to radio - as is currently: The spec 1.3 has not yet an entry for...

The value "off" is really nonsensical. Maybe we could introduce the value "silent" and use it as the default for theese roles. So we had in the characteristics table of...

To expose an element with the role generic is not the same as to not taking it in account by computing parent/child relationship of non-generic element roles. E.g. the parent...

I think, there are following situations and their combinations to have in mind: - Is the concerned control (input, checkbox, ...) in a cell of a table of in a...