Summary: | AX: intent to remove non-standard role=text feature | ||
---|---|---|---|
Product: | WebKit | Reporter: | James Craig <jcraig> |
Component: | Accessibility | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | CC: | andresg_22, herr.ernst, webkit-bug-importer, yegor.jbanov |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=260685 |
Description
James Craig
2023-08-23 17:44:16 PDT
Patch up at https://webkit.org/b/260684 Tracker to remove entirely at some point in the future is https://webkit.org/b/260685 Consider not removing role=text. When text is rendered into a 2d, WebGL, or WebGPU canvas a DOM overlay is necessary to communicate to a screen reader such as VoiceOver what text is rendered in the canvas. Currently, thanks to role=text in Safari there's a clean way to annotate it (and VoiceOver does a good job of reading it). Other browsers require hacks to make text work, such as artificially giving the text a different role (e.g. heading, or group, even when the text is neither). I filed a feature request for Chromium to adopt role=text with more detail: https://issues.chromium.org/issues/40875151 I hope you reconsider and instead push for the standards committee to adopt the text role. For an example of a high-traffic site, earth.google.com uses it in Safari (transitively via Flutter). I wish I knew about this intent earlier, but this went through way too quickly. I posted more detail in https://bugs.webkit.org/show_bug.cgi?id=260641, but I think it's better to push other browsers to adopt this role rather than remove it. There's an important use-case for the text role. Sorry, I meant to post my last message in https://bugs.webkit.org/show_bug.cgi?id=260685, not here. |