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
N.B. All of the "Role Parity" issues are intended to gather feedback from stakeholders who need role parity from us including, but not limited to, groups working on Web Components and AOM. Comments on matters other than determining "which of these mapped elements require a specific role, versus a generic role" should be raised in another GitHub issue. Thank you for your understanding!
The following elements lack a corresponding ARIA role in the HTML AAM, but they are mapped on ALL platforms.
Assumption: Since all platforms map them, all platforms have a need for them. Thus they require a new role. But we need to determine which of these require a dedicated/specific role versus a generic role.
But we need to determine which of these require a dedicated/specific role versus a generic role.
As with #696 (comment), for web components what matters is achieving the ability to create the same experience for AT users using web components as when using native elements. So, specific vs. generic depends largely on how existing ATs treat each of these cases; do they announce them specifically, or generically. I am hopeful those with domain expertise can help elucidate that subject.
N.B. All of the "Role Parity" issues are intended to gather feedback from stakeholders who need role parity from us including, but not limited to, groups working on Web Components and AOM. Comments on matters other than determining "which of these mapped elements require a specific role, versus a generic role" should be raised in another GitHub issue. Thank you for your understanding!
The following elements lack a corresponding ARIA role in the HTML AAM, but they are mapped on ALL platforms.
Assumption: Since all platforms map them, all platforms have a need for them. Thus they require a new role. But we need to determine which of these require a dedicated/specific role versus a generic role.
a
(no href) (generic - roleinline
)abbr
(generic - roleinline
- with TBD attribute)address
(specific)audio
(specific)blockquote
(specific: Add blockquote, caption, footer, header, and paragraph roles #718)canvas
(needs more discussion)caption
(specific: Add blockquote, caption, footer, header, and paragraph roles #718)details
(needs more discussion)div
(generic - roleblock
)dl
(specific)embed
(needs more discussion)fieldset
(specific)figcaption
(specific Add blockquote, caption, footer, header, and paragraph roles #718)footer
not scoped tobody
element (generic: Add blockquote, caption, footer, header, and paragraph roles #718)form
without accessible name (generic - roleblock
)header
not scoped tobody
element) (generic: Add blockquote, caption, footer, header, and paragraph roles #718)iframe
(specific)input
(type=color
) (more discussion)input
(type=date
) (more discussion)input
(type=datetime
-local) (more discussion)input
(type=file
) (more discussion)input
(type=month
) (more discussion)input
(type=password
) (more discussion)input
(type=time
) (more discussion)input
(type=week
) (more discussion)label
(specific)legend
(specific,caption
will be expanded whenfieldset
is added to ARIA)mark
(genericinline
with TBD attribute)meter
(specific)object
(needs more discussion, seeembed
above)p
(specific: Add blockquote, caption, footer, header, and paragraph roles #718)pre
(genericblock
with TBD attribute)q
(genericinline
with possible TBD attribute)ruby
(more discussion, check with i18n)section
(without accessible name) (genericblock
)summary
(needs more discussion)time
(specific)video
(specific)The text was updated successfully, but these errors were encountered: