Skip to content
https://yaml.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
2
PASS
7
INFO
0
Checks
13
7 PASS 2 REVIEW 4 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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
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::
Search functionality detected
Got: role-search
Info::
5 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 5 <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.
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title YAML Ain't Markup Language ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 1 pass AA only
title - YAML Ain't Markup Language
3.06:1
#000000
on
#4051B5
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title - YAML Ain't Markup …3.06:14.5:1
#000000
#4051B5
Fail
span YAML Ain't Markup La…6.95:14.5:1
#000000
#8691CD
Pass
div Initializing search21.00:14.5:1
#000000
#FFFFFF
Pass
div yaml/www.yaml.org21.00:14.5:1
#000000
#FFFFFF
Pass
li 39621.00:14.5:1
#000000
#FFFFFF
Pass
li 31621.00:14.5:1
#000000
#FFFFFF
Pass
a About21.00:14.5:1
#000000
#FFFFFF
Pass
a Libraries21.00:14.5:1
#000000
#FFFFFF
Pass
a Tools21.00:14.5:1
#000000
#FFFFFF
Pass
label YAML Ain't Markup La…21.00:14.5:1
#000000
#FFFFFF
Pass
div yaml/www.yaml.org21.00:14.5:1
#000000
#FFFFFF
Pass
li 39621.00:14.5:1
#000000
#FFFFFF
Pass
li 31621.00:14.5:1
#000000
#FFFFFF
Pass
span About21.00:14.5:1
#000000
#FFFFFF
Pass
span Libraries21.00:14.5:1
#000000
#FFFFFF
Pass
span Tools21.00:14.5:1
#000000
#FFFFFF
Pass
span %YAML 1.221.00:14.5:1
#000000
#FFFFFF
Pass
span ---21.00:14.5:1
#000000
#FFFFFF
Pass
span YAML21.00:14.5:1
#000000
#FFFFFF
Pass
pre YAML Ain't Markup La…21.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.

A
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Header" SEARCH 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
1 headings
PASS
1 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A
Alt Text Quality
2 of 2 images have issues
PASS
2 of 2 images have issues
Warning::
2 image(s) with generic alt text
2 images 2 generic
IssueCount
generic2 image(s)
A
Form Accessibility
1 of 5 controls have issues
PASS
1 of 5 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="__search">
Info::
4 control(s) properly labeled
5 controls
4 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#__drawercheckboxYAML Ain't Markup Languagefor/id
#__palette_0radioSwitch to dark modearia-label
#__palette_1radioSwitch to light modearia-label
querytextSearcharia-label
#__searchcheckbox(none)none

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

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

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+
Dark Mode Support
Full dark mode support
PASS
Full dark mode support
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: light
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 light ✓Dark theme-color #4051b5 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 25 passed
PASS
93

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 dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Type to start searching body > header.md-header > nav.md-header__inner > div.md-search

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.

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
Copyright © 2001-2026 YAML Made with Material for MkDocs footer.md-footer > div.md-footer-meta > div.md-footer-meta__inner > div.md-copyright
Copyright © 2001-2026 YAML div.md-footer-meta > div.md-footer-meta__inner > div.md-copyright > div.md-copyright__highlight
Material for MkDocs div.md-footer-meta > div.md-footer-meta__inner > div.md-copyright > a

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
●`[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.
●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
●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
●All heading elements contain content.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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>`.
○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