Ensemble front-end testing

Issues reported for Internet Archive home

About the page

URL: https://archive.org/
Tested 34 days ago on 2026-10-07 at 21:51 by job 261007T2132-0in
Rule engines: 12 called, 7 able to test, violations reported by 6
Results: 412 violations, 33 violators, 18 issues
Download the full technical report (JSON)

History

This is the only available report about the page.

Request a retest

Issues reported

Highest priority: 6

svg image not named
- Why it matters: User cannot get help understanding an image
- Priority: highest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (Accessibility Checker)
- Results: 1 violation, 1 violator
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 (Accessibility Checker)
- Results: 2 violations, 1 violator
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 (Alfa)
- Results: 1 violation, 1 violator
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 1 rule engine (Alfa)
- Results: 5 violations, 4 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)
- Results: 2 violations, 2 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 1 rule engine (QualWeb)
- Results: 10 violations, 1 violator
Where was the issue found?

High priority: 5

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 3 rule engines (Accessibility Checker + Alfa + Axe)
- Results: 74 violations, 3 violators
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)
- Results: 3 violations, 3 violators
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 1 rule engine (Axe)
- Results: 1 violation, 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: 11 violations, 1 violator
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)
- Results: 4 violations, 3 violators
Where was the issue found?

Low priority: 3

heading level skipped
- Why it matters: Helper misdescribes the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (Alfa + Axe)
- Results: 2 violations, 2 violators
Where was the issue found?
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 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
Where was the issue found?
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
Where was the issue found?

Lowest priority: 4

text contrast improvable
- Why it matters: Content is not easy to understand
- Priority: lowest
- Related WCAG standard: 1.4.6
- Reported by 3 rule engines (Alfa + Axe + QualWeb)
- Results: 264 violations, 22 violators
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 2 rule engines (Accessibility Checker + Axe)
- Results: 2 violations, 1 violator
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: 26 violations, 17 violators
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, 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 Internet Archive home web page. Describe them and propose a plan to resolve the genuine defects.