Issue metadata
Sign in to add a comment
|
Expose all unrecognized aria attributes |
||||||||||||||||||||||||
Issue descriptionFor forward compatibility with new WAI-ARIA properties in future versions, user agents SHOULD expose all properties not in the table below as a text string, removing the "aria-" prefix from the name, if the API supports it. For example, aria-foo="bar" would be exposed with a text string foo=bar in UIA, since aria-foo is not a currently known WAI-ARIA property. The following list specifies the accessibility APIs for exposing properties as text strings. ◦MSAA: not supported ◦IAccessible2: expose as an object attribute pair ( property:string) ◦UIA: expose an object attribute pair in AriaProperties (property=string) ◦ATK/AT-SPI: expose as an object attribute pair (property:string) "
,
Mar 6 2017
,
Mar 27 2017
,
Apr 21 2017
,
Apr 21 2017
,
Jul 27 2017
,
Jul 27 2017
This is only a "nice-to-have". Chrome updates so frequently, and across users, that it's easy to expose new parts of ARIA as they come along. It would make it easier to experiment, but I wouldn't want to sacrifice any performance for that. I'm concerned that going through all the attributes for each element looking for the "aria-" prefix would hurt performance.
,
Jul 27 2017
Also, this is only a "SHOULD" in the spec. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by nek...@chromium.org
, Nov 14 2016