Skip to content
https://91shex.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
5
REVIEW
5
PASS
14
INFO
0
Checks
24
14 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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
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::
2 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 2 <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
49 landmarks
REVIEW
49 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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
Form Accessibility
6 of 7 controls have issues
REVIEW
6 of 7 controls have issues
Warning::
6 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="login-email">; <input type="password" id="login-password">; <input type="text" id="register-email">; <input type="password" id="register-password">; <input type="password" id="register-confirm">; <input type="text">
Info::
1 control(s) properly labeled
7 controls
1 labeled
6 placeholder only
0 unlabeled
ControlTypeLabelMethod
#site_search_inputsearch搜索帖子、账号或标签for/id
#login-emailtext(请输入账号)placeholder only
#login-passwordpassword(请输入密码)placeholder only
#register-emailtext(4-16位字母/数字)placeholder only
#register-passwordpassword(至少6位)placeholder only
#register-confirmpassword(再次输入密码)placeholder only
inputtext(请输入昵称)placeholder only

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

<input type="text" id="login-email">; <input type="password" id="login-password">; <input type="text" id="register-email">; <input type="password" id="register-password">; <input type="password" id="register-confirm">; <input type="text">

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
Mobile Keyboard & Autofill
1/4 eligible field(s) missing autocomplete or inputmode
REVIEW
1/4 eligible field(s) missing autocomplete or inputmode
Info::
1 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.
Got: <input type="search" id="site_search_input">
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 91成人社区最新黑料与成人视…
1.16:1
#000000
on
#171516
needs 3.0:1 (large text)
32px · bottom of viewport
h2 推荐
1.16:1
#000000
on
#171516
needs 3.0:1 (large text)
24px · bottom of viewport
h2 关注
1.16:1
#000000
on
#171516
needs 3.0:1 (large text)
24px · bottom of viewport
h2 最新
1.16:1
#000000
on
#171516
needs 3.0:1 (large text)
24px · bottom of viewport
title 91社 - 网红黑料与成人视频分…
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · top of page (header area)
span 91社
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · top of page (header area)
a 登录
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · top of page (header area)
span 首页
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · top of page (header area)
span 首页
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · above the fold
span 精选专题
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · above the fold
span 精选专题
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · above the fold
span 创作者
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · above the fold
span 创作者
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · above the fold
span 排行榜
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · above the fold
span 排行榜
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · above the fold
span 博客
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · above the fold
span 博客
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · above the fold
span 消息
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · mid-page
span 消息
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · mid-page
span 我的
1.16:1
#000000
on
#171516
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 91成人社区最新…1.16:13.0:1
#000000
#171516
Fail
h2 推荐1.16:13.0:1
#000000
#171516
Fail
h2 关注1.16:13.0:1
#000000
#171516
Fail
h2 最新1.16:13.0:1
#000000
#171516
Fail
title 91社 - 网红黑料…1.16:14.5:1
#000000
#171516
Fail
span 91社1.16:14.5:1
#000000
#171516
Fail
a 登录1.16:14.5:1
#000000
#171516
Fail
span 首页1.16:14.5:1
#000000
#171516
Fail
span 首页1.16:14.5:1
#000000
#171516
Fail
span 精选专题1.16:14.5:1
#000000
#171516
Fail
span 精选专题1.16:14.5:1
#000000
#171516
Fail
span 创作者1.16:14.5:1
#000000
#171516
Fail
span 创作者1.16:14.5:1
#000000
#171516
Fail
span 排行榜1.16:14.5:1
#000000
#171516
Fail
span 排行榜1.16:14.5:1
#000000
#171516
Fail
span 博客1.16:14.5:1
#000000
#171516
Fail
span 博客1.16:14.5:1
#000000
#171516
Fail
span 消息1.16:14.5:1
#000000
#171516
Fail
span 消息1.16:14.5:1
#000000
#171516
Fail
span 我的1.16:14.5:1
#000000
#171516
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
44 headings
PASS
44 headings
Info::
Single H1 present
  • H1 91成人社区最新黑料与成人视频资源
  • H2 推荐
  • H3 FapHouse台湾极品网黄 qubegirl化身饥渴小情妇跪舔多体位打桩到失神
  • H3 少妇白洁_第十二集_91社最新原创AI成人短剧
  • H3 Sweetiefox化身村姑户外挑逗扣穴胡萝卜爆菊彻底放纵
  • H3 妹妹的日常_第十集_91社最新原创AI成人短剧
  • H3 长生录 从侄女上门求丹开始长生_第十集_91社最新原创AI成人短剧
  • H3 穿过薄雾的早晨_第八集_91社最新原创AI成人短剧
  • H3 台湾美腿女神Alleys贝拉变身兔女郎机器人 浓毛狂野任宅男开发享受浓稠暴力中出
  • H3 ST站高颜值主播bigassgirl-00黑丝全裸开票直播水晶棒M腿挑逗白浆喷涌
  • H3 胡椒籽推特极品开裆黑丝骑乘弹力抽插白浆不断溢出
  • H3 霉霉学姐每日大赛原创黑丝油光后入视角喷射高潮
  • H3 日本FC2素人无码 精致长发美女被各种姿势干到高潮发软
  • H3 渡己_第九集 91社最新原创AI女优短剧激情上演
  • H3 推特极品福利姬梦中梦 和服半透T恤白虎娇躯骑乘娇喘到爆
  • H3 妹妹的日常_第九集_91社最新原创AI成人短剧
  • H3 少妇白洁_第十一集_91社最新原创AI成人短剧
  • H3 长生录 从侄女上门求丹开始长生_第九集_91社最新原创AI成人短剧
  • H3 妹妹的日常_第八集_91社最新原创AI成人短剧
  • H3 长生录 从侄女上门求丹开始长生_第八集_91社最新原创AI成人短剧
  • H3 渡己_第八集_91社最新原创AI成人短剧
  • H3 少妇白洁_第十集_91社最新原创AI成人短剧
  • H2 关注
  • H2 最新
  • H3 国产极品主播迷人奈制服黑丝足交假屌骑乘弹力插
  • H3 Puting_q黑丝直播玩道具高潮迭起血脉喷张
  • H3 司宁青穿豹纹皮靴重度调教直播羞辱长靴插马眼
  • H3 JVID高颜值Caroline卡洛琳穿越到家 大尺度翘臀黑森林极致诱惑
  • H3 JVID极品美腿模特啾啾最新作品 化身淫欲小秘书翘臀若隐若现欲望层层剥开
  • H3 JVID混血女神Mia酒店房务员激情加班 热情回应客人所有要求
  • H3 JVID雅捷职场女秘书被男同事无套内射满小腹
  • H3 JVID高颜值甜美女神肉包Mini化身白色小猫夜夜撒娇引人欲罢不能
  • H3 JVID极品制服百合双人缠绵 高颜值姐妹花互舔互摸
  • H3 JVID肉包Mini白色猫耳尾巴诱惑今晚我是你的小猫
  • H3 极品网黄爹咪 JVID露脸写真 被绑手铐戴眼罩后摘罩露出骚脸 各种姿势大尺度展写真
  • H3 极品网黄爹咪JVID露脸写真 被绑手铐戴眼罩后摘罩露骚脸多姿势大尺度
  • H3 JVID高清禁忌师生恋 人气模特妍妍与闺蜜女教师湿吻抚摸玩弄扣穴
  • H3 极品JVID甜美女神婕咪淼淼双人三穴齐开女子宿舍超尺度挑逗舔乳
  • H3 雅婕最新流出 短发御姐业务员签保单床上高潮
  • H3 JVID顶级女神黎菲兒 新作流出 按摩师撩拨高潮不断被彻底征服
  • H3 欧美无码BANGBROS 眼镜妹深喉黑人多姿势白虎高潮
  • H3 黑人美妞清晨唤醒日男 口手并用榨取狂喷如开香槟
  • H3 推特情侣小Q小K女友初次激战黑人巨根深插高强度打桩
  • H3 推特肥臀测评博主12Baegirl 误食剧情第一视角黑人巨根服侍
A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Info::
3 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: - H2: "推荐" - H2: "关注" - H2: "最新"
Got: 3 ≤2-char heading(s)
Info::
31 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: 31 all-caps heading(s)
A+
Alt Text Quality
All 199 images OK
PASS
All 199 images OK
Info::
199 image(s) with good alt text
199 images 199 good alt text
All images have appropriate alt text.
A
Form Input Types
2 input(s) using type=text where a specific type would help
PASS
2 input(s) using type=text where a specific type would help
Info::
Input "login-email" should use type="email" (currently type="text")
Field name "login-email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
Info::
Input "register-email" should use type="email" (currently type="text")
Field name "register-email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A
Form Input Quality
1 input-semantic issue(s) across 7 form control(s)
PASS
1 input-semantic issue(s) across 7 form control(s)
Info::
3 password field(s) missing or with invalid `autocomplete`
Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" id="login-password">, <input type="password" id="register-password">, <input type="password" id="register-confirm">.
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+
Tabindex Anti-Patterns
40 explicit tabindex attribute(s) checked, no anti-patterns
PASS
40 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 18 visible text node(s) render at >= 12 CSS pixels
PASS
All 18 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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 页面未找到 - 91社 ✓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
1 mobile-depth signal(s) detected
PASS
1 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.
A
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 26 passed
PASS
92

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
登录 header#app-header > div.relative > div.relative > a.mobile-not-login
全部 div.topic-wrap > div.topic-bar > div.topic-chips > a.topic-chip
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
+关注 div.feed > article.post-card > header.flex > button.btn-follow
加载更多 div.tab-panels > div.tab-panel > div.flex-center > a.load-more-btn

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
深 article.post-card > header.flex > div.flex > a.dx-avatar
+6 查看全部 div.tab-panel > div.feed > article.post-card > div.post-media-link
A article.post-card > header.flex > div.flex > a.dx-avatar
O article.post-card > header.flex > div.flex > a.dx-avatar
+7 查看全部 div.tab-panel > div.feed > article.post-card > div.post-media-link
A article.post-card > header.flex > div.flex > a.dx-avatar
A article.post-card > header.flex > div.flex > a.dx-avatar
A article.post-card > header.flex > div.flex > a.dx-avatar
短 article.post-card > header.flex > div.flex > a.dx-avatar
+11 查看全部 div.tab-panel > div.feed > article.post-card > div.post-media-link
主 article.post-card > header.flex > div.flex > a.dx-avatar
+6 查看全部 div.tab-panel > div.feed > article.post-card > div.post-media-link
丝 article.post-card > header.flex > div.flex > a.dx-avatar
+7 查看全部 div.tab-panel > div.feed > article.post-card > div.post-media-link
丝 article.post-card > header.flex > div.flex > a.dx-avatar
+9 查看全部 div.tab-panel > div.feed > article.post-card > div.post-media-link
A article.post-card > header.flex > div.flex > a.dx-avatar
+9 查看全部 div.tab-panel > div.feed > article.post-card > div.post-media-link
A article.post-card > header.flex > div.flex > a.dx-avatar
福 article.post-card > header.flex > div.flex > a.dx-avatar
+7 查看全部 div.tab-panel > div.feed > article.post-card > div.post-media-link
A article.post-card > header.flex > div.flex > a.dx-avatar
A article.post-card > header.flex > div.flex > a.dx-avatar
A article.post-card > header.flex > div.flex > a.dx-avatar
A article.post-card > header.flex > div.flex > a.dx-avatar
A article.post-card > header.flex > div.flex > a.dx-avatar
A article.post-card > header.flex > div.flex > a.dx-avatar
A article.post-card > header.flex > div.flex > a.dx-avatar
○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
●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
●`[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
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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
●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
●Image elements do not have `[alt]` attributes that are redundant text.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○Form elements have associated labels
○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.
○`[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
○Identical links have the same purpose.
○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