Skip to content
https://numbeo.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
5
REVIEW
7
PASS
1
INFO
0
Checks
13
1 PASS 7 REVIEW 5 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

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

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

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::
5 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 5 <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
Alt Text Quality
1 of 9 images have issues
REVIEW
1 of 9 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
7 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
9 images 1 good alt text 7 decorative 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="country" id="country">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="city_selector_menu_city_id" id="city_selector_menu_city_id">; <input type="text" id="city_selector_city_id">
3 controls
0 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
#city_selector_menu_city_idtext(Select City)placeholder only
#city_selector_city_idtext(Type and Pick City)placeholder only
#countryselect(none)none

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

<select name="country" id="country">

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

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

<input type="text" name="city_selector_menu_city_id" id="city_selector_menu_city_id">; <input type="text" id="city_selector_city_id">

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

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 Numbeo.com General Error Message Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
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
a Cost of Living Comparison
3.94:1
#000000
on
#546C93
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Cost of Living14.36:13.0:1
#000000
#C4D7F3
Pass
h3 Countries:14.36:13.0:1
#000000
#C4D7F3
Pass
title Cost of Living21.00:14.5:1
#000000
#FFFFFF
Pass
a Cost Of Living9.78:14.5:1
#000000
#B0B1B2
Pass
a Cost Of Living21.00:14.5:1
#000000
#FFFFFF
Pass
a Cost of Living Compa…3.94:14.5:1
#000000
#546C93
Fail
a Cost of Living Calcu…21.00:14.5:1
#000000
#FFFFFF
Pass
a Cost Of Living Index…21.00:14.5:1
#000000
#FFFFFF
Pass
a Cost Of Living Index21.00:14.5:1
#000000
#FFFFFF
Pass
a Cost Of Living Index…21.00:14.5:1
#000000
#FFFFFF
Pass
a Food Prices12.17:14.5:1
#000000
#C5C5C5
Pass
a Prices By City7.28:14.5:1
#000000
#989898
Pass
a Prices By Country21.00:14.5:1
#000000
#FFFFFF
Pass
a Basket of Goods and …21.00:14.5:1
#000000
#FFFFFF
Pass
a Taxi Fare Calculator21.00:14.5:1
#000000
#FFFFFF
Pass
a Gas Prices Calculato…21.00:14.5:1
#000000
#FFFFFF
Pass
a Methodology and Moti…21.00:14.5:1
#000000
#FFFFFF
Pass
a Salary Calculator21.00:14.5:1
#000000
#FFFFFF
Pass
a Update Data for Your…21.00:14.5:1
#000000
#FFFFFF
Pass
a Property Prices17.52:14.5:1
#000000
#E9EBE9
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.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 7 failing, 22 passed
REVIEW
78

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.

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
Countries: body > div#content_and_footer > div#content > h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#content > div > a > img div#content > div > a > img

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
---Select Country--- Afghanistan Aland Islands Albania Alderney Algeria America… div.select_location_form > div.standard_margin_inlineblock > form > select#country

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
tbody > tr > td > a.menu_link3 tbody > tr > td > a.menu_link3
div#content_and_footer > div#content > div > a div#content_and_footer > div#content > div > a

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. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
sharing local price information div#content > div.standard_margin > p > a

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Afghanistan tbody > tr > td > a
Aland Islands tbody > tr > td > a
Albania tbody > tr > td > a
Alderney tbody > tr > td > a
Algeria tbody > tr > td > a
Andorra tbody > tr > td > a
Angola tbody > tr > td > a
Anguilla tbody > tr > td > a
Argentina tbody > tr > td > a
Armenia tbody > tr > td > a
Aruba tbody > tr > td > a
Australia tbody > tr > td > a
Austria tbody > tr > td > a
Azerbaijan tbody > tr > td > a
Bahamas tbody > tr > td > a
Bahrain tbody > tr > td > a
Bangladesh tbody > tr > td > a
Barbados tbody > tr > td > a
Belarus tbody > tr > td > a
Belgium tbody > tr > td > a
Belize tbody > tr > td > a
Benin tbody > tr > td > a
Bermuda tbody > tr > td > a
Bhutan tbody > tr > td > a
Bolivia tbody > tr > td > a
Bonaire tbody > tr > td > a
Botswana tbody > tr > td > a
Brazil tbody > tr > td > a
Brunei tbody > tr > td > a
Bulgaria tbody > tr > td > a
Burkina Faso tbody > tr > td > a
Burundi tbody > tr > td > a
Cambodia tbody > tr > td > a
Cameroon tbody > tr > td > a
Canada tbody > tr > td > a
Cape Verde tbody > tr > td > a
Cayman Islands tbody > tr > td > a
Central African Republic tbody > tr > td > a
Chad tbody > tr > td > a
Chile tbody > tr > td > a
China tbody > tr > td > a
Colombia tbody > tr > td > a
Comoros tbody > tr > td > a
Cook Islands tbody > tr > td > a
Costa Rica tbody > tr > td > a
Croatia tbody > tr > td > a
Cuba tbody > tr > td > a
Curacao tbody > tr > td > a
Cyprus tbody > tr > td > a
Denmark tbody > tr > td > a
Djibouti tbody > tr > td > a
Dominica tbody > tr > td > a
Ecuador tbody > tr > td > a
Egypt tbody > tr > td > a
El Salvador tbody > tr > td > a
Equatorial Guinea tbody > tr > td > a
Eritrea tbody > tr > td > a
Estonia tbody > tr > td > a
Eswatini tbody > tr > td > a
Ethiopia tbody > tr > td > a
Falkland Islands tbody > tr > td > a
Faroe Islands tbody > tr > td > a
Fiji tbody > tr > td > a
Finland tbody > tr > td > a
France tbody > tr > td > a
French Guiana tbody > tr > td > a
French Polynesia tbody > tr > td > a
French Southern Territories tbody > tr > td > a
Gabon tbody > tr > td > a
Gambia tbody > tr > td > a
Georgia tbody > tr > td > a
Germany tbody > tr > td > a
Ghana tbody > tr > td > a
Gibraltar tbody > tr > td > a
Greece tbody > tr > td > a
Greenland tbody > tr > td > a
Grenada tbody > tr > td > a
Guadeloupe tbody > tr > td > a
Guam tbody > tr > td > a
Guatemala tbody > tr > td > a
Guernsey tbody > tr > td > a
Guinea tbody > tr > td > a
Guinea-Bissau tbody > tr > td > a
Guyana tbody > tr > td > a
Haiti tbody > tr > td > a
Honduras tbody > tr > td > a
Hong Kong (China) tbody > tr > td > a
Hungary tbody > tr > td > a
Iceland tbody > tr > td > a
India tbody > tr > td > a
Indonesia tbody > tr > td > a
Iran tbody > tr > td > a
Iraq tbody > tr > td > a
Ireland tbody > tr > td > a
Isle Of Man tbody > tr > td > a
Israel tbody > tr > td > a
Italy tbody > tr > td > a
Jamaica tbody > tr > td > a
Japan tbody > tr > td > a
Jersey tbody > tr > td > a
Jordan tbody > tr > td > a
Kazakhstan tbody > tr > td > a
Kenya tbody > tr > td > a
Kiribati tbody > tr > td > a
Kuwait tbody > tr > td > a
Kyrgyzstan tbody > tr > td > a
Laos tbody > tr > td > a
Latvia tbody > tr > td > a
Lebanon tbody > tr > td > a
Lesotho tbody > tr > td > a
Liberia tbody > tr > td > a
Libya tbody > tr > td > a
Liechtenstein tbody > tr > td > a
Lithuania tbody > tr > td > a
Luxembourg tbody > tr > td > a
Macao (China) tbody > tr > td > a
Madagascar tbody > tr > td > a
Malawi tbody > tr > td > a
Malaysia tbody > tr > td > a
Maldives tbody > tr > td > a
Mali tbody > tr > td > a
Malta tbody > tr > td > a
Marshall Islands tbody > tr > td > a
Martinique tbody > tr > td > a
Mauritania tbody > tr > td > a
Mauritius tbody > tr > td > a
Mexico tbody > tr > td > a
Micronesia tbody > tr > td > a
Moldova tbody > tr > td > a
Monaco tbody > tr > td > a
Mongolia tbody > tr > td > a
Montenegro tbody > tr > td > a
Montserrat tbody > tr > td > a
Morocco tbody > tr > td > a
Mozambique tbody > tr > td > a
Myanmar tbody > tr > td > a
Namibia tbody > tr > td > a
Nauru tbody > tr > td > a
Nepal tbody > tr > td > a
Netherlands tbody > tr > td > a
New Caledonia tbody > tr > td > a
New Zealand tbody > tr > td > a
Nicaragua tbody > tr > td > a
Niger tbody > tr > td > a
Nigeria tbody > tr > td > a
Niue tbody > tr > td > a
North Korea tbody > tr > td > a
North Macedonia tbody > tr > td > a
Northern Mariana Islands tbody > tr > td > a
Norway tbody > tr > td > a
Pakistan tbody > tr > td > a
Palau tbody > tr > td > a
Palestine tbody > tr > td > a
Panama tbody > tr > td > a
Papua New Guinea tbody > tr > td > a
Paraguay tbody > tr > td > a
Peru tbody > tr > td > a
Philippines tbody > tr > td > a
Poland tbody > tr > td > a
Portugal tbody > tr > td > a
Puerto Rico tbody > tr > td > a
Reunion tbody > tr > td > a
Romania tbody > tr > td > a
Russia tbody > tr > td > a
Rwanda tbody > tr > td > a
Saint Helena tbody > tr > td > a
Saint Kitts And Nevis tbody > tr > td > a
Saint Lucia tbody > tr > td > a
Samoa tbody > tr > td > a
San Marino tbody > tr > td > a
Sao Tome And Principe tbody > tr > td > a
Saudi Arabia tbody > tr > td > a
Senegal tbody > tr > td > a
Serbia tbody > tr > td > a
Seychelles tbody > tr > td > a
Sierra Leone tbody > tr > td > a
Singapore tbody > tr > td > a
Sint Maarten tbody > tr > td > a
Slovakia tbody > tr > td > a
Slovenia tbody > tr > td > a
Solomon Islands tbody > tr > td > a
Somalia tbody > tr > td > a
South Africa tbody > tr > td > a
South Korea tbody > tr > td > a
South Sudan tbody > tr > td > a
Spain tbody > tr > td > a
Sri Lanka tbody > tr > td > a
Sudan tbody > tr > td > a
Suriname tbody > tr > td > a
Sweden tbody > tr > td > a
Switzerland tbody > tr > td > a
Syria tbody > tr > td > a
Taiwan tbody > tr > td > a
Tajikistan tbody > tr > td > a
Tanzania tbody > tr > td > a
Thailand tbody > tr > td > a
Timor-Leste tbody > tr > td > a
Togo tbody > tr > td > a
Tonga tbody > tr > td > a
Tunisia tbody > tr > td > a
Turkey tbody > tr > td > a
Turkmenistan tbody > tr > td > a
Turks And Caicos Islands tbody > tr > td > a
Uganda tbody > tr > td > a
Ukraine tbody > tr > td > a
United Arab Emirates tbody > tr > td > a
United Kingdom tbody > tr > td > a
United States tbody > tr > td > a
Uruguay tbody > tr > td > a
Us Virgin Islands tbody > tr > td > a
Uzbekistan tbody > tr > td > a
Vanuatu tbody > tr > td > a
Venezuela tbody > tr > td > a
Vietnam tbody > tr > td > a
Wallis And Futuna tbody > tr > td > a
Western Sahara tbody > tr > td > a
Zambia tbody > tr > td > a
Zimbabwe tbody > tr > td > a

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.

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
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
`[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
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Deprecated ARIA roles were not used
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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
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
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
`<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
Skip links are focusable.
`<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.
`<td>` elements in a large `<table>` have one or more table headers.
A
Heading Hierarchy
27 headings, 1 skip(s)
PASS
27 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Cost of Living
  • H3 Countries: skipped
  • H4 A
  • H4 B
  • H4 C
  • H4 D
  • H4 E
  • H4 F
  • H4 G
  • H4 H
  • H4 I
  • H4 J
  • H4 K
  • H4 L
  • H4 M
  • H4 N
  • H4 O
  • H4 P
  • H4 Q
  • H4 R
  • H4 S
  • H4 T
  • H4 U
  • H4 V
  • H4 W
  • H4 Y
  • H4 Z

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

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

Send Feedback