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 7 REVIEW 3 FIX

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #ffffff

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

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

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

9 issue(s) across 48 links and 0 buttons

REVIEW

9 issue(s) across 48 links and 0 buttons

8 link(s) with no accessible text

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

Got: https://twitter.com/pfsense; https://youtube.com/c/netgateofficial; https://reddit.com/r/pfsense; http://github.com/pfsense; https://twitter.com/pfsense; https://youtube.com/c/netgateofficial; https://reddit.com/r/pfsense; http://github.com/pfsense

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://www.netgate.com/our-services/professional-services.html ("Learn More")

39 link(s) with descriptive text

48 links

8 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://twitter.com/pfsense	(empty)	empty	Add link text or aria-label
https://youtube.com/c/netgateofficial	(empty)	empty	Add link text or aria-label
https://reddit.com/r/pfsense	(empty)	empty	Add link text or aria-label
http://github.com/pfsense	(empty)	empty	Add link text or aria-label
https://www.netgate.com/our-services/pro…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Professional Services.Html
https://twitter.com/pfsense	(empty)	empty	Add link text or aria-label
https://youtube.com/c/netgateofficial	(empty)	empty	Add link text or aria-label
https://reddit.com/r/pfsense	(empty)	empty	Add link text or aria-label
http://github.com/pfsense	(empty)	empty	Add link text or aria-label

39 links and buttons have descriptive text

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

https://twitter.com/pfsense; https://youtube.com/c/netgateofficial; https://reddit.com/r/pfsense; http://github.com/pfsense; https://twitter.com/pfsense; https://youtube.com/c/netgateofficial; https://reddit.com/r/pfsense; http://github.com/pfsense

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

Generic link text like 'click here' doesn't describe the destination.

https://www.netgate.com/our-services/professional-services.html ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title pfSense Logo ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

7 icon(s) detected

REVIEW

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 11 fail WCAG AA

REVIEW

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

9 pass 11 fail WCAG AA

h1 Open Source Security

1.10:1

#000000

#061118

needs 3.0:1 (large text)

32px · mid-page

h2 Secure networks start here.™

1.09:1

#000000

#061016

needs 3.0:1 (large text)

24px · mid-page

title pfSense® - World's Most Trusted Open So…

1.02:1

#000000

#010504

needs 4.5:1 (normal text)

16px · top of page (header area)

a Buy Cloud

1.05:1

#000000

#03090A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Buy Appliance

1.07:1

#000000

#040D11

needs 4.5:1 (normal text)

16px · top of page (header area)

a Support

1.14:1

#000000

#07151E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Blog

1.19:1

#000000

#091A25

needs 4.5:1 (normal text)

16px · above the fold

span navigation

1.19:1

#000000

#091A26

needs 4.5:1 (normal text)

16px · above the fold

a Get Started

1.16:1

#000000

#081722

needs 4.5:1 (normal text)

16px · above the fold

a Cloud

1.20:1

#000000

#0A1B29

needs 4.5:1 (normal text)

16px · above the fold

a Products

1.21:1

#000000

#0A1C2B

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Open Source Security	1.10:1	3.0:1	#000000	#061118	Fail
h2 Secure networks star…	1.09:1	3.0:1	#000000	#061016	Fail
h2 Virtual Appliances	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 SOLUTIONS	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 PRODUCT SUPPORT	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 PROFESSIONAL SERVICE…	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 pfSense Training	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 Screenshots, feature…	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 About Us	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 Support & Services	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 How To Buy	19.26:1	3.0:1	#000000	#F5F5F5	Pass
title pfSense® - World's …	1.02:1	4.5:1	#000000	#010504	Fail
a Buy Cloud	1.05:1	4.5:1	#000000	#03090A	Fail
a Buy Appliance	1.07:1	4.5:1	#000000	#040D11	Fail
a Support	1.14:1	4.5:1	#000000	#07151E	Fail
a Blog	1.19:1	4.5:1	#000000	#091A25	Fail
span navigation	1.19:1	4.5:1	#000000	#091A26	Fail
a Get Started	1.16:1	4.5:1	#000000	#081722	Fail
a Cloud	1.20:1	4.5:1	#000000	#0A1B29	Fail
a Products	1.21:1	4.5:1	#000000	#0A1C2B	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.

Lighthouse Accessibility Audits

Score 84/100 — 4 failing, 18 passed

REVIEW

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
Get Started Now `div#bg > div.container > div.main-title > a.btn`
pfSense Plus for cloud `div.row > div.col-sm-7 > div.btn-container > a.btn`
Get Support `div.row > div.col-sm-7 > div.btn-container > a.btn`
Netgate `div.row > div.col-sm-7 > p.p-space > a`
Enroll Now `div.row > div.col-sm-7 > div.btn-container > a.btn`
Learn what pfSense software can do for you `body > div#top > div.promo > p.promo__describe`
Privacy Policy `footer.footer > div.container > div.copy > a`
Terms and Conditions `footer.footer > div.container > div.copy > a`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Netgate `div.row > div.col-sm-7 > p.p-space > a`
Netgate `div.row > div.col-sm-7 > p.p-space > a`
Netgate `div.row > div.col-sm-7 > p.p-space > a`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.social > ul > li.social__item > a.social__link `div.social > ul > li.social__item > a.social__link`
div.social > ul > li.social__item > a.social__link `div.social > ul > li.social__item > a.social__link`
div.social > ul > li.social__item > a.social__link `div.social > ul > li.social__item > a.social__link`
div.social > ul > li.social__item > a.social__link `div.social > ul > li.social__item > a.social__link`

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.

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.no-applicationcache `html.no-applicationcache`

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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

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

●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

●Deprecated ARIA roles were not used

●ARIA IDs are unique

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

○Buttons have an accessible name

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

○Image elements have `[alt]` attributes

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

○No element has a `[tabindex]` value greater than 0

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

○Identical links have the same purpose.

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

A+

Heading Hierarchy

11 headings

PASS

11 headings

Single H1 present

H1 Open Source Security
H2 Secure networks start here.™ With thousands of enterprises using pfSense® software, it is rapidly becoming the world's most trusted open source network security solution.
H2 Securely Connect to the Cloud Virtual Appliances
H2 Enterprise, Open Source SOLUTIONS
H2 Help, Documentation, Answers PRODUCT SUPPORT
H2 Security, Design, Implementation PROFESSIONAL SERVICES
H2 Global, Access, Knowledge pfSense Training
H3 Screenshots, feature descriptions, and more
H3 About Us
H3 Support & Services
H3 How To Buy

A+

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

5 image(s) with good alt text

5 images 5 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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