Kilotest: Diagnoses of text contrast improvable violation by HTML element 502 on New_Public page

Basics

About the New_Public page

• URL: https://newpublic.org/
• Tested 20 days ago by job 40e on 2026-05-13 at 05:28

About HTML element 502

• Tag name: DIV
• Text: The Washington Post … Read the article
• Start tag: <div class="swiper-slide Press__slide">
• XPath: /html/body/div[1]/div[1]/div[1]/div[1]/div[4]/div[2]/div[1]/div[1]/div[4]
• Bounding box: x = 2207, y = 5605, width = 460, height = 284

Take me there

About the text contrast improvable issue

• Why it matters: Content is not easy to understand
• Priority: lowest
• Related WCAG standard: 1.4.6

Diagnoses

Here is how tools diagnose the text contrast improvable issue for HTML element 502 of the New_Public page.

1. Expected color contrast ratio for large font size at least 4.5:1, but got ratio: 1.51:1,<code>background-color: #fcc8a6</code>, <code>foreground-color: #ffffff</code>, <code>font-size: 24pt</code> (original: <code>32px</code>), <code>font-weight: 600</code>.%6 <small>Note:</small> The element is possibly visually hidden and that state might be temporary. For example the lazy loading technique can be used and the element will be visible at some point.

   Tool: ASLint (eSSENTIAL Accessibility)

   Rule: color_contrast_aaa4

2. Expected color contrast ratio for large font size at least 4.5:1, but got ratio: 1.51:1,<code>background-color: #fcc8a6</code>, <code>foreground-color: #ffffff</code>, <code>font-size: 18pt</code> (original: <code>24px</code>), <code>font-weight: 500</code>.%6 <small>Note:</small> The element is possibly visually hidden and that state might be temporary. For example the lazy loading technique can be used and the element will be visible at some point.

   Tool: ASLint (eSSENTIAL Accessibility)

   Rule: color_contrast_aaa4