Issues reported for Run! home

About the page

URL: https://www.designedtorun.com/
Tested 190 days ago on 2026-05-04 at 17:29 by job 260504T1700-mgf
Rule engines: 10 called, 10 able to test, violations reported by 10
Results: 1686 violations, 397 violators, 71 issues
Download the full technical report (JSON)

History

This is the only available report about the page.

Request a retest

Issues reported

Highest priority: 15

control not named
- Why it matters: User cannot get help on how to operate a form item
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 6 rule engines (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + QualWeb + WAVE)
- Results: 19 violations, 9 violators
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 5 rule engines (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + WAVE)
- Results: 160 violations, 134 violators
Where was the issue found?
button not named
- Why it matters: User cannot get help explaining a button
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 5 rule engines (Alfa + Axe + HTML CodeSniffer + QualWeb + WAVE)
- Results: 10 violations, 6 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 4 rule engines (Editoria11y + Html Checker API + HTML CodeSniffer + WAVE)
- Results: 8 violations, 3 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: 18 violations, 18 violators
Where was the issue found?
attribute invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (Accessibility Checker + Html Checker API)
- Results: 4 violations, 4 violators
Where was the issue found?
label reference invalid
- Why it matters: User cannot get help understanding an item in a form
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + Html Checker API)
- Results: 2 violations, 2 violators
Where was the issue found?
meta bans zoom
- Why it matters: User cannot adjust the page size for readability
- Priority: highest
- Related WCAG standard: 1.4.4
- 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?
parent invalid
- Why it matters: User cannot properly operate an item
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 7 violations, 7 violators
Where was the issue found?
input not named
- Why it matters: User cannot get help on what information to enter in a form item
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 4 violations, 4 violators
Where was the issue found?
aria attribute invalid
- Why it matters: Item behavior violates user expectations
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
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: 1 violation, 1 violator
Where was the issue found?
aria reference invalid
- Why it matters: Item behavior violates user expectations
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (WAVE)
- Results: 1 violation, 1 violator
Where was the issue found?

High priority: 12

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)
- Results: 2 violations, 1 violator
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)
- Results: 2 violations, 2 violators
Where was the issue found?
role invalid
- Why it matters: User cannot get help on the nature of an item
- Priority: high
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- Results: 1 violation, 1 violator
Where was the issue found?
tab-opening link action unstated
- Why it matters: Following a link opens a new window, surprising a user
- Priority: high
- Related WCAG standard: 3.2.5
- Reported by 1 rule engine (Editoria11y)
- Results: 6 violations, 6 violators
Where was the issue found?
meta element duplicated
- Why it matters: Browser may process the page incorrectly
- 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?
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: 2 violations, 2 violators
Where was the issue found?
link element href missing
- Why it matters: User cannot reach a promised location
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (HTML CodeSniffer)
- 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: 2 violations, 2 violators
Where was the issue found?
control child of link or button
- Why it matters: User cannot reliably choose an item to click or tap
- Priority: high
- Related WCAG standard: 2.5.5
- Reported by 1 rule engine (Testaro)
- Results: 2 violations, 2 violators
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
- Priority: high
- Related WCAG standard: 4.1.2
- 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: 26 violations, 26 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: 11 violations, 11 violators
Where was the issue found?

Low priority: 14

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 5 rule engines (Accessibility Checker + ASLint + HTML CodeSniffer + QualWeb + WAVE)
- Results: 6 violations, 2 violators
Where was the issue found?
heading level skipped
- Why it matters: Helper misdescribes the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 5 rule engines (Alfa + Axe + Editoria11y + Html Checker API + WAVE)
- Results: 15 violations, 7 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 2 rule engines (Alfa + Testaro)
- Results: 100 violations, 98 violators
Where was the issue found?
link href missing
- Why it matters: Helper cannot properly explain a link to a user
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + Testaro)
- Results: 8 violations, 8 violators
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)
- Results: 5 violations, 5 violators
Where was the issue found?
heading heads nothing
- Why it matters: Helper misdescribes the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Alfa)
- Results: 7 violations, 7 violators
Where was the issue found?
main missing
- 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 (Axe)
- Results: 1 violation, 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: 3 violations, 3 violators
Where was the issue found?
link incomplete
- Why it matters: User may fail to reach a promised location
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 4 violations, 4 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: 1 violation, 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 1 rule engine (Testaro)
- Results: 8 violations, 8 violators
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)
- Results: 1 violation, 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: 29 violations, 29 violators
Where was the issue found?
adjacent links not combined
- Why it matters: Keyboard-only user expends extra effort to skip a link
- Priority: low
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (WAVE)
- Results: 1 violation, 1 violator
Where was the issue found?

Lowest priority: 30

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 (Alfa + ASLint + Axe + HTML CodeSniffer + QualWeb)
- Results: 398 violations, 218 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 3 rule engines (Accessibility Checker + Alfa + Axe)
- Results: 218 violations, 153 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 + HTML CodeSniffer + Testaro)
- Results: 18 violations, 12 violators
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 + Testaro)
- Results: 11 violations, 7 violators
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 2 rule engines (Alfa + Testaro)
- Results: 84 violations, 78 violators
Where was the issue found?
image dubiously named
- Why it matters: Helper may describe an image inadequately
- Priority: lowest
- Related WCAG standard: 1.1.1
- Reported by 2 rule engines (ASLint + WAVE)
- Results: 2 violations, 2 violators
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 page
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (Axe + WAVE)
- Results: 3 violations, 3 violators
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 2 rule engines (HTML CodeSniffer + QualWeb)
- Results: 169 violations, 162 violators
Where was the issue found?
item makes testing inconclusive
- Why it matters: Item prevents a conclusive accessibility test
- Priority: lowest
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Alfa)
- Results: 28 violations, 9 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: 3 violations, 3 violators
Where was the issue found?
fieldset missing?
- Why it matters: User may be unable to get help recognizing a group of related form items
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 2 violations, 2 violators
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: 7 violations, 7 violators
Where was the issue found?
tabindex redundant
- Why it matters: Revision risks interfering with navigation by a keyboard-only user
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 10 violations, 6 violators
Where was the issue found?
heading abnormally long
- Why it matters: User has difficulty understanding the topic of a part of the page
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Editoria11y)
- Results: 1 violation, 1 violator
Where was the issue found?
aria attribute redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Html Checker API)
- Results: 2 violations, 1 violator
Where was the issue found?
tabindex attribute nullifies presentation role
- Why it matters: User encounters content intended to be hidden
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
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 (HTML CodeSniffer)
- Results: 2 violations, 2 violators
Where was the issue found?
overflow hidden?
- Why it matters: User may be unable to enlarge the text for readability
- Priority: lowest
- Related WCAG standard: 1.4.4
- Reported by 1 rule engine (QualWeb)
- Results: 110 violations, 110 violators
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: 6 violations, 6 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: 22 violations, 22 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: 4 violations, 4 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: 6 violations, 1 violator
Where was the issue found?
title attribute invalid
- Why it matters: User gets too little, too much, or repeated help explaining an item
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- Results: 30 violations, 30 violators
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: 15 violations, 15 violators
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 (WAVE)
- Results: 5 violations, 5 violators
Where was the issue found?
nearby images have same alt
- Why it matters: User cannot get help differentiating two adjacent images
- Priority: lowest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (WAVE)
- Results: 14 violations, 14 violators
Where was the issue found?
noscript element not equivalent?
- Why it matters: User who has disabled JavaScript may be denied some content
- Priority: lowest
- Related WCAG standard: 4.1
- Reported by 1 rule engine (WAVE)
- Results: 2 violations, 2 violators
Where was the issue found?
underlining dubious
- Why it matters: User may be misled into believing some text is a link
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (WAVE)
- Results: 2 violations, 2 violators
Where was the issue found?
title attribute redundant
- Why it matters: Helper repeats the explanation of an item
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (WAVE)
- Results: 24 violations, 24 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 Run! home web page. Describe them and propose a plan to resolve the genuine defects.

Issues reported for Run! home

About the page

History

Issues reported

control not named

contrast poor

button not named

image not named

svg image not named

attribute invalid

label reference invalid

meta bans zoom

meta charset declared too late

attribute value invalid

parent invalid

input not named

aria attribute invalid

Tab-focusable elements wrong

aria reference invalid

group not named

forms not distinctly named

role invalid

tab-opening link action unstated

meta element duplicated

code invalid

link element href missing

box size absolute

control child of link or button

input has placeholder instead of name

element focusability and operability conflict

hover indication poor

legend missing

heading level skipped

line height low

link href missing

font size absolute

heading heads nothing

main missing

heading structure illogical

link incomplete

links named identically

link indication poor

page content moves spontaneously

focus indication improvable

adjacent links not combined

text contrast improvable

content beyond landmarks

tab-opening link action unstated?

target small

all-capital text

image dubiously named

heading-like styles dubious

text contrast not testable

item makes testing inconclusive

button name not visible

fieldset missing?

labeling risky

tabindex redundant

heading abnormally long

aria attribute redundant

tabindex attribute nullifies presentation role

position sticky

overflow hidden?

label location dubious

large visible-element count

text distortion

role assigned instead of implicit

inconsistent heading, link, or button styles

title attribute invalid

z-index not zero

image name redundant

nearby images have same alt

noscript element not equivalent?

underlining dubious

title attribute redundant

What you can do

Do it yourself

Use artificial intelligence