Issues reported for Charity Navigator home

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

About the page

URL: https://www.charitynavigator.org/
Tested 34 days ago on 2026-10-07 at 19:56 by job 261007T1941-rxh
Rule engines: 12 called, 12 able to test, violations reported by 11
Results: 712 violations, 294 violators, 48 issues
Download the full technical report (JSON)

History

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

Issues reported

Highest priority: 13

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)
- Results: 64 violations, 17 violators
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 7 rule engines (Alfa + Axe + HTML CodeSniffer + Pour + QualWeb + SureA11y + WAVE)
- Results: 13 violations, 5 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 6 rule engines (Accessibility Checker + Alfa + Axe + Pour + SureA11y + WAVE)
- Results: 14 violations, 7 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: 156 violations, 105 violators
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 (ASLint + HTML CodeSniffer + QualWeb + WAVE)
- Results: 46 violations, 28 violators
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 (Accessibility Checker + Pour + WAVE)
- Results: 3 violations, 3 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: 9 violations, 9 violators
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)
- Results: 8 violations, 8 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 2 rule engines (Html Checker API + WAVE)
- Results: 9 violations, 4 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: 31 violations, 31 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: 23 violations, 23 violators
Where was the issue found?
sizes 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?

High priority: 11

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?
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: 8 violations, 2 violators
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: 3 violations, 3 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: 2 violations, 2 violators
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: 23 violations, 1 violator
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: 3 violations, 3 violators
Where was the issue found?
font small
- Why it matters: Text is difficult to read
- Priority: high
- Related WCAG standard: 1.4
- Reported by 1 rule engine (Testaro)
- 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: 4 violations, 4 violators
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)
- 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: 23 violations, 23 violators
Where was the issue found?

Low priority: 7

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 + Pour)
- Results: 12 violations, 6 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 1 rule engine (Alfa)
- Results: 3 violations, 3 violators
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)
- 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: 5 violations, 4 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: 2 violations, 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: 53 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: 42 violations, 42 violators
Where was the issue found?

Lowest priority: 17

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)
- Results: 51 violations, 29 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: 3 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 2 rule engines (Alfa + Pour)
- Results: 37 violations, 33 violators
Where was the issue found?
element referenced by multiple labels
- Why it matters: User cannot get reliable help on the topics of form items
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + WAVE)
- Results: 4 violations, 3 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: 6 violations, 6 violators
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: 2 violations, 2 violators
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)
- Results: 2 violations, 2 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 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?
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)
- Results: 2 violations, 2 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: 6 violations, 6 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: 2 violations, 2 violators
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: 4 violations, 4 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?
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: 11 violations, 11 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 Charity Navigator home web page. Describe them and propose a plan to resolve the genuine defects.

Issues reported for Charity Navigator home

About the page

History

Issues reported

link not named

button not named

contrast poor

ID not unique

image link not named

control not named

svg image not named

internal link broken

image not named

attribute invalid

attribute value invalid

sizes attribute invalid

ID empty

h1 not 1st heading

CSS property does not exist

CSS invalid

attribute obsolete

code invalid

invalid CSS at-rule

box size absolute

font small

small targets too near to each other

input has placeholder instead of name

element focusability and operability conflict

heading level skipped

line height low

heading heads nothing

heading structure illogical

links named identically

duplicate attribute

focus indication improvable

text contrast improvable

tab-opening link action unstated?

target small

element referenced by multiple labels

button name not visible

fieldset missing?

labeling risky

link name vague

text contrast not testable

label location dubious

container size unit not percentage

all-capital text

large visible-element count

text distortion

role assigned instead of implicit

inconsistent heading, link, or button styles

z-index not zero

What you can do

Do it yourself

Use artificial intelligence