Skip to content
https://fortinet.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Alt Text Quality
Action
21 of 71 images have issues
FIX
21 of 71 images have issues
Critical::
21 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
21 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
50 image(s) with good alt text
71 images 50 good alt text 21 missing
IssueCount
missing21 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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
No navigation patterns
FIX
No navigation patterns
Info::
11 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 11 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
18 landmarks
REVIEW
18 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (4 found)
A page should have only one <main> landmark.
Info::
11 <nav> landmark(s) found
Warning::
11 of 11 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
8 icon(s) detected
REVIEW
8 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, 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
h1 The New Security Reality
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h1 Shaped by AI
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h2 Born Integrated. Built Intelligent. Only…
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Close Security Gaps and Increase Network…
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest from Fortinet
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Fortify Your Network Through the Converg…
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Secure and Transform Your Business with …
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Delivering Unrivaled Security & Performa…
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Global Threat Protection Delivered Daily
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
24px · bottom of viewport
h2 IHG Hotels & Resorts Boosts IT Efficienc…
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Jersey Mikes Streamlines Secure Network…
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Fortinet Secure SD-WAN Provides Direct-t…
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Leading Global Provider of Packaging Sol…
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Largest Organizations Across the Wor…
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Upcoming Events
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Secure Networking
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Secure Networking
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Unified SASE
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Unified SASE
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Security Operations
2.63:1
#000000
on
#4F5153
needs 3.0:1 (large text)
19px · 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
h1 The New Security Rea…2.63:13.0:1
#000000
#4F5153
Fail
h1 Shaped by AI2.63:13.0:1
#000000
#4F5153
Fail
h2 Born Integrated. Bui…2.63:13.0:1
#000000
#4F5153
Fail
h2 Close Security Gaps …2.63:13.0:1
#000000
#4F5153
Fail
h2 Latest from Fortinet2.63:13.0:1
#000000
#4F5153
Fail
h2 Fortify Your Network…2.63:13.0:1
#000000
#4F5153
Fail
h2 Secure and Transform…2.63:13.0:1
#000000
#4F5153
Fail
h2 Delivering Unrivaled…2.63:13.0:1
#000000
#4F5153
Fail
h2 Global Threat Protec…2.63:13.0:1
#000000
#4F5153
Fail
h2 IHG Hotels & Resorts…2.63:13.0:1
#000000
#4F5153
Fail
h2 Jersey Mikes Streaml…2.63:13.0:1
#000000
#4F5153
Fail
h2 Fortinet Secure SD-W…2.63:13.0:1
#000000
#4F5153
Fail
h2 Leading Global Provi…2.63:13.0:1
#000000
#4F5153
Fail
h2 The Largest Organiza…2.63:13.0:1
#000000
#4F5153
Fail
h2 Upcoming Events2.63:13.0:1
#000000
#4F5153
Fail
h3 Secure Networking2.63:13.0:1
#000000
#4F5153
Fail
h3 Secure Networking2.63:13.0:1
#000000
#4F5153
Fail
h3 Unified SASE2.63:13.0:1
#000000
#4F5153
Fail
h3 Unified SASE2.63:13.0:1
#000000
#4F5153
Fail
h3 Security Operations2.63:13.0:1
#000000
#4F5153
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
23 headings
PASS
23 headings
Info::
Single H1 present
  • H1 The New Security Reality Shaped by AI
  • H2 Born Integrated. Built Intelligent. Only FortiAI.
  • H2 Close Security Gaps and Increase Network Performance
  • H2 Latest from Fortinet
  • H2 Fortify Your Network Through the Convergence of Networking and Security
  • H3 Secure Networking
  • H3 Secure Networking
  • H3 Unified SASE
  • H3 Unified SASE
  • H3 Security Operations
  • H3 Security Operations
  • H2 Secure and Transform Your Business with AI​
  • H2 Delivering Unrivaled Security & Performance through Innovation​
  • H2 Global Threat Protection Delivered Daily
  • H2 IHG Hotels & Resorts Boosts IT Efficiency Close to 60% with Fortinet Secure SD-WAN
  • H2 Jersey Mikes Streamlines Secure Network Management by Leveraging FortiSwitch Across 2,500+ Restaurants
  • H2 Fortinet Secure SD-WAN Provides Direct-to-AWS Connectivity for the British Columbia Automobile Association
  • H2 Leading Global Provider of Packaging Solutions Enhances Operational Efficiency Through Secure SD-WAN Architecture
  • H2 The Largest Organizations Across the World Trust Fortinet
  • H2 Upcoming Events
  • H3 Enterprise
  • H3 Small Mid-Sized Businesses
  • H3 Service Providers
A
Form Accessibility
1 of 7 controls have issues
PASS
1 of 7 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="q" id="desktop-seark">
Info::
6 control(s) properly labeled
7 controls
6 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#searchtextSearchfor/id
#news-progressbarrangeNews Slideraria-label
#customer-progressbarrangeCustomer Slideraria-label
#events-progressbarrangeEvents Slideraria-label
#emailemailEnter Email Addressfor/id
#emailemailEnter Email Addressfor/id
#desktop-searktext(Search)placeholder only

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

<input type="text" name="q" id="desktop-seark">

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+
Lighthouse Accessibility Audits
Score 97/100 — 2 failing, 28 passed
PASS
97

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
READ THE PRESS RELEASE p > a.ftnt-download-anchor > b > span.ftnt-download-anchor
READ THE PRESS RELEASE p > a.ftnt-download-anchor > b > span.ftnt-download-anchor
READ THE PRESS RELEASE p > a.ftnt-download-anchor > b > span.ftnt-download-anchor

These are opportunities to improve the legibility of your content.

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
English div.dg-app > div.dg-main-language-dropdown > button.language-dropdown-trigger
○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.
●`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
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●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 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
○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.
○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