[MGNLUI-4046] Identify search fields by their function Created: 21/Oct/16 Updated: 27/Jun/17 |
|
| Status: | Open |
| Project: | Magnolia UI |
| Component/s: | app |
| Affects Version/s: | 5.4.9 |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | WAI-ARIA, accessibility | ||
| Remaining Estimate: | 2d | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | 2d | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Epic Link: | Accessibility improvements |
| Description |
|
When you tab into a search field in an app the screen reader speaks "Text field with autocompletion" but doesn't tell that this is a search field. It doesn't know the function of the field. Investigate how we can pass the name or role of the field in an ARIA attribute. Investigate what is the ARIA best practice for search fields. Investigate why the screen reader cannot access and speak the placeholder text "Search" that we already have in the search field. |