Repository navigation
1.4.1 and G182 - clarifying if context comes into play when links use additional cues, but have counterparts that aren't links not using color #5240
Unanswered
Blackbaud-MattGregg
asked this question in
Q&A
Replies: 2 comments 1 reply
|
I would fail it under 1.4.1 in that case. Thanks! |
1 reply
|
Is colour the only difference between large plain text and a link? Are they "similar" or exactly the same apart from colour? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'd be interested in interpretation of if SC 1.4.1 would find the use of color for links non-conformant when the presence of a similar component that is just text also exists. On its own, I think the link passes because it is not relying on color alone. It has font-size and/or font-weight differences compared to the text it it grouped with. However, the same component can also not be a link, it can be just text.
When these two are 'close' (same page) it could be hard to distinguish which is a link vs not a link. A conformance issue of color use (1.4.1)? on its own when only one instance? or only when there is another instance that isn't a link which creates the potential for losing differention? If the non-conformance is due to the context of another instance that is just text, where does boundary of closeness end (same 'small' viewport, 'page' (what about modals, popovers that open from page), or application/site)
Some example of this with a key metric component as well as a description list where sometimes values can be text or they can be links. I grouped them in the same boxes, but the link vs text could be in different boxes or sections of a page as well.

I found this related discussion which had an answer as non-conformance but didn't get into rationale. Was it because there was already bold text and it that wasn't there it wouldn't be a fail?
#4467
All reactions