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

Starting in Chromium 133.0.6852.0 (currently in Canary), you can run Chrome/Edge with the command --enable-blink-features=AccessibilityCustomElementRoleNone. It changes custom elements to use a default role of none, meaning that the custom element will be removed from the a11y tree, with these exceptions:

* is focusable
* has aria-live,
* has aria-owns
* uses element internals to set an ARIA property
* uses an ARIA relation via an element attribute (e.g. myCustomElement.ariaLabelledByElements = [ labelElement ]; )

Since it's a default role, that means it only takes place if the author did not provide their own role for the element.

If I don't hear any objections, I'll update to "experiment" stage which turns it on when "experimental web platform features" is enabled in chrome://flags.



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

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