Kilotest: Diagnoses of text contrast not testable violation by HTML element 327 on 350 Sacramento page

Basics

About the 350 Sacramento page

• URL: https://350sacramento.org/
• Tested 28 days ago by job 029 on 2026-05-04 at 16:59

About HTML element 327

• Tag name: A
• Text: 2025 IMPACT REPORT
• Start tag: <a class="nectar-button large regular accent-color regular-button button-home" role="button" style="margin-right: 25px; margin-bottom: 5px; color: #015657; background-color: #FFFFFF;" target="_blank" href="https://350sacramento.org/wp-content/uploads/2026/01/2025-Annual-Impact-Report-350-Sacramento.pdf" data-color-override="#FFFFFF" data-hover-color-override="false" data-hover-text-color-override="#fff">
• XPath: [not obtained]
• Bounding box: x = 613, y = 549, width = 205, height = 70

Take me there

About the text contrast not testable issue

• Why it matters: Text may be difficult to read
• Priority: lowest
• Related WCAG standard: 1.4.3

Diagnoses

Here is how tools diagnose the text contrast not testable issue for HTML element 327 of the 350 Sacramento page.

1. Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour.

   Tool: HTML CodeSniffer (Squiz Labs)

   Rule: W-WCAG2AAA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour