How to make sure the overscroll area can be closed in an accessible way
Open
Nobody has claimed this yet.
needs-triage
overscroll
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
This issue was lifted almost verbatim from this comment by @smhigley:
We need to solve for the following two cases:
- If the overscroll area is modal (see #1384), so the original button isn't in the a11y tree. This would affect screen reader and voice control software. (Desktop screen reader users could potentially use escape, but not touch SR users or VC users)
- Whether or not it's not modal, if the scroll causes the orignal button to be outside the visible area. This would not affect screen readers, but would affect some switch users, voice control users, and some people not using any AT but with mobility disabilities that affect their ability to scroll.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the source comment in openui/open-ui#1372 and the related modal overscroll issue #1384. Identify an accessible way to close the overscroll area when the original button is unavailable or outside the visible area, and define behavior for screen reader, voice control, switch, touch, and mobility-disabled users.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100