Kilotest: Diagnoses of text contrast improvable violation by HTML element 132 on Salesforce page

Basics

About the Salesforce page

• URL: https://www.salesforce.com/
• Tested 30 days ago by job mh2 on 2026-06-20 at 13:56

About HTML element 132

• Tag name: P
• Text: Humans and agents work inside the systems that run your business. The result: faster decisions, stronger customer relationships, and non-stop growth. Now with Headless 360, every Salesforce capability is accessible from any tool, any agent, any interface — wherever work happens.
• Start tag: <p>
• XPath: /html/body/div[2]/main[1]/div[3]/section[1]/div[1]/div[1]/header[1]/div[2]/p[1]
• Bounding box: x = 0, y = 0, width = 0, height = 0

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 rule engines diagnose the text contrast improvable issue for HTML element 132 of the Salesforce page.

1. Expected color contrast ratio for small font size at least 7:1, but got ratio: 6.7:1, <code>background-color: #ffffff</code>, <code>foreground-color: #0b5cab</code>, <code>font-size: 14pt</code> (original: <code>18px</code>), <code>font-weight: 400</code>. <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_aaa7