- From: Robert Linder via GitHub <sysbot+gh@w3.org>
- Date: Fri, 29 Jan 2021 19:39:13 +0000
- To: public-css-archive@w3.org
> - accessibility: a first-class interaction model on the web should be usable for everyone, including when using assistive technologies. I don't know what the current situation is like or what the challenges are. But custom JS-based implementations might neglect this aspect, potentially leaving web maps inaccessible. None of the reviewed [web map tools](https://maps4html.org/HTML-Map-Element-UseCases-Requirements/examples/create-map.html) are pannable _when using a screen reader_, because screen readers have their own built-in commands for the arrow keys. [Azure maps](https://azuremapscodesamples.azurewebsites.net/) and [Esri's a11y-map](https://github.com/Esri/a11y-map) (these happen to not be on the reviewed reference tools list) have worked around this by applying `role=application` to the focusable and pannable element, which may have further implications affecting screen reader users. There's a similar consideration for Google's `<model-viewer>` (https://github.com/google/model-viewer/issues/443). -- GitHub Notification of comment by Malvoz Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5275#issuecomment-770008199 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 29 January 2021 19:39:18 UTC