Opened 3 weeks ago
Last modified 11 days ago
#5757 new enhancement
Color blind feature for translate.wordpress.org ?
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Translate Site & Plugins | Keywords: | needs-patch |
Cc: |
Description
Lately when I'm going through all the waiting strings for all the plugins and themes in my locale, I notice that I sometimes have a hard time seeing the difference between the orange of fuzzy strings and the red of refused strings.
This becomes especially annoying when for a plugin suddenly 200+ strings go fuzzy, and you want to reject to completely redo them...
Personally, I'm not color-blind, but I do think that people being color-blind especially for red will have an even harder time seeing the difference. So, I think it would be cool to have a feature in your translation settings or something along those lines to change the colors to make things like written above easier when checked.
Attachments (2)
Change History (7)
This ticket was mentioned in Slack in #accessibility by nekojonez. View the logs.
3 weeks ago
This ticket was mentioned in Slack in #accessibility by ryokuhi. View the logs.
3 weeks ago
This ticket was mentioned in Slack in #polyglots by nao. View the logs.
2 weeks ago
#4
@
11 days ago
- Keywords needs-patch added
Hey all, sharing a potential design solution based on an idea @NekoJonez had in the Accessibility Team channel on Slack! The idea was to add an additional column that indicates the status of individual strings in a table view. We discussed potentially adding an icon but since there are 6 different status options, I thought a text label might be more clear.
A few notes:
- We could potentially add this new column after the “Priority” column and before the “Original string” column, with the label of “Status”
- Another thing that I found was making it difficult to differentiate between one cell to the next was the very light gray border color being used. I would recommend using a darker gray like the gray used for the header bar area (hex # 666C70)
- The “Details” link in blue (last column to the right) is also not providing enough contrast with certain color-coding combinations. I would suggest using the regular black text color with an underline to indicate that it’s a link.
- We could also tweak the red and orange color for "Fuzzy" and "Rejected" rows to help make the difference more pronounced (mockup uses # EB9090 for red and # F6A983 for orange).
Revised design for translation tables that show the status of strings for a specific project in a locale