-
Splitting this out from https://github.com/WordPress/gutenberg/issues/13550#issuecomment-491850649
See #15293 from the WPCampus accessibility audit. Although it specifically refers to notices in th…
-
We currently use native input controls (select, date input, etc) for touch devices. But we need to make sure we use native controls if assistive technology such as screen readers are being used.
-
## 🐛 Bug
The null state message for the notifications pane includes references to features that do not exist. And the notification pane copy could be better for users implying assistive technologies.…
-
Scope
---
Though the `Toast` component was developed with accessibility best practices in mind (including the usage of `role="status"`, the contents of the rendered `Toast` component are not announc…
-
### Bug description
SfPdfVieweronTap callback is not working on pdfs that have more than one page with **FlutterSemantics enabled**.
### Steps to reproduce
1. Load a pdf which has more than p…
-
PING recently reviewed the WAI-ARIA 1.2 spec (https://github.com/w3c/aria/issues/1371) and suggested adding a privacy considerations section (none exists right now) discussing how `aria-hidden` can be…
-
One of the goals of the [ARIA and Assistive Technologies Community Group](https://www.w3.org/community/aria-at/) is to help web developers understand the current state of support for WAI-ARIA by assis…
-
Has there any research been done on how the TTS portion of the API interacts with screen readers and other forms of assistive technology?
-
**Feature request summary**
Per @addyosmani's request, I'm following up with a feature request after today's discussion here, https://twitter.com/scottjehl/status/1278372113716576258 which duplicates…
-
## Issue
Several core architectural features of the Web Platform (in HTML, CSS, client-side JavaScript, etc) may be abused to allow heuristic detectability of assistive technology, conflicting wit…