Kilotest: Issues reported for Center for Justice and Accountability Justice Circle

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 Center for Justice and Accountability Justice Circle web page. Summarize them and propose a plan to resolve the genuine ones.

URL: https://cja.org/justice-circle/
Tested 3 days ago on 2026-10-07 at 19:58 by job 261007T1941-uf9
Summary of results:
- Rule engines:
  - Called: 12
  - Were able to test: 12
  - Reported any rule violations: 10
- Violations: 602
- Violators: 253
- Issues: 59
Download the full technical report (JSON)

History

This is the only report about the page.

Should Kilotest retest the page?

Issues reported

Highest priority: 14

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)
- Violations: 6
- Violators: 4
- Where was the issue found?
iframe not named
- Why it matters: User cannot get help on the topic of an embedded page
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + HTML CodeSniffer)
- Violations: 2
- Violators: 1
- 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: 12
- Violators: 8
- Where was the issue found?
dialog not named
- Why it matters: User cannot get help explaining a pop-up window
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (ASLint + SureA11y)
- Violations: 2
- 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 2 rule engines (HTML CodeSniffer + Pour)
- Violations: 4
- Violators: 4
- Where was the issue found?
figure not named
- Why it matters: User cannot get help on the topic of a figure
- Priority: highest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (Accessibility Checker)
- Violations: 11
- Violators: 11
- 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 (Accessibility Checker)
- Violations: 9
- Violators: 9
- Where was the issue found?
invalid landmark child of navigation role
- Why it matters: User cannot get help on how some of the page is organized
- Priority: highest
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (ASLint)
- Violations: 1
- Violators: 1
- Where was the issue found?
script element invalid
- Why it matters: Browser processes the page improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Violations: 2
- Violators: 1
- 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)
- Violations: 7
- Violators: 7
- Where was the issue found?
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 1 rule engine (QualWeb)
- Violations: 2
- Violators: 1
- 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 (SureA11y)
- Violations: 2
- Violators: 1
- 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 1 rule engine (SureA11y)
- Violations: 2
- Violators: 1
- 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: 1
- Violators: 1
- Where was the issue found?

High priority: 16

autocomplete invalid
- Why it matters: User cannot get help entering personal information in a form item
- Priority: high
- Related WCAG standard: 1.3.5
- Reported by 4 rule engines (Accessibility Checker + ASLint + Html Checker API + HTML CodeSniffer)
- Violations: 6
- Violators: 5
- 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 4 rule engines (Html Checker API + Pour + SureA11y + Testaro)
- Violations: 4
- Violators: 2
- Where was the issue found?
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 3 rule engines (Accessibility Checker + Alfa + HTML CodeSniffer)
- Violations: 5
- Violators: 3
- Where was the issue found?
target very small
- Why it matters: User cannot reliably choose an item to click or tap
- Priority: high
- Related WCAG standard: 2.5.8
- Reported by 3 rule engines (Alfa + Pour + SureA11y)
- Violations: 17
- Violators: 11
- 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 2 rule engines (Accessibility Checker + Testaro)
- Violations: 19
- Violators: 19
- Where was the issue found?
form submission button missing
- Why it matters: User cannot easily submit a form
- Priority: high
- Related WCAG standard: 3.2.2
- Reported by 2 rule engines (ASLint + HTML CodeSniffer)
- Violations: 2
- Violators: 2
- 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)
- Violations: 1
- Violators: 1
- Where was the issue found?
h1 not 1st heading
- Why it matters: User cannot understand the topic of the page
- Priority: high
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Alfa)
- 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 API)
- Violations: 2
- Violators: 1
- 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)
- Violations: 4
- Violators: 4
- 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 API)
- Violations: 4
- Violators: 1
- Where was the issue found?
landmarks 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 (Pour)
- Violations: 4
- Violators: 3
- Where was the issue found?
font small
- Why it matters: Text is difficult to read
- Priority: high
- Related WCAG standard: 1.4
- Reported by 1 rule engine (Testaro)
- Violations: 1
- Violators: 1
- 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)
- Violations: 1
- Violators: 1
- 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?
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)
- Violations: 5
- Violators: 3
- Where was the issue found?

Low priority: 8

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 4 rule engines (Accessibility Checker + ASLint + HTML CodeSniffer + QualWeb)
- Violations: 8
- Violators: 2
- 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: 3
- Violators: 2
- 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)
- Violations: 1
- Violators: 1
- Where was the issue found?
decorative element has title
- Why it matters: Hovering-produced information is denied to a keyboard-only user
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Violations: 9
- Violators: 9
- 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: 61
- Violators: 61
- 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: 1
- Violators: 1
- 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)
- Violations: 1
- 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: 41
- Violators: 41
- Where was the issue found?

Lowest priority: 21

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: 55
- Violators: 24
- 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: 40
- Violators: 21
- 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: 2
- Violators: 1
- 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 2 rule engines (Accessibility Checker + QualWeb)
- Violations: 4
- Violators: 2
- 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 + Pour)
- Violations: 68
- Violators: 56
- 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 2 rule engines (Alfa + Pour)
- Violations: 2
- Violators: 2
- Where was the issue found?
complementary not named
- 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 1 rule engine (Accessibility Checker)
- Violations: 1
- Violators: 1
- Where was the issue found?
false aria-hidden value risky
- Why it matters: User may be misled by erroneously hidden or revealed page content
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Violations: 1
- Violators: 1
- Where was the issue found?
title attribute empty
- Why it matters: Hovering does not get the promised explanation of an item
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Violations: 1
- Violators: 1
- 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)
- Violations: 1
- Violators: 1
- 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 (Pour)
- Violations: 5
- Violators: 2
- 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 (Pour)
- Violations: 13
- Violators: 8
- Where was the issue found?
list-like br use dubious
- Why it matters: User cannot get help recognizing a list of items
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Violations: 1
- Violators: 1
- 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 1 rule engine (Testaro)
- Violations: 67
- Violators: 67
- Where was the issue found?
all-italic text
- Why it matters: Text is difficult to read
- Priority: lowest
- Related WCAG standard: 3.1.5
- Reported by 1 rule engine (Testaro)
- Violations: 1
- Violators: 1
- 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?
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: 15
- Violators: 15
- 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: 5
- Violators: 1
- 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)
- Violations: 12
- Violators: 12
- 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: 23
- Violators: 23
- 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: 19
- Violators: 19
- Where was the issue found?

Kilotest: Issues reported for Center for Justice and Accountability Justice Circle

About the tests

Do it yourself

Or use AI

History

Issues reported

attribute invalid

iframe not named

aria attribute invalid

dialog not named

contrast poor

figure not named

image not named

invalid landmark child of navigation role

script element invalid

attribute value invalid

control not named

input not named

button not named

Tab-focusable elements wrong

autocomplete invalid

control child of link or button

group not named

target very small

small targets too near to each other

form submission button missing

role invalid

h1 not 1st heading

CSS invalid

code invalid

invalid CSS at-rule

landmarks not distinctly named

font small

input has placeholder instead of name

element focusability and operability conflict

hover indication poor

legend missing

heading structure illogical

heading heads nothing

decorative element has title

line height low

links named identically

link indication poor

focus indication improvable

text contrast improvable

tab-opening link action unstated?

role redundant

label location dubious

target small

content beyond landmarks

complementary not named

false aria-hidden value risky

title attribute empty

labeling risky

aria attribute redundant

tabindex redundant

list-like br use dubious

all-capital text

all-italic text

large visible-element count

role assigned instead of implicit

inconsistent heading, link, or button styles

title attribute invalid

z-index not zero

hovering changes content