Bug 1324356 - Screen readers do not get hints about component selection when creating issues
Summary: Screen readers do not get hints about component selection when creating issues
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: User Interface
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeff Fearn ๐Ÿž
QA Contact: Jeff Fearn ๐Ÿž
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-06 07:10 UTC by Stanislav Ochotnicky
Modified: 2025-10-16 23:45 UTC (History)
4 users (show)

Fixed In Version: 5.0.4.rh95
Clone Of:
Environment:
Last Closed: 2024-06-03 00:51:01 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github selectize selectize.js issues 798 0 None open Aria accessibility just lacking 2020-03-09 04:03:36 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.