Kilotest: Issues reported for Run!

About the Run! page

• URL: https://www.designedtorun.com/
• Tested by job rok on 2026-04-05 at 01:26
• Page prevented testing by 1 tool (WAVE)

Issues reported

Summary

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

66 issues were reported (14 highest, 13 high, 13 low, 26 lowest priority)

Details

Highest priority

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 5 tools (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + QualWeb)
• Where was the issue found?

contrast poor

• Why it matters: Content is difficult to understand
• Related WCAG standard: 1.4.3
• Reported by 5 tools (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + WallyAX)
• Where was the issue found?

button not named

• Why it matters: User cannot get help explaining a button
• Related WCAG standard: 4.1.2
• Reported by 5 tools (Alfa + 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 (Editoria11y + Html Checker API + 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 2 tools (Accessibility Checker + ASLint)
• Where was the issue found?

attribute invalid

• Why it matters: Item behaves improperly
• Related WCAG standard: 1.3.1
• Reported by 2 tools (Accessibility Checker + Html Checker API)
• Where was the issue found?

meta bans zoom

• Why it matters: User cannot adjust the document size for readability
• Related WCAG standard: 1.4.4
• Reported by 1 tool (ASLint)
• Where was the issue found?

label reference invalid

• Why it matters: User cannot get help understanding an item in a form
• Related WCAG standard: 1.3.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?

parent invalid

• Why it matters: User cannot properly operate an item
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

input not named

• Why it matters: User cannot get help on what information to enter in a form item
• Related WCAG standard: 4.1.2
• Reported by 1 tool (HTML CodeSniffer)
• 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?

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?

High priority

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?

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?

role invalid

• Why it matters: User cannot get help on the nature of an item
• Related WCAG standard: 4.1.2
• Reported by 1 tool (Accessibility Checker)
• 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?

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?

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?

control child of link or button

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

input has placeholder instead of name

• Why it matters: User cannot get reliable help on what information to enter in a form item
• Related WCAG standard: 4.1.2
• 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?

link element href missing

• Why it matters: User cannot reach a promised location
• Related WCAG standard: 4.1
• Reported by 1 tool (WallyAX)
• 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

heading level skipped

• Why it matters: Helper misdescribes the document
• Related WCAG standard: 1.3.1
• Reported by 5 tools (Alfa + Axe + Editoria11y + Html Checker API + WallyAX)
• Where was the issue found?

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 4 tools (Accessibility Checker + ASLint + QualWeb + 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?

link href missing

• Why it matters: Helper cannot properly explain a link to a user
• Related WCAG standard: 1.3.1
• Reported by 2 tools (ASLint + Testaro)
• 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?

heading heads nothing

• Why it matters: Helper misdescribes the document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Alfa)
• Where was the issue found?

main missing

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

links named identically

• Why it matters: User cannot get help differentiating links
• Related WCAG standard: 2.4.4
• 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?

link incomplete

• Why it matters: User may fail to reach a promised location
• 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?

Lowest priority

text contrast improvable

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

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?

all-capital text

• Why it matters: Text is difficult to read
• Related WCAG standard: 3.1.5
• Reported by 2 tools (Alfa + 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?

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?

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?

fieldset missing?

• Why it matters: User may be unable to get help recognizing a group of related form items
• Related WCAG standard: 1.3.1
• 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?

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?

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?

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

heading abnormally long

• Why it matters: User has difficulty understanding the topic of a part of the document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Editoria11y)
• 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?

tabindex attribute nullifies presentation role

• Why it matters: User encounters content intended to be hidden
• 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?

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?

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?

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?