Skip to content
https://walgreens.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
2
PASS
7
INFO
0
Checks
13
7 PASS 2 REVIEW 4 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Missing
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set Dark theme-color Not set CSS indicators Not detected

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found Inline @media print Not detected
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

A+
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Top navigation with the logo, search field, account and cart" MAIN CONTENTINFO footer
A
Heading Hierarchy
25 headings, 1 skip(s)
PASS
25 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Select a store to shop
  • H2 WAG10
  • H1 Walgreens: Pharmacy, Health & Wellness, Photo & More for You
  • H3 Offers just for you skipped
  • H2 To clip coupons, you'll need a myWalgreens membership.
  • H2 A healthy spring is blooming
  • H2 Because your health matters
  • H2 Custom photo gifts for Mom
  • H2 Deals of the Week
  • H3 Recently viewed items
  • H2 Buy again
  • H2 Explore more
  • H2 Featured categories
  • H2 Customer Service
  • H2 myWalgreens®
  • H2 Company Information
  • H2 Walgreens API/Affiliate Program
  • H2 Terms and Conditions
  • H2 Privacy & Security
  • H2 Walgreens Advertising Group
  • H2 Walgreens Clinical Trials
  • H2 Sell Your Pharmacy
  • H2 View all products by:
  • H2 Top photo products:
  • H2 PRICING PROMISE:

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A
Alt Text Quality
13 of 76 images have issues
PASS
13 of 76 images have issues
Warning::
13 image(s) with generic alt text
Info::
58 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
76 images 5 good alt text 58 decorative 13 generic
IssueCount
generic13 image(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ntt-placeholderinputSearch by keyword or item numberaria-label
#store-header-searchtextEnter city, state or ZIP codearia-label
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Walgreens
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name Walgreens 192×192 icon 512×512 icon Start URL https://www.walgreens.com Display Mode standalone
Name Walgreens Display Mode standalone Theme Color #02a0c0 Background Color #02a0c0 Icons 2 icon(s)
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Walgreens: Pharmacy,…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Select a store to sh…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 WAG1021.00:13.0:1
#000000
#FFFFFF
Pass
h2 To clip coupons, you…21.00:13.0:1
#000000
#FFFFFF
Pass
title Walgreens: Pharmacy,…18.79:14.5:1
#000000
#F4F2EF
Pass
a Skip to main content20.14:14.5:1
#000000
#FBFAF9
Pass
strong Get $7 in rewards* o…21.00:13.0:1
#000000
#FFFFFF
Pass
strong Shop Deals of the We…21.00:13.0:1
#000000
#FFFFFF
Pass
strong Up to 60% OFF Cleara…21.00:13.0:1
#000000
#FFFFFF
Pass
span Nearest store21.00:14.5:1
#000000
#FFFFFF
Pass
strong 151 N State St, Chic…21.00:13.0:1
#000000
#FFFFFF
Pass
p We see you have a sh…21.00:14.5:1
#000000
#FFFFFF
Pass
strong Update store21.00:13.0:1
#000000
#FFFFFF
Pass
strong Account21.00:13.0:1
#000000
#FFFFFF
Pass
span Menu21.00:14.5:1
#000000
#FFFFFF
Pass
strong Account21.00:13.0:1
#000000
#FFFFFF
Pass
a Sign in21.00:14.5:1
#000000
#FFFFFF
Pass
a Create an account21.00:14.5:1
#000000
#FFFFFF
Pass
a Your Account21.00:14.5:1
#000000
#FFFFFF
Pass
a Walgreens Cash Rewar…21.00:14.5:1
#000000
#FFFFFF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 27 passed
PASS
94

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Offers just for you div.wag-glider-header > div.header > div > h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.dow-product-rec-card > a#dow-card-817480-0 > div.product__img > img
div.dow-product-rec-card > a#dow-card-817481-1 > div.product__img > img
div.dow-product-rec-card > a#dow-card-817482-2 > div.product__img > img
div.dow-product-rec-card > a#dow-card-817483-3 > div.product__img > img
div.dow-product-rec-card > a#dow-card-817557-4 > div.product__img > img
div.dow-product-rec-card > a#dow-card-817558-5 > div.product__img > img
div.dow-product-rec-card > a#dow-card-817559-6 > div.product__img > img
div.dow-product-rec-card > a#dow-card-817708-7 > div.product__img > img
div.dow-product-rec-card > a#dow-card-817709-8 > div.product__img > img
div.dow-product-rec-card > a#dow-card-817710-9 > div.product__img > img
div.dow-product-rec-card > a#dow-card-817761-10 > div.product__img > img
div.dow-product-rec-card > a#dow-card-817763-11 > div.product__img > img
div.dow-product-rec-card > a#dow-card-817762-13 > div.product__img > img

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback