Skip to content
https://unicode.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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: #ddffff
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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
Heading Hierarchy
Action
11 headings, 1 skip(s)
REVIEW
11 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Everyone in the world should be able to use their own language on phones and computers.
  • H2 Everyone in the world should be able to use their own language on phones and computers.
  • H2 Everyone in the world should be able to use their own language on phones and computers.
  • H2 Everyone in the world should be able to use their own language on phones and computers.
  • H2 Everyone in the world should be able to use their own language on phones and computers.
  • H4 Technical Work skipped
  • H4 Support Unicode
  • H4 About Us
  • H4 News and Events
  • H4 Legal & Licensing
  • H4 Contact

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

B
Form Accessibility
2 of 4 controls have issues
REVIEW
2 of 4 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">
Info::
2 control(s) properly labeled
4 controls
2 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
qtextSearch for:none
qtextSearch for:none
inputsubmit(none)none
inputsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit">; <input type="submit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

B
Favicon & Branding
9 icon(s) detected
REVIEW
9 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
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Unicode
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Unicode ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓
Name Unicode Display Mode standalone Theme Color #ddffff Background Color #ddffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA 5 pass AA only
title Unicode – The World Standard for Text …
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · top of page (header area)
span About Unicode
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · top of page (header area)
span Technical Quick Start Guide
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · top of page (header area)
span Support Unicode
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · above the fold
span Give a Gift of Stock
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · above the fold
span Donate Now
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · above the fold
span Adopt a Character
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · above the fold
span About Adopt a Character
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · above the fold
span Grant Program
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · above the fold
span Sponsor Stories
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · above the fold
span Sponsors
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · above the fold
span Adopt Now
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · above the fold
span Membership
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · mid-page
span Why Join
4.11:1
#000000
on
#5455FE
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Everyone in the worl…4.11:13.0:1
#000000
#5455FE
Pass
h2 Everyone in the worl…4.11:13.0:1
#000000
#5455FE
Pass
h2 Everyone in the worl…4.11:13.0:1
#000000
#5455FE
Pass
h2 Everyone in the worl…4.11:13.0:1
#000000
#5455FE
Pass
h2 Everyone in the worl…4.11:13.0:1
#000000
#5455FE
Pass
title Unicode – The Worl…4.11:14.5:1
#000000
#5455FE
Fail
a Skip to content4.11:14.5:1
#000000
#5455FE
Fail
span About Unicode4.11:14.5:1
#000000
#5455FE
Fail
span Technical Quick Star…4.11:14.5:1
#000000
#5455FE
Fail
span Support Unicode4.11:14.5:1
#000000
#5455FE
Fail
span Give a Gift of Stock4.11:14.5:1
#000000
#5455FE
Fail
span Donate Now4.11:14.5:1
#000000
#5455FE
Fail
span Adopt a Character4.11:14.5:1
#000000
#5455FE
Fail
span About Adopt a Charac…4.11:14.5:1
#000000
#5455FE
Fail
span Grant Program4.11:14.5:1
#000000
#5455FE
Fail
span Sponsor Stories4.11:14.5:1
#000000
#5455FE
Fail
span Sponsors4.11:14.5:1
#000000
#5455FE
Fail
span Adopt Now4.11:14.5:1
#000000
#5455FE
Fail
span Membership4.11:14.5:1
#000000
#5455FE
Fail
span Why Join4.11:14.5:1
#000000
#5455FE
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+
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "Main Menu" MAIN CONTENTINFO footer
A+
Alt Text Quality
All 7 images OK
PASS
All 7 images OK
Info::
7 image(s) with good alt text
7 images 7 good alt text
All images have appropriate alt text.
A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 20 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.

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
div.side-header-wrapper > div.fusion-main-menu-container > nav.fusion-mobile-nav-holder > button.fusion-mobile-selector div.side-header-wrapper > div.fusion-main-menu-container > nav.fusion-mobile-nav-holder > button.fusion-mobile-selector

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.

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
TECHNICAL WORK div.fusion-columns > div.fusion-column > section#nav_menu-2 > h4.widget-title

These are opportunities to improve keyboard navigation in your application.

○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●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
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Document has a main landmark.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback