Kilotest: Issues reported for Mozilla Foundation

About the Mozilla Foundation page

• URL: https://www.mozilla.org/en-US/
• Tested by job 6v4 on 2026-04-03 at 03:56

Issues reported

Summary

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

61 issues were reported (13 highest, 12 high, 13 low, 23 lowest priority)

Details

Highest priority

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?

blink element

• Why it matters: Motion-sensitive user may suffer harm
• Related WCAG standard: 2.2.2
• Reported by 2 tools (ASLint + 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 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?

aria attribute invalid

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

select element invalid

• Why it matters: User cannot properly select among options
• Related WCAG standard: 4.1.2
• 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?

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?

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

page language invalid

• Why it matters: Speaking helper may mispronounce the document text
• Related WCAG standard: 3.1.1
• Reported by 1 tool (WallyAX)
• 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 1 tool (WallyAX)
• Where was the issue found?

High priority

element obsolete

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

form submission button missing

• Why it matters: User cannot easily submit a form
• Related WCAG standard: 3.2.2
• Reported by 3 tools (ASLint + QualWeb + WallyAX)
• 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 2 tools (Accessibility Checker + WallyAX)
• 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?

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?

negative text-indent

• Why it matters: Helper may hide content from a user
• Related WCAG standard: 4.1
• Reported by 1 tool (ASLint)
• Where was the issue found?

animation long or repetitive

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

tab-opening link action unstated

• Why it matters: Following a link opens a new window, surprising a user
• Related WCAG standard: 3.2.5
• Reported by 1 tool (Editoria11y)
• 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?

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?

skip method missing or invalid

• Why it matters: Keyboard-only user cannot easily reach the specific content of the document
• Related WCAG standard: 2.4.1
• Reported by 1 tool (WallyAX)
• Where was the issue found?

Low priority

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 5 tools (Accessibility Checker + ASLint + QualWeb + WallyAX + WAVE)
• 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?

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?

banner 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 2 tools (QualWeb + WallyAX)
• Where was the issue found?

assertive region not atomic

• Why it matters: User may be unable to get help on what content has changed
• Related WCAG standard: 4.1.3
• Reported by 1 tool (Alfa)
• 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?

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?

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

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

text contrast improvable

• Why it matters: Content is not easy to understand
• Related WCAG standard: 1.4.6
• Reported by 3 tools (ASLint + Axe + 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 3 tools (ASLint + HTML CodeSniffer + 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 3 tools (ASLint + HTML CodeSniffer + WallyAX)
• 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?

hr misused

• Why it matters: User cannot get help on the nature of segments of the document
• Related WCAG standard: 1.3.1
• Reported by 2 tools (ASLint + Testaro)
• 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?

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?

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?

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 attribute redundant

• Why it matters: Document includes unnecessary code
• Related WCAG standard: 4.1.2
• 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?

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?

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?

hovering changes content

• Why it matters: User cannot explore the document reliably with a mouse
• Related WCAG standard: 3.2.5
• Reported by 1 tool (Testaro)
• 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?

underlining dubious

• Why it matters: User may be misled into believing some text is a link
• Related WCAG standard: 1.3.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?