Bug 1324356

Summary:	Screen readers do not get hints about component selection when creating issues
Product:	[Community] Bugzilla	Reporter:	Stanislav Ochotnicky <sochotni>
Component:	User Interface	Assignee:	Jeff Fearn 🐞 <jfearn>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jeff Fearn 🐞 <jfearn>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.0	CC:	huiwang, ltyrycht, pvlcek, qgong
Target Milestone:	---	Keywords:	UserExperience
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.0.4.rh95	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-03 00:51:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stanislav Ochotnicky 2016-04-06 07:10:41 UTC

Description of problem:
I have a report from user using screen reader (Orca) that bugzilla component selection when reporting bugs is not giving proper hints. Specifically:
 * when selecting component field there's no hint about type of field
 * Selection changes are not announced

I put Pavel on CC, maybe he can elaborate more

Comment 1 Stanislav Ochotnicky 2016-04-06 07:13:42 UTC

Oh, one suggested option/question was if it would be possible to have accessibility setting where the component selection would be ordinary dropdown (with the performance impact it causes)

Comment 2 Lukáš Tyrychtr 2018-05-29 09:21:45 UTC

Just a quick update, the upstream issue has a somewhat working, unfortunately not merged, solution in the last comment.

Comment 4 Jeff Fearn 🐞 2024-05-21 23:51:09 UTC

On QA server:

Comparing the wave report between production and live there are almost twice as many Aria entries in the new UI.

The new UI looks the same and functions without client or server errors.

The audio promoting appears to work properly, but I am not confident that the test set-up is an accurate reflection of real world usage.

It is at least better and a better platform for future changes as required.

Comment 5 Jeff Fearn 🐞 2024-06-03 00:51:01 UTC

This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.