Skip to content
https://pwc.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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::
24 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 24 <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
Landmark Structure
Action
25 landmarks
REVIEW
25 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
24 <nav> landmark(s) found
Warning::
21 of 24 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Skip Links" MAIN (missing!) CONTENTINFO (missing!)

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 26 passed
REVIEW
88

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.

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Healthcare div.col-xs-12 > ul.secnav-tabs__navigation > li.active > a
Technology div.col-xs-12 > ul.secnav-tabs__navigation > li.secnav-tabs__tab > a
Technology, media and telecommunications div.col-xs-12 > ul.secnav-tabs__navigation > li.secnav-tabs__tab > a

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Menu div.slim-page-header-v2 > div.headerv2-container > header.slimheader-v2 > div#slim-hamburger

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to content body.basepage > nav#skipNav > a#skipToContent
Skip to footer body.basepage > nav#skipNav > a#skipToFooter
PwC homepage div.slim-page-header-v2 > div.headerv2-container > header.slimheader-v2 > a#logoUrl

These are opportunities to improve keyboard navigation in your application.

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
Cookie Notice div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-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
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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 are distinguishable without relying on color.
●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
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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.
○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
○Form elements have associated labels
○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
○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.
○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.
A+
Heading Hierarchy
19 headings
PASS
19 headings
Info::
Single H1 present
  • H1 PwC US – Audit, assurance, tax and consulting services
  • H2 We help cut through the AI noise. So you can solve the business problems that matter most.
  • H2 We help cut through the AI noise. So you can solve the business problems that matter most.
  • H2 Featured
  • H2 Leading through uncertainty in the age of AI
  • H2 Client case studies
  • H3 Rush
  • H3 Trimble
  • H3 Amazon Leo
  • H2 Grow your skills. Make your mark.
  • H3 At PwC, your ideas matter — and your growth does too. With the flexibility, support and experiences to help you move forward, so you can shape what’s next.
  • H2 Cookies: The choice is yours
  • H2 Cookies: The choice is yours
  • H3 Manage Consent Preferences
  • H4 Necessary Cookies
  • H4 Analytical/Performance Cookies
  • H4 Functional Cookies
  • H4 Marketing Cookies
  • H3 Cookie List
A+
Alt Text Quality
All 13 images OK
PASS
All 13 images OK
Info::
8 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
13 images 5 good alt text 8 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 11 controls have issues
PASS
1 of 11 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="searchfield" id="slimSearch">
Info::
10 control(s) properly labeled
11 controls
10 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#countrySearchtextFind a country or regionfor/id
inputsubmitSearcharia-label
#ot-group-id-2checkboxAnalytical/Performance Cookiesfor/id
#ot-group-id-3checkboxFunctional Cookiesfor/id
#ot-group-id-4checkboxMarketing Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#slimSearchtext(Search for industries, products, services and more)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="searchfield" id="slimSearch">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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 PwC US – Audit, as…19.54:13.0:1
#000000
#F5F7F8
Pass
h2 We help cut through …19.54:13.0:1
#000000
#F5F7F8
Pass
h2 solve the business p…19.54:13.0:1
#000000
#F5F7F8
Pass
h2 We help cut through …19.54:13.0:1
#000000
#F5F7F8
Pass
h2 solve the business p…19.54:13.0:1
#000000
#F5F7F8
Pass
h2 Featured19.54:13.0:1
#000000
#F5F7F8
Pass
h2 Leading through unce…19.54:13.0:1
#000000
#F5F7F8
Pass
h2 Client case studies19.54:13.0:1
#000000
#F5F7F8
Pass
h2 Grow your skills. Ma…19.54:13.0:1
#000000
#F5F7F8
Pass
h2 Cookies: The choice …19.54:13.0:1
#000000
#F5F7F8
Pass
h2 Cookies: The choice …19.54:13.0:1
#000000
#F5F7F8
Pass
h3 Rush19.54:13.0:1
#000000
#F5F7F8
Pass
h3 Trimble19.54:13.0:1
#000000
#F5F7F8
Pass
h3 Amazon Leo19.54:13.0:1
#000000
#F5F7F8
Pass
h3 At PwC, your ideas m…19.54:13.0:1
#000000
#F5F7F8
Pass
h3 Manage Consent Prefe…19.54:13.0:1
#000000
#F5F7F8
Pass
h3 Cookie List19.54:13.0:1
#000000
#F5F7F8
Pass
title PwC: Audit and assur…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to footer21.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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback