Updates for prohibited attributes for elements with implicit role of generic

[cmorten]

Raising this issue to track updates to relevant "aria group" tests to remove use of prohibited states and properties on elements that have an implicit role of generic, e.g. <div>, <span>, and other elements. This may be a little premature depending on what W3C spec status is being tracked by WPT for each of the relevant specs.

WAI-ARIA 1.2 introduced the generic role and has been assigned to several elements such as <div>. The generic role has a number of prohibited properties and states:

• aria-label
• aria-labelledby
• aria-roledescription

See https://www.w3.org/TR/wai-aria-1.2/#generic.

There are a number of tests that use the <div> element (historically had no corresponding role and a natural go to) which are now invalid under the proposed recommendation WAI-ARIA 1.2 as they use one or more of the above prohibited properties or states.

For example see the following accname tests which use a <div> element with prohibited properties or states:

• https://github.com/web-platform-tests/wpt/blob/master/accname/manual/name_test_case_596-manual.html
• https://github.com/web-platform-tests/wpt/blob/master/accname/manual/name_test_case_597-manual.html
• https://github.com/web-platform-tests/wpt/blob/master/accname/manual/name_test_case_598-manual.html
• https://github.com/web-platform-tests/wpt/blob/master/accname/manual/name_test_case_599-manual.html

I expect the set of impacting tests to include, but not be limited to, the above set of tests.

R.E. whether this is an appropriate time to update such tests, in the html-aam tests the roles test has already been updated to assert <div>, <span>, and other elements have a role of generic, see https://github.com/web-platform-tests/wpt/blob/master/html-aam/roles.html#L58. The core-aam tests also now include one assertion verifying the prohibited aria-roledescription attribute on elements with generic role, see https://github.com/web-platform-tests/wpt/blob/master/core-aam/generic_roledescription_prohibited-manual.html#L64.

One path forward would be to swap the use of <div> with a new, different element that has no corresponding role under WAI-ARIA, but given these changes, it may not be particularly future-proof to churn as I get the impression more of these elements with no corresponding role currently may likely gain an assigned implicit role in future versions of the spec. Some thought needed as to the appropriate replacement element, or if there are other paths forward perhaps?

[cmorten]

Relates somewhat to web-platform-tests/interop-accessibility#48 like discussion