Kilotest: Issues reported for US Digital Response

About the tests

How to deal with the issues

Do it yourself

Explore the issues below in as much detail as you want. Decide which ones are actual defects. Plan and implement corrections.

Or use AI

Make Kilotest available to your AI assistant. There are step-by-step instructions for this.

After that, you can ask:

Kilotest reports defects on the US Digital Response web page. Summarize them and propose a plan to resolve the genuine ones.

URL: https://www.usdigitalresponse.org/
Tested 2 days ago on 2026-10-07 at 23:22 by job 261007T2305-nes
Summary of results:
- Rule engines:
  - Called: 12
  - Were able to test: 12
  - Reported any rule violations: 11
- Violations: 814
- Violators: 261
- Issues: 38
Download the full technical report (JSON)

History

This is the only report about the page.

Should Kilotest retest the page?

Issues reported

Highest priority: 11

link not named
- Why it matters: User cannot get help understanding what a link points to
- Priority: highest
- Related WCAG standard: 2.4.4
- Reported by 7 rule engines (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + Pour + QualWeb + SureA11y)
- Violations: 7
- Violators: 2
- 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 6 rule engines (Accessibility Checker + Alfa + Axe + Pour + SureA11y + WAVE)
- Violations: 23
- Violators: 9
- Where was the issue found?
ID not unique
- Why it matters: User may be pointed to the wrong item
- Priority: highest
- Related WCAG standard: 4.1
- Reported by 4 rule engines (ASLint + Html Checker + HTML CodeSniffer + QualWeb)
- Violations: 130
- Violators: 54
- 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)
- Violations: 8
- Violators: 8
- 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 2 rule engines (Accessibility Checker + WAVE)
- Violations: 28
- Violators: 14
- 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 2 rule engines (Alfa + SureA11y)
- Violations: 28
- Violators: 14
- Where was the issue found?
attribute invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Accessibility Checker)
- Violations: 14
- Violators: 14
- 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 1 rule engine (ASLint)
- Violations: 14
- Violators: 14
- 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)
- Violations: 15
- Violators: 15
- 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)
- Violations: 5
- Violators: 5
- 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 1 rule engine (WAVE)
- Violations: 6
- Violators: 6
- Where was the issue found?

High priority: 8

form submission button missing
- Why it matters: User cannot easily submit a form
- Priority: high
- Related WCAG standard: 3.2.2
- Reported by 3 rule engines (ASLint + HTML CodeSniffer + QualWeb)
- Violations: 3
- Violators: 2
- Where was the issue found?
code obsolete
- Why it matters: Page contains code that is no longer standard
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Accessibility Checker)
- Violations: 1
- Violators: 1
- Where was the issue found?
attribute obsolete
- Why it matters: Page includes obsolete code that the browser may fail to process
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (ASLint)
- Violations: 1
- Violators: 1
- Where was the issue found?
CSS invalid
- Why it matters: Page cannot be properly displayed
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- Violations: 1
- Violators: 1
- Where was the issue found?
invalid CSS at-rule
- Why it matters: Page cannot be properly displayed in particular contexts
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- Violations: 8
- Violators: 1
- 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)
- Violations: 2
- Violators: 2
- 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
- Priority: high
- Related WCAG standard: 2.5.8
- Reported by 1 rule engine (Testaro)
- Violations: 18
- Violators: 18
- 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)
- Violations: 1
- Violators: 1
- Where was the issue found?

Low priority: 5

heading level skipped
- Why it matters: Helper misdescribes the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 4 rule engines (Alfa + Axe + Html Checker + Pour)
- Violations: 12
- Violators: 6
- 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 2 rule engines (ASLint + HTML CodeSniffer)
- Violations: 8
- Violators: 8
- 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 1 rule engine (Testaro)
- Violations: 53
- Violators: 53
- 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)
- Violations: 3
- Violators: 1
- 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)
- Violations: 42
- Violators: 42
- Where was the issue found?

Lowest priority: 14

text contrast improvable
- Why it matters: Content is not easy to understand
- Priority: lowest
- Related WCAG standard: 1.4.6
- Reported by 7 rule engines (Alfa + ASLint + Axe + HTML CodeSniffer + Pour + QualWeb + SureA11y)
- Violations: 269
- Violators: 97
- 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 + Pour + Testaro)
- Violations: 12
- Violators: 5
- Where was the issue found?
role redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + Pour)
- Violations: 6
- Violators: 5
- Where was the issue found?
link destination not URL
- Why it matters: Helper cannot properly explain a link to a user
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Violations: 2
- Violators: 2
- 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 (ASLint)
- Violations: 1
- Violators: 1
- Where was the issue found?
aria-label on non-labelable role
- Why it matters: User is misinformed about an item
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Violations: 14
- Violators: 14
- 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 1 rule engine (Pour)
- Violations: 19
- Violators: 19
- 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 1 rule engine (QualWeb)
- Violations: 4
- Violators: 4
- 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)
- Violations: 1
- Violators: 1
- Where was the issue found?
double br use dubious
- Why it matters: User may be unable to get help to fully understand the text
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- Violations: 1
- Violators: 1
- 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)
- Violations: 39
- Violators: 39
- 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)
- Violations: 4
- Violators: 1
- 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)
- Violations: 10
- Violators: 10
- Where was the issue found?
hovering changes content
- Why it matters: User cannot explore the page reliably with a mouse
- Priority: lowest
- Related WCAG standard: 3.2.5
- Reported by 1 rule engine (Testaro)
- Violations: 1
- Violators: 1
- Where was the issue found?

Kilotest: Issues reported for US Digital Response

About the tests

Do it yourself

Or use AI

History

Issues reported

link not named

contrast poor

ID not unique

svg image not named

aria reference invalid

aria attribute invalid

attribute invalid

label reference invalid

attribute value invalid

Tab-focusable elements wrong

image not named

form submission button missing

code obsolete

attribute obsolete

CSS invalid

invalid CSS at-rule

box size absolute

small targets too near to each other

element focusability and operability conflict

heading level skipped

heading structure illogical

line height low

links named identically

focus indication improvable

text contrast improvable

tab-opening link action unstated?

role redundant

link destination not URL

position sticky

aria-label on non-labelable role

target small

text contrast not testable

large visible-element count

double br use dubious

role assigned instead of implicit

inconsistent heading, link, or button styles

z-index not zero

hovering changes content