Kilotest: Issues reported for Human Rights Watch 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 Human Rights Watch contact web page. Summarize them and propose a plan to resolve the genuine ones.
- URL: https://www.hrw.org/contact-us
- Tested 2 days ago on 2026-10-07 at 21:44 by job
261007T2129-ov7 - Summary of results:
- Rule engines:
- Called: 12
- Were able to test: 12
- Reported any rule violations: 11
- Violations: 1653
- Violators: 652
- Issues: 54
- Rule engines:
- Download the full technical report (JSON)
History
This is the only report about the page.
Should Kilotest retest the page?
Issues reported
Highest priority: 16
-
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 8 rule engines (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + Pour + QualWeb + SureA11y + WAVE)
- Violations: 10
- Violators: 3
-
contrast poor
- Why it matters: Content is difficult to understand
- Priority: highest
- Related WCAG standard: 1.4.3
- Reported by 5 rule engines (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + WAVE)
- Violations: 8
- Violators: 6
-
ID not unique
- Why it matters: User may be pointed to the wrong item
- Priority: highest
- Related WCAG standard: 4.1
- Reported by 3 rule engines (ASLint + Html Checker + HTML CodeSniffer)
- Violations: 16
- Violators: 12
-
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: 40
- Violators: 40
-
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 (ASLint + HTML CodeSniffer)
- Violations: 2
- Violators: 2
-
abbr title missing
- Why it matters: User cannot get help understanding an abbreviation
- Priority: highest
- Related WCAG standard: 3.1.4
- Reported by 2 rule engines (ASLint + QualWeb)
- Violations: 4
- Violators: 3
-
aria reference invalid
- Why it matters: Item behavior violates user expectations
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Accessibility Checker)
- Violations: 5
- Violators: 5
-
aria attribute invalid
- Why it matters: Item behavior violates user expectations
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Alfa)
- Violations: 2
- Violators: 2
-
focusable element hidden
- Why it matters: Keyboard-only user cannot navigate properly to the operable items
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (ASLint)
- Violations: 1
- Violators: 1
-
requirement invalid
- Why it matters: User may fail to get help determining whether a form item must be completed
- Priority: highest
- Related WCAG standard: 1.3.5
- Reported by 1 rule engine (ASLint)
- Violations: 2
- Violators: 2
-
parent invalid
- Why it matters: User cannot properly operate an item
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Violations: 1
- Violators: 1
-
itemid invalid
- Why it matters: User cannot get help to identify a referent
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Violations: 16
- Violators: 9
-
attribute invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Violations: 5
- Violators: 5
-
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: 1
- Violators: 1
-
ID empty
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Violations: 3
- Violators: 3
-
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: 39
- Violators: 38
High priority: 9
-
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 3 rule engines (ASLint + Html Checker + Testaro)
- Violations: 6
- Violators: 6
-
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
-
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 (ASLint)
- Violations: 1
- Violators: 1
-
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)
- Violations: 4
- Violators: 4
-
summary has explicit role
- Why it matters: User cannot detect details
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- Violations: 1
- Violators: 1
-
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
-
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 1 rule engine (SureA11y)
- Violations: 2
- Violators: 2
-
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: 20
- Violators: 20
-
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: 3
- Violators: 3
Low priority: 11
-
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: 4
- Violators: 2
-
link indication poor
- Why it matters: User cannot differentiate a link from plain text
- Priority: low
- Related WCAG standard: 1.3.3
- Reported by 3 rule engines (Alfa + Pour + Testaro)
- Violations: 90
- Violators: 80
-
link href missing
- Why it matters: Helper cannot properly explain a link to a user
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 3 rule engines (ASLint + Html Checker + Testaro)
- Violations: 7
- Violators: 6
-
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: 7
- Violators: 5
-
font size absolute
- Why it matters: User cannot adjust the text size for readability
- Priority: low
- Related WCAG standard: 1.4.4
- Reported by 1 rule engine (Alfa)
- Violations: 1
- Violators: 1
-
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: 2
- Violators: 2
-
links not grouped as nav
- Why it matters: User cannot get help identifying links as a navigation tool
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Violations: 2
- Violators: 2
-
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: 14
- Violators: 14
-
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: 7
- Violators: 1
-
menu navigation nonstandard
- Why it matters: Menus behave improperly for a keyboard-only user
- Priority: low
- Related WCAG standard: 2.1.1
- Reported by 1 rule engine (Testaro)
- Violations: 1
- Violators: 1
-
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: 113
- Violators: 113
Lowest priority: 18
-
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: 924
- Violators: 452
-
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: 31
- Violators: 22
-
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: 7
- Violators: 4
-
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: 144
- Violators: 134
-
button name not visible
- Why it matters: User cannot get help explaining a button
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (ASLint)
- Violations: 6
- Violators: 6
-
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
-
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: 5
- Violators: 5
-
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: 1
- Violators: 1
-
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 1 rule engine (QualWeb)
- Violations: 1
- Violators: 1
-
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: 4
- Violators: 4
-
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: 4
- Violators: 4
-
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
-
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: 2
- Violators: 2
-
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: 19
- Violators: 19
-
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
-
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: 36
- Violators: 36
-
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: 11
- Violators: 11
-
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: 5
- Violators: 5