Kilotest: Issues reported for Water for People

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 Water for People web page. Summarize them and propose a plan to resolve the genuine ones.

URL: https://www.waterforpeople.org/
Tested 2 days ago on 2026-10-07 at 23:26 by job 261007T2306-eav
Summary of results:
- Rule engines:
  - Called: 12
  - Were able to test: 12
  - Reported any rule violations: 12
- Violations: 1506
- Violators: 473
- Issues: 70
Download the full technical report (JSON)

History

This is the only report about the page.

Should Kilotest retest the page?

Issues reported

Highest priority: 19

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 10 rule engines (Accessibility Checker + Alfa + Axe + Editoria11y + Html Checker + HTML CodeSniffer + Pour + QualWeb + SureA11y + WAVE)
- Violations: 18
- Violators: 7
- Where was the issue found?
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: 47
- Violators: 18
- 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 6 rule engines (Accessibility Checker + Alfa + Axe + Pour + SureA11y + WAVE)
- Violations: 34
- Violators: 14
- Where was the issue found?
attribute invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 4 rule engines (Accessibility Checker + Axe + Html Checker + SureA11y)
- Violations: 46
- Violators: 40
- Where was the issue found?
image 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 4 rule engines (Editoria11y + HTML CodeSniffer + QualWeb + WAVE)
- Violations: 4
- Violators: 2
- 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)
- Violations: 5
- Violators: 5
- 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 2 rule engines (Pour + WAVE)
- Violations: 2
- Violators: 1
- 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: 6
- Violators: 6
- 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 1 rule engine (Alfa)
- Violations: 38
- Violators: 38
- Where was the issue found?
internal link broken
- Why it matters: User cannot reach a promised page location
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Violations: 1
- Violators: 1
- 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: 2
- Violators: 1
- Where was the issue found?
control label invisible
- Why it matters: User cannot understand how to operate a form item
- Priority: highest
- Related WCAG standard: 2.4.6
- Reported by 1 rule engine (Axe)
- 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)
- Violations: 4
- Violators: 4
- Where was the issue found?
target empty
- Why it matters: Item is displayed improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Violations: 75
- Violators: 75
- 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)
- Violations: 9
- Violators: 9
- Where was the issue found?
link element misplaced
- Why it matters: Page fails to get a needed external resource
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Violations: 3
- Violators: 3
- 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 (HTML CodeSniffer)
- Violations: 2
- Violators: 2
- 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 (HTML CodeSniffer)
- Violations: 1
- 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: 4
- Violators: 4
- Where was the issue found?

High priority: 17

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: 49
- Violators: 13
- 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 5 rule engines (Accessibility Checker + Alfa + Axe + QualWeb + SureA11y)
- Violations: 10
- Violators: 5
- 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 3 rule engines (ASLint + HTML CodeSniffer + QualWeb)
- Violations: 3
- Violators: 2
- 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: 21
- Violators: 20
- 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 (Alfa + Pour)
- Violations: 18
- Violators: 18
- Where was the issue found?
focusable element not active
- Why it matters: Keyboard-only user cannot navigate properly to the operable items
- Priority: high
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Axe + QualWeb)
- Violations: 14
- Violators: 8
- Where was the issue found?
skip method missing or invalid
- Why it matters: Keyboard-only user cannot easily reach the specific content of the page
- Priority: high
- Related WCAG standard: 2.4.1
- Reported by 2 rule engines (Axe + WAVE)
- 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: 2
- Violators: 2
- 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?
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: 15
- Violators: 9
- Where was the issue found?
animation long or repetitive
- Why it matters: Motion-sensitive user may suffer harm
- Priority: high
- Related WCAG standard: 2.2.2
- Reported by 1 rule engine (ASLint)
- Violations: 1
- Violators: 1
- 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)
- Violations: 39
- 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)
- 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)
- Violations: 9
- Violators: 9
- 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)
- Violations: 9
- Violators: 9
- 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: 13
- Violators: 13
- Where was the issue found?

Low priority: 10

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: 20
- Violators: 10
- Where was the issue found?
fieldset missing
- Why it matters: User cannot get help recognizing a group of related form items
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (Accessibility Checker + Testaro)
- Violations: 12
- Violators: 6
- 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: 13
- Violators: 13
- Where was the issue found?
main missing
- 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 2 rule engines (Axe + Pour)
- Violations: 2
- Violators: 1
- 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)
- Violations: 14
- Violators: 11
- 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: 6
- Violators: 6
- Where was the issue found?
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 1 rule engine (Pour)
- Violations: 2
- Violators: 2
- 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: 2
- 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: 15
- Violators: 15
- 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: 73
- Violators: 73
- Where was the issue found?

Lowest priority: 24

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: 159
- Violators: 61
- 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 4 rule engines (Accessibility Checker + Alfa + Axe + Pour)
- Violations: 227
- Violators: 180
- 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: 23
- Violators: 20
- 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?
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: 87
- Violators: 78
- 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)
- Violations: 6
- Violators: 6
- 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)
- Violations: 2
- Violators: 2
- 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: 6
- Violators: 6
- 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?
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: 41
- Violators: 41
- Where was the issue found?
aria-label on non-labelable role
- Why it matters: User is misinformed about an item
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Violations: 40
- Violators: 40
- 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: 8
- Violators: 8
- 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: 5
- Violators: 5
- 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)
- Violations: 4
- Violators: 4
- 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 1 rule engine (QualWeb)
- Violations: 6
- Violators: 6
- 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)
- Violations: 8
- Violators: 8
- 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: 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: 125
- Violators: 125
- 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?
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: 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: 22
- Violators: 22
- 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: 6
- 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: 17
- Violators: 17
- 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: 37
- Violators: 37
- Where was the issue found?

Kilotest: Issues reported for Water for People

About the tests

Do it yourself

Or use AI

History

Issues reported

image not named

link not named

contrast poor

attribute invalid

image link not named

svg image not named

control not named

no role-required name

aria attribute invalid

internal link broken

invalid landmark child of navigation role

control label invisible

attribute value invalid

target empty

ID empty

link element misplaced

button not named

input not named

Tab-focusable elements wrong

heading empty

visible label not in name

form submission button missing

small targets too near to each other

target very small

focusable element not active

skip method missing or invalid

code obsolete

forms not distinctly named

role invalid

animation long or repetitive

invalid CSS at-rule

CSS invalid

code invalid

attribute obsolete

input has placeholder instead of name

element focusability and operability conflict

heading level skipped

fieldset missing

heading structure illogical

main missing

font size absolute

heading heads nothing

legend missing

links named identically

link indication poor

focus indication improvable

text contrast improvable

content beyond landmarks

tab-opening link action unstated?

role redundant

target small

link name vague

button name not visible

fieldset missing?

labeling risky

link destination not URL

aria-label on non-labelable role

aria attribute redundant

tabindex redundant

text contrast not testable

event not keyboard-triggerable?

label location dubious

container size unit not percentage

all-capital text

large visible-element count

double br use dubious

role assigned instead of implicit

inconsistent heading, link, or button styles

title attribute invalid

z-index not zero