Issues reported for Donovan’s Venom home
About the page
- URL: https://www.thedonovan.org/
- Tested 24 days ago on 2026-10-18 at 05:21 by job
261018T0518-wr3 - Rule engines: 12 called, 12 able to test, violations reported by 12
- Results: 837 violations, 251 violators, 52 issues
- Download the full technical report (JSON)
History
This is the only available report about the page.
Issues reported
Highest priority: 11
-
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 4 rule engines (Accessibility Checker + Alfa + Axe + SureA11y)
- Results: 5 violations, 4 violators
-
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 3 rule engines (Accessibility Checker + Pour + SureA11y)
- Results: 3 violations, 1 violator
-
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: 5 violations, 3 violators
-
attribute invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (Accessibility Checker + Html Checker API)
- Results: 2 violations, 2 violators
-
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 (Accessibility Checker + WAVE)
- Results: 5 violations, 5 violators
-
figure not named
- Why it matters: User cannot get help on the topic of a figure
- Priority: highest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (Accessibility Checker)
- Results: 9 violations, 9 violators
-
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 1 rule engine (Editoria11y)
- Results: 1 violation, 1 violator
-
target empty
- Why it matters: Item is displayed improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
-
attribute missing
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
-
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)
- Results: 1 violation, 1 violator
-
contrast poor
- Why it matters: Content is difficult to understand
- Priority: highest
- Related WCAG standard: 1.4.3
- Reported by 1 rule engine (WAVE)
- Results: 1 violation, 1 violator
High priority: 12
-
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 3 rule engines (Alfa + Pour + SureA11y)
- Results: 18 violations, 11 violators
-
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 2 rule engines (Accessibility Checker + Axe)
- Results: 2 violations, 2 violators
-
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)
- Results: 11 violations, 9 violators
-
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)
- Results: 5 violations, 5 violators
-
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: 24 violations, 1 violator
-
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
-
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: 66 violations, 1 violator
-
table not marked as such
- Why it matters: Helper misinforms a user about whether items are cells of a table
- Priority: high
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
-
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: 7 violations, 7 violators
-
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: 2 violations, 2 violators
-
element beyond display when focused
- Why it matters: Keyboard-only user cannot navigate properly to the operable items
- Priority: high
- Related WCAG standard: 1.4.10
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
-
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)
- Results: 6 violations, 3 violators
Low priority: 11
-
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)
- Results: 2 violations, 1 violator
-
decorative element exposed
- Why it matters: Helper alerts a user to an uninformative image
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 2 violations, 2 violators
-
decorative element has title
- Why it matters: Hovering-produced information is denied to a keyboard-only user
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 1 violation, 1 violator
-
cell headers ambiguous?
- Why it matters: User may be unable to get help on relationships in a table
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Results: 4 violations, 4 violators
-
title long
- Why it matters: Hovering makes an overly verbose explanation pop up
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
-
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: 23 violations, 23 violators
-
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
-
table misused
- Why it matters: Helper misinforms a user about whether items are cells of a table
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
-
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
-
duplicate attribute
- Why it matters: Browser processes the page improperly
- Priority: low
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Testaro)
- Results: 3 violations, 2 violators
-
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: 11 violations, 11 violators
Lowest priority: 18
-
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: 227 violations, 64 violators
-
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)
- Results: 180 violations, 103 violators
-
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: 38 violations, 26 violators
-
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: 67 violations, 64 violators
-
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: 2 violations, 2 violators
-
role redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- Results: 1 violation, 1 violator
-
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: 1 violation, 1 violator
-
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: 14 violations, 7 violators
-
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: 3 violations, 3 violators
-
heading located in table
- Why it matters: Complex relationships in a table may confuse a user
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Editoria11y)
- Results: 1 violation, 1 violator
-
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: 1 violation, 1 violator
-
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: 1 violation, 1 violator
-
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
-
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: 28 violations, 28 violators
-
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
-
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: 1 violation, 1 violator
-
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: 32 violations, 32 violators
-
hovering changes content
- Why it matters: User cannot explore the page reliably with a mouse
- Priority: lowest
- Related WCAG standard: 3.2.5
- Reported by 1 rule engine (Testaro)
- Results: 2 violations, 2 violators
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 Donovan’s Venom home web page. Describe them and propose a plan to resolve the genuine defects.