Kilotest: Diagnoses of text contrast improvable violation by HTML element 353 on US Digital Response page

Basics

About the page

• URL: https://www.usdigitalresponse.org/
• Tested 2 days ago on 2026-10-07 at 23:22 by job 261007T2305-nes
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 11
  • Violations: 814
  • Violators: 261
  • Issues: 38
• Download the full technical report (JSON)

About the issue

• Why it matters: Content is not easy to understand
• Priority: lowest
• Related WCAG standard: 1.4.6
• Reported by 7 rule engines (Alfa + ASLint + Axe + HTML CodeSniffer + Pour + QualWeb + SureA11y)
• Violations: 269
• Violators: 97

About the violator

• Tag name: DIV
• Text: Unfortunately no. We prioritize requests that align with our offerings, would benefit from USDR's skill set, and allow us to partner directly with local and state governments. We can also consult on internal capacity building. When we can’t offer support, we will do our best to suggest other resources.
• Start tag: <div class="rtf w-richtext">
• XPath: [not obtained]
• Bounding box: x = 431, y = 5556, width = 1056, height = 81
• Reported by ASLint

Take me there

Diagnoses

Here is how rule engines diagnose the text contrast improvable issue for HTML element 353 of the US Digital Response page.

1. Element was excluded from scanning because it's not visible either due to being explicitly hidden or e.g. is being rendered outside of viewport, having transparency etc.

   Rule engine: ASLint (eSSENTIAL Accessibility)

   Rule: color_contrast_aaa7