Skip to content
https://huangguoai.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
5
REVIEW
7
PASS
12
INFO
0
Checks
24
12 PASS 7 REVIEW 5 FIX
D
Tap Target Adequacy
Action
27 tap target(s) too small or too close together
FIX
27 tap target(s) too small or too close together
Warning::
27 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
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
Landmark Structure
18 landmarks
REVIEW
18 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
2 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 ASIDE "推广" CONTENTINFO footer

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

B
Mobile Keyboard & Autofill
2/7 eligible field(s) missing autocomplete or inputmode
REVIEW
2/7 eligible field(s) missing autocomplete or inputmode
Info::
2 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search, email.
Got: <input type="search" name="keyword">, <input type="email" name="email">
B
Tabindex Anti-Patterns
0 positive, 5 -1-on-focusable
REVIEW
0 positive, 5 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
C
Mobile-Readable Font Sizes
Action
82% of visible text renders at >= 12 CSS px (59 below threshold)
REVIEW
82% of visible text renders at >= 12 CSS px (59 below threshold)
Warning::
59 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("广告"); <h1> 11.0px ("黄果短剧"); <span> 11.0px ("·AI短剧与原创短剧在线观看"); <span> 11.0px ("更新至3集"); <span> 11.0px ("8.6w").
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, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 黄果短剧
1.01:1
#000000
on
#020203
needs 3.0:1 (large text)
32px · bottom of viewport
h2 热门标签
1.01:1
#000000
on
#020203
needs 3.0:1 (large text)
24px · bottom of viewport
h2 黄果原创
1.01:1
#000000
on
#020203
needs 3.0:1 (large text)
24px · bottom of viewport
h2 精选推荐
1.01:1
#000000
on
#020203
needs 3.0:1 (large text)
24px · bottom of viewport
h2 最近上新
1.01:1
#000000
on
#020203
needs 3.0:1 (large text)
24px · bottom of viewport
h2 热播短剧
1.01:1
#000000
on
#020203
needs 3.0:1 (large text)
24px · bottom of viewport
h2 专题推荐
1.01:1
#000000
on
#020203
needs 3.0:1 (large text)
24px · bottom of viewport
h2 黄果短剧官方入口
1.01:1
#000000
on
#020203
needs 3.0:1 (large text)
24px · bottom of viewport
h2 永不失联|收藏保存地址
1.01:1
#000000
on
#020203
needs 3.0:1 (large text)
24px · bottom of viewport
h3 精品高分AI短剧专辑
1.01:1
#000000
on
#020203
needs 3.0:1 (large text)
19px · bottom of viewport
h3 家庭伦理AI短剧专辑
1.01:1
#000000
on
#020203
needs 3.0:1 (large text)
19px · bottom of viewport
h3 校园青春AI成人短剧
1.01:1
#000000
on
#020203
needs 3.0:1 (large text)
19px · bottom of viewport
title 黄果短剧官网 - AI短剧、原创矅
1.03:1
#000000
on
#050403
needs 4.5:1 (normal text)
16px · top of page (header area)
span 黄果短剧
1.02:1
#000000
on
#040403
needs 4.5:1 (normal text)
16px · top of page (header area)
a 首页
1.03:1
#000000
on
#050403
needs 4.5:1 (normal text)
16px · top of page (header area)
a 黄果原创
1.03:1
#000000
on
#050504
needs 4.5:1 (normal text)
16px · top of page (header area)
a 短剧
1.18:1
#000000
on
#1E1615
needs 4.5:1 (normal text)
16px · above the fold
a 漫剧
1.43:1
#000000
on
#2D2724
needs 4.5:1 (normal text)
16px · above the fold
a 专题
1.18:1
#000000
on
#201514
needs 4.5:1 (normal text)
16px · above the fold
a 排行榜
1.24:1
#000000
on
#27191C
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 黄果短剧1.01:13.0:1
#000000
#020203
Fail
h2 热门标签1.01:13.0:1
#000000
#020203
Fail
h2 黄果原创1.01:13.0:1
#000000
#020203
Fail
h2 精选推荐1.01:13.0:1
#000000
#020203
Fail
h2 最近上新1.01:13.0:1
#000000
#020203
Fail
h2 热播短剧1.01:13.0:1
#000000
#020203
Fail
h2 专题推荐1.01:13.0:1
#000000
#020203
Fail
h2 黄果短剧官方å……1.01:13.0:1
#000000
#020203
Fail
h2 永不失联|收è—…1.01:13.0:1
#000000
#020203
Fail
h3 精品高分AI短剧…1.01:13.0:1
#000000
#020203
Fail
h3 家庭伦理AI短剧…1.01:13.0:1
#000000
#020203
Fail
h3 校园青春AI成人…1.01:13.0:1
#000000
#020203
Fail
title 黄果短剧官网 -…1.03:14.5:1
#000000
#050403
Fail
span 黄果短剧1.02:14.5:1
#000000
#040403
Fail
a 首页1.03:14.5:1
#000000
#050403
Fail
a 黄果原创1.03:14.5:1
#000000
#050504
Fail
a 短剧1.18:14.5:1
#000000
#1E1615
Fail
a 漫剧1.43:14.5:1
#000000
#2D2724
Fail
a 专题1.18:14.5:1
#000000
#201514
Fail
a 排行榜1.24:14.5:1
#000000
#27191C
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.

A+
Heading Hierarchy
54 headings
PASS
54 headings
Info::
Single H1 present
  • H1 黄果短剧
  • H2 热门标签
  • H2 黄果原创
  • H3 警界之花
  • H3 陈夫人你和孩子我都要
  • H3 从永劫无间开始:操翻游戏界
  • H3 镜魂:萧浩的复仇
  • H3 我的老师竟是大吊女皇
  • H3 炮友
  • H3 来自女儿深沉的爱
  • H2 精选推荐
  • H3 猩红入侵
  • H3 任意门
  • H3 家庭教师
  • H3 蜜桃臀
  • H3 微信性爱系统
  • H3 母猪师尊
  • H3 高三爱情故事
  • H2 最近上新
  • H3 高冷千金的贴身高手
  • H3 萝莉便利店
  • H3 重生逆袭:丑小鸭变万人迷
  • H3 法袍之下
  • H3 blg牛逼
  • H3 童锦程约会宇宙
  • H3 月亮-广寒宫
  • H3 黑道X上班族
  • H3 假面之下,心动难藏
  • H3 我的小姨子
  • H3 庆余年
  • H3 指令之环
  • H3 曹操穿越10国
  • H3 有五个姐姐的我第二季
  • H2 热播短剧
  • H3 神瞳觉醒 第一季
  • H3 女友帮我操闺蜜
  • H3 少妇白洁
  • H3 时停手表
  • H3 失踪的飞机杯
  • H3 母子同欢
  • H3 母上攻略
  • H3 网调我的冰山妈妈
  • H3 东京牛头人
  • H3 艳福风流传
  • H3 妈妈陪儿子高考
  • H3 存在感:零
  • H3 50元买断人妻
  • H3 全班地铁求生_只有我一个男生
  • H2 专题推荐
  • H3 精品高分AI短剧专辑
  • H3 家庭伦理AI短剧专辑
  • H3 校园青春AI成人短剧
  • H2 黄果短剧官方入口
  • H2 永不失联|收藏保存地址
A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Info::
1 heading(s) are too short (≤2 characters) to convey meaning
Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "炮友"
Got: 1 ≤2-char heading(s)
Info::
49 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 49 all-caps heading(s)
A+
Alt Text Quality
All 153 images OK
PASS
All 153 images OK
Info::
85 decorative image(s) correctly marked
Info::
68 image(s) with good alt text
153 images 68 good alt text 85 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 7 controls labeled
PASS
All 7 controls labeled
Info::
7 control(s) properly labeled
7 controls
7 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
keywordsearchnone
usernametext账号none
passwordpassword密码none
usernametext账号none
passwordpassword密码none
confirm_passwordpassword确认密码none
emailemail电子邮箱(选填)none
A+
Form Input Types
7 form control(s) checked, no type mismatches
PASS
7 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
7 form control(s) checked, no input-semantic issues
PASS
7 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "zh-CN"
PASS
Lang attribute set to "zh-CN"
Info::
<html lang="zh-CN"> is set and valid
Got: zh-CN
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 页面未找到 · 黄果短剧 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
Info::
Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices
The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.
A
Lighthouse Accessibility Audits
Score 93/100 — 3 failing, 26 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.

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 黄果短剧 · ALL RIGHTS RESERVED footer#app-footer > div.hg-footer__inner > div.hg-footer__brand > p.hg-footer__copy
本站内容仅限 18 岁以上成年人 footer#app-footer > div.hg-footer__inner > div.hg-footer__brand > p.hg-footer__copy
备用访问地址: div.hg-footer__brand > div.hg-footer__addrs > p > span
备用访问地址: div.hg-footer__brand > div.hg-footer__addrs > p > span
备用访问地址: div.hg-footer__brand > div.hg-footer__addrs > p > span
永久地址发布页2: div.hg-footer__brand > div.hg-footer__addrs > p > span
永久地址发布页3: div.hg-footer__brand > div.hg-footer__addrs > p > span
AI成人短剧 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
AI成人漫剧 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
黄果原创 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
专题 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
排行榜 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
最近上新 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
热门推荐 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
关于我们 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
官方域名与账号说明 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
常见问题 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
联系我们 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
加入我们 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
回家的路 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
隐私政策 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
使用协议 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
DMCA div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
内容移除 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
2257 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > 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
切换轮播,第1张 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播,第2张 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播,第3张 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播,第4张 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播,第5张 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播,第6张 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播,第7张 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播,第8张 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播,第9张 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播,第10张 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播,第11张 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播,第12张 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
AI成人漫剧 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
黄果原创 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
专题 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
排行榜 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
最近上新 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
热门推荐 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
官方域名与账号说明 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
常见问题 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
联系我们 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
加入我们 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
回家的路 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
使用协议 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
DMCA div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
内容移除 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
2257 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a

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
搜索短剧 header#app-header > div.header > div.hg-header__inner > button.hg-header__search-btn
○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
●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○The page contains a heading, skip link, or landmark region
○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
○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
○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.
○`<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
○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