You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following code should pass, but throws a contrast error: <p>Sample: <span style="color: #7c7cff; background-color: #ffffff; font-size: 14pt; font-weight: bold;">I am 14pt bold text and should pass</span></p>
The error is:
This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.4:1. Recommendation: change text colour to #6666e9.
WCAG 2.0 AA requirement is 3:1 for large text, defined as 14 point and bold or larger, or 18 point or larger. This text is 14pt bold, and so should pass.
The text was updated successfully, but these errors were encountered:
It probably didn't come to my attention before because I had in my head the mention in the standard of "120% of the default body text", which is actually 19.2px (=14.4pt) in most browsers, hence for a moment I thought this wasn't a bug, but you're most certainly correct.
Will get to it in the next release. Thanks for the report!
…s for the calculation are preserved and the error for the given use case is resolved. Unit test added and passing for the issue however the basic failure isn't generating with the correct code that the auditor is presenting. It's likely to be an issue with the unit test or unit test runner code rather than an actual failure to detect (works when run manually).
The following code should pass, but throws a contrast error:
<p>Sample: <span style="color: #7c7cff; background-color: #ffffff; font-size: 14pt; font-weight: bold;">I am 14pt bold text and should pass</span></p>
The error is:
WCAG 2.0 AA requirement is 3:1 for large text, defined as 14 point and bold or larger, or 18 point or larger. This text is 14pt bold, and so should pass.
The text was updated successfully, but these errors were encountered: