Skip to content
https://pg.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
66
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
13
6 PASS 2 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-6dqdng
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://pg.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://pg.com/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Back-to-top 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)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA
h1 Recognized as a 2026 Where You Work Matt…
2.21:1
#000000
on
#003DA5
needs 3.0:1 (large text)
32px · bottom of viewport
h2 READ OUR LATEST STORIES
2.21:1
#000000
on
#003DA5
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Products that make life a little easier
2.21:1
#000000
on
#003DA5
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Reducing our footprint one step at a tim…
2.21:1
#000000
on
#003DA5
needs 3.0:1 (large text)
24px · bottom of viewport
span Home page
2.20:1
#000000
on
#003DA4
needs 4.5:1 (normal text)
16px · top of page (header area)
span USA
2.21:1
#000000
on
#003DA5
needs 4.5:1 (normal text)
16px · top of page (header area)
span Our Brands
2.21:1
#000000
on
#003DA5
needs 4.5:1 (normal text)
16px · above the fold
span Brands
2.21:1
#000000
on
#003DA5
needs 4.5:1 (normal text)
16px · above the fold
span Innovation
2.21:1
#000000
on
#003DA5
needs 4.5:1 (normal text)
16px · above the fold
span Product Safety
2.21:1
#000000
on
#003DA5
needs 4.5:1 (normal text)
16px · above the fold
span Ingredients
2.21:1
#000000
on
#003DA5
needs 4.5:1 (normal text)
16px · above the fold
span Fragrance Ingredients
2.21:1
#000000
on
#003DA5
needs 4.5:1 (normal text)
16px · above the fold
span #BECRUELTYFREE
2.21:1
#000000
on
#003DA5
needs 4.5:1 (normal text)
16px · above the fold
span Our Impact
2.21:1
#000000
on
#003DA5
needs 4.5:1 (normal text)
16px · above the fold
span Community Impact
2.21:1
#000000
on
#003DA5
needs 4.5:1 (normal text)
16px · above the fold
span CSDW
2.21:1
#000000
on
#003DA5
needs 4.5:1 (normal text)
16px · mid-page
span Equality & Inclusion
2.21:1
#000000
on
#003DA5
needs 4.5:1 (normal text)
16px · mid-page
span Gender
2.21:1
#000000
on
#003DA5
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Recognized as a 2026…2.21:13.0:1
#000000
#003DA5
Fail
h2 READ OUR LATEST STOR…2.21:13.0:1
#000000
#003DA5
Fail
h2 Products that make l…2.21:13.0:1
#000000
#003DA5
Fail
h2 Reducing our footpri…2.21:13.0:1
#000000
#003DA5
Fail
title Procter & Gamble21.00:14.5:1
#000000
#FFFFFF
Pass
span Skip to main content21.00:14.5:1
#000000
#FFFFFF
Pass
span Home page2.20:14.5:1
#000000
#003DA4
Fail
span USA2.21:14.5:1
#000000
#003DA5
Fail
span Our Brands2.21:14.5:1
#000000
#003DA5
Fail
span Brands2.21:14.5:1
#000000
#003DA5
Fail
span Innovation2.21:14.5:1
#000000
#003DA5
Fail
span Product Safety2.21:14.5:1
#000000
#003DA5
Fail
span Ingredients2.21:14.5:1
#000000
#003DA5
Fail
span Fragrance Ingredient…2.21:14.5:1
#000000
#003DA5
Fail
span #BECRUELTYFREE2.21:14.5:1
#000000
#003DA5
Fail
span Our Impact2.21:14.5:1
#000000
#003DA5
Fail
span Community Impact2.21:14.5:1
#000000
#003DA5
Fail
span CSDW2.21:14.5:1
#000000
#003DA5
Fail
span Equality & Inclusion2.21:14.5:1
#000000
#003DA5
Fail
span Gender2.21:14.5:1
#000000
#003DA5
Fail

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+
Landmark Structure
6 landmarks
PASS
6 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 "Main Navigation" MAIN ASIDE CONTENTINFO footer
A+
Heading Hierarchy
4 headings
PASS
4 headings
Info::
Single H1 present
  • H1 Recognized as a 2026 Where You Work Matters Platinum Employer
  • H2 READ OUR LATEST STORIES
  • H2 Products that make life a little easier
  • H2 Reducing our footprint one step at a time
A
Alt Text Quality
1 of 45 images have issues
PASS
1 of 45 images have issues
Warning::
1 image(s) with generic alt text
Info::
2 image(s) with alt text over 125 characters
Info::
22 decorative image(s) correctly marked
Info::
20 image(s) with good alt text
45 images 20 good alt text 22 decorative 1 generic
IssueCount
generic1 image(s)
too long2 image(s)
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#6ksJIHiOacMiUIGWiIs68MsearchSearch herefor/id
A+
Lighthouse Accessibility Audits
Score 96/100 — 2 failing, 24 passed
PASS
96

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Contact Careers Partners & Investors Investors Partner with us Suppliers Our Co… li#global-navigation > ul.navigation__group__items > li#global-navigation-footer > ul.navigation__group__items

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
4/22/2026 Inspiring More Sustainable Habits Through Thoughtful Design and Inno… div.slick-track > div.slick-slide > div > a.blog-item
See our efforts div.hp-msg > div.hp-msg__wrapper > div.hp-msg__content > a.external-link
○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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○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
○`<frame>` or `<iframe>` elements have a title
○`<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