Kilotest: Issues reported for Freedom of the Press Foundation

About the Freedom of the Press Foundation page

• URL: https://freedom.press/
• Tested by job e71 on 2026-04-02 at 14:24

Issues reported

Summary

11 tools reported issues (Accessibility Checker + Alfa + ASLint + Axe + Editoria11y + Html Checker API + HTML CodeSniffer + QualWeb + Testaro + WallyAX + WAVE)

52 issues were reported (12 highest, 7 high, 7 low, 26 lowest priority)

Details

Highest priority

image not named

• Why it matters: User cannot get help to know what is in an image
• Related WCAG standard: 1.1.1
• Reported by 7 tools (Accessibility Checker + Alfa + Axe + Html Checker API + QualWeb + WallyAX + WAVE)
• 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 5 tools (Alfa + ASLint + Html Checker API + HTML CodeSniffer + WallyAX)
• Where was the issue found?

attribute invalid

• Why it matters: Item behaves improperly
• Related WCAG standard: 1.3.1
• Reported by 3 tools (Accessibility Checker + Axe + Html Checker API)
• Where was the issue found?

aria attribute invalid

• Why it matters: Item behavior violates user expectations
• Related WCAG standard: 4.1.2
• Reported by 3 tools (Alfa + QualWeb + WallyAX)
• 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 2 tools (Accessibility Checker + WallyAX)
• Where was the issue found?

contrast poor

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

label reference invalid

• Why it matters: User cannot get help understanding an item in a form
• Related WCAG standard: 1.3.1
• Reported by 1 tool (ASLint)
• Where was the issue found?

attribute value 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?

autocomplete missing

• Why it matters: User cannot get help entering personal information in a form
• Related WCAG standard: 1.3.5
• Reported by 1 tool (Testaro)
• 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?

link not named

• Why it matters: User cannot get help understanding what a link points to
• Related WCAG standard: 2.4.4
• Reported by 1 tool (WallyAX)
• Where was the issue found?

aria reference invalid

• Why it matters: Item behavior violates user expectations
• Related WCAG standard: 1.3.1
• Reported by 1 tool (WAVE)
• Where was the issue found?

High priority

code obsolete

• Why it matters: Document contains code that is no longer standard
• Related WCAG standard: 4.1
• Reported by 1 tool (Accessibility Checker)
• Where was the issue found?

forms not distinctly named

• Why it matters: User cannot get help on how some of the document is organized
• Related WCAG standard: 1.3.6
• Reported by 1 tool (Accessibility Checker)
• 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?

code invalid

• Why it matters: Invalid code in the document may prevent a helper from working
• Related WCAG standard: 4.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

element obsolete

• Why it matters: Document includes obsolete code that the browser may fail to process
• Related WCAG standard: 4.1
• Reported by 1 tool (QualWeb)
• 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?

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

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 2 tools (Editoria11y + WAVE)
• 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?

semantic properties represented with styles

• Why it matters: User cannot get help to fully understand the text
• Related WCAG standard: 1.3.1
• Reported by 2 tools (Testaro + WallyAX)
• Where was the issue found?

link href missing

• 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?

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?

page content moves spontaneously

• Why it matters: Motion-sensitive user may suffer harm
• Related WCAG standard: 2.2.2
• Reported by 1 tool (Testaro)
• 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 4 tools (Alfa + ASLint + Axe + HTML CodeSniffer)
• 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?

role redundant

• Why it matters: Document includes unnecessary code
• Related WCAG standard: 4.1.2
• Reported by 2 tools (Accessibility Checker + Html Checker API)
• 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?

image dubiously named

• Why it matters: Helper may describe an image inadequately
• Related WCAG standard: 1.1.1
• Reported by 2 tools (ASLint + WAVE)
• 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?

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?

fieldset missing?

• Why it matters: User may be unable to get help recognizing a group of related form items
• Related WCAG standard: 1.3.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?

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?

links dubiously share name

• Why it matters: User may be unable to get help differentiating links
• Related WCAG standard: 2.4.4
• Reported by 1 tool (Axe)
• 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?

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?

aria-label on non-labelable role

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

section heading missing

• Why it matters: User cannot understand the topic of a part of the document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• 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?

text contrast not testable

• Why it matters: Text may be difficult to read
• Related WCAG standard: 1.4.3
• Reported by 1 tool (HTML CodeSniffer)
• 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 (Testaro)
• Where was the issue found?

large visible-element count

• Why it matters: User cannot easily find items in the document
• Related WCAG standard: 2.4
• Reported by 1 tool (Testaro)
• Where was the issue found?

text distortion

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

role assigned instead of implicit

• Why it matters: User may misunderstand the purpose of an item
• Related WCAG standard: 4.1.2
• Reported by 1 tool (Testaro)
• 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?

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?

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 1 tool (WallyAX)
• Where was the issue found?

heading-like styles dubious

• Why it matters: User may be unable to understand the topic of a part of the document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (WAVE)
• Where was the issue found?

noscript element not equivalent?

• Why it matters: User who has disabled JavaScript may be denied some content
• Related WCAG standard: 4.1
• Reported by 1 tool (WAVE)
• Where was the issue found?