Kilotest: Issues reported for WebAIM

About the WebAIM page

• URL: https://webaim.org/
• Tested by job fgt on 2026-04-02 at 14:55

Issues reported

Summary

8 tools reported issues (Alfa + ASLint + Axe + Html Checker API + HTML CodeSniffer + QualWeb + Testaro + WallyAX)

25 issues were reported (4 highest, 3 high, 6 low, 12 lowest priority)

Details

Highest priority

contrast poor

• Why it matters: Content is difficult to understand
• Related WCAG standard: 1.4.3
• Reported by 1 tool (Axe)
• Where was the issue found?

image button not named

• Why it matters: User cannot get help understanding an image used as a button
• Related WCAG standard: 1.1.1
• Reported by 1 tool (QualWeb)
• Where was the issue found?

focus indication poor

• Why it matters: Keyboard-only user cannot choose an item to operate
• Related WCAG standard: 2.4.7
• Reported by 1 tool (Testaro)
• Where was the issue found?

control not named

• Why it matters: User cannot get help on how to operate a form item
• Related WCAG standard: 4.1.2
• Reported by 1 tool (WallyAX)
• Where was the issue found?

High priority

h1 not 1st heading

• Why it matters: User cannot understand the topic of the document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Alfa)
• Where was the issue found?

element beyond display when focused

• Why it matters: Keyboard-only user cannot navigate properly to the operable items
• Related WCAG standard: 1.4.10
• Reported by 1 tool (Testaro)
• Where was the issue found?

hover indication poor

• Why it matters: User cannot explore the document reliably with a mouse
• Related WCAG standard: 3.3.2
• Reported by 1 tool (Testaro)
• Where was the issue found?

Low priority

heading structure illogical

• Why it matters: Helper misdescribes the document
• Related WCAG standard: 1.3.1
• Reported by 2 tools (ASLint + HTML CodeSniffer)
• Where was the issue found?

links named identically

• Why it matters: User cannot get help differentiating links
• Related WCAG standard: 2.4.4
• Reported by 2 tools (QualWeb + Testaro)
• Where was the issue found?

line height low

• Why it matters: Text is difficult to read
• Related WCAG standard: 1.4.8
• Reported by 1 tool (Testaro)
• Where was the issue found?

link indication poor

• Why it matters: User cannot differentiate a link from plain text
• Related WCAG standard: 1.3.3
• Reported by 1 tool (Testaro)
• Where was the issue found?

primary heading not h1

• Why it matters: User cannot understand the topic of the document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (WallyAX)
• Where was the issue found?

heading names repeated

• Why it matters: User cannot differentiate parts of the document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (WallyAX)
• Where was the issue found?

Lowest priority

all-italic text

• Why it matters: Text is difficult to read
• Related WCAG standard: 3.1.5
• Reported by 3 tools (Alfa + ASLint + Testaro)
• Where was the issue found?

text contrast improvable

• Why it matters: Content is not easy to understand
• Related WCAG standard: 1.4.6
• Reported by 3 tools (Alfa + Axe + HTML CodeSniffer)
• Where was the issue found?

text contrast not testable

• Why it matters: Text may be difficult to read
• Related WCAG standard: 1.4.3
• Reported by 2 tools (Alfa + HTML CodeSniffer)
• Where was the issue found?

target small

• Why it matters: User cannot reliably choose an item to click or tap
• Related WCAG standard: 2.5.5
• Reported by 2 tools (Alfa + Testaro)
• Where was the issue found?

item makes testing inconclusive

• Why it matters: Item prevents a conclusive accessibility test
• Related WCAG standard: 4.1
• Reported by 1 tool (Alfa)
• Where was the issue found?

labeling risky

• Why it matters: User may misunderstand a form control
• Related WCAG standard: 3.3.2
• Reported by 1 tool (ASLint)
• Where was the issue found?

image dubiously named

• Why it matters: Helper may describe an image inadequately
• Related WCAG standard: 1.1.1
• Reported by 1 tool (ASLint)
• Where was the issue found?

type redundant

• Why it matters: Document includes unnecessary code
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

label location dubious

• Why it matters: User may fail to notice the explanation of an item in a form
• Related WCAG standard: 3.3.2
• Reported by 1 tool (QualWeb)
• Where was the issue found?

inconsistent heading, link, or button styles

• Why it matters: User cannot easily distinguish items of different types
• Related WCAG standard: 3.2.4
• Reported by 1 tool (Testaro)
• Where was the issue found?

title attribute invalid

• Why it matters: User gets too little, too much, or repeated help explaining an item
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Testaro)
• Where was the issue found?

z-index not zero

• Why it matters: User cannot predict the effect of clicking
• Related WCAG standard: 1.4
• Reported by 1 tool (Testaro)
• Where was the issue found?