Skip to content
https://www.nixos.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
2
REVIEW
4
PASS
7
INFO
0
Checks
13
7 PASS 4 REVIEW 2 FIX
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::
Back-to-top link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
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 Not Found | Nix & NixOS Custom Styling Navigation Homepage Link Search Form
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Nix & NixOS
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name Nix & NixOS 192×192 icon 512×512 icon Start URL / Display Mode
Name Nix & NixOS Theme Color #fff Background Color #fff Icons 2 icon(s)
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode Dark Mode Supported
color-scheme meta Not set Dark theme-color #fff CSS indicators Detected

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA 13 pass AA only
h1 Declarative builds
2.80:1
#000000
on
#3B5487
needs 3.0:1 (large text)
32px · above the fold
h1 and deployments.
2.80:1
#000000
on
#3B5487
needs 3.0:1 (large text)
32px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Declarative builds2.80:13.0:1
#000000
#3B5487
Fail
h1 and deployments.2.80:13.0:1
#000000
#3B5487
Fail
h2 Choose from over 120…3.46:13.0:1
#000000
#4B6291
Pass
h2 Examples3.46:13.0:1
#000000
#4B6291
Pass
h2 Footer3.46:13.0:1
#000000
#4B6291
Pass
h3 Try new tools withou…3.46:13.0:1
#000000
#4B6291
Pass
h3 Multiple languages, …3.46:13.0:1
#000000
#4B6291
Pass
h3 Declarative dev-envi…3.46:13.0:1
#000000
#4B6291
Pass
h3 Minimal docker image…3.46:13.0:1
#000000
#4B6291
Pass
h3 Declarative cloud im…3.46:13.0:1
#000000
#4B6291
Pass
h3 Test your configurat…3.46:13.0:1
#000000
#4B6291
Pass
h3 The Project3.46:13.0:1
#000000
#4B6291
Pass
h3 Get in Touch3.46:13.0:1
#000000
#4B6291
Pass
h3 Contribute3.46:13.0:1
#000000
#4B6291
Pass
h3 Stay up to Date3.46:13.0:1
#000000
#4B6291
Pass
title Nix & NixOS | Declar…21.00:14.5:1
#000000
#FFFFFF
Pass
a Explore21.00:14.5:1
#000000
#FFFFFF
Pass
a Download18.37:14.5:1
#000000
#ECF0F7
Pass
a Learn18.18:14.5:1
#000000
#E8EFFC
Pass
a Governance18.18:14.5:1
#000000
#E8EFFC
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.

A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
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 Navigation" MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
15 headings
PASS
15 headings
Info::
Single H1 present
  • H1 Declarative builds and deployments.
  • H2 Choose from over 120 000 Packages
  • H2 Examples
  • H3 Try new tools without fear
  • H3 Multiple languages, one tool
  • H3 Declarative dev-environments
  • H3 Minimal docker images
  • H3 Declarative cloud images
  • H3 Test your configurations
  • H2 Footer
  • H3 The Project
  • H3 Get in Touch
  • H3 Contribute
  • H3 Stay up to Date
  • H4 Connect with us:
A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
querytextSearch NixOS Packages and Optionsnone
A
Favicon & Branding
10 icon(s) detected
PASS
10 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Present
Manifest Icons Present
Multiple Sizes Present
A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 27 passed
PASS
97

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

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
00:00 div.ap-wrapper > div.ap-player > div.ap-control-bar > span.ap-timer
00:00 div.ap-wrapper > div.ap-player > div.ap-control-bar > span.ap-timer
00:00 div.ap-wrapper > div.ap-player > div.ap-control-bar > span.ap-timer
00:00 div.ap-wrapper > div.ap-player > div.ap-control-bar > span.ap-timer
00:00 div.ap-wrapper > div.ap-player > div.ap-control-bar > span.ap-timer
00:00 div.ap-wrapper > div.ap-player > div.ap-control-bar > span.ap-timer
00:00 div.ap-wrapper > div.ap-player > div.ap-control-bar > span.ap-timer

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.

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
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.
`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.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` 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
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.
`[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