[ROLE PARITY] Verify we do NOT need new roles for these elements which already have roles

[joanmarie]

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 verifying (or disputing) that "we do NOT need new roles for these elements which already have roles" should be raised in another GitHub issue. Thank you for your understanding!

The following elements are already mapped in the HTML AAM to an ARIA role with an apparent one-to-one correspondence. In addition, the HTML AAM platform mapping for all platforms is "Use WAI-ARIA mapping."

Assumption: We already have parity and no new roles are needed for these elements. Confirmation needed.

• article: article
• button: button
• dialog: dialog
• figure: figure
• form (with accessible name): form
• h1, h2, h3, h4, h5, h6: heading (level mapped using aria-level mapping)
• hr: separator
• img: img
• input (type=button): button
• input (type=checkbox): checkbox
• input (type=number): spinbutton
• input (type=radio): radio
• input (type=range): slider
• input (type=search, no suggestions source element): searchbox
• li (parent is ol or ul): listitem
• main: main
• math: math
• menu (type=context): menu
• menuitem (type=checkbox): menuitemcheckbox
• menuitem (type=command): menuitem
• menuitem (type=radio): menuitemradio
• nav: navigation
• option (in a list of options or represents a suggestion in a datalist): option
• progress: progressbar
• table: table
• td (in table that is not a grid): cell
• td (in table that is a grid): gridcell
• th (is a column header): columnheader
• th (is a row header): rowheader
• th (not a header, table is not a grid): cell
• th (not a header, table is a grid): gridcell

If you agree with the above, please explicitly indicate so (e.g. with a +1/thumbs-up "reaction"). If you disagree, please comment with the element(s) for which you feel a new role is needed. Thanks!

[joanmarie]

I have triaged the landmark and table-related roles from issue #695. I believe the following roles also belong here, namely as roles for which parity has already been achieved:

• aside: complementary
• footer (scoped to body element): contentinfo
• header (scoped to body element): banner
• output: status
• tr: row

[joanmarie]

Closing with no further work required for this issue.