Text fields and related information should be accessible to screen readers
Closed, ResolvedPublic3 Estimated Story Points
Actions

Assigned To

Authored By

	ECohen_WMDE
	Sep 17 2021, 4:01 PM

Description

Current Issue

Fields are not connected to the parameter label or description (if available) and read out as only "edit text blank" without additional information about what the field expects from the user.
Screenshots from using VoiceOver

Screen Shot 2021-09-17 at 17.58.40.png (1×2 px, 723 KB)

Screen Shot 2021-09-17 at 17.57.59.png (950×2 px, 490 KB)

Notes

Is this happening because we are not using the default OOUI widget for FieldLayout?
Possible fix: add IDs for aria-labeledby and aria-describedby so that the label is read out with the field and users have the option to listen to description if they would like to
Might have useful information: https://www.w3.org/WAI/tutorials/forms/
Information on aria-describedby https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA1.html

Requirements

As a user, when I focus a field, I have access to information about the field, including label, instructions, and if it's required

Details

	Subject	Repo	Branch	Lines +/-
	Make text fields and related information accessible to screen readers	mediawiki/extensions/VisualEditor	master	+16 -25

Customize query in gerrit

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Open		None	T289653 Screenreader support for the new VisualEditor template editor sidebar
		Resolved		lilients_WMDE	T291273 Text fields and related information should be accessible to screen readers

Event Timeline

ECohen_WMDE created this task.Sep 17 2021, 4:01 PM

ECohen_WMDE mentioned this in T291277: Screen reader should not see the More/Less button.Sep 17 2021, 4:18 PM

ECohen_WMDE moved this task from Backlog to Ready for story time on the WMDE-Templates-FocusArea board.Sep 17 2021, 5:16 PM

matmarex moved this task from To Triage to Triaged on the VisualEditor board.Sep 20 2021, 12:30 PM

awight set the point value for this task to 3.Sep 29 2021, 1:29 PM

ECohen_WMDE updated the task description. (Show Details)Oct 15 2021, 8:54 AM

ECohen_WMDE updated the task description. (Show Details)Oct 15 2021, 9:17 AM

Lena_WMDE added a project: WMDE-TechWish-Sprint-2021-10-13 .Oct 18 2021, 3:08 PM

lilients_WMDE claimed this task.Oct 21 2021, 8:02 AM

lilients_WMDE moved this task from Sprint Backlog to Doing on the WMDE-TechWish-Sprint-2021-10-13 board.

Change 732712 had a related patch set uploaded (by Svantje Lilienthal; author: Svantje Lilienthal):

[mediawiki/extensions/VisualEditor@master] Make text fields and related information accessible to screen readers

https://gerrit.wikimedia.org/r/732712

gerritbot added a project: Patch-For-Review.Oct 21 2021, 2:24 PM

lilients_WMDE moved this task from Doing to Tech Review on the WMDE-TechWish-Sprint-2021-10-13 board.Oct 21 2021, 2:25 PM

lilients_WMDE updated the task description. (Show Details)Oct 21 2021, 2:27 PM

Change 732712 merged by jenkins-bot:

[mediawiki/extensions/VisualEditor@master] Make text fields and related information accessible to screen readers

https://gerrit.wikimedia.org/r/732712

ReleaseTaggerBot added a project: MW-1.38-notes (1.38.0-wmf.6; 2021-10-26).Oct 22 2021, 1:00 PM

Maintenance_bot removed a project: Patch-For-Review.Oct 22 2021, 1:10 PM

Note: we should check the order of the elements.

Currently it reads as follows:

label
"required"
entry with "entry"
description with required information

Not sure if that makes sense, because the display order is label, description, required, entry.

lilients_WMDE moved this task from Tech Review to Demo on the WMDE-TechWish-Sprint-2021-10-13 board.Oct 25 2021, 7:34 AM

@lilients_WMDE I wouldn't worry about the order of elements matching how it is displayed in the UI. It should stick with whatever is standard for screenreaders, since that is what users will expect and be able to navigate most easily.

Thanks, @ECohen_WMDE. It also looks as if the order differs in different tools. So I guess we can not do much.

It also looks as if the order differs in different tools. So I guess we can not do much.

Ok thanks for checking! I think if it's different in different tools, then it's even more important not to override it so that everyone gets the order they are accustomed to with their tool.

thiemowmde closed this task as Resolved.Oct 26 2021, 8:45 AM

thiemowmde moved this task from Demo to Done on the WMDE-TechWish-Sprint-2021-10-13 board.

	F34646223: Screen Shot 2021-09-17 at 17.58.40.png
	Sep 17 2021, 4:01 PM

	F34646225: Screen Shot 2021-09-17 at 17.57.59.png
	Sep 17 2021, 4:01 PM

Text fields and related information should be accessible to screen readersClosed, ResolvedPublic3 Estimated Story PointsActions