Kilotest: Issues reported for Partners in Health 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 Partners in Health contact web page. Summarize them and propose a plan to resolve the genuine ones.

URL: https://www.pih.org/contact
Tested 2 days ago on 2026-10-07 at 22:07 by job 261007T2147-1s2
Summary of results:
- Rule engines:
  - Called: 12
  - Were able to test: 12
  - Reported any rule violations: 11
- Violations: 613
- Violators: 208
- Issues: 56
Download the full technical report (JSON)

History

This is the only report about the page.

Should Kilotest retest the page?

Issues reported

Highest priority: 18

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 8 rule engines (Accessibility Checker + Alfa + ASLint + Axe + HTML CodeSniffer + Pour + QualWeb + SureA11y)
- Violations: 10
- Violators: 5
- 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: 7
- Violators: 3
- Where was the issue found?
meta bans zoom
- Why it matters: User cannot adjust the page size for readability
- Priority: highest
- Related WCAG standard: 1.4.4
- Reported by 6 rule engines (Alfa + ASLint + Axe + Pour + QualWeb + SureA11y)
- Violations: 6
- Violators: 2
- 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 3 rule engines (HTML CodeSniffer + Pour + WAVE)
- Violations: 6
- Violators: 5
- 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 2 rule engines (Accessibility Checker + WAVE)
- Violations: 6
- Violators: 3
- 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 2 rule engines (ASLint + HTML CodeSniffer)
- Violations: 2
- Violators: 2
- 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 2 rule engines (Html Checker + WAVE)
- Violations: 2
- Violators: 1
- Where was the issue found?
label not named
- Why it matters: User cannot get help on the topic of a form item
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Accessibility Checker)
- Violations: 3
- Violators: 3
- Where was the issue found?
dialog not named
- Why it matters: User cannot get help explaining a pop-up window
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (ASLint)
- Violations: 2
- Violators: 2
- Where was the issue found?
label reference invalid
- Why it matters: User cannot get help understanding an item in a form
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Violations: 3
- Violators: 2
- Where was the issue found?
meta charset declared too late
- Why it matters: Browser may display incorrect text
- Priority: highest
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- 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: 2
- Violators: 2
- 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)
- Violations: 2
- Violators: 2
- 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: 3
- Violators: 3
- Where was the issue found?
label referent ineligible
- Why it matters: User cannot get help understanding an item in a form
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- Violations: 3
- Violators: 3
- 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 1 rule engine (HTML CodeSniffer)
- Violations: 1
- Violators: 1
- 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?
aria attribute invalid
- Why it matters: Item behavior violates user expectations
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (SureA11y)
- Violations: 3
- Violators: 3
- Where was the issue found?

High priority: 16

group not named
- Why it matters: User cannot get help on the topic of a group of form items
- Priority: high
- Related WCAG standard: 4.1.2
- Reported by 3 rule engines (Accessibility Checker + Alfa + HTML CodeSniffer)
- Violations: 11
- Violators: 11
- 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 2 rule engines (ASLint + Html Checker)
- Violations: 5
- Violators: 5
- Where was the issue found?
label empty
- Why it matters: User cannot get help on the topics of form items
- Priority: high
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + WAVE)
- 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: 5
- Violators: 4
- 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: 4
- 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: 3
- Violators: 3
- 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: 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 (ASLint)
- Violations: 1
- Violators: 1
- Where was the issue found?
meta X-UA-Compatible incomplete
- Why it matters: Internet Explorer may display the page incorrectly
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- 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)
- 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: 2
- Violators: 2
- 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)
- Violations: 1
- Violators: 1
- 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: 29
- Violators: 29
- 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: 4
- Violators: 4
- Where was the issue found?
hover indication poor
- Why it matters: User cannot explore the page reliably with a mouse
- Priority: high
- Related WCAG standard: 2.4
- Reported by 1 rule engine (Testaro)
- Violations: 2
- Violators: 2
- 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 1 rule engine (WAVE)
- Violations: 1
- Violators: 1
- Where was the issue found?

Low priority: 8

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 4 rule engines (Accessibility Checker + ASLint + HTML CodeSniffer + QualWeb)
- Violations: 28
- Violators: 11
- Where was the issue found?
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
- 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: 4
- Violators: 4
- 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?
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 1 rule engine (ASLint)
- 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: 19
- Violators: 19
- 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: 6
- Violators: 6
- 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: 21
- Violators: 21
- Where was the issue found?

Lowest priority: 14

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: 126
- Violators: 67
- 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: 80
- Violators: 25
- 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: 69
- Violators: 46
- 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: 7
- Violators: 4
- 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: 56
- Violators: 56
- 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?
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
- 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: 4
- Violators: 4
- 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: 12
- Violators: 12
- 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: 2
- Violators: 2
- 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: 4
- 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: 18
- Violators: 18
- Where was the issue found?

Kilotest: Issues reported for Partners in Health contact

About the tests

Do it yourself

Or use AI

History

Issues reported

iframe not named

contrast poor

meta bans zoom

control not named

aria reference invalid

internal link broken

image not named

label not named

dialog not named

label reference invalid

meta charset declared too late

attribute value invalid

attribute invalid

ID empty

label referent ineligible

link not named

input not named

aria attribute invalid

group not named

attribute obsolete

label empty

landmarks not distinctly named

code obsolete

navigations not distinctly named

role invalid

autocomplete invalid

meta X-UA-Compatible incomplete

CSS invalid

code invalid

element closure invalid

small targets too near to each other

input has placeholder instead of name

hover indication poor

skip method missing or invalid

legend missing

heading level skipped

heading structure illogical

main missing

link href missing

line height low

link indication poor

focus indication improvable

text contrast improvable

content beyond landmarks

tab-opening link action unstated?

role redundant

target small

labeling risky

text contrast not testable

label location dubious

all-capital text

large visible-element count

double br use dubious

role assigned instead of implicit

inconsistent heading, link, or button styles

z-index not zero