Kilotest: Issues reported for International Consortium of Investigative Journalists

About the International Consortium of Investigative Journalists page

• URL: https://www.icij.org/
• Tested by job zzl on 2026-04-03 at 03:59
• Page prevented testing by 3 tools (Testaro + WallyAX + WAVE)

Issues reported

Summary

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

48 issues were reported (12 highest, 9 high, 8 low, 19 lowest priority)

Details

Highest priority

link not named

• Why it matters: User cannot get help understanding what a link points to
• Related WCAG standard: 2.4.4
• Reported by 6 tools (Accessibility Checker + Alfa + Axe + Editoria11y + HTML CodeSniffer + QualWeb)
• Where was the issue found?

ID not unique

• Why it matters: User may be pointed to the wrong item
• Related WCAG standard: 4.1.1
• Reported by 4 tools (Alfa + ASLint + Html Checker API + HTML CodeSniffer)
• Where was the issue found?

button not named

• Why it matters: User cannot get help explaining a button
• Related WCAG standard: 4.1.2
• Reported by 4 tools (Alfa + Axe + HTML CodeSniffer + QualWeb)
• Where was the issue found?

contrast poor

• Why it matters: Content is difficult to understand
• Related WCAG standard: 1.4.3
• Reported by 3 tools (Accessibility Checker + Alfa + Axe)
• Where was the issue found?

image link not named

• Why it matters: User cannot get help understanding what a link points to
• Related WCAG standard: 2.4.4
• Reported by 3 tools (ASLint + Editoria11y + QualWeb)
• Where was the issue found?

svg image not named

• Why it matters: User cannot get help understanding an image
• Related WCAG standard: 1.1.1
• Reported by 2 tools (Accessibility Checker + ASLint)
• 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 (Accessibility Checker)
• Where was the issue found?

figure not named

• Why it matters: User cannot get help on the topic of a figure
• Related WCAG standard: 1.1.1
• Reported by 1 tool (Accessibility Checker)
• Where was the issue found?

no role-required name

• Why it matters: User cannot get help understanding an item
• Related WCAG standard: 4.1.2
• Reported by 1 tool (Accessibility Checker)
• Where was the issue found?

attribute invalid

• Why it matters: Item behaves improperly
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

parent invalid

• Why it matters: User cannot properly operate an item
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

heading image not named

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

High priority

heading empty

• Why it matters: User cannot get help on the topic of a part of the document
• Related WCAG standard: 2.4.6
• Reported by 6 tools (Accessibility Checker + Alfa + ASLint + Axe + Html Checker API + QualWeb)
• Where was the issue found?

group not named

• Why it matters: User cannot get help on the topic of a group of form items
• Related WCAG standard: 4.1.2
• Reported by 1 tool (Accessibility Checker)
• Where was the issue found?

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?

label empty

• Why it matters: User cannot get help on the topics of form items
• Related WCAG standard: 1.3.1
• Reported by 1 tool (ASLint)
• Where was the issue found?

meta invalid

• Why it matters: Document fails to include needed data
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

CSS invalid

• Why it matters: Document cannot be properly displayed
• Related WCAG standard: 4.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

element closure invalid

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

attribute obsolete

• Why it matters: Document includes obsolete code that the browser may fail to process
• Related WCAG standard: 4.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

box size absolute

• Why it matters: User cannot enlarge the content of an item for readability
• Related WCAG standard: 1.4.4
• Reported by 1 tool (QualWeb)
• Where was the issue found?

Low priority

heading level skipped

• Why it matters: Helper misdescribes the document
• Related WCAG standard: 1.3.1
• Reported by 4 tools (Alfa + Axe + Editoria11y + Html Checker API)
• Where was the issue found?

legend missing

• Why it matters: User cannot get help on the topic of a group of form items
• Related WCAG standard: 4.1.2
• Reported by 3 tools (Accessibility Checker + ASLint + QualWeb)
• Where was the issue found?

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?

font size absolute

• Why it matters: User cannot adjust the text size for readability
• Related WCAG standard: 1.4.4
• Reported by 1 tool (Alfa)
• Where was the issue found?

heading heads nothing

• Why it matters: Helper misdescribes the document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Alfa)
• Where was the issue found?

image alt long

• Why it matters: Helper gives a user an overly verbose explanation of an image
• Related WCAG standard: 1.1.1
• Reported by 1 tool (Editoria11y)
• 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 1 tool (QualWeb)
• Where was the issue found?

links not grouped as nav

• Why it matters: User cannot get help identifying links as a navigation tool
• Related WCAG standard: 1.3.1
• Reported by 1 tool (QualWeb)
• Where was the issue found?

Lowest priority

text contrast improvable

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

content beyond landmarks

• Why it matters: User cannot get help on how some of the document is organized
• Related WCAG standard: 1.3.6
• Reported by 3 tools (Accessibility Checker + Alfa + Axe)
• 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 3 tools (Alfa + HTML CodeSniffer + QualWeb)
• Where was the issue found?

tab-opening link action unstated?

• Why it matters: Following a link opens a new window, possibly surprising a user
• Related WCAG standard: 3.2.5
• Reported by 2 tools (ASLint + HTML CodeSniffer)
• Where was the issue found?

position sticky

• Why it matters: User may be unable to see needed content or may be forced to scroll in both dimensions
• Related WCAG standard: 1.4.10
• Reported by 2 tools (ASLint + 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 1 tool (Alfa)
• Where was the issue found?

button name not visible

• Why it matters: User cannot get help explaining a button
• Related WCAG standard: 4.1.2
• Reported by 1 tool (ASLint)
• Where was the issue found?

custom button keyboard-inoperable?

• Why it matters: Custom item may prevent a keyboard-only user from operating it
• Related WCAG standard: 2.1.1
• Reported by 1 tool (ASLint)
• Where was the issue found?

link name vague

• Why it matters: User may misunderstand what a link points to
• Related WCAG standard: 2.4.4
• Reported by 1 tool (ASLint)
• Where was the issue found?

link destination not URL

• Why it matters: Helper cannot properly explain a link to a user
• Related WCAG standard: 1.3.1
• 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?

image name contains image

• Why it matters: User is redundantly told an image is an image
• Related WCAG standard: 1.1.1
• Reported by 1 tool (Editoria11y)
• Where was the issue found?

all-capital text

• Why it matters: Text is difficult to read
• Related WCAG standard: 3.1.5
• Reported by 1 tool (Editoria11y)
• 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?

image dubiously marked decorative

• Why it matters: Helper ignores an image that is apparently informative
• Related WCAG standard: 1.1.1
• Reported by 1 tool (HTML CodeSniffer)
• Where was the issue found?

nav links better as list?

• Why it matters: User cannot get help recognizing a list of navigation links
• Related WCAG standard: 1.3.1
• Reported by 1 tool (HTML CodeSniffer)
• Where was the issue found?

overflow hidden?

• Why it matters: User may be unable to enlarge the text for readability
• Related WCAG standard: 1.4.4
• Reported by 1 tool (QualWeb)
• Where was the issue found?

image link text suspect

• Why it matters: Keyboard-only user may misunderstand the effect of following a link
• Related WCAG standard: 2.4.4
• Reported by 1 tool (QualWeb)
• 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?