Skip to content
https://home-assistant.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
1 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 1 <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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 (missing!) CONTENTINFO footer

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

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 Home Assistant ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 89/100 — 4 failing, 17 passed
REVIEW
89

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
2026.4.3 div.grid-wrapper > div.grid > div.grid__item > a.release-date
We are a non-profit and can't be sold or acquired. div.grid__item > a.material-card > div > p.lead
Home Assistant is a project by the Open Home Foundation. div.grid__item > a.material-card > div > p
Read our founder's vision for the perfect home automation div.grid > div.grid__item > a.material-card > p.lead
LEARN MORE div.grid__item > div.join-community > div.links > a
LEARN MORE div.grid__item > div.join-community > div.links > a
FORUMS div.grid__item > div.join-community > div.links > a
CHAT div.grid__item > div.join-community > div.links > a
NEWSLETTER div.grid__item > div.join-community > div.links > a
Works with over 1000 brands div.grid__item > div.feature-cards > div.card > div.card-header
EXPLORE INTEGRATIONS div.feature-cards > div.card > div.card-content > a.button
Powerful automations div.grid__item > div.feature-cards > div.card > div.card-header
EXPLORE AUTOMATIONS div.feature-cards > div.card > div.card-content > a.button
Versatile dashboards div.grid__item > div.feature-cards > div.card > div.card-header
EXPLORE DASHBOARDS div.feature-cards > div.card > div.card-content > a.button
Assist, our voice assistant div.grid__item > div.feature-cards > div.card > div.card-header
EXPLORE ASSIST div.feature-cards > div.card > div.card-content > a.button
Extend your system with apps div.grid__item > div.feature-cards > div.card > div.card-header
Explore apps for Home Assistant div.feature-cards > div.card > div.card-content > a.button
All your smart home data stays local div.grid__item > div.feature-cards > div.card > div.card-header
Companion Mobile Apps div.grid__item > div.feature-cards > div.card > div.card-header
DOWNLOAD APPS div.feature-cards > div.card > div.card-content > a.button
Home Energy Management div.grid__item > div.feature-cards > div.card > div.card-header
LEARN MORE div.feature-cards > div.card > div.card-content > a.button
Home Assistant Cast div.grid__item > div.feature-cards > div.card > div.card-header
LEARN MORE div.feature-cards > div.card > div.card-content > a.button
NFC Tags div.grid__item > div.feature-cards > div.card > div.card-header
LEARN MORE div.feature-cards > div.card > div.card-content > a.button
Open Home Foundation div.footer-nav > div.company > p > a
Nabu Casa div.footer-nav > div.company > p > a
GitHub repo div.grid__item > ul > li > a.external-link
Developers Portal div.grid__item > ul > li > a.external-link
Design Portal div.grid__item > ul > li > a.external-link
Data Science Portal div.grid__item > ul > li > a.external-link
Community Forum div.grid__item > ul > li > a.external-link
Creator Network div.grid__item > ul > li > a.external-link
Works With Home Assistant div.grid__item > ul > li > a.external-link
Our community div.grid__item > ul > li > a
Reporting issues div.grid__item > ul > li > a
Integration Alerts div.grid__item > ul > li > a.external-link
Security Alerts div.grid__item > ul > li > a
System Status div.grid__item > ul > li > a.external-link
iOS and Apple devices div.grid__item > ul > li > a.external-link
Android and Wear OS div.grid__item > ul > li > a.external-link
...and more! div.grid__item > ul > li > a.external-link
Merch store div.grid__item > ul > li > a
Home Assistant Cloud div.grid__item > ul > li > a
Privacy Notices div.grid__item > ul > li > a
Contributor License Agreement div.grid__item > ul > li > a
Terms of Service div.grid__item > ul > li > a
Code of Conduct div.grid__item > ul > li > a
Credits div.grid__item > ul > li > a
License div.grid__item > ul > li > a
Sign up for our newsletter div.footer-nav > div.socials > p > a.external-link
Works With Home Assistant div.socials > div.web-notice > p > a
email our team div.socials > div.web-notice > p > a
contact support div.socials > div.web-notice > p > a
Jekyll div.socials > div.web-notice > p > a
Oscailte theme div.socials > div.web-notice > p > 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.grid-wrapper > div.grid > div.grid__item > a.site-title div.grid-wrapper > div.grid > div.grid__item > a.site-title

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 html

These items highlight common accessibility best practices.

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
Shop our merch store! Grab some swag while supporting the Open Home Foundation div.frontpage > div.grid > div.grid__item > a.material-card
○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
●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.
●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
○`[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
○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
○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.
○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.
○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
15 headings
PASS
15 headings
Info::
Single H1 present
  • H1 Awakenyour home
  • H2 Release Notes
  • H2 Recent Blog Posts
  • H2 Alexa, turn on the lights
  • H2 Ok Google, turn off the AC
  • H2 Join The Community
  • H2 Features
  • H2 In the press
  • H2 The Home Assistant project is sponsored by
  • H3 Join us and contribute!
  • H3 System status
  • H3 Companion apps
  • H3 Support us
  • H3 Governance
  • H3 Follow us
A
Alt Text Quality
1 of 18 images have issues
PASS
1 of 18 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
17 image(s) with good alt text
18 images 17 good alt text 1 missing
IssueCount
missing1 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

A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="toggle">
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#togglecheckbox(none)none

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

<input type="checkbox" id="toggle">

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

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 Awaken8.89:13.0:1
#000000
#00B3FF
Pass
h2 Release Notes8.58:13.0:1
#000000
#00AFFF
Pass
h2 Recent Blog Posts8.58:13.0:1
#000000
#00AFFF
Pass
h2 Alexa, turn on the l…8.58:13.0:1
#000000
#00AFFF
Pass
h2 Ok Google, turn off …8.58:13.0:1
#000000
#00AFFF
Pass
h2 Join The Community8.58:13.0:1
#000000
#00AFFF
Pass
h2 Features8.58:13.0:1
#000000
#00AFFF
Pass
h2 In the press8.58:13.0:1
#000000
#00AFFF
Pass
h2 The Home Assistant p…8.58:13.0:1
#000000
#00AFFF
Pass
h3 Join us and contribu…8.58:13.0:1
#000000
#00AFFF
Pass
h3 System status8.58:13.0:1
#000000
#00AFFF
Pass
h3 Companion apps8.58:13.0:1
#000000
#00AFFF
Pass
h3 Support us8.58:13.0:1
#000000
#00AFFF
Pass
h3 Governance8.58:13.0:1
#000000
#00AFFF
Pass
h3 Follow us8.58:13.0:1
#000000
#00AFFF
Pass
title Home Assistant12.89:14.5:1
#000000
#00DEFF
Pass
a 2026.4.312.58:14.5:1
#000000
#00DBFF
Pass
a Getting started12.37:14.5:1
#000000
#00D9FF
Pass
a Documentation12.06:14.5:1
#000000
#00D6FF
Pass
a Installation11.86:14.5:1
#000000
#00D4FF
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