Issues reported for Foundation for Individual Rights and Expression home

About the page

URL: https://www.thefire.org/
Tested 29 days ago on 2026-10-12 at 20:20 by job 261012T1913-fxq
Rule engines: 12 called, 11 able to test, violations reported by 10
Results: 608 violations, 311 violators, 49 issues
Download the full technical report (JSON)

History

191 days ago (oldest)
34 days ago
29 days ago (latest; this report)

Request a retest

Issues reported

Highest priority: 13

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 6 rule engines (Accessibility Checker + Axe + HTML CodeSniffer + Pour + QualWeb + SureA11y)
- Results: 6 violations, 1 violator
Where was the issue found?
contrast poor
- Why it matters: Content is difficult to understand
- Priority: highest
- Related WCAG standard: 1.4.3
- Reported by 4 rule engines (HTML CodeSniffer + Pour + SureA11y + WAVE)
- Results: 22 violations, 20 violators
Where was the issue found?
image not named
- Why it matters: User cannot get help to know what is in an image
- Priority: highest
- Related WCAG standard: 1.1.1
- Reported by 3 rule engines (Html Checker API + HTML CodeSniffer + WAVE)
- Results: 13 violations, 11 violators
Where was the issue found?
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: 4 violations, 4 violators
Where was the issue found?
focusable element hidden
- Why it matters: Keyboard-only user cannot navigate properly to the operable items
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + SureA11y)
- Results: 36 violations, 36 violators
Where was the issue found?
CSS bans element rotation
- Why it matters: User must read sideways after rotating a device
- Priority: highest
- Related WCAG standard: 1.3.4
- Reported by 1 rule engine (Accessibility Checker)
- Results: 3 violations, 3 violators
Where was the issue found?
audio or video caption track missing
- Why it matters: User cannot get help reading speech as text
- Priority: highest
- Related WCAG standard: 1.2.1
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
Where was the issue found?
iframe not named
- Why it matters: User cannot get help on the topic of an embedded page
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
Where was the issue found?
meta charset declared too late
- Why it matters: Browser may display incorrect text
- Priority: highest
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
Where was the issue found?
attribute value invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 2 violations, 2 violators
Where was the issue found?
attribute invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 77 violations, 27 violators
Where was the issue found?
ID empty
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 6 violations, 6 violators
Where was the issue found?
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: 47 violations, 47 violators
Where was the issue found?

High priority: 10

CSS property does not exist
- Why it matters: Page cannot be properly displayed
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
Where was the issue found?
CSS invalid
- Why it matters: Page cannot be properly displayed
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
Where was the issue found?
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 API)
- Results: 6 violations, 6 violators
Where was the issue found?
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 API)
- Results: 5 violations, 5 violators
Where was the issue found?
element closure invalid
- Why it matters: Page contains invalid code
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
Where was the issue found?
box size absolute
- Why it matters: User cannot enlarge the content of an item for readability
- Priority: high
- Related WCAG standard: 1.4.4
- Reported by 1 rule engine (QualWeb)
- Results: 81 violations, 81 violators
Where was the issue found?
font small
- Why it matters: Text is difficult to read
- Priority: high
- Related WCAG standard: 1.4
- Reported by 1 rule engine (Testaro)
- Results: 3 violations, 3 violators
Where was the issue found?
small targets too near to each other
- Why it matters: User cannot reliably choose an item to click or tap
- Priority: high
- Related WCAG standard: 2.5.8
- Reported by 1 rule engine (Testaro)
- Results: 2 violations, 2 violators
Where was the issue found?
element focusability and operability conflict
- Why it matters: Keyboard-only user cannot operate an item
- Priority: high
- Related WCAG standard: 2.1.1
- Reported by 1 rule engine (Testaro)
- Results: 23 violations, 23 violators
Where was the issue found?
hover indication poor
- Why it matters: User cannot explore the page reliably with a mouse
- Priority: high
- Related WCAG standard: 2.4
- Reported by 1 rule engine (Testaro)
- Results: 15 violations, 8 violators
Where was the issue found?

Low priority: 8

heading level skipped
- Why it matters: Helper misdescribes the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 3 rule engines (Axe + Html Checker API + Pour)
- Results: 6 violations, 4 violators
Where was the issue found?
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 2 rule engines (ASLint + Pour)
- Results: 2 violations, 1 violator
Where was the issue found?
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 (SureA11y + Testaro)
- Results: 2 violations, 1 violator
Where was the issue found?
heading structure illogical
- Why it matters: Helper misdescribes the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 6 violations, 5 violators
Where was the issue found?
cell headers ambiguous?
- Why it matters: User may be unable to get help on relationships in a table
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Results: 5 violations, 5 violators
Where was the issue found?
line height low
- Why it matters: Text is difficult to read
- Priority: low
- Related WCAG standard: 1.4.8
- Reported by 1 rule engine (Testaro)
- Results: 8 violations, 8 violators
Where was the issue found?
links named identically
- Why it matters: User cannot get help differentiating links
- Priority: low
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (Testaro)
- Results: 2 violations, 1 violator
Where was the issue found?
focus indication improvable
- Why it matters: Keyboard-only user cannot easily choose an item to operate
- Priority: low
- Related WCAG standard: 2.4.7
- Reported by 1 rule engine (Testaro)
- Results: 34 violations, 34 violators
Where was the issue found?

Lowest priority: 18

text contrast improvable
- Why it matters: Content is not easy to understand
- Priority: lowest
- Related WCAG standard: 1.4.6
- Reported by 5 rule engines (ASLint + HTML CodeSniffer + Pour + QualWeb + SureA11y)
- Results: 35 violations, 24 violators
Where was the issue found?
tab-opening link action unstated?
- Why it matters: Following a link opens a new window, possibly surprising a user
- Priority: lowest
- Related WCAG standard: 3.2.5
- Reported by 3 rule engines (ASLint + Pour + Testaro)
- Results: 17 violations, 12 violators
Where was the issue found?
role redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + Pour)
- Results: 4 violations, 2 violators
Where was the issue found?
table caption missing or empty
- Why it matters: User cannot get help on the topic of a table
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + QualWeb)
- Results: 2 violations, 2 violators
Where was the issue found?
complementary not named
- 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 1 rule engine (Accessibility Checker)
- Results: 2 violations, 2 violators
Where was the issue found?
button name not visible
- Why it matters: User cannot get help explaining a button
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (ASLint)
- Results: 5 violations, 4 violators
Where was the issue found?
link name vague
- Why it matters: User may misunderstand what a link points to
- Priority: lowest
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
Where was the issue found?
labeling risky
- Why it matters: User may misunderstand a form control
- Priority: lowest
- Related WCAG standard: 3.3.2
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
Where was the issue found?
link destination not URL
- Why it matters: Helper cannot properly explain a link to a user
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
Where was the issue found?
target small
- Why it matters: User cannot reliably choose an item to click or tap
- Priority: lowest
- Related WCAG standard: 2.5.5
- Reported by 1 rule engine (Pour)
- Results: 12 violations, 12 violators
Where was the issue found?
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 1 rule engine (Pour)
- Results: 1 violation, 1 violator
Where was the issue found?
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: 1 violation, 1 violator
Where was the issue found?
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: 46 violations, 46 violators
Where was the issue found?
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
Where was the issue found?
text distortion
- Why it matters: Text is difficult to read
- Priority: lowest
- Related WCAG standard: 3.1.5
- Reported by 1 rule engine (Testaro)
- Results: 14 violations, 14 violators
Where was the issue found?
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: 3 violations, 3 violators
Where was the issue found?
inconsistent heading, link, or button styles
- Why it matters: User cannot easily distinguish items of different types
- Priority: lowest
- Related WCAG standard: 3.2.4
- Reported by 1 rule engine (Testaro)
- Results: 5 violations, 1 violator
Where was the issue found?
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: 35 violations, 35 violators
Where was the issue found?

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 Foundation for Individual Rights and Expression home web page. Describe them and propose a plan to resolve the genuine defects.

Issues reported for Foundation for Individual Rights and Expression home

About the page

History

Issues reported

link not named

contrast poor

image not named

svg image not named

focusable element hidden

CSS bans element rotation

audio or video caption track missing

iframe not named

meta charset declared too late

attribute value invalid

attribute invalid

ID empty

Tab-focusable elements wrong

CSS property does not exist

CSS invalid

attribute obsolete

code invalid

element closure invalid

box size absolute

font small

small targets too near to each other

element focusability and operability conflict

hover indication poor

heading level skipped

not exactly 1 h1 heading

link indication poor

heading structure illogical

cell headers ambiguous?

line height low

links named identically

focus indication improvable

text contrast improvable

tab-opening link action unstated?

role redundant

table caption missing or empty

complementary not named

button name not visible

link name vague

labeling risky

link destination not URL

target small

content beyond landmarks

label location dubious

all-capital text

large visible-element count

text distortion

role assigned instead of implicit

inconsistent heading, link, or button styles

z-index not zero

What you can do

Do it yourself

Use artificial intelligence