Skip to content
https://symantec.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
D
Favicon & Branding
Action
4 icon(s) detected
FIX
4 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::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
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 ✗
C
Alt Text Quality
Action
9 of 19 images have issues
REVIEW
9 of 19 images have issues
Critical::
9 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
10 image(s) with good alt text
19 images 10 good alt text 9 missing
IssueCount
missing9 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title symantec.com has moved to broadcom.com ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Navigation UX
Action
2 navigation pattern(s)
REVIEW
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
9 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 9 <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.
A
Landmark Structure
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Info::
9 <nav> landmark(s) found
Warning::
8 of 9 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN CONTENTINFO footer

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

A
Heading Hierarchy
27 headings
PASS
27 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Info::
1 hidden heading(s) (aria-hidden)
  • H1 Data-Centric Hybrid Security
  • H1 Symantec Enterprise Cloud duplicate H1
  • H2 Continued innovation from a name you trust
  • H2 Threat and Data Protection Innovation
  • H2 Artificial Intelligence in Cybersecurity
  • H2 Leading Cybersecurity Portfolios
  • H2 Evolve Your Security with Your Organization
  • H3 Cross-Control Point, Cross-Platform
  • H3 Move to the Cloud on Your Timeline
  • H3 Great Security and User Experience
  • H2 Differentiated Intelligence
  • H2 Partner Ecosystem
  • H2 Connect with Our Experts
  • H2 Cookies
  • H2 Privacy Preference Center
  • H2 Privacy Preference Center hidden
  • H3 Your Privacy
  • H3 Strictly Necessary Cookies
  • H3 Functional Cookies
  • H3 Performance Cookies
  • H3 Targeting Cookies
  • H4 Your Privacy
  • H4 Strictly Necessary Cookies
  • H4 Functional Cookies
  • H4 Performance Cookies
  • H4 Targeting Cookies
  • H3 Cookie List

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Form Accessibility
All 9 controls labeled
PASS
All 9 controls labeled
Info::
9 control(s) properly labeled
9 controls
9 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
qtextSEARCHaria-label
#ot-group-id-3checkboxFunctional Cookiesfor/id
#ot-group-id-2checkboxPerformance Cookiesfor/id
#ot-group-id-4checkboxTargeting Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
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 Data-Centric Hybrid …19.60:13.0:1
#000000
#F7F7F7
Pass
h1 Symantec Enterprise …19.60:13.0:1
#000000
#F7F7F7
Pass
h2 Continued innovation…19.60:13.0:1
#000000
#F7F7F7
Pass
h2 Threat and Data Prot…19.60:13.0:1
#000000
#F7F7F7
Pass
h2 Artificial Intellige…19.60:13.0:1
#000000
#F7F7F7
Pass
h2 Leading Cybersecurit…19.60:13.0:1
#000000
#F7F7F7
Pass
h2 Evolve Your Security…19.60:13.0:1
#000000
#F7F7F7
Pass
h2 Differentiated Intel…19.60:13.0:1
#000000
#F7F7F7
Pass
h2 Partner Ecosystem19.60:13.0:1
#000000
#F7F7F7
Pass
h2 Connect with Our Exp…19.60:13.0:1
#000000
#F7F7F7
Pass
h2 Cookies19.60:13.0:1
#000000
#F7F7F7
Pass
h2 Privacy Preference C…19.60:13.0:1
#000000
#F7F7F7
Pass
h2 Privacy Preference C…19.60:13.0:1
#000000
#F7F7F7
Pass
h3 Cross-Control Point,…19.60:13.0:1
#000000
#F7F7F7
Pass
h3 Move to the Cloud on…19.60:13.0:1
#000000
#F7F7F7
Pass
h3 Great Security and U…19.60:13.0:1
#000000
#F7F7F7
Pass
h3 Your Privacy19.60:13.0:1
#000000
#F7F7F7
Pass
h3 Strictly Necessary C…19.60:13.0:1
#000000
#F7F7F7
Pass
h3 Functional Cookies19.60:13.0:1
#000000
#F7F7F7
Pass
h3 Performance Cookies19.60:13.0:1
#000000
#F7F7F7
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 92/100 — 3 failing, 27 passed
PASS
92

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookie Notice. div.ot-sdk-eight > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link

These are opportunities to improve the legibility of your content.

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.row > div.content-block-image > picture > img.image-source div.row > div.content-block-image > picture > img.image-source
div.row > div.content-block-image > picture > img.image-source div.row > div.content-block-image > picture > img.image-source
div.row > div.content-block-image > picture > img.image-source div.row > div.content-block-image > picture > img.image-source
div.ProductCard > div.row > div.col-lg-8 > img.image-source div.ProductCard > div.row > div.col-lg-8 > img.image-source
div.ProductCard > div.row > div.col-lg-8 > img.image-source div.ProductCard > div.row > div.col-lg-8 > img.image-source
div.ImageCard > div.card-body > div.lnk > img.image-source div.ImageCard > div.card-body > div.lnk > img.image-source
div.ImageCard > div.card-body > div.lnk > img.image-source div.ImageCard > div.card-body > div.lnk > img.image-source
div.ImageCard > div.card-body > div.lnk > img.image-source div.ImageCard > div.card-body > div.lnk > img.image-source

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.

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.ot-sdk-eight > 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
●`[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
●Elements use only permitted ARIA attributes
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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.
○`[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
○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.
○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