Skip to content
https://ui.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
3
REVIEW
6
PASS
4
INFO
0
Checks
13
4 PASS 6 REVIEW 3 FIX
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: #000000
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
4 navigation landmark(s) detected
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 4 <nav> element(s)
Back to Top
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.
B
Landmark Structure
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <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 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

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 Ubiquiti - Error ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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 Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Ubiquiti
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Ubiquiti ✓192×192 icon ✗512×512 icon ✗Start URL . ✓Display Mode standalone ✓
Name Ubiquiti Display Mode standalone Theme Color #000000 Background Color #ffffff Icons 1 icon(s)
B
Lighthouse Accessibility Audits
Score 82/100 — 4 failing, 23 passed
REVIEW
82

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.

ARIA

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
button.sc-iQQMTY > div.sc-eSoUyW > svg.Logo-module_logo__2wFoO > path.Logo-module_motif-active__3MNLk button.sc-iQQMTY > div.sc-eSoUyW > svg.Logo-module_logo__2wFoO > path.Logo-module_motif-active__3MNLk
button.sc-iQQMTY > div.sc-eSoUyW > svg.Logo-module_logo__2wFoO > path.Logo-module_motif-active__3MNLk button.sc-iQQMTY > div.sc-eSoUyW > svg.Logo-module_logo__2wFoO > path.Logo-module_motif-active__3MNLk
button.sc-iQQMTY > div.sc-eSoUyW > svg.Logo-module_logo__2wFoO > path.Logo-module_motif-active__3MNLk button.sc-iQQMTY > div.sc-eSoUyW > svg.Logo-module_logo__2wFoO > path.Logo-module_motif-active__3MNLk
button.sc-iQQMTY > div.sc-eSoUyW > svg.Logo-module_logo__2wFoO > path.Logo-module_motif-active__3MNLk button.sc-iQQMTY > div.sc-eSoUyW > svg.Logo-module_logo__2wFoO > path.Logo-module_motif-active__3MNLk
button.sc-iQQMTY > div.sc-eSoUyW > svg.Logo-module_logo__2wFoO > path.Logo-module_motif-active__3MNLk button.sc-iQQMTY > div.sc-eSoUyW > svg.Logo-module_logo__2wFoO > path.Logo-module_motif-active__3MNLk
button.sc-iQQMTY > div.sc-eSoUyW > svg.Logo-module_logo__2wFoO > path.Logo-module_motif-active__3MNLk button.sc-iQQMTY > div.sc-eSoUyW > svg.Logo-module_logo__2wFoO > path.Logo-module_motif-active__3MNLk

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header.sc-fkmhvJ > nav.sc-iuhUfm > div.sc-ojjAE > button.sc-hLykhl header.sc-fkmhvJ > nav.sc-iuhUfm > div.sc-ojjAE > button.sc-hLykhl
div.sc-iwaiTi > div.sc-cxNIPq > div.sc-joajlr > button.sc-ektKWF div.sc-iwaiTi > div.sc-cxNIPq > div.sc-joajlr > button.sc-ektKWF
div.sc-iwaiTi > div.sc-cxNIPq > div.sc-joajlr > button.sc-ektKWF div.sc-iwaiTi > div.sc-cxNIPq > div.sc-joajlr > button.sc-ektKWF
div.sc-iwaiTi > div.sc-cxNIPq > div.sc-joajlr > button.sc-ektKWF div.sc-iwaiTi > div.sc-cxNIPq > div.sc-joajlr > button.sc-ektKWF
div.sc-iwaiTi > div.sc-cxNIPq > div.sc-joajlr > button.sc-ektKWF div.sc-iwaiTi > div.sc-cxNIPq > div.sc-joajlr > button.sc-ektKWF

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
nav.sc-iuhUfm > div.sc-ojjAE > div.sc-eCblmX > a.sc-irpZDE nav.sc-iuhUfm > div.sc-ojjAE > div.sc-eCblmX > a.sc-irpZDE

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.

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
Store div.sc-ojjAE > div.sc-fGgTrs > div.sc-bYwwMP > a.sc-kLojuI
Cookies Settings div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-pc-btn-handler
Accept All Cookies div#onetrust-button-group-parent > div#onetrust-button-group > div.onetrust-banner-options > button#onetrust-accept-btn-handler
More Information div > div#ot-pc-content > div#ot-pc-desc > a.privacy-notice-link
Allow All div#onetrust-pc-sdk > div > div#ot-pc-content > button#accept-recommended-btn-handler
Confirm My Choices div > div.ot-pc-footer > div.ot-btn-container > button.save-preference-btn-handler

These are opportunities to improve the legibility of your content.

○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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●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
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Elements with visible text labels have matching accessible names.
○`[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
○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
○Links are distinguishable without relying on color.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
A
Heading Hierarchy
5 headings
PASS
5 headings
Warning::
Multiple H1 headings (5 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Company
  • H1 Training duplicate H1
  • H1 Buy Now duplicate H1
  • H1 Tools duplicate H1
  • H1 Stay in Touch duplicate H1

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+
Alt Text Quality
1 of 4 images have issues
PASS
1 of 4 images have issues
Warning::
1 image(s) with generic alt text
Info::
3 image(s) with good alt text
4 images 3 good alt text 1 generic
IssueCount
generic1 image(s)
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 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="EMAIL">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
EMAILtext(Email)placeholder only

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

<input type="text" name="EMAIL">

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+
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 Company21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Training21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Buy Now21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Tools21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Stay in Touch21.00:13.0:1
#000000
#FFFFFF
Pass
title UniFi - Rethinking I…21.00:14.5:1
#000000
#FFFFFF
Pass
span Start Here21.00:14.5:1
#000000
#FFFFFF
Pass
span Cloud Gateways21.00:14.5:1
#000000
#FFFFFF
Pass
span Switching21.00:14.5:1
#000000
#FFFFFF
Pass
span WiFi21.00:14.5:1
#000000
#FFFFFF
Pass
span Camera Security21.00:14.5:1
#000000
#FFFFFF
Pass
span Door Access21.00:14.5:1
#000000
#FFFFFF
Pass
span Integrations21.00:14.5:1
#000000
#FFFFFF
Pass
a What's New21.00:14.5:1
#000000
#FFFFFF
Pass
a Support21.00:14.5:1
#000000
#FFFFFF
Pass
a Store21.00:14.5:1
#000000
#FFFFFF
Pass
div How It Works?21.00:14.5:1
#000000
#FFFFFF
Pass
div Cloud Gateways21.00:14.5:1
#000000
#FFFFFF
Pass
div Switching21.00:14.5:1
#000000
#FFFFFF
Pass
div WiFi21.00:14.5:1
#000000
#FFFFFF
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.

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

Send Feedback