Issues reported for Human Rights Watch home

About the page

URL: https://www.hrw.org/
Tested 30 days ago on 2026-10-11 at 22:57 by job 261011T2252-61q
Rule engines: 12 called, 11 able to test, violations reported by 10
Results: 2049 violations, 1063 violators, 62 issues
Download the full technical report (JSON)

History

34 days ago (oldest)
30 days ago (latest; this report)

Request a retest

Issues reported

Highest priority: 16

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 + Axe + HTML CodeSniffer + Pour + SureA11y + WAVE)
- Results: 16 violations, 8 violators
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 API + HTML CodeSniffer + QualWeb)
- Results: 54 violations, 33 violators
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)
- Results: 40 violations, 40 violators
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 (ASLint + HTML CodeSniffer)
- Results: 2 violations, 2 violators
Where was the issue found?
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)
- Results: 4 violations, 3 violators
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 1 rule engine (Accessibility Checker)
- Results: 5 violations, 5 violators
Where was the issue found?
region not named
- Why it matters: User cannot get help surveying the parts of the page
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- Results: 6 violations, 6 violators
Where was the issue found?
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)
- Results: 1 violation, 1 violator
Where was the issue found?
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)
- Results: 2 violations, 2 violators
Where was the issue found?
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 API)
- Results: 24 violations, 24 violators
Where was the issue found?
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 API)
- Results: 16 violations, 9 violators
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 (Html Checker API)
- Results: 5 violations, 5 violators
Where was the issue found?
ID empty
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 3 violations, 3 violators
Where was the issue found?
presentation element has child
- Why it matters: Keyboard-only user cannot reach an item intended to be reachable
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 5 violations, 5 violators
Where was the issue found?
list child invalid
- Why it matters: User cannot get help on which items are in a list
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (SureA11y)
- Results: 10 violations, 10 violators
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)
- Results: 38 violations, 34 violators
Where was the issue found?

High priority: 16

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)
- Results: 3 violations, 2 violators
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 (Accessibility Checker + SureA11y)
- Results: 10 violations, 5 violators
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)
- Results: 7 violations, 6 violators
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 2 rule engines (Pour + SureA11y)
- Results: 90 violations, 46 violators
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)
- Results: 3 violations, 3 violators
Where was the issue found?
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 1 rule engine (Accessibility Checker)
- Results: 18 violations, 18 violators
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 (ASLint)
- Results: 2 violations, 2 violators
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 (Axe)
- Results: 20 violations, 20 violators
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)
- Results: 5 violations, 5 violators
Where was the issue found?
element closure invalid
- Why it matters: Page contains invalid code
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 5 violations, 1 violator
Where was the issue found?
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 API)
- Results: 1 violation, 1 violator
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)
- Results: 3 violations, 1 violator
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 (Html Checker API)
- Results: 4 violations, 4 violators
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)
- Results: 12 violations, 12 violators
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)
- Results: 53 violations, 53 violators
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)
- Results: 127 violations, 127 violators
Where was the issue found?

Low priority: 11

not exactly 1 h1 heading
- Why it matters: User cannot understand the topic of the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 3 rule engines (ASLint + Axe + Pour)
- Results: 3 violations, 1 violator
Where was the issue found?
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 2 rule engines (ASLint + Testaro)
- Results: 2 violations, 2 violators
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 1 rule engine (HTML CodeSniffer)
- Results: 2 violations, 1 violator
Where was the issue found?
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)
- Results: 1 violation, 1 violator
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)
- Results: 107 violations, 107 violators
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)
- Results: 4 violations, 1 violator
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)
- Results: 4 violations, 4 violators
Where was the issue found?
page content moves spontaneously
- Why it matters: Motion-sensitive user may suffer harm
- Priority: low
- Related WCAG standard: 2.2.2
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
Where was the issue found?
duplicate attribute
- Why it matters: Browser processes the page improperly
- Priority: low
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Testaro)
- Results: 6 violations, 4 violators
Where was the issue found?
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)
- Results: 1 violation, 1 violator
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)
- Results: 110 violations, 110 violators
Where was the issue found?

Lowest priority: 19

text contrast improvable
- Why it matters: Content is not easy to understand
- Priority: lowest
- Related WCAG standard: 1.4.6
- Reported by 6 rule engines (ASLint + Axe + HTML CodeSniffer + Pour + QualWeb + SureA11y)
- Results: 752 violations, 580 violators
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)
- Results: 49 violations, 34 violators
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)
- Results: 5 violations, 3 violators
Where was the issue found?
link name vague
- Why it matters: User may misunderstand what a link points to
- Priority: lowest
- Related WCAG standard: 2.4.4
- Reported by 2 rule engines (ASLint + Pour)
- Results: 4 violations, 4 violators
Where was the issue found?
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)
- Results: 56 violations, 56 violators
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)
- Results: 1 violation, 1 violator
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)
- Results: 11 violations, 7 violators
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)
- Results: 5 violations, 5 violators
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)
- Results: 1 violation, 1 violator
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)
- Results: 121 violations, 121 violators
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)
- Results: 1 violation, 1 violator
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)
- Results: 2 violations, 2 violators
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 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
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)
- Results: 33 violations, 33 violators
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)
- Results: 1 violation, 1 violator
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)
- Results: 80 violations, 80 violators
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)
- Results: 5 violations, 1 violator
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)
- Results: 49 violations, 49 violators
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)
- Results: 37 violations, 37 violators
Where was the issue found?

What you can do

Choose how to address these issues:

Do it yourself

Explore the issues, following the links above. Decide which issues are actual defects. Plan and implement corrections. Then retest the page.

Use artificial intelligence

Make Kilotest available to an AI assistant. Then give it a prompt like this:

Kilotest reports issues on the Human Rights Watch home web page. Describe them and propose a plan to resolve the genuine defects.

Issues reported for Human Rights Watch home

About the page

History

Issues reported

contrast poor

ID not unique

svg image not named

iframe not named

abbr title missing

aria reference invalid

region not named

focusable element hidden

requirement invalid

parent invalid

itemid invalid

attribute invalid

ID empty

presentation element has child

list child invalid

image not named

form submission button missing

visible label not in name

landmarks not distinctly named

target very small

forms not distinctly named

heading empty

autocomplete invalid

role invalid

code invalid

element closure invalid

summary has explicit role

invalid CSS at-rule

attribute obsolete

box size absolute

small targets too near to each other

element focusability and operability conflict

not exactly 1 h1 heading

link href missing

heading structure illogical

links not grouped as nav

line height low

links named identically

link indication poor

page content moves spontaneously

duplicate attribute

menu navigation nonstandard

focus indication improvable

text contrast improvable

tab-opening link action unstated?

role redundant

link name vague

button name not visible

title attribute empty

fieldset missing?

link destination not URL

position sticky

target small

aria attribute redundant

text contrast not testable

label location dubious

all-capital text

large visible-element count

role assigned instead of implicit

inconsistent heading, link, or button styles

title attribute invalid

z-index not zero

What you can do

Do it yourself

Use artificial intelligence