Closed Bug 1177857 Opened 10 years ago Closed 10 years ago

Treeherder job spans should be buttons for a11y

Categories

(Tree Management :: Treeherder, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wlach, Assigned: wlach)

References

Details

Attachments

(2 files)

For screen readers, it would be useful if the job elements were buttons, instead of spans. This is an easy change to make, so we should just do it.
Summary: Treeherder job spans should be buttons again → Treeherder job spans should be buttons
Attached file PR
Attachment #8626690 - Flags: review?(tojonmz)
Status: NEW → ASSIGNED
OS: Unspecified → All
Priority: -- → P2
Hardware: Unspecified → All
Summary: Treeherder job spans should be buttons → Treeherder job spans should be buttons for a11y
Comment on attachment 8626690 [details] [review] PR r+ in advance for Will assuming a suitable transparency tweak for non-failed selected jobs.
Attachment #8626690 - Flags: review?(tojonmz) → review+
Just needed to shuffle some CSS to fix the transparency issue. Pushed afterwards.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Blocks: 1053279
I didn't notice this testing the first iteration of the PR, but RyanVM noticed the landed iteration on production this morning. When manually selecting the new a11y job buttons we (or the browser) draws them in quite different styles to its former span approach, and also different to using the n,p keys. See attached. It might be nice if we could draw them the same as they were before, consistently with the two workflows, and sans the browser btn stylings. Currently a dashed btn on Firefox, a haloed btn on Chrome, and a dark background.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: