Issues reported for Hesperian Health Guides home

Warning: This report is not the latest about the page. See history below.

About the page

URL: https://hesperian.org/
Tested 166 days ago on 2026-05-28 at 23:15 by job 260528T2254-glp
Rule engines: 10 called, 10 able to test, violations reported by 10
Results: 1003 violations, 317 violators, 62 issues
Download the full technical report (JSON)

History

166 days ago (oldest; this report)
76 days ago
34 days ago (latest)

Issues reported

Highest priority: 12

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 6 rule engines (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + QualWeb + WAVE)
- Results: 22 violations, 6 violators
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 5 rule engines (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + WAVE)
- Results: 34 violations, 21 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 (Alfa + ASLint + Html Checker API + HTML CodeSniffer)
- Results: 77 violations, 25 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: 10 violations, 10 violators
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)
- Results: 27 violations, 5 violators
Where was the issue found?
CSS bans page rotation
- Why it matters: User must read sideways after rotating a device
- Priority: highest
- Related WCAG standard: 1.3.4
- Reported by 1 rule engine (ASLint)
- Results: 2 violations, 1 violator
Where was the issue found?
text in Private Use Area
- Why it matters: User cannot read all of the text
- Priority: highest
- Related WCAG standard: 3.1.3
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
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: 12 violations, 12 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: 3 violations, 3 violators
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)
- Results: 1 violation, 1 violator
Where was the issue found?
parent missing
- Why it matters: Keyboard-only user cannot operate a custom tool
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 10 violations, 10 violators
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)
- Results: 1 violation, 1 violator
Where was the issue found?

High priority: 10

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)
- Results: 2 violations, 2 violators
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)
- Results: 1 violation, 1 violator
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 (Axe)
- Results: 1 violation, 1 violator
Where was the issue found?
CSS property does not exist
- Why it matters: Page cannot be properly displayed
- 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?
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)
- Results: 4 violations, 2 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: 48 violations, 1 violator
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 1 rule engine (HTML CodeSniffer)
- Results: 1 violation, 1 violator
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 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
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: 2 violations, 2 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: 13 violations, 13 violators
Where was the issue found?

Low priority: 13

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 API + WAVE)
- Results: 8 violations, 4 violators
Where was the issue found?
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 4 rule engines (ASLint + Axe + Html Checker API + WAVE)
- Results: 4 violations, 3 violators
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 2 rule engines (Alfa + Testaro)
- Results: 15 violations, 14 violators
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 2 rule engines (Axe + Testaro)
- Results: 19 violations, 18 violators
Where was the issue found?
image alt long
- Why it matters: Helper gives a user an overly verbose explanation of an image
- Priority: low
- Related WCAG standard: 1.1.1
- Reported by 2 rule engines (Editoria11y + WAVE)
- Results: 3 violations, 2 violators
Where was the issue found?
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)
- Results: 7 violations, 5 violators
Where was the issue found?
line height absolute
- Why it matters: User cannot adjust the line height of text for readability
- Priority: low
- Related WCAG standard: 1.4.12
- Reported by 1 rule engine (Alfa)
- Results: 3 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: 4 violations, 3 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: 1 violation, 1 violator
Where was the issue found?
semantic properties represented with styles
- Why it matters: User cannot get help to fully understand the text
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- Results: 2 violations, 2 violators
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: 44 violations, 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: 47 violations, 47 violators
Where was the issue found?
adjacent links not combined
- Why it matters: Keyboard-only user expends extra effort to skip a link
- Priority: low
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (WAVE)
- Results: 1 violation, 1 violator
Where was the issue found?

Lowest priority: 27

text contrast improvable
- Why it matters: Content is not easy to understand
- Priority: lowest
- Related WCAG standard: 1.4.6
- Reported by 5 rule engines (Alfa + ASLint + Axe + HTML CodeSniffer + QualWeb)
- Results: 52 violations, 39 violators
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 3 rule engines (Accessibility Checker + Alfa + Axe)
- Results: 89 violations, 44 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 + HTML CodeSniffer + Testaro)
- Results: 9 violations, 6 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 + Html Checker API)
- Results: 11 violations, 6 violators
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 2 rule engines (HTML CodeSniffer + QualWeb)
- Results: 24 violations, 19 violators
Where was the issue found?
event not keyboard-triggerable?
- Why it matters: Keyboard-only user may be unable to perform an action
- Priority: lowest
- Related WCAG standard: 2.1.1
- Reported by 2 rule engines (HTML CodeSniffer + WAVE)
- Results: 6 violations, 2 violators
Where was the issue found?
no option focusable
- Why it matters: Keyboard-only user cannot choose an option
- Priority: lowest
- Related WCAG standard: 2.1.1
- Reported by 1 rule engine (Accessibility Checker)
- Results: 2 violations, 2 violators
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 (Alfa)
- Results: 6 violations, 6 violators
Where was the issue found?
item makes testing inconclusive
- Why it matters: Item prevents a conclusive accessibility test
- Priority: lowest
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Alfa)
- Results: 10 violations, 5 violators
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)
- Results: 2 violations, 2 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: 23 violations, 3 violators
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 (ASLint)
- Results: 20 violations, 20 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: 1 violation, 1 violator
Where was the issue found?
type redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 8 violations, 8 violators
Where was the issue found?
section heading missing
- Why it matters: User cannot understand the topic of a part of the page
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
Where was the issue found?
heading-like styles dubious
- Why it matters: User may be unable to understand the topic of a part of the page
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 1 violation, 1 violator
Where was the issue found?
overflow hidden?
- Why it matters: User may be unable to enlarge the text for readability
- Priority: lowest
- Related WCAG standard: 1.4.4
- Reported by 1 rule engine (QualWeb)
- Results: 53 violations, 53 violators
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: 66 violations, 66 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?
text distortion
- Why it matters: Text is difficult to read
- Priority: lowest
- Related WCAG standard: 3.1.5
- Reported by 1 rule engine (Testaro)
- Results: 11 violations, 11 violators
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)
- 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: 6 violations, 6 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: 3 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: 70 violations, 70 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: 93 violations, 93 violators
Where was the issue found?
noscript element not equivalent?
- Why it matters: User who has disabled JavaScript may be denied some content
- Priority: lowest
- Related WCAG standard: 4.1
- Reported by 1 rule engine (WAVE)
- Results: 1 violation, 1 violator
Where was the issue found?
title attribute redundant
- Why it matters: Helper repeats the explanation of an item
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (WAVE)
- Results: 1 violation, 1 violator
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 Hesperian Health Guides home web page. Describe them and propose a plan to resolve the genuine defects.

Issues reported for Hesperian Health Guides home

About the page

History

Issues reported

link not named

contrast poor

ID not unique

svg image not named

invalid landmark child of navigation role

CSS bans page rotation

text in Private Use Area

attribute invalid

parent invalid

attribute value invalid

parent missing

Tab-focusable elements wrong

navigations not distinctly named

h1 not 1st heading

landmarks not distinctly named

CSS property does not exist

CSS invalid

code invalid

visible label not in name

element obsolete

small targets too near to each other

element focusability and operability conflict

heading level skipped

not exactly 1 h1 heading

line height low

link indication poor

image alt long

font size absolute

line height absolute

heading structure illogical

links named identically

semantic properties represented with styles

duplicate attribute

focus indication improvable

adjacent links not combined

text contrast improvable

content beyond landmarks

tab-opening link action unstated?

role redundant

text contrast not testable

event not keyboard-triggerable?

no option focusable

target small

item makes testing inconclusive

false aria-hidden value risky

title attribute empty

tabindex redundant

link destination not URL

type redundant

section heading missing

heading-like styles dubious

overflow hidden?

all-capital text

large visible-element count

text distortion

double br use dubious

role assigned instead of implicit

inconsistent heading, link, or button styles

title attribute invalid

z-index not zero

noscript element not equivalent?

title attribute redundant

What you can do

Do it yourself

Use artificial intelligence