You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently section four, allowed descendant of ARIA roles, is marked as non-normative.
The next version of ARIA in HTML will be revising this section to create both normative and non-normative sub-sections. Things we should keep / expand upon:
Examples of non-conforming descendants with explanations as to why.
more clearly calling out explicit roles and their specific restrictions - 'whys' would be covered in related examples.
making a parallel to the kinds of content different ARIA roles represent should remain, but downplayed in comparison to the normative requirements.
if possible we should make reference to the role categorizations that the ARIA spec has already defined (widget, doc structure, landmark, live regions, and window roles)
The text was updated successfully, but these errors were encountered:
another example we talked about today would be ensuring this section covered the following:
<button><spanrole=article>...</article></button>
or
<p><spanrole=article>...</article></p>
etc
scottaohara
changed the title
Create normative requirements for section 4
Create normative requirements for allowed descendants of ARIA roles
Mar 12, 2022
scottaohara
changed the title
Create normative requirements for allowed descendants of ARIA roles
Create normative requirements for allowed descendants of explicit ARIA roles
Mar 12, 2022
Presently section four, allowed descendant of ARIA roles, is marked as non-normative.
The next version of ARIA in HTML will be revising this section to create both normative and non-normative sub-sections. Things we should keep / expand upon:
The text was updated successfully, but these errors were encountered: