LGTM1. Thanks for catching us up here! On Sat, Sep 3, 2022, 08:13 Valerie Young <[email protected]> wrote:
> *Contact emails* > [email protected], [email protected] > > *Explainer* > > https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-brailleroledescription > > https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-braillelabel > > *Specification* > https://w3c.github.io/aria/#aria-brailleroledescription > > *Summary* > Add the aria-brailleroledescription and aria-braillelabel attributes. > > These ARIA attributes can be used to override the role description or > accessible name for an element when the output of a screen reader is > directed to a braille device, primarily for purposes of brevity. > > See https://w3c.github.io/aria/#aria-brailleroledescription > and https://w3c.github.io/aria/#aria-braillelabel > > *Blink component* > Blink>Accessibility > > *TAG review* > > *TAG review status* > Not applicable > > *Risks* > *Interoperability and Compatibility* > There are none. > > *Gecko:* Shipped/Shipping And all aria* attributes are exposed by default > in firefox. > > *WebKit:* Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=220719 > ) > > *Web developers: *No signals > > *WebView application risks* > *Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications?* > No > > *Debuggability* > you will see "aria-brailleroledescription" and "aria-braillelabel" in the > dev tools and accessibility tree by default. > > *Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)?* > Yes > > *Is this feature fully tested by web-platform-tests?* > Yes, https://github.com/web-platform-tests/wpt/pull/35323 > > *Flag name* > > *Requires code in //chrome?* > False > > *Tracking bug* > https://bugs.chromium.org/p/chromium/issues/detail?id=1289234 > > *Estimated milestones* > No milestones specified > > *Anticipated spec changes* > Open questions about a feature may be a source of future web compat or > interop issues. Please list open issues (e.g. links to known github issues > in the project for the feature specification) whose resolution may > introduce web compat/interop risk (e.g., changing to naming or structure of > the API in a non-backward-compatible way). > > *Link to entry on the Chrome Platform Status* > https://chromestatus.com/feature/5166332144779264 > > This intent message was generated by Chrome Platform Status. > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b0364a0d-8acc-7507-d765-8134f5efa50b%40igalia.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b0364a0d-8acc-7507-d765-8134f5efa50b%40igalia.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfUFRhwzz32GCjn%3DtoEr0TX8-utmRDVHUyPGtkHTbUFqTw%40mail.gmail.com.
