Kilotest: Issues reported for Prometheus

About the Prometheus page

• URL: https://www.joinprometheus.org/
• Tested by job 2ft on 2026-04-07 at 19:19
• Page prevented testing by 3 tools (Accessibility Checker + Alfa + WAVE)

Issues reported

Summary

8 tools reported issues (ASLint + Axe + Editoria11y + Html Checker API + HTML CodeSniffer + QualWeb + Testaro + WallyAX)

45 issues were reported (8 highest, 13 high, 6 low, 18 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 4 tools (Axe + HTML CodeSniffer + QualWeb + 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 + WallyAX)
• Where was the issue found?

link element invalid

• Why it matters: Document fails to get a needed external resource
• Related WCAG standard: 1.3.1
• Reported by 2 tools (HTML CodeSniffer + WallyAX)
• 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 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?

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?

High priority

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?

image named with filename

• Why it matters: Helper gives a user the filename of an image instead of describing it
• Related WCAG standard: 1.1.1
• Reported by 2 tools (ASLint + Editoria11y)
• 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?

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?

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?

invalid at-rule

• Why it matters: Document cannot be properly displayed in particular contexts
• Related WCAG standard: 4.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

element reloads or redirects

• Why it matters: Document change may surprise a user
• Related WCAG standard: 2.2.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?

font small

• Why it matters: Text is difficult to read
• Related WCAG standard: 1.4
• Reported by 1 tool (Testaro)
• 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?

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?

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 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 3 tools (ASLint + QualWeb + WallyAX)
• 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?

not exactly 1 h1 heading

• Why it matters: User cannot understand the topic of the document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

label types incompatible

• Why it matters: User cannot get reliable help on the topics of form items
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Testaro)
• 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?

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

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?

text contrast improvable

• Why it matters: Content is not easy to understand
• Related WCAG standard: 1.4.6
• Reported by 3 tools (HTML CodeSniffer + QualWeb + WallyAX)
• 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 2 tools (HTML CodeSniffer + QualWeb)
• Where was the issue found?

false aria-hidden value risky

• Why it matters: User may be misled by erroneously hidden or revealed document content
• Related WCAG standard: 2.4.6
• Reported by 1 tool (ASLint)
• Where was the issue found?

dir invalid

• Why it matters: Item may behave improperly
• 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?

tabindex redundant

• Why it matters: Revision risks interfering with navigation by a keyboard-only user
• Related WCAG standard: 1.3.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?

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?

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?

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?

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?

title attribute invalid

• Why it matters: User gets too little, too much, or repeated help explaining an item
• Related WCAG standard: 1.3.1
• 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?