Kilotest: Issues reported for Disability Rights Advocates contact

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 Disability Rights Advocates contact web page. Summarize them and propose a plan to resolve the genuine ones.

URL: https://dralegal.org/contact-us/
Tested 2 days ago on 2026-10-07 at 21:12 by job 261007T2109-hmz
Summary of results:
- Rule engines:
  - Called: 12
  - Were able to test: 12
  - Reported any rule violations: 12
- Violations: 340
- Violators: 233
- Issues: 32
Download the full technical report (JSON)

History

This is the only report about the page.

Should Kilotest retest the page?

Issues reported

Highest priority: 6

ID not unique
- Why it matters: User may be pointed to the wrong item
- Priority: highest
- Related WCAG standard: 4.1
- Reported by 2 rule engines (ASLint + Html Checker API)
- Violations: 54
- Violators: 42
- 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 (SureA11y + WAVE)
- Violations: 6
- Violators: 6
- Where was the issue found?
no role-required name
- Why it matters: User cannot get help understanding an item
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- Violations: 2
- Violators: 2
- 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 1 rule engine (ASLint)
- Violations: 1
- 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: 4
- Violators: 3
- Where was the issue found?
autocomplete missing
- Why it matters: User cannot get help entering personal information in a form
- Priority: highest
- Related WCAG standard: 1.3.5
- Reported by 1 rule engine (Testaro)
- Violations: 3
- Violators: 3
- Where was the issue found?

High priority: 12

heading empty
- Why it matters: User cannot get help on the topic of a part of the page
- Priority: high
- Related WCAG standard: 2.4.6
- Reported by 8 rule engines (Accessibility Checker + Alfa + ASLint + Axe + Editoria11y + HTML CodeSniffer + Pour + WAVE)
- Violations: 15
- Violators: 4
- Where was the issue found?
visible label not in name
- Why it matters: User cannot get help choosing a form control to operate
- Priority: high
- Related WCAG standard: 2.5.3
- Reported by 2 rule engines (Alfa + QualWeb)
- Violations: 2
- Violators: 2
- Where was the issue found?
element obsolete
- Why it matters: Page includes obsolete code that the browser may fail to process
- Priority: high
- Related WCAG standard: 4.1
- Reported by 2 rule engines (ASLint + QualWeb)
- Violations: 6
- Violators: 6
- 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 2 rule engines (Axe + Pour)
- Violations: 6
- Violators: 4
- Where was the issue found?
navigations 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)
- Violations: 2
- 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: 7
- Violators: 7
- 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)
- Violations: 2
- Violators: 2
- 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 API)
- Violations: 1
- Violators: 1
- Where was the issue found?
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 1 rule engine (Html Checker API)
- Violations: 2
- Violators: 2
- 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: 8
- Violators: 8
- 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: 27
- Violators: 27
- Where was the issue found?

Low priority: 2

main child of landmark
- 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 (Pour)
- Violations: 1
- Violators: 1
- 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: 10
- Violators: 10
- Where was the issue found?

Lowest priority: 12

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: 79
- Violators: 65
- 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: 8
- Violators: 5
- 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: 51
- Violators: 51
- 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?
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)
- Violations: 3
- Violators: 3
- 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?
no default option
- Why it matters: User may risk erroneously submitting a form
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (ASLint)
- Violations: 4
- Violators: 3
- Where was the issue found?
container size unit not percentage
- Why it matters: User may be unable to see all of an item without scrolling in both dimensions
- Priority: lowest
- Related WCAG standard: 1.4.10
- Reported by 1 rule engine (QualWeb)
- Violations: 9
- 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: 6
- Violators: 6
- 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?
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: 12
- Violators: 12
- Where was the issue found?

Kilotest: Issues reported for Disability Rights Advocates contact

About the tests

Do it yourself

Or use AI

History

Issues reported

ID not unique

contrast poor

no role-required name

iframe not named

attribute value invalid

autocomplete missing

heading empty

visible label not in name

element obsolete

landmarks not distinctly named

navigations not distinctly named

code obsolete

forms not distinctly named

attribute obsolete

CSS invalid

autocomplete invalid

box size absolute

small targets too near to each other

main child of landmark

line height low

text contrast improvable

role redundant

target small

complementary not named

fieldset missing?

labeling risky

no default option

container size unit not percentage

large visible-element count

role assigned instead of implicit

inconsistent heading, link, or button styles

z-index not zero