Notify users of input validation with aria-live
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 50/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- html
- Domain
- accessibility, documentation
Research direction
Start with the linked Stacks documentation at Inputs > Validation states and compare it with the linked Deque aria-live example. Done means the validation guidance covers announcing dynamically added messages with aria-live="assertive" and addresses the reproduced screen-reader case.
Written by the indexing model from the issue text.
Description
Describe the bug
For the input validation, there should be an aria-live="assertive" on the validation message in cases where the message is added to the DOM/view. (There’s an example of this here from Deque.) With this attribute, screen readers will read this announcement to users when it appears. There is no mention of this in the Stacks documentation.
To Reproduce
Steps to reproduce the behavior:
- In Pickles (or any other SO4T instance) go to Questions, open the filter, and save a custom filter.
- Use a screen reader of your choosing to observe what happens when you change a filter and try to save another custom filter with the same name.
- Note that the validation message is not read out.
Expected behavior
Include a note in Inputs > Validation states about using aria-live.
- Dominant language
- TypeScript
- Stars
- 672
- Forks
- 107
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 26
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.
More from StackExchange/Stacks
-
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
StackExchange/Stacks#1030 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
StackExchange/Stacks#1842 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
StackExchange/Stacks#1413 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
StackExchange/Stacks#1242 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
StackExchange/Stacks#1224 ·
All issues in StackExchange/Stacks
Similar issues
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/rig#534 ·
-
automation missing-model model-sync provider:pioneer
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
anomalyco/models.dev#7701 ·