Kilotest: Issues reported for Mozilla Foundation

About the tests

How to deal with the issues

Do it yourself

Explore the issues below in as much detail as you want. Decide which ones are actual defects. Plan and implement corrections.

Or use AI

Make Kilotest available to your AI assistant. There are step-by-step instructions for this.

After that, you can ask:

Kilotest reports defects on the Mozilla Foundation web page. Summarize them and propose a plan to resolve the genuine ones.

URL: https://www.mozilla.org/en-US/
Tested 32 days ago on 2026-09-08 at 04:02 by job 260908T0359-xmh
Summary of results:
- Rule engines:
  - Called: 12
  - Were able to test: 12
  - Reported any rule violations: 11
- Violations: 753
- Violators: 192
- Issues: 47
Download the full technical report (JSON)

History

160 days ago (oldest)
32 days ago (latest; this report)

Should Kilotest retest the page?

Issues reported

Highest priority: 13

blink element
- Why it matters: Motion-sensitive user may suffer harm
- Priority: highest
- Related WCAG standard: 2.2.2
- Reported by 6 rule engines (Accessibility Checker + Axe + Html Checker API + HTML CodeSniffer + QualWeb + WAVE)
- Violations: 6
- Violators: 1
- 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)
- Violations: 5
- Violators: 5
- 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 2 rule engines (ASLint + HTML CodeSniffer)
- Violations: 2
- Violators: 2
- Where was the issue found?
figure not named
- Why it matters: User cannot get help on the topic of a figure
- Priority: highest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (Accessibility Checker)
- Violations: 1
- Violators: 1
- Where was the issue found?
requirement invalid
- Why it matters: User may fail to get help determining whether a form item must be completed
- Priority: highest
- Related WCAG standard: 1.3.5
- Reported by 1 rule engine (ASLint)
- Violations: 3
- Violators: 3
- Where was the issue found?
element unknown
- Why it matters: Page includes an unknown element that the browser cannot process
- Priority: highest
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Violations: 1
- Violators: 1
- 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)
- Violations: 6
- Violators: 6
- Where was the issue found?
sizes attribute invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Violations: 1
- Violators: 1
- Where was the issue found?
select element invalid
- Why it matters: User cannot properly select among options
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Html Checker API)
- Violations: 2
- Violators: 2
- 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)
- Violations: 6
- Violators: 6
- Where was the issue found?
obsolete element creates non-stoppable motion
- Why it matters: Motion-sensitive user suffers harm
- Priority: highest
- Related WCAG standard: 2.2.2
- Reported by 1 rule engine (SureA11y)
- Violations: 1
- Violators: 1
- Where was the issue found?
autocomplete missing
- Why it matters: User cannot get help entering personal information in a form
- Priority: highest
- Related WCAG standard: 1.3.5
- Reported by 1 rule engine (Testaro)
- Violations: 1
- Violators: 1
- 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 1 rule engine (WAVE)
- Violations: 8
- Violators: 8
- Where was the issue found?

High priority: 11

element obsolete
- Why it matters: Page includes obsolete code that the browser may fail to process
- Priority: high
- Related WCAG standard: 4.1
- Reported by 3 rule engines (Alfa + ASLint + QualWeb)
- Violations: 12
- Violators: 12
- Where was the issue found?
form submission button missing
- Why it matters: User cannot easily submit a form
- Priority: high
- Related WCAG standard: 3.2.2
- Reported by 3 rule engines (ASLint + HTML CodeSniffer + QualWeb)
- Violations: 3
- Violators: 2
- Where was the issue found?
group not named
- Why it matters: User cannot get help on the topic of a group of form items
- Priority: high
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + HTML CodeSniffer)
- Violations: 2
- Violators: 1
- Where was the issue found?
animation long or repetitive
- Why it matters: Motion-sensitive user may suffer harm
- Priority: high
- Related WCAG standard: 2.2.2
- Reported by 2 rule engines (ASLint + Pour)
- Violations: 13
- Violators: 2
- Where was the issue found?
code obsolete
- Why it matters: Page contains code that is no longer standard
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Accessibility Checker)
- Violations: 1
- Violators: 1
- Where was the issue found?
forms not distinctly named
- Why it matters: User cannot get help on how some of the page is organized
- Priority: high
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (Accessibility Checker)
- Violations: 2
- Violators: 2
- Where was the issue found?
negative text-indent
- Why it matters: Helper may hide content from a user
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (ASLint)
- Violations: 18
- Violators: 18
- 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)
- Violations: 1
- Violators: 1
- 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)
- Violations: 14
- Violators: 14
- 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)
- Violations: 24
- Violators: 24
- 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)
- Violations: 1
- Violators: 1
- Where was the issue found?

Low priority: 9

legend missing
- Why it matters: User cannot get help on the topic of a group of form items
- Priority: low
- Related WCAG standard: 4.1.2
- Reported by 4 rule engines (Accessibility Checker + ASLint + HTML CodeSniffer + QualWeb)
- Violations: 4
- Violators: 1
- 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 2 rule engines (ASLint + HTML CodeSniffer)
- Violations: 3
- Violators: 2
- Where was the issue found?
assertive region not atomic
- Why it matters: User may be unable to get help on what content has changed
- Priority: low
- Related WCAG standard: 4.1.3
- Reported by 1 rule engine (Alfa)
- Violations: 1
- Violators: 1
- Where was the issue found?
font size absolute
- Why it matters: User cannot adjust the text size for readability
- Priority: low
- Related WCAG standard: 1.4.4
- Reported by 1 rule engine (Alfa)
- Violations: 2
- Violators: 2
- Where was the issue found?
banner child of landmark
- Why it matters: User cannot get help on how some of the page is organized
- Priority: low
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (QualWeb)
- Violations: 1
- Violators: 1
- 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)
- Violations: 1
- Violators: 1
- Where was the issue found?
semantic properties represented with styles
- Why it matters: User cannot get help to fully understand the text
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- Violations: 9
- Violators: 9
- Where was the issue found?
page content moves spontaneously
- Why it matters: Motion-sensitive user may suffer harm
- Priority: low
- Related WCAG standard: 2.2.2
- Reported by 1 rule engine (Testaro)
- Violations: 1
- Violators: 1
- 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)
- Violations: 71
- Violators: 71
- Where was the issue found?

Lowest priority: 14

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)
- Violations: 18
- Violators: 12
- 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 2 rule engines (Alfa + Pour)
- Violations: 84
- Violators: 84
- Where was the issue found?
text contrast improvable
- Why it matters: Content is not easy to understand
- Priority: lowest
- Related WCAG standard: 1.4.6
- Reported by 2 rule engines (ASLint + QualWeb)
- Violations: 396
- Violators: 32
- Where was the issue found?
role redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- Violations: 1
- Violators: 1
- 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
- Priority: lowest
- Related WCAG standard: 1.4.10
- Reported by 1 rule engine (ASLint)
- Violations: 1
- Violators: 1
- Where was the issue found?
image name redundant
- Why it matters: Helper repeats the explanation of an image
- Priority: lowest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (Pour)
- Violations: 1
- Violators: 1
- Where was the issue found?
text contrast not testable
- Why it matters: Text may be difficult to read
- Priority: lowest
- Related WCAG standard: 1.4.3
- Reported by 1 rule engine (QualWeb)
- Violations: 4
- Violators: 4
- 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)
- Violations: 1
- Violators: 1
- Where was the issue found?
hr misused
- Why it matters: User cannot get help on the nature of segments of the page
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- Violations: 2
- Violators: 2
- Where was the issue found?
double br use dubious
- Why it matters: User may be unable to get help to fully understand the text
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- Violations: 1
- Violators: 1
- 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)
- Violations: 4
- Violators: 4
- 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)
- Violations: 5
- Violators: 1
- 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)
- Violations: 6
- Violators: 6
- Where was the issue found?
hovering changes content
- Why it matters: User cannot explore the page reliably with a mouse
- Priority: lowest
- Related WCAG standard: 3.2.5
- Reported by 1 rule engine (Testaro)
- Violations: 2
- Violators: 2
- Where was the issue found?

Kilotest: Issues reported for Mozilla Foundation

About the tests

Do it yourself

Or use AI

History

Issues reported

blink element

svg image not named

iframe not named

figure not named

requirement invalid

element unknown

attribute value invalid

sizes attribute invalid

select element invalid

attribute invalid

obsolete element creates non-stoppable motion

autocomplete missing

contrast poor

element obsolete

form submission button missing

group not named

animation long or repetitive

code obsolete

forms not distinctly named

negative text-indent

code invalid

box size absolute

small targets too near to each other

hover indication poor

legend missing

heading structure illogical

assertive region not atomic

font size absolute

banner child of landmark

links named identically

semantic properties represented with styles

page content moves spontaneously

focus indication improvable

tab-opening link action unstated?

target small

text contrast improvable

role redundant

position sticky

image name redundant

text contrast not testable

large visible-element count

hr misused

double br use dubious

role assigned instead of implicit

inconsistent heading, link, or button styles

z-index not zero

hovering changes content