Skip to content
https://www.paloaltonetworks.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
D
Landmark Structure
Action
8 landmarks
FIX
8 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
5 <nav> landmark(s) found
Warning::
2 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "whole" SEARCH MAIN (missing!) CONTENTINFO footer

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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

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 ✗
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
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: #8ad3de
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 5 <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
Form Accessibility
Action
9 of 11 controls have issues
REVIEW
9 of 11 controls have issues
Critical::
9 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>
Info::
2 control(s) properly labeled
11 controls
2 labeled
0 placeholder only
9 unlabeled
ControlTypeLabelMethod
#mobile_anchor_nav_id_c0f9e150-da38-4645-b732-711582971777selectnone
#PAN_FOOTER_EMAIL_FIELDtextEnter your email now to subscribe!none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

C
Favicon & Branding
Action
17 icon(s) detected
REVIEW
17 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
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Your modern workspace that stops evasive…
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 AI and agents, and safely enables work f…
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 RECOMMENDED
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 A new
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 is here
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Platformization empowers you to harness …
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Introducing the Platforms, powered by Pr…
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 speed and scale.
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Intelligence-driven.
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Response-ready.
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Secure whatever,
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 whenever, wherever —
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 with less complexity.
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our customers are securing their
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trusted by
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Here for you.
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Here for
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Staying ahead demands
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 you can trust.
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get the latest news, invites to events, …
1.04:1
#000000
on
#060606
needs 3.0:1 (large text)
24px · bottom of viewport

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Your modern workspac…1.04:13.0:1
#000000
#060606
Fail
h2 AI and agents, and s…1.04:13.0:1
#000000
#060606
Fail
h2 RECOMMENDED1.04:13.0:1
#000000
#060606
Fail
h2 A new1.04:13.0:1
#000000
#060606
Fail
h2 is here1.04:13.0:1
#000000
#060606
Fail
h2 Platformization empo…1.04:13.0:1
#000000
#060606
Fail
h2 Introducing the Plat…1.04:13.0:1
#000000
#060606
Fail
h2 speed and scale.1.04:13.0:1
#000000
#060606
Fail
h2 Intelligence-driven.1.04:13.0:1
#000000
#060606
Fail
h2 Response-ready.1.04:13.0:1
#000000
#060606
Fail
h2 Secure whatever,1.04:13.0:1
#000000
#060606
Fail
h2 whenever, wherever …1.04:13.0:1
#000000
#060606
Fail
h2 with less complexity…1.04:13.0:1
#000000
#060606
Fail
h2 Our customers are se…1.04:13.0:1
#000000
#060606
Fail
h2 Trusted by1.04:13.0:1
#000000
#060606
Fail
h2 Here for you.1.04:13.0:1
#000000
#060606
Fail
h2 Here for1.04:13.0:1
#000000
#060606
Fail
h2 Staying ahead demand…1.04:13.0:1
#000000
#060606
Fail
h2 you can trust.1.04:13.0:1
#000000
#060606
Fail
h2 Get the latest news,…1.04:13.0:1
#000000
#060606
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+
Heading Hierarchy
62 headings
PASS
62 headings
Info::
Single H1 present
  • H1 The Most Secure Browser Built for the Agentic AI Era
  • H2 Your modern workspace that stops evasive threats, controls AI and agents, and safely enables work from anywhere.
  • H2 RECOMMENDED
  • H3 Introducing Prisma AIRS 3.0
  • H3 Defining the future of AI and quantum
  • H3 Palo Alto Networks Announces Intent to Acquire Koi to Secure the Agentic Endpoint
  • H3 Attacks are happening 4x faster. Are you ready?
  • H3 Unit 42 MSIAM 2.0 is here: The 24/7 managed SOC.
  • H3 Symphony 2026: The Agentic SOC Summit
  • H3 Prisma® AIRS™: Secure your AI at scale. Deploy Bravely.
  • H3 Quantum-Safe Summit: Secure today. Ready for tomorrow.
  • H3 Ignite: What’s Next. The future of security is here
  • H2 A new AI world is here
  • H3 AI is rapidly transforming your organization
  • H3 ~1.5X growth
  • H3 development
  • H3 INCREASE IN EXPLOITED ZERO DAYS (YoY, 2023)
  • H3 INCREASE IN RANSOMWARE ATTACKS (YoY, 2023)
  • H3 INCREASE IN DATA BREACHES AND LEAKS (YoY, 2023)
  • H3 Attackers are supercharging their speed and scale.
  • H2 Platformization empowers you to harness AI-ready infrastructure. And leverage services powered by Precision AI® to keep everything secure.
  • H3 90 % reduction in MTTR
  • H3 up to  30.9 B
  • H3 480 B endpoints scanned daily
  • H2 Introducing the Platforms, powered by Precision AI
  • H3 AI-powered Network Security
  • H3 AI-Driven Security Operations
  • H3 Real-Time Cloud Security
  • H2 So you can defend at speed and scale.
  • H3 1 T
  • H3 3.0 K
  • H3 250.0 K
  • H3 6.19 B
  • H3 8.59 M
  • H3 12.14 B
  • H2 Intelligence-driven. Response-ready.
  • H2 Secure whatever, whenever, wherever — with less complexity.
  • H2 Our customers are securing their digital transformation
  • H2 Trusted by the best
  • H2 Here for you. Here for what’s next.
  • H3 Ignite on Tour
  • H3 Executive Briefing Center
  • H3 Under Attack? We’re Here.
  • H3 AI-powered security platforms
  • H3 Product Demo Center
  • H3 Future-proof your Security
  • H3 Events Around the World
  • H3 Partner Portal
  • H3 Become a Partner
  • H3 Managed Services Program
  • H3 Customer Login
  • H3 Education and Training
  • H3 Customer Success Tools
  • H2 Staying ahead demands perspectives you can trust.
  • H3 Securing Your AI-Powered Network Transformation: A Guide for C-Suite Leaders
  • H3 A New Era of Cybersecurity with AI
  • H3 When It Comes to Cyber Resilience and AI, Be Sure to Stretch the Limits of Your Imagination
  • H3 Quarterly thought leadership on the issues that matter most to cybersecurity executives
  • H2 Get the latest news, invites to events, and threat alerts
  • H2 Products and Services
  • H2 Company
  • H2 Popular Links
A+
Alt Text Quality
All 137 images OK
PASS
All 137 images OK
Info::
28 decorative image(s) correctly marked
Info::
109 image(s) with good alt text
137 images 109 good alt text 28 decorative
All images have appropriate alt text.
A+
Lighthouse Accessibility Audits
Score 99/100 — 1 failing, 32 passed
PASS
99

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○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
●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.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●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 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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●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
○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
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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.
○Elements with visible text labels have matching accessible names.
○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