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

Thanks @smhigley, something like that could work.
If the author doesn't supply their own role, we can guess role=none, unless the custom element itself is focusable, or has a global ARIA property that's likely to be used on a generic (in which case we would keep the current generic role mapping). By doing this and resolving https://github.com/w3c/aria/issues/2303, we would have a satisfactory solution for existing content.

For me, aria-live and aria-details seem like the only global ARIA properties that should undo the role=none default. But maybe it's not that important to support this exception, and we should just require the author provide a role if they don't want role=none for the custom element. If this is true, then I think we are just making a new default role for custom elements of "none". @smhigley WDYT?


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

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