Re: [WICG/webcomponents] Web components authors are currently using ARIA in problematic ways that lead to duplicate announcements (Issue #1073)

Dropping a thought here that was briefly talked about during the TPAC ARIA/Web components session:

If it's possible to add a default role based on the existence of `referencetarget`, or potentially some specific attributes defined in `referencetargetmap` (e.g. `role`). When those are defined, we may want to add a default `role=none` mapping to solve the duplicate/nested attribute issue mentioned here, but without always setting a default role `none` to differentiate between intentionally exposing a11y information on the custom element node.

I think this would ideally be done with an HTML AAM mapping rather than adding a literal `role` IDL attribute to the custom element, unless that isn't technically feasible.

I'm curious what other folks think, and also whether this is technically feasible and if so, what the logic to set the default `role=none` should be.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1073#issuecomment-2375010998
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1073/2375010998@github.com>