Selected finding
Visual contrast accessibility issue
Benchmark frequency is directional market context only. It is not a compliance benchmark, legal conclusion, or severity score. Rare findings may be top-ranked only when retained evidence is strong; common findings may remain medium when evidence is automated or context-dependent. Rarity is not severity, and prevalence is not compliance risk.
Observed
Retained automated accessibility evidence showed text or controls with contrast-related signals that may fall below the applicable automated threshold for the detected element and state.
Why this matters
Users with low vision, color-vision differences, glare, aging-related vision changes, zoomed interfaces, or high-brightness environments may struggle to read text or distinguish controls when contrast is too low. For review teams, the signal can help identify design-token, component-state, or template-level contrast issues that may affect usability and accessibility.
Detection methodology
CertScore retains representative automated accessibility evidence for contrast-related checks, including the rule identifier, affected selector or element reference, page URL, impact label when available, and WCAG-oriented references. The finding is surfaced when retained evidence indicates that text, controls, or meaningful visual elements may fall below the applicable automated contrast threshold for the observed state. CertScore treats automated contrast results as review signals. The scanner does not infer full WCAG conformance or non-conformance from a single automated rule result. Reviewers should consider text size, font weight, element purpose, component state, decorative or inactive status, surrounding context, responsive breakpoint, and whether the retained evidence reflects the affected user-visible state.
Confidence semantics: Good when representative automated contrast-rule evidence includes rule ID, selector or element reference, page context, impact label, and WCAG-oriented references; stronger when retained evidence also includes computed color pairs, contrast ratio, text-size/state context, and repeated examples across templates. Manual review is still needed for context, exceptions, user impact, and remediation quality.
Top-finding calibrationWhat must be retained to surface, top-rank, demote, or suppress this finding.
Minimum to surface
- Automated contrast rule with selector, page, and WCAG reference.
High confidence requires
- Color pair or ratio.
- Element state.
- Meaningful visible content.
Top ranking requires
- Repeated component.
- Critical user path.
- Control or focus indicator.
Demote or suppress when
- Decorative, inactive, logo, or incidental context without manual review.
These rules describe ranking calibration for already-projected findings. They do not create findings from raw signals.
Example evidence
Text contrast example
rule=color-contrastartifact=contrast_001role=finding_supporting_artifacturl=https://example.com/pricingselector=[data-example-component="pricing-card"] .example-muted-copyimpact=seriouswcag_refs=1.4.3 Contrast (Minimum)element_type=textstate=defaultcomputed_color_pair=not_retained_in_public_samplereview_caveat=manual review should confirm color pair, text size, font weight, state, and whether the text is meaningful user-visible content
Review context
component=pricing_cardpossible_source=design_tokenstates_to_review=default, hover, focus, active, disabled, placeholder, errorresponsive_scope=public desktop/mobile page states observed in scan scopemanual_review_needed=true
What should not count by itself
token_name=muted.foreground [audit_only_without_affected_element]selector=.text-muted [insufficient_without_rule_and_page_context]brand_logo_low_contrast [requires_exception/context_review]disabled_button [requires_inactive_state_review]
View redacted sample JSONHide redacted sample JSON
{
"findingId": "visual_contrast_accessibility_issue",
"label": "Visual contrast accessibility issue",
"category": "Accessibility",
"criticality": "medium",
"evidenceConfidence": "good",
"directVsInferred": "direct_observation",
"evidence": {
"summary": "Retained automated accessibility evidence showed text or controls with contrast-related signals that may fall below the applicable automated threshold for the detected element and state.",
"examples": [
{
"title": "Text contrast example",
"lines": [
"rule=color-contrast",
"artifact=contrast_001",
"role=finding_supporting_artifact",
"url=https://example.com/pricing",
"selector=[data-example-component=\"pricing-card\"] .example-muted-copy",
"impact=serious",
"wcag_refs=1.4.3 Contrast (Minimum)",
"element_type=text",
"state=default",
"computed_color_pair=not_retained_in_public_sample",
"review_caveat=manual review should confirm color pair, text size, font weight, state, and whether the text is meaningful user-visible content"
]
},
{
"title": "Review context",
"lines": [
"component=pricing_card",
"possible_source=design_token",
"states_to_review=default, hover, focus, active, disabled, placeholder, error",
"responsive_scope=public desktop/mobile page states observed in scan scope",
"manual_review_needed=true"
]
},
{
"title": "What should not count by itself",
"lines": [
"token_name=muted.foreground [audit_only_without_affected_element]",
"selector=.text-muted [insufficient_without_rule_and_page_context]",
"brand_logo_low_contrast [requires_exception/context_review]",
"disabled_button [requires_inactive_state_review]"
]
}
]
}
}Regulatory review context
Accessibility: low visual contrast
Retained automated accessibility evidence showed text or controls with contrast-related signals that may be relevant to WCAG-oriented accessibility review. Applicability depends on the affected element, visual state, text size, purpose, decorative or inactive status, page context, organization type, jurisdiction, and manual accessibility review.
View applicability notes
Legal and regulatory frameworks
- WCAG 1.4.3 Contrast (Minimum) (AA)Text or images of text have contrast-related evidence that may require Contrast (Minimum) review.
- WCAG 1.4.11 Non-text Contrast (AA)Controls, icons, focus states, boundaries, or meaningful graphical objects have contrast-related evidence that may require non-text contrast review.
Jurisdictional contexts
- ADA Title II web/mobile accessibility reviewState or local government web content or mobile apps may be in scope depending on organization context, service context, and manual review.
- ADA Title III public accommodation accessibility reviewA business open to the public provides goods, services, or communications through the website.
- Section 508 ICT accessibility reviewFederal agency ICT, federal web content, or federal procurement/vendor review may be in scope depending on organization context, procurement context, and manual review.
- EN 301 549 / EU accessibility reviewEU public-sector, procurement, Web Accessibility Directive, or European Accessibility Act service context may be in scope depending on organization context, service context, and manual review.
- UK public-sector accessibility reviewUK public-sector website or mobile app may be in scope depending on organization context, service context, and manual review.
WCAG references are technical review references. Legal obligations and incorporated versions may vary by jurisdiction and organization type, including WCAG 2.0, 2.1, 2.2, EN 301 549, ADA Title II, Section 508, EU Web Accessibility Directive / European Accessibility Act, and UK public-sector accessibility rules. This finding does not determine legal status or WCAG conformance. Review the retained selector, color pair, text size, component state, element purpose, page context, applicable exceptions, organization type, jurisdiction, and manual accessibility findings.
Evidence standard
Strong
- Representative automated contrast evidence includes rule ID, affected selector or element reference, page URL, impact label, and WCAG-oriented reference.
- Retained evidence gives enough context for review of whether the element is normal text, large text, a control, icon, border, focus indicator, graphical object, placeholder text, error text, inactive component, decorative content, incidental content, or logo/brand content.
- Retained evidence includes computed foreground/background colors and contrast ratio when available, or a retained automated rule result sufficient for reviewer inspection.
- Evidence indicates the affected element is meaningful user-visible content or a meaningful UI component, rather than purely decorative content or an inactive component.
- Repeated examples across templates, components, states, or breakpoints may strengthen confidence when retained.
Good
- Representative automated contrast-rule evidence includes rule ID, selector or element reference, page URL, impact label, and WCAG-oriented references.
- The retained example is enough for a reviewer to locate the affected element and verify the contrast pair manually.
- The evidence is likely text contrast or control contrast, but details such as exact text-size classification, visual state, or repeated-instance scope may require manual review.
Audit-only
- Contextual contrast signals exist, but retained evidence lacks enough detail to confirm the affected element, state, color pair, or applicable threshold.
- Low-contrast colors appear in design tokens, screenshots, CSS, or component naming, but no retained automated contrast artifact identifies a user-visible affected element.
- The issue may involve text over images, gradients, video, transparency, pseudo-elements, canvas, or shadow DOM where automated evidence is incomplete.
Insufficient
- Color values or design-token names without a retained affected element or automated contrast artifact.
- Selector alone without rule ID, page context, or contrast-related evidence.
- A screenshot, visual impression, or user report without retained automated evidence or reviewer-confirmed contrast measurements.
- Disabled or inactive, decorative, incidental, or logo/brand content treated as finding-supporting evidence without context review.
- Claims about WCAG status or legal status based only on automated evidence without manual context review.
Evidence levels explain how CertScore treats retained accessibility artifacts. They are not legal conclusions.
Common causes
- Design tokens or theme variables produce low foreground/background contrast.
- Disabled, placeholder, muted, secondary, hover, focus, active, or error states reuse colors that fall below the relevant threshold.
- Text over images, gradients, video, or transparent overlays lacks a stable contrast-safe treatment.
- Icon-only controls, form borders, focus indicators, or graphical objects rely on subtle color differences.
- Component libraries or templates were updated without contrast regression checks across breakpoints and states.
Recommended review questions
- Which selector, component, page, and visual state triggered the automated contrast evidence?
- Is the affected element normal text, large text, an icon-only control, a form border, a focus indicator, a graphical object, placeholder text, error text, inactive component, decorative content, incidental content, or logo/brand content?
- What foreground and background colors, design tokens, or CSS variables produced the contrast pair?
- Does the relevant threshold differ because the text is large, bold, inactive, incidental, decorative, or part of a logo/brand mark?
- Does the issue appear only in one instance, or is it repeated across templates, components, themes, or responsive breakpoints?
- Were hover, focus, active, disabled, placeholder, error, and dark/light mode states reviewed?
- Could text over an image, gradient, video, transparency, canvas, pseudo-element, or shadow DOM affect the real contrast seen by users?
- Does the proposed remediation preserve design intent while meeting the applicable contrast threshold?
- Should a manual accessibility review confirm context, user impact, exemptions, and remediation quality?
Limitations and cautions
- This finding is an automated accessibility review signal, not a legal conclusion, certification, or determination of WCAG conformance or non-conformance.
- Automated contrast checks can identify many computed color-contrast issues, but they may miss or misread text over images, gradients, video, canvas, transparency, pseudo-elements, shadow DOM, dynamic states, responsive breakpoints, and authenticated or user-triggered states.
- Automated evidence may not fully determine text size, font weight, meaningfulness, decorative status, inactive status, logo/brand status, or whether a non-text visual element is necessary to understand the interface.
- Manual review is needed to confirm context, applicable threshold, exception status, user impact, and remediation quality.
- Remediation should be verified across default, hover, focus, active, disabled, placeholder, error, dark/light mode, and responsive states where relevant.
- CertScore retains representative evidence for review and may not list every repeated instance across a template or component library.
- Findings should be evaluated with implementation context and applicable accessibility requirements before operational or legal reliance.
- Automated findings may contain errors and should be reviewed with the retained evidence.
- Not detected means not observed in the scan scope; it is not proof of absence.
- Findings are runtime evidence and public-surface observations for review, not legal conclusions.
