Issues reported for Salesforce known issues
About the page
- URL: https://help.salesforce.com/s/issues
- Tested 169 days ago on 2026-05-26 at 03:57 by job
260526T0354-54m - Rule engines: 10 called, 9 able to test, violations reported by 8
- Results: 2549 violations, 179 violators, 49 issues
- Download the full technical report (JSON)
History
This is the only available report about the page.
Issues reported
Highest priority: 18
-
control not named
- Why it matters: User cannot get help on how to operate a form item
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 5 rule engines (Accessibility Checker + Axe + HTML CodeSniffer + QualWeb + WAVE)
- Results: 20 violations, 2 violators
-
svg image not named
- Why it matters: User cannot get help understanding an image
- Priority: highest
- Related WCAG standard: 1.1.1
- Reported by 2 rule engines (Accessibility Checker + ASLint)
- Results: 18 violations, 4 violators
-
contrast poor
- Why it matters: Content is difficult to understand
- Priority: highest
- Related WCAG standard: 1.4.3
- Reported by 2 rule engines (Accessibility Checker + Axe)
- Results: 4 violations, 1 violator
-
attribute invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (Accessibility Checker + Html Checker)
- Results: 351 violations, 2 violators
-
aria attribute missing
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Axe + QualWeb)
- Results: 9 violations, 1 violator
-
button not named
- Why it matters: User cannot get help explaining a button
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Axe + QualWeb)
- Results: 10 violations, 1 violator
-
aria-controls or -owns invalid
- Why it matters: Keyboard-only user cannot reach an item
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Accessibility Checker)
- Results: 4 violations, 1 violator
-
region not named
- Why it matters: User cannot get help surveying the parts of the page
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- Results: 1 violation, 1 violator
-
label reference invalid
- Why it matters: User cannot get help understanding an item in a form
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
-
aria attribute invalid
- Why it matters: Item behavior violates user expectations
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Axe)
- Results: 12 violations, 1 violator
-
attribute value invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Results: 1 violation, 1 violator
-
ID empty
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Results: 3 violations, 3 violators
-
parent invalid
- Why it matters: User cannot properly operate an item
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Results: 3 violations, 1 violator
-
label referent ineligible
- Why it matters: User cannot get help understanding an item in a form
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Results: 3 violations, 1 violator
-
input not named
- Why it matters: User cannot get help on what information to enter in a form item
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 1 violation, 1 violator
-
link not named
- Why it matters: User cannot get help understanding what a link points to
- Priority: highest
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (QualWeb)
- Results: 2 violations, 1 violator
-
image link not named
- Why it matters: User cannot get help understanding what a link points to
- Priority: highest
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
-
Tab-focusable elements wrong
- Why it matters: Item selections by a keyboard-only user are useless or impossible
- Priority: highest
- Related WCAG standard: 2.1.1
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
High priority: 10
-
role invalid
- Why it matters: User cannot get help on the nature of an item
- Priority: high
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + Axe)
- Results: 2 violations, 1 violator
-
form submission button missing
- Why it matters: User cannot easily submit a form
- Priority: high
- Related WCAG standard: 3.2.2
- Reported by 2 rule engines (HTML CodeSniffer + QualWeb)
- Results: 2 violations, 1 violator
-
code obsolete
- Why it matters: Page contains code that is no longer standard
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Accessibility Checker)
- Results: 3 violations, 3 violators
-
CSS invalid
- Why it matters: Page cannot be properly displayed
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- Results: 1837 violations, 2 violators
-
attribute obsolete
- Why it matters: Page includes obsolete code that the browser may fail to process
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- Results: 7 violations, 4 violators
-
code invalid
- Why it matters: Invalid code in the page may prevent a helper from working
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- Results: 4 violations, 4 violators
-
stylesheet prohibited
- Why it matters: Browser displays the page improperly
- Priority: high
- Related WCAG standard: 1.4
- Reported by 1 rule engine (Html Checker)
- Results: 9 violations, 9 violators
-
script prohibited
- Why it matters: Browser processes the page improperly
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- Results: 20 violations, 20 violators
-
image prohibited
- Why it matters: Browser fails to display an image
- Priority: high
- Related WCAG standard: 1.4
- Reported by 1 rule engine (Html Checker)
- Results: 8 violations, 1 violator
-
heading empty
- Why it matters: User cannot get help on the topic of a part of the page
- Priority: high
- Related WCAG standard: 2.4.6
- Reported by 1 rule engine (QualWeb)
- Results: 3 violations, 1 violator
Low priority: 5
-
not exactly 1 h1 heading
- Why it matters: User cannot understand the topic of the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 3 rule engines (Axe + Html Checker + WAVE)
- Results: 3 violations, 2 violators
-
link indication poor
- Why it matters: User cannot differentiate a link from plain text
- Priority: low
- Related WCAG standard: 1.3.3
- Reported by 2 rule engines (Axe + Testaro)
- Results: 2 violations, 2 violators
-
main missing
- Why it matters: User cannot get help on how some of the page is organized
- Priority: low
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (Axe)
- Results: 1 violation, 1 violator
-
link href missing
- Why it matters: Helper cannot properly explain a link to a user
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Results: 1 violation, 1 violator
-
decorative element exposed
- Why it matters: Helper alerts a user to an uninformative image
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
Lowest priority: 16
-
content beyond landmarks
- Why it matters: User cannot get help on how some of the page is organized
- Priority: lowest
- Related WCAG standard: 1.3.6
- Reported by 2 rule engines (Accessibility Checker + Axe)
- Results: 10 violations, 1 violator
-
role redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + Html Checker)
- Results: 8 violations, 1 violator
-
text contrast improvable
- Why it matters: Content is not easy to understand
- Priority: lowest
- Related WCAG standard: 1.4.6
- Reported by 2 rule engines (Axe + QualWeb)
- Results: 6 violations, 1 violator
-
text contrast not testable
- Why it matters: Text may be difficult to read
- Priority: lowest
- Related WCAG standard: 1.4.3
- Reported by 2 rule engines (HTML CodeSniffer + QualWeb)
- Results: 4 violations, 3 violators
-
image name redundant
- Why it matters: Helper repeats the explanation of an image
- Priority: lowest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (Accessibility Checker)
- Results: 1 violation, 1 violator
-
type redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Results: 68 violations, 68 violators
-
section heading missing
- Why it matters: User cannot understand the topic of a part of the page
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Results: 1 violation, 1 violator
-
position sticky
- Why it matters: User may be unable to see needed content or may be forced to scroll in both dimensions
- Priority: lowest
- Related WCAG standard: 1.4.10
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 5 violations, 5 violators
-
overflow hidden?
- Why it matters: User may be unable to enlarge the text for readability
- Priority: lowest
- Related WCAG standard: 1.4.4
- Reported by 1 rule engine (QualWeb)
- Results: 12 violations, 1 violator
-
image link text suspect
- Why it matters: Keyboard-only user may misunderstand the effect of following a link
- Priority: lowest
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (QualWeb)
- Results: 2 violations, 1 violator
-
label location dubious
- Why it matters: User may fail to notice the explanation of an item in a form
- Priority: lowest
- Related WCAG standard: 3.3.2
- Reported by 1 rule engine (QualWeb)
- Results: 5 violations, 1 violator
-
all-capital text
- Why it matters: Text is difficult to read
- Priority: lowest
- Related WCAG standard: 3.1.5
- Reported by 1 rule engine (Testaro)
- Results: 4 violations, 4 violators
-
large visible-element count
- Why it matters: User cannot easily find items in the page
- Priority: lowest
- Related WCAG standard: 2.4
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
-
role assigned instead of implicit
- Why it matters: User may misunderstand the purpose of an item
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Testaro)
- Results: 66 violations, 56 violators
-
title attribute invalid
- Why it matters: User gets too little, too much, or repeated help explaining an item
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
-
z-index not zero
- Why it matters: User cannot predict the effect of clicking
- Priority: lowest
- Related WCAG standard: 1.4
- Reported by 1 rule engine (Testaro)
- Results: 7 violations, 7 violators
What you can do
Choose how to address these issues:
Do it yourself
Explore the issues, following the links above. Decide which issues are actual defects. Plan and implement corrections. Then retest the page.
Use artificial intelligence
Make Kilotest available to an AI assistant. Then give it a prompt like this:
Kilotest reports issues on the Salesforce known issues web page. Describe them and propose a plan to resolve the genuine defects.