Kilotest: Issues reported for Foundation for Individual Rights and Expression

About the Foundation for Individual Rights and Expression page

• URL: https://www.fire.org/
• Tested by job br1 on 2026-04-05 at 23:06
• Page prevented testing by 1 tool (Alfa)

Issues reported

Summary

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

81 issues were reported (25 highest, 14 high, 14 low, 28 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 5 tools (Accessibility Checker + Axe + HTML CodeSniffer + QualWeb + WallyAX)
• Where was the issue found?

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 3 tools (Html Checker API + WallyAX + WAVE)
• 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?

focusable element hidden

• Why it matters: Keyboard-only user cannot navigate properly to the operable items
• Related WCAG standard: 4.1.2
• Reported by 2 tools (Accessibility Checker + Axe)
• Where was the issue found?

audio track missing

• Why it matters: User cannot get help reading speech as text
• Related WCAG standard: 1.2.1
• Reported by 2 tools (ASLint + QualWeb)
• Where was the issue found?

video not named

• Why it matters: User cannot get help reading video content as text
• Related WCAG standard: 1.2.2
• Reported by 2 tools (Axe + QualWeb)
• 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?

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

CSS bans element rotation

• Why it matters: User must read sideways after rotating a device
• Related WCAG standard: 1.3.4
• Reported by 1 tool (Accessibility Checker)
• Where was the issue found?

control label invisible

• Why it matters: User cannot understand how to operate a form item
• Related WCAG standard: 2.4.6
• Reported by 1 tool (ASLint)
• Where was the issue found?

requirement invalid

• Why it matters: User may fail to get help determining whether a form item must be completed
• Related WCAG standard: 1.3.5
• Reported by 1 tool (ASLint)
• Where was the issue found?

audio or video caption track missing

• Why it matters: User cannot get help reading speech as text
• Related WCAG standard: 1.2.1
• Reported by 1 tool (ASLint)
• Where was the issue found?

video alternative missing

• Why it matters: User cannot get help consuming a video recording as text or speech
• Related WCAG standard: 1.2.1
• Reported by 1 tool (ASLint)
• Where was the issue found?

iframe not named

• Why it matters: User cannot get help on the topic of an embedded document
• Related WCAG standard: 4.1.2
• Reported by 1 tool (ASLint)
• Where was the issue found?

CSS bans page rotation

• Why it matters: User must read sideways after rotating a device
• Related WCAG standard: 1.3.4
• 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?

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?

aria attribute invalid

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

video transcript missing

• Why it matters: User cannot get help reading video content as text
• Related WCAG standard: 1.2.2
• Reported by 1 tool (QualWeb)
• Where was the issue found?

video audio track missing

• Why it matters: User cannot get help hearing video content as speech
• Related WCAG standard: 1.2.1
• Reported by 1 tool (QualWeb)
• Where was the issue found?

video audio description missing

• Why it matters: User cannot get help hearing video content as speech
• Related WCAG standard: 1.2.1
• Reported by 1 tool (QualWeb)
• 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?

Tab-focusable elements wrong

• Why it matters: Item selections by a keyboard-only user are useless or impossible
• Related WCAG standard: 2.1.1
• 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?

object not named

• Why it matters: User cannot get help explaining a custom item
• Related WCAG standard: 1.1.1
• Reported by 1 tool (WAVE)
• Where was the issue found?

High priority

attribute obsolete

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

font small

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

visible label not in name

• Why it matters: User cannot get help choosing a form control to operate
• Related WCAG standard: 2.5.3
• Reported by 2 tools (HTML CodeSniffer + QualWeb)
• Where was the issue found?

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?

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

landmarks 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 (Axe)
• 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?

autocomplete invalid

• Why it matters: User cannot get help entering personal information in a form item
• Related WCAG standard: 1.3.5
• 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 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?

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?

element focusability and operability conflict

• Why it matters: Keyboard-only user cannot operate an item
• Related WCAG standard: 2.1.1
• 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

multiple banners

• 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 + Axe + WallyAX)
• 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?

not exactly 1 h1 heading

• Why it matters: User cannot understand the topic of the document
• Related WCAG standard: 1.3.1
• Reported by 2 tools (ASLint + WAVE)
• Where was the issue found?

heading level skipped

• Why it matters: Helper misdescribes the document
• Related WCAG standard: 1.3.1
• Reported by 2 tools (Html Checker API + 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?

autoplay

• Why it matters: Motion- or noise-sensitive user may suffer harm
• Related WCAG standard: 1.4.2
• Reported by 1 tool (ASLint)
• Where was the issue found?

aside child of landmark

• 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 (Axe)
• 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?

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?

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

adjacent links not combined

• Why it matters: Keyboard-only user expends extra effort to skip a link
• Related WCAG standard: 2.4.4
• Reported by 1 tool (WAVE)
• 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 3 tools (ASLint + Axe + HTML CodeSniffer)
• 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 3 tools (ASLint + HTML CodeSniffer + Testaro)
• 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?

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

all-italic text

• Why it matters: Text is difficult to read
• Related WCAG standard: 3.1.5
• Reported by 2 tools (ASLint + 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 2 tools (HTML CodeSniffer + WallyAX)
• Where was the issue found?

complementary not 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?

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 1 tool (Accessibility Checker)
• 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?

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?

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?

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?

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

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?

container size unit not percentage

• Why it matters: User may be unable to see all of an item without scrolling in both dimensions
• Related WCAG standard: 1.4.10
• Reported by 1 tool (QualWeb)
• 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?

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

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?

audio or video alternatives missing?

• Why it matters: User may be unable to get help reading video content as text
• Related WCAG standard: 1.2.2
• Reported by 1 tool (WAVE)
• Where was the issue found?