Automattic / Automattic/o2

Resolved-unresolved state accessibility

Open
#81 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
338
Forks
56
Avg merge
24m
Merged PRs (30d)
16

Description

This was reported in the Italian forums. The resolved/unresolved state is conveyed via a "border" (actually a CSS generated element background) color. Red or green.

For accessibility, color alone is not sufficient to convey such an important information and it would need an additional indicator, a different shape or something like that. Worth reminding the most common form of color perception impairment is about green and reds.

Also, I'm not 100% sure if it is actually used, but besides the red #e6000a I see some occurrences of red which translates to #ff0000 and when used against white, this red gives a contrast ratio under the 4.5:1 recommended by the WCAG level AA.

Contributor guide

No contributing guide indexed for this repository

Research direction

Locate the CSS-generated element background that conveys resolved and unresolved states, then inspect how the red and green indicators are used. Verify that the states have a non-color indicator and that red against white meets WCAG AA contrast; done means the distinction remains clear for users with color-perception impairments.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
accessibility, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.