Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 2 REVIEW 8 FIX

Landmark Structure

Action

17 landmarks

FIX

17 landmarks

No <main> landmark found

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

11 <nav> landmark(s) found

8 of 11 <nav> elements are unlabeled

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

No banner (header) landmark

No contentinfo (footer) landmark

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

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

Link & Button Quality

Action

11 issue(s) across 230 links and 30 buttons

FIX

11 issue(s) across 230 links and 30 buttons

7 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /; /; https://x.com/F5; https://www.linkedin.com/company/f5/; https://www.facebook.com/f5incorporated; https://www.instagram.com/f5.global/; https://www.youtube.com/user/f5networksinc

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://www.f5.com/company/blog/nginx/our-design-vision-for-nginx-one-the-ult…"]

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.f5.com/company/policies/privacy-notice

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button#f5-hamburger-button; button.inline-flex (#469 on page); button.inline-flex (#474 on page); button.inline-flex (#533 on page)

221 link(s) with descriptive text

230 links

7 empty

0 generic text

1 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
https://www.f5.com/company/blog/nginx/ou…	Navigate to undefined	img no alt	Add alt attribute to the image
https://x.com/F5	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/f5/	(empty)	empty	Add link text or aria-label
https://www.facebook.com/f5incorporated	(empty)	empty	Add link text or aria-label
https://www.instagram.com/f5.global/	(empty)	empty	Add link text or aria-label
https://www.youtube.com/user/f5networksi…	(empty)	empty	Add link text or aria-label
https://www.f5.com/company/policies/priv…	privacy policy	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

247 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/; /; https://x.com/F5; https://www.linkedin.com/company/f5/; https://www.facebook.com/f5incorporated; https://www.instagram.com/f5.global/; https://www.youtube.com/user/f5networksinc

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://www.f5.com/company/blog/nginx/our-design-vision-for-nginx-one-the-ult…"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://www.f5.com/company/policies/privacy-notice

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button#f5-hamburger-button; button.inline-flex (#469 on page); button.inline-flex (#474 on page); button.inline-flex (#533 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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-9iv4d9

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.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://nginx.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://nginx.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 control(s) rely on placeholder only

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

Got: <input type="text" id="MobileSearchInput">; <input type="text" id="SearchInput">

2 controls

0 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
#MobileSearchInput	text	(Search all F5 sites)	placeholder only
#SearchInput	text	(Search all F5 sites)	placeholder only

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

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA

a AI infrastructure

2.26:1

#000000

#474747

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a AI security

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Application delivery and traffic managem…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Edge distribution

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Networking for Kubernetes

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Network security

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Post-quantum cryptography

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Service providers

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Web application and API protection

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Zero trust architecture

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Banking and financial services

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a E-commerce

2.03:1

#000000

#404040

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

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)

Element	Ratio	Required	FG	BG	Result
h1 F5 NGINX Products	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 An Architecture for …	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 Products	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 NGINX One Components	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 Resources	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 Next steps	9.90:1	3.0:1	#000000	#B2B2B2	Pass
title NGINX \| F5	9.90:1	4.5:1	#000000	#B2B2B2	Pass
a AI infrastructure	2.26:1	4.5:1	#000000	#474747	Fail
a AI security	1.00:1	4.5:1	#000000	#000000	Fail
a Application delivery…	1.00:1	4.5:1	#000000	#000000	Fail
a Edge distribution	1.00:1	4.5:1	#000000	#000000	Fail
a Networking for Kuber…	1.00:1	4.5:1	#000000	#000000	Fail
a Network security	1.00:1	4.5:1	#000000	#000000	Fail
a Post-quantum cryptog…	1.00:1	4.5:1	#000000	#000000	Fail
a Service providers	1.00:1	4.5:1	#000000	#000000	Fail
a Web application and …	1.00:1	4.5:1	#000000	#000000	Fail
a Zero trust architect…	1.00:1	4.5:1	#000000	#000000	Fail
a Banking and financia…	1.00:1	4.5:1	#000000	#000000	Fail
a E-commerce	2.03:1	4.5:1	#000000	#404040	Fail
a Healthcare	8.03:1	4.5:1	#000000	#A0A0A0	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.

Heading Hierarchy

13 headings, 1 skip(s)

PASS

13 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 F5 NGINX Products
H2 An Architecture for Modern Applications
H2 Products
H2 NGINX One Components
H2 Awards and Recognition
H2 Resources
H6 Featured skipped
H5 Our design vision for NGINX One: The ultimate data plane SaaS
H5 Blogs
H5 Webinars
H5 Open source resources
H5 Related use cases
H2 Next steps

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

2 decorative image(s) correctly marked

1 image(s) with good alt text

3 images 1 good alt text 2 decorative

All images have appropriate alt text.

A+

Lighthouse Accessibility Audits

Score 99/100 — 2 failing, 27 passed

PASS

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Featured `div.container > div.grid > div.space-y-gutter-md > h6.d-supplementary`

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
NGINX One The core NGINX data plane software enhanced with SaaS-based tools for… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
F5 WAF for NGINX and F5 DoS for NGINX Comprehensive WAF security and denial-of-… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
NGINXaaS for Azure An Infrastructure-as-a-Service version of NGINX that enables… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
F5 NGINXaaS for Google Cloud Enhance app delivery and security in Google Cloud … `div.grid-cols-1 > span.w-full > div.h-full > a.group`
NGINX Plus An all-in-one, cloud-native load balancer, reverse proxy, web server… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
F5 WAF for NGINX A comprehensive WAF security solution designed to protect apps… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
NGINX Instance Manager Identify, secure, manage, and monitor all NGINX Open Sou… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
NGINX Ingress Controller Implements unified API gateways, load balancers, and i… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
NGINX Gateway Fabric Streamlines app, service, and API connectivity across hybr… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
NGINX One Console Configure, secure, monitor and manage NGINX instances at scal… `div.grid-cols-1 > span.w-full > div.h-full > a.group`
2024 TrustRadius Top Rated Award `div.grid-cols-1 > span.w-full > div.h-full > a.group`
Contact us Find out how F5 products and solutions can enable you to achieve you… `div.flex > div.flex > div.w-full > a.group`
Explore packaging options Explore the best options for your organization. Explo… `div.flex > div.flex > div.w-full > a.group`
Try NGINX One for Free Try the NGINX ecosystem with data plane and traffic mana… `div.flex > div.flex > div.w-full > a.group`

○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.

●`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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

○`[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

○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.

○`<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

○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.