Kilotest: Issues reported for Probably Good

About the Probably Good page

URL: https://probablygood.org/
Tested 3 days ago by job n2u on 2026-05-30 at 00:32
Page not testable by WAVE (Utah State University): Timed out at 25 seconds

Issues reported

Summary

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

45 issues were reported (10 highest, 10 high, 5 low, 20 lowest priority)

153 violators were reported

Download the full technical report

Details

Highest priority: 10

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 (Accessibility Checker + Editoria11y + HTML CodeSniffer)
- 8 violators were reported
- Where was the issue found?
internal link broken
- Why it matters: User cannot reach a promised document location
- Related WCAG standard: 1.3.1
- Reported by 2 tools (ASLint + HTML CodeSniffer)
- 2 violators were reported
- 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)
- 1 violator was reported
- Where was the issue found?
contrast poor
- Why it matters: Content is difficult to understand
- Related WCAG standard: 1.4.3
- Reported by 1 tool (Axe)
- 12 violators were reported
- 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)
- 2 violators were reported
- 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)
- 3 violators were reported
- 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)
- 3 violators were reported
- 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 1 tool (HTML CodeSniffer)
- 3 violators were reported
- 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)
- 1 violator was reported
- 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)
- 1 violator was reported
- Where was the issue found?

High priority: 10

code obsolete
- Why it matters: Document contains code that is no longer standard
- Related WCAG standard: 4.1
- Reported by 1 tool (Accessibility Checker)
- 4 violators were reported
- Where was the issue found?
element in head invalid
- Why it matters: Browser processes the document improperly
- Related WCAG standard: 4.1.1
- Reported by 1 tool (ASLint)
- 1 violator was reported
- 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 1 tool (ASLint)
- 1 violator was reported
- 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)
- 1 violator was reported
- 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)
- 2 violators were reported
- Where was the issue found?
autocomplete invalid
- Why it matters: User cannot get help entering personal information in a form item
- Related WCAG standard: 1.3.5
- Reported by 1 tool (HTML CodeSniffer)
- 1 violator was reported
- 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)
- 4 violators were reported
- 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
- Related WCAG standard: 2.5.8
- Reported by 1 tool (Testaro)
- 13 violators were reported
- 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)
- 1 violator was reported
- 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)
- 1 violator was reported
- Where was the issue found?

Low priority: 5

decorative element has title
- Why it matters: Hovering-produced information is denied to a keyboard-only user
- Related WCAG standard: 1.3.1
- Reported by 2 tools (ASLint + HTML CodeSniffer)
- 2 violators were reported
- 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)
- 4 violators were reported
- 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)
- 7 violators were reported
- 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)
- 12 violators were reported
- Where was the issue found?
focus indication improvable
- Why it matters: Keyboard-only user cannot easily choose an item to operate
- Related WCAG standard: 2.4.7
- Reported by 1 tool (Testaro)
- 41 violators were reported
- Where was the issue found?

Lowest priority: 20

text contrast improvable
- Why it matters: Content is not easy to understand
- Related WCAG standard: 1.4.6
- Reported by 5 tools (Alfa + ASLint + Axe + HTML CodeSniffer + QualWeb)
- 9 violators were reported
- 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)
- 47 violators were reported
- 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 (Alfa + HTML CodeSniffer)
- 20 violators were reported
- 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 1 tool (Alfa)
- 17 violators were reported
- 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)
- 4 violators were reported
- 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)
- 3 violators were reported
- Where was the issue found?
custom button keyboard-inoperable?
- Why it matters: Custom item may prevent a keyboard-only user from operating it
- Related WCAG standard: 2.1.1
- Reported by 1 tool (ASLint)
- 2 violators were reported
- 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)
- 1 violator was reported
- 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)
- 1 violator was reported
- Where was the issue found?
link destination not URL
- Why it matters: Helper cannot properly explain a link to a user
- Related WCAG standard: 1.3.1
- Reported by 1 tool (ASLint)
- 2 violators were reported
- 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)
- 1 violator was reported
- 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)
- 14 violators were reported
- 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 1 tool (HTML CodeSniffer)
- 2 violators were reported
- 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)
- 25 violators were reported
- 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)
- 1 violator was reported
- 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)
- 1 violator was reported
- 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)
- 6 violators were reported
- 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)
- 1 violator was reported
- 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)
- 11 violators were reported
- 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)
- 12 violators were reported
- Where was the issue found?

Kilotest: Issues reported for Probably Good

About the Probably Good page

Issues reported

Summary

Details

image not named

internal link broken

aria attribute invalid

contrast poor

attribute value invalid

parent invalid

attribute invalid

link element invalid

input not named

autocomplete missing

code obsolete

element in head invalid

form submission button missing

meta invalid

CSS invalid

autocomplete invalid

box size absolute

small targets too near to each other

input has placeholder instead of name

hover indication poor

decorative element has title

links named identically

line height low

link indication poor

focus indication improvable

text contrast improvable

content beyond landmarks

text contrast not testable

target small

item makes testing inconclusive

button name not visible

custom button keyboard-inoperable?

link name vague

labeling risky

link destination not URL

links dubiously share name

type redundant

position sticky

overflow hidden?

label location dubious

large visible-element count

role assigned instead of implicit

inconsistent heading, link, or button styles

title attribute invalid

z-index not zero