Contact emails [email protected]<mailto:[email protected]>
Explainer No formal explainer but https://github.com/w3c/aria/issues/667 discusses use cases and alternatives. Specification https://w3c.github.io/aria/#aria-colindextext, https://w3c.github.io/aria/#aria-rowindextext Summary The `aria-rowindextext` and `aria-colindextext` properties can be used by developers to express semantics about a table or grid to assistive tech. These attributes are applied in addition to `aria-rowindex` or `aria-colindex` in cases where the numeric indices of rows or columns are not meaningful, for example a chessboard or a spreadsheet where the columns are named by letters rather than numbers. These properties are reflected in JavaScript as: * `Element.ariaRowIndexText` * `Element.ariaColIndexText` * `ElementInternals.ariaRowIndexText` * `ElementInternals.ariaColIndexText` These are part of the Interop2024 Accessibility focus area: https://wpt.fyi/results/wai-aria/idlharness.window.html?label=master&label=experimental&aligned&view=interop&q=label%3Ainterop-2024-accessibility Blink component Blink>Accessibility TAG review These properties were included for WAI-ARIA 1.3 which was reviewed by the TAG at https://github.com/w3ctag/design-reviews/issues/927 TAG review status Resolution: Satisfied Risks Interoperability and Compatibility None Gecko: Shipped/Shipping WebKit: No signal (https://bugs.webkit.org/show_bug.cgi?id=257142) Web developers: No direct signals, but this is part of the Interop2024 Accessibility focus area: https://wpt.fyi/results/?label=master&label=experimental&aligned&view=interop&q=label%3Ainterop-2024-accessibility Other signals: Ergonomics None. Activation It isn't possible to polyfill the functionality of delivering the semantics to AT. However the properties can be set on browsers that don't support them yet without causing errors, so gradual adoption should be straightforward. The property reflection behavior could be polyfilled if necessary. Security We do not anticipate any security impact from this feature. 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? None Debuggability The property values can be observed in chrome://accessibility. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)? Yes Is this feature fully tested by web-platform-tests? Yes https://wpt.fyi/results/wai-aria/idlharness.window.html?label=master&label=experimental&aligned&view=interop&q=label%3Ainterop-2024-accessibility https://wpt.fyi/results/html/dom/aria-attribute-reflection.html?label=master&label=experimental&aligned&view=interop&q=label%3Ainterop-2024-accessibility https://wpt.fyi/results/custom-elements/ElementInternals-accessibility.html?label=master&label=experimental&aligned&view=interop&q=%2Fcustom-elements%2F Flag name on chrome://flags None Finch feature name AriaRowColIndexText Requires code in //chrome? False Estimated milestones Shipping on desktop 128 Anticipated spec changes None Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5182419585204224 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/MW4PR00MB1453C3FD8F1F3CD3E8133243C5C02%40MW4PR00MB1453.namprd00.prod.outlook.com.
