Kilotest: Issues reported for Parking Reform Network

About the Parking Reform Network page

• URL: https://parkingreform.org/
• Tested by job 7sb on 2026-04-02 at 14:54

Issues reported

Summary

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

79 issues were reported (16 highest, 17 high, 10 low, 36 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 8 tools (Accessibility Checker + Alfa + Axe + Editoria11y + HTML CodeSniffer + QualWeb + WallyAX + WAVE)
• Where was the issue found?

contrast poor

• Why it matters: Content is difficult to understand
• Related WCAG standard: 1.4.3
• Reported by 6 tools (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + WallyAX + WAVE)
• 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?

figure not named

• Why it matters: User cannot get help on the topic of a figure
• Related WCAG standard: 1.1.1
• Reported by 1 tool (Accessibility Checker)
• Where was the issue found?

interactive component not named

• Why it matters: User cannot get help understanding a custom item
• Related WCAG standard: 4.1.2
• Reported by 1 tool (Accessibility Checker)
• Where was the issue found?

image link not named

• Why it matters: User cannot get help understanding what a link points to
• Related WCAG standard: 2.4.4
• Reported by 1 tool (Editoria11y)
• 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?

labeled element ambiguous

• Why it matters: User cannot get help on the topic of a form item
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

label contains control with nonmatching ID

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

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?

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?

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?

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

High priority

font small

• Why it matters: Text is difficult to read
• Related WCAG standard: 1.4
• Reported by 2 tools (ASLint + Testaro)
• 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 2 tools (Html Checker API + WallyAX)
• Where was the issue found?

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

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?

heading empty

• Why it matters: User cannot get help on the topic of a part of the document
• Related WCAG standard: 2.4.6
• Reported by 1 tool (Accessibility Checker)
• 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 (Accessibility Checker)
• Where was the issue found?

target very small

• Why it matters: User cannot reliably choose an item to click or tap
• Related WCAG standard: 2.5.8
• Reported by 1 tool (Alfa)
• 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)
• 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?

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?

attribute obsolete

• Why it matters: Document includes obsolete code that the browser may fail to process
• Related WCAG standard: 4.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

visible label not in name

• Why it matters: User cannot get help choosing a form control to operate
• Related WCAG standard: 2.5.3
• Reported by 1 tool (HTML CodeSniffer)
• 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?

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?

element beyond display when focused

• Why it matters: Keyboard-only user cannot navigate properly to the operable items
• Related WCAG standard: 1.4.10
• 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?

Low priority

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?

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?

duplicate attribute

• Why it matters: Browser processes the document improperly
• Related WCAG standard: 4.1.1
• Reported by 1 tool (Testaro)
• Where was the issue found?

tablist navigation nonstandard

• Why it matters: Tablist items behave improperly for a keyboard-only user
• Related WCAG standard: 2.1.1
• 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 (WallyAX)
• Where was the issue found?

image alt long

• Why it matters: Helper gives a user an overly verbose explanation of an image
• Related WCAG standard: 1.1.1
• Reported by 1 tool (WAVE)
• Where was the issue found?

fieldset missing

• Why it matters: User cannot get help recognizing a group of related form items
• Related WCAG standard: 1.3.1
• Reported by 1 tool (WAVE)
• 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 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?

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?

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

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 2 tools (Alfa + Axe)
• 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?

all-italic text

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

skip method missing or invalid?

• Why it matters: Keyboard-only user may be unable easily to reach the specific content of the document
• Related WCAG standard: 2.4.1
• Reported by 1 tool (Alfa)
• 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?

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?

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

dubious application role

• Why it matters: User actions may have unexpected effects
• Related WCAG standard: 1.3.1
• Reported by 1 tool (ASLint)
• 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)
• 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?

attribute value bad?

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

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?

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?

noscript element not equivalent?

• Why it matters: User who has disabled JavaScript may be denied some content
• Related WCAG standard: 4.1
• Reported by 1 tool (WAVE)
• Where was the issue found?

title attribute redundant

• Why it matters: Helper repeats the explanation of an item
• Related WCAG standard: 1.3.1
• Reported by 1 tool (WAVE)
• Where was the issue found?