Issues reported for CVS home
About the page
- URL: https://www.cvs.com/
- Tested 5 days ago on 2026-11-06 at 04:34 by job
261106T0429-307 - Rule engines: 12 called, 9 able to test, violations reported by 8
- Results: 772 violations, 411 violators, 36 issues
- Download the full technical report (JSON)
History
- 188 days ago (oldest)
- 5 days ago (latest; this report)
Issues reported
Highest priority: 14
-
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 5 rule engines (Accessibility Checker + Alfa + Axe + Pour + SureA11y)
- Results: 10 violations, 6 violators
-
ID not unique
- Why it matters: User may be pointed to the wrong item
- Priority: highest
- Related WCAG standard: 4.1
- Reported by 3 rule engines (ASLint + HTML CodeSniffer + QualWeb)
- Results: 93 violations, 75 violators
-
aria reference invalid
- Why it matters: Item behavior violates user expectations
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Accessibility Checker)
- Results: 1 violation, 1 violator
-
attribute invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Accessibility Checker)
- Results: 9 violations, 9 violators
-
aria attribute missing
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- Results: 5 violations, 5 violators
-
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
-
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 (ASLint)
- Results: 2 violations, 2 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 (ASLint)
- Results: 2 violations, 2 violators
-
control label invisible
- Why it matters: User cannot understand how to operate a form item
- Priority: highest
- Related WCAG standard: 2.4.6
- Reported by 1 rule engine (Axe)
- Results: 1 violation, 1 violator
-
iframe not named
- Why it matters: User cannot get help on the topic of an embedded page
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 2 violations, 2 violators
-
link element misplaced
- Why it matters: Page fails to get a needed external resource
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 1 violation, 1 violator
-
button not named
- Why it matters: User cannot get help explaining a button
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 8 violations, 8 violators
-
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 1 rule engine (Pour)
- Results: 1 violation, 1 violator
-
interactive component not named
- Why it matters: User cannot get help understanding a custom item
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (SureA11y)
- Results: 1 violation, 1 violator
High priority: 7
-
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 5 rule engines (Accessibility Checker + Alfa + Axe + QualWeb + SureA11y)
- Results: 24 violations, 22 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 3 rule engines (Accessibility Checker + ASLint + Axe)
- Results: 14 violations, 14 violators
-
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 2 rule engines (Alfa + Pour)
- Results: 9 violations, 9 violators
-
font small
- Why it matters: Text is difficult to read
- Priority: high
- Related WCAG standard: 1.4
- Reported by 1 rule engine (Alfa)
- Results: 29 violations, 12 violators
-
form submission button missing
- Why it matters: User cannot easily submit a form
- Priority: high
- Related WCAG standard: 3.2.2
- Reported by 1 rule engine (ASLint)
- Results: 2 violations, 2 violators
-
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 (ASLint)
- Results: 1 violation, 1 violator
-
element 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 (QualWeb)
- Results: 1 violation, 1 violator
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: 3 violations, 2 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: 35 violations, 35 violators
-
line height absolute
- Why it matters: User cannot adjust the line height of text for readability
- Priority: low
- Related WCAG standard: 1.4.12
- Reported by 1 rule engine (Alfa)
- Results: 26 violations, 26 violators
-
link href missing
- Why it matters: Helper cannot properly explain a link to a user
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 2 violations, 2 violators
Lowest priority: 11
-
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: 71 violations, 41 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: 5 violations, 4 violators
-
role redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + Pour)
- Results: 28 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: 184 violations, 177 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 2 rule engines (ASLint + Pour)
- Results: 58 violations, 53 violators
-
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: 5 violations, 5 violators
-
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: 19 violations, 11 violators
-
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
-
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: 5 violations, 5 violators
-
aria attribute redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Pour)
- Results: 48 violations, 48 violators
-
tabindex redundant
- Why it matters: Revision risks interfering with navigation by a keyboard-only user
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Pour)
- Results: 64 violations, 64 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 CVS home web page. Describe them and propose a plan to resolve the genuine defects.