Skip to content
https://openresty.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
44
GRADE
F
FIX
6
REVIEW
7
PASS
0
INFO
0
Checks
13
7 REVIEW 6 FIX
F
Alt Text Quality
Action
33 of 33 images have issues
FIX
33 of 33 images have issues
Critical::
33 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
32 image-in-link without alt text
An image inside a link with no alt creates an empty link.
33 images 33 missing
IssueCount
missing33 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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Present
PNG Icons Missing
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
2 landmarks
REVIEW
2 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
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 header 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

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
Heading Hierarchy
12 headings
REVIEW
12 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 OpenResty®
  • H2 More Interesting Topics
  • H3 26 Mar 2026
  • H3 25 Mar 2026
  • H3 03 Mar 2026
  • H3 28 Feb 2026
  • H3 21 Oct 2025
  • H3 16 Jul 2025
  • H3 03 Apr 2025
  • H3 31 Mar 2025
  • H3 17 Oct 2024
  • H3 21 Jul 2024

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

C
Form Accessibility
Action
4 of 4 controls have issues
REVIEW
4 of 4 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="image" name="submit">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="name">; <input type="email" name="email">; <input type="search" name="query" id="search">
4 controls
0 labeled
3 placeholder only
1 unlabeled
ControlTypeLabelMethod
nametext(Enter your full name)placeholder only
emailemail(Enter your business email)placeholder only
#searchsearch(Search OpenResty.org)placeholder only
submitimage(none)none

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

<input type="image" name="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

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

<input type="text" name="name">; <input type="email" name="email">; <input type="search" name="query" id="search">

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title 404 Not Found 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 7 pass AA only
p Advanced observability built for OpenRes…
3.52:1
#000000
on
#446D44
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 OpenResty®20.32:13.0:1
#000000
#F9FCF9
Pass
h2 More Interesting Top…20.32:13.0:1
#000000
#F9FCF9
Pass
h3 26 Mar 202620.32:13.0:1
#000000
#F9FCF9
Pass
h3 25 Mar 202620.32:13.0:1
#000000
#F9FCF9
Pass
h3 03 Mar 202620.32:13.0:1
#000000
#F9FCF9
Pass
h3 28 Feb 202620.32:13.0:1
#000000
#F9FCF9
Pass
h3 21 Oct 202520.32:13.0:1
#000000
#F9FCF9
Pass
h3 16 Jul 202520.32:13.0:1
#000000
#F9FCF9
Pass
h3 03 Apr 202520.32:13.0:1
#000000
#F9FCF9
Pass
h3 31 Mar 202520.32:13.0:1
#000000
#F9FCF9
Pass
h3 17 Oct 202420.32:13.0:1
#000000
#F9FCF9
Pass
h3 21 Jul 202420.32:13.0:1
#000000
#F9FCF9
Pass
title OpenResty® - Open s…5.48:14.5:1
#000000
#588F58
Pass
a OpenResty5.29:14.5:1
#000000
#578C57
Pass
small Scalable Web Platfor…5.15:14.5:1
#000000
#558A55
Pass
span Contribute on GitHub5.03:14.5:1
#000000
#548854
Pass
span Official Forum4.84:14.5:1
#000000
#528552
Pass
span Try OpenResty XRay4.72:14.5:1
#000000
#518351
Pass
div OpenResty XRay4.59:14.5:1
#000000
#4F814F
Pass
p Advanced observabili…3.52:14.5:1
#000000
#446D44
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.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 6 failing, 21 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.

ARIA

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
OpenResty® Scalable Web Platform by Extending NGINX with Lua Contribute on Git… body > header

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
Installation nav#nav > ul > li > a
YouTube Channel nav#nav > ul > li > a
Video Tutorials nav#nav > ul > li > a
Enterprise Solutions nav#nav > ul > li > a
Getting Started nav#nav > ul > li > a
Upgrading nav#nav > ul > li > a
Changes nav#nav > ul > li > a
Events nav#nav > ul > li > a
Components nav#nav > ul > li > a
Community nav#nav > ul > li > a
Benchmark nav#nav > ul > li > a
Contact us nav#nav > ul > li > a
Debugging nav#nav > ul > li > a
Donate Online nav#nav > ul > li > a
Donors nav#nav > ul > li > a
eBooks nav#nav > ul > li > a
FAQ nav#nav > ul > li > a
Getting Involved nav#nav > ul > li > a
Presentations nav#nav > ul > li > a
Profiling nav#nav > ul > li > a
Quality Assurance nav#nav > ul > li > a
Resources nav#nav > ul > li > a
Samples nav#nav > ul > li > a
User Survey nav#nav > ul > li > a
About nav#nav > ul > li > a
中文站 nav#nav > ul > li > a
OpenResty.com nav#nav > ul > li > a
OpenResty 1.29.2.3 div.news > div.news-item > div.news-description > a
OpenResty 1.27.1.2 div.news > div.news-item > div.news-description > a
Binary Evidence-Driven Vulnerability Scanning: Eliminating False Positives with… div.news > div.news-item > div.news-description > a
OpenResty XRay Version 26.2.1. Now Available div.news > div.news-item > div.news-description > a
End-to-End Client Real IP Passthrough in OpenResty Edge div.news > div.news-item > div.news-description > a
How OpenResty XRay Enables Full-Stack Dynamic Tracing in Production div.news > div.news-item > div.news-description > a
What is OpenResty Edge div.news > div.news-item > div.news-description > a
Introduction to OpenResty XRay div.news > div.news-item > div.news-description > a
Nginx div.item > div.body > p > a
LuaJIT div.item > div.body > p > a
3rd-party Nginx modules div.item > div.body > p > a
Nginx div.item > div.body > p > a
Nginx div.item > div.body > p > a
Nginx div.item > div.body > p > a
Nginx div.item > div.body > p > a
Nginx div.item > div.body > p > a
Nginx div.item > div.body > p > a
Nginx div.item > div.body > p > a
Components div.item > div.body > p > a
GettingStarted div.item > div.body > p > a
Download div.item > div.body > p > a
Community div.item > div.body > p > a
OpenResty Inc. div.item > div.body > p > a
26 MAR 2026 div#timeline > ul > li > h3
Changes li > ul > li > a
Download li > ul > li > a
25 MAR 2026 div#timeline > ul > li > h3
OpenResty 1.29.2.3 Released li > ul > li > a
ChangeLog for 1.29.2.x li > ul > li > a
03 MAR 2026 div#timeline > ul > li > h3
OpenResty 1.29.2.1 Released li > ul > li > a
28 FEB 2026 div#timeline > ul > li > h3
OpenResty® Linux Packages li > ul > li > a
21 OCT 2025 div#timeline > ul > li > h3
OpenResty® EC2 Test Cluster li > ul > li > a
16 JUL 2025 div#timeline > ul > li > h3
Lua Cjson Library li > ul > li > a
03 APR 2025 div#timeline > ul > li > h3
OpenResty 1.27.1.2 Released li > ul > li > a
31 MAR 2025 div#timeline > ul > li > h3
ChangeLog for 1.27.1.x li > ul > li > a
17 OCT 2024 div#timeline > ul > li > h3
OpenResty 1.27.1.1 Released li > ul > li > a
21 JUL 2024 div#timeline > ul > li > h3
ChangeLog for 1.19.9.x li > ul > li > a
OpenResty 1.25.3.2 Released li > ul > li > a
ChangeLog for 1.25.3.x li > ul > li > a
OpenResty 1.21.4.4 Released li > ul > li > a
ChangeLog for 1.21.4.x li > ul > li > a
OpenResty 1.19.9.2 Released li > ul > li > a
OpenResty® is a registered trademark owned by OpenResty Inc. body > div.content-footer > div.footer > p
OpenResty Inc div.content-footer > div.footer > p > a
Copyright © 2017, 2018, 2019, 2020, 2021, 2022 by Yichun Zhang (agentzh) body > div.content-footer > div.footer > p
100% Powered by OpenResty and PostgreSQL ( view the source code of this site) body > div.content-footer > div.footer > p
view the source code of this site div.content-footer > div.footer > p > a

These are opportunities to improve the legibility of your content.

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
header > p.site-name > a > img header > p.site-name > a > img
header > p.right > a > img header > p.right > a > img
header > p.right > a > img.dark-img header > p.right > a > img.dark-img
header > p.right > a.enterprise-button > img header > p.right > a.enterprise-button > img
div.news-item > a > picture > img.news-img div.news-item > a > picture > img.news-img
div.news-item > a > picture > img.news-img div.news-item > a > picture > img.news-img
div.news > div.news-item > a > img.news-img div.news > div.news-item > a > img.news-img
div.news > div.news-item > a > img.news-img div.news > div.news-item > a > img.news-img
div.news > div.news-item > a > img.news-img div.news > div.news-item > a > img.news-img
div.news > div.news-item > a > img.news-img div.news > div.news-item > a > img.news-img
div.news > div.news-item > a > img.news-img div.news > div.news-item > a > img.news-img
div.news > div.news-item > a > img.news-img div.news > div.news-item > a > img.news-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img
div.swiper-slide > a.article-item > div.blog-img > img.article-img div.swiper-slide > a.article-item > div.blog-img > img.article-img

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
body > header > p.site-name > a body > header > p.site-name > a
section#main > div.news > div.news-item > a section#main > div.news > div.news-item > a
section#main > div.news > div.news-item > a section#main > div.news > div.news-item > a
section#main > div.news > div.news-item > a section#main > div.news > div.news-item > a
section#main > div.news > div.news-item > a section#main > div.news > div.news-item > a
section#main > div.news > div.news-item > a section#main > div.news > div.news-item > a
section#main > div.news > div.news-item > a section#main > div.news > div.news-item > a
section#main > div.news > div.news-item > a section#main > div.news > div.news-item > a
section#main > div.news > div.news-item > a section#main > div.news > div.news-item > 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.

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
Go to slide 1 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 6 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 7 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 8 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 9 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 10 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 11 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 12 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 13 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 14 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 15 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 16 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 17 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 18 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 19 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 20 div#swiper-parent > div#article-carousel > div.swiper-pagination > span.swiper-pagination-bullet

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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
`<input type="image">` elements have `[alt]` text
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
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
No element has a `[tabindex]` value greater than 0
Heading elements appear in a sequentially-descending order
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` 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
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.
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.
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