Ensemble front-end testing

Issues reported for Example home

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

About the page

URL: https://example.com
Tested 90 days ago on 2026-08-12 at 21:32 by job 260812T2131-thr
Rule engines: 10 called, 10 able to test, violations reported by 6
Results: 13 violations, 7 violators, 9 issues
Download the full technical report (JSON)

History

90 days ago (oldest; this report)
17 days ago
17 days ago (latest)

Issues reported

Highest priority: 0

None

High priority: 1

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 (Accessibility Checker)
- Results: 1 violation, 1 violator
Where was the issue found?

Low priority: 4

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: 2 violations, 1 violator
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 1 rule engine (Axe)
- Results: 1 violation, 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: 1 violation, 1 violator
Where was the issue found?
no landmarks
- Why it matters: User cannot get help on how the page is organized
- Priority: low
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (WAVE)
- Results: 1 violation, 1 violator
Where was the issue found?

Lowest priority: 4

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 2 rule engines (Accessibility Checker + Axe)
- Results: 3 violations, 3 violators
Where was the issue found?
text contrast improvable
- Why it matters: Content is not easy to understand
- Priority: lowest
- Related WCAG standard: 1.4.6
- Reported by 2 rule engines (Alfa + Axe)
- Results: 2 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 1 rule engine (Alfa)
- Results: 1 violation, 1 violator
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 (ASLint)
- Results: 1 violation, 1 violator
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 Example home web page. Describe them and propose a plan to resolve the genuine defects.