When using high contrast settings in firefox (preferences->content->colours set white-on-black and always) the status of jobs is invisible since it is shown only using colours. It can be worked-around using the Stylish add-on adding an :after pseudo-element to each colour button with a content property to add a tick, a cross or other symbol. But maybe there's an even better idea, particularly to draw one's eye to particular statuses the way colours do.

Oh I had an idea. This could be much easier to scan if it the results were aligned in some way: Test name: result Test naem: result Etc, the most obvious is a table. Colours and symbols could be used together in the table layout, a special "vision impaired mode" won't be necessary and I believe it'll be more readable for everyone. Thanks.

This is still a problem and slows down my work. Further on the table idea, You could have a coloum in the table per status, and move items between columns as they change status. Also use colour. Here is some information about my assessability settings: http://paul.bone.id.au/2017/11/26/how-i-see-the-web/ Thanks.

Hi Paul, sorry there hasn't been a reply here sooner - I can only imagine how annoying this issue must be. The Treeherder team is pretty understaffed at the moment (we've gone from 5 people to 2, and are lacking in a strong frontend person currently). Regarding the table layout idea, I'm not sure how this would work given the sheer number of jobs we have. For example this not too unusual mozilla-central push has 7500 jobs: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&revision=e4de69553e3faf8136eb9bb7f2f741e1b7e6f866&group_state=expanded In table format this would consume pages and pages of screen estate.

Mmm, My second idea might be better. Where the symbols/icons move between columns of a table. It'll still takeup more room that the current version. If it were optional that may help. I don't have any other ideas at this stage. Thanks for responding.

Bug 1475438 has a different approach for surfacing this information, that doesn't have the issues of comment 3 (taking up too much screen estate). Whilst it sounds like that bug will only partly help, any additional solution will probably need to be something other than a table layout.