Issues reported for Dr. Catherine Akurut curriculum vitae
About the page
- URL: https://catherineakurut-cv.netlify.app/
- Tested 157 days ago on 2026-06-06 at 23:12 by job
260606T2311-pk7 - Rule engines: 10 called, 10 able to test, violations reported by 9
- Results: 834 violations, 253 violators, 25 issues
- Download the full technical report (JSON)
History
This is the only available report about the page.
Issues reported
Highest priority: 1
-
contrast poor
- Why it matters: Content is difficult to understand
- Priority: highest
- Related WCAG standard: 1.4.3
- Reported by 4 rule engines (Accessibility Checker + Alfa + Axe + WAVE)
- Results: 142 violations, 72 violators
High priority: 3
-
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 (Axe)
- Results: 2 violations, 2 violators
-
tab-opening link action unstated
- Why it matters: Following a link opens a new window, surprising a user
- Priority: high
- Related WCAG standard: 3.2.5
- Reported by 1 rule engine (Editoria11y)
- Results: 12 violations, 12 violators
-
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: 2 violations, 2 violators
Low priority: 5
-
links named identically
- Why it matters: User cannot get help differentiating links
- Priority: low
- Related WCAG standard: 2.4.4
- Reported by 2 rule engines (QualWeb + Testaro)
- Results: 21 violations, 11 violators
-
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: 3 violations, 3 violators
-
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: 12 violations, 12 violators
-
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)
- Results: 12 violations, 12 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: 25 violations, 25 violators
Lowest priority: 16
-
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: 433 violations, 192 violators
-
all-italic text
- Why it matters: Text is difficult to read
- Priority: lowest
- Related WCAG standard: 3.1.5
- Reported by 3 rule engines (Alfa + ASLint + Testaro)
- Results: 28 violations, 27 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 + HTML CodeSniffer + Testaro)
- Results: 39 violations, 26 violators
-
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: 21 violations, 21 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 1 rule engine (Alfa)
- Results: 2 violations, 2 violators
-
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: 8 violations, 4 violators
-
position sticky
- Why it matters: User may be unable to see needed content or may be forced to scroll in both dimensions
- Priority: lowest
- Related WCAG standard: 1.4.10
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
-
links dubiously share name
- Why it matters: User may be unable to get help differentiating links
- Priority: lowest
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (Axe)
- Results: 1 violation, 1 violator
-
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 (Axe)
- Results: 1 violation, 1 violator
-
link names a file instead of a purpose
- Why it matters: User may fail to understand what a link points to
- Priority: lowest
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (Editoria11y)
- Results: 1 violation, 1 violator
-
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: 6 violations, 6 violators
-
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: 49 violations, 49 violators
-
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
-
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: 5 violations, 5 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: 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: 6 violations, 6 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 Dr. Catherine Akurut curriculum vitae web page. Describe them and propose a plan to resolve the genuine defects.