Input requested on ARIA/HTML role parity

[LJWatson]

The ARIA WG is working on achieving role parity with HTML. They've asked for help from the Web Components community.

Initial triage has already been done, and elements put into several categories. A summary is given below, but please check the original request for more information and better explanations.

Elements with no ARIA role and no accessibility API mapping

• Assumption: if no platform has a need for them to be mapped, there is no need to create a role for them.
• Input needed: Confirmation that the assumption is valid.
• Issue for comment: [ROLE PARITY] Verify we do NOT need new roles for these "not mapped" elements w3c/aria#693

Elements with an ARIA role and with consistent accessibility API mappings

• Assumption: we have parity and no new roles are needed.
• Input needed: confirmation that the assumption is valid.
• Issue for comments: [ROLE PARITY] Verify we do NOT need new roles for these elements which already have roles w3c/aria#694

Elements with no ARIA role and without consistent accessibility API mappings

• Assumption: a role is probably needed, but a generic role will suffice.
• Input needed: confirmation that the assumption is valid.
• Issue for comments: [ROLE PARITY] Determine if any of these mostly unmapped elements require a specific role w3c/aria#698

Elements with an ARIA role but without a 1-1 accessibility API mapping

• Assumption: some elements may need a dedicated role, others may not.
• Input needed: consensus on the elements that need new roles, and those that don't (and that can be added to [ROLE PARITY] Verify we do NOT need new roles for these elements which already have roles w3c/aria#694)
• Issue for comments: [ROLE PARITY] Determine which of these elements with existing ARIA role mappings require a new role w3c/aria#696

Elements without an ARIA role but with consistent accessibility API mappings

• Assumption: if all platforms map them, all platforms need them, and thus a role is needed for each.
• Input needed: consensus on which elements need a dedicated role, and which can use the generic role (mentioned above).
• Issue for comments: [ROLE PARITY] Determine which of these mapped elements require a specific role, versus a generic role w3c/aria#697

[annevk]

Thanks for raising this, I think @domenic adequately captured the concerns around ARIA and custom elements. Since everything already has a dedicated issue I'll close this so discussion can continue there.