Skip to content
https://wanwuu.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
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
7 landmarks
REVIEW
7 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
3 of 13 controls have issues
REVIEW
3 of 13 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="register-email">; <input type="password" id="register-password">; <textarea id="report-content">
Info::
10 control(s) properly labeled
13 controls
10 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputsearchSearcharia-label
#searchsearchSearcharia-label
#searchsearchSearcharia-label
#login-emailtext用户名 (杜绝注册多个帐号，将删除所有帐号，并封IP)for/id
#login-passwordpassword密码for/id
#pwa-hiddencheckboxnone
#report-item1radio损害了我的权利或涉及其它法律问题for/id
#report-item2radio版权原因for/id
#report-item3radio垃圾或误导性内容for/id
#report-item4radio内容不当或令人反感for/id
#register-passwordpassword(请输入密码)placeholder only
#register-emailtext(请输入用户名)placeholder only
#report-contenttextarea(额外信息)placeholder only

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

<input type="text" id="register-email">; <input type="password" id="register-password">; <textarea id="report-content">

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
Mobile Keyboard & Autofill
Action
3/5 eligible field(s) missing autocomplete or inputmode
REVIEW
3/5 eligible field(s) missing autocomplete or inputmode
Warning::
3 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">, <input type="search" id="search">, <input type="search" id="search">
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 热门SM调教视频合集与精选资…
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
32px · bottom of viewport
h2 当前最热
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 最近更新
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 直播回放
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 国产sm
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 日韩sm
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 欧美sm
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 动漫sm
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 调教av
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 AI成人短剧
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
24px · bottom of viewport
h2 精选合集
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
24px · bottom of viewport
h3 白袜
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 走绳绳艺
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 恋足舔脚
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 野生缅北
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 踩踏
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 母狗
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 男M
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
19px · bottom of viewport
h3 黑丝
1.18:1
#000000
on
#181818
needs 3.0:1 (large text)
19px · bottom of viewport
title 玩物社区 - 调教母狗与女王调…
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 热门SM调教视频…1.18:13.0:1
#000000
#181818
Fail
h2 当前最热1.18:13.0:1
#000000
#181818
Fail
h2 最近更新1.18:13.0:1
#000000
#181818
Fail
h2 直播回放1.18:13.0:1
#000000
#181818
Fail
h2 国产sm1.18:13.0:1
#000000
#181818
Fail
h2 日韩sm1.18:13.0:1
#000000
#181818
Fail
h2 欧美sm1.18:13.0:1
#000000
#181818
Fail
h2 动漫sm1.18:13.0:1
#000000
#181818
Fail
h2 调教av1.18:13.0:1
#000000
#181818
Fail
h2 AI成人短剧1.18:13.0:1
#000000
#181818
Fail
h2 精选合集1.18:13.0:1
#000000
#181818
Fail
h3 白袜1.18:13.0:1
#000000
#181818
Fail
h3 走绳绳艺1.18:13.0:1
#000000
#181818
Fail
h3 恋足舔脚1.18:13.0:1
#000000
#181818
Fail
h3 野生缅北1.18:13.0:1
#000000
#181818
Fail
h3 踩踏1.18:13.0:1
#000000
#181818
Fail
h3 母狗1.18:13.0:1
#000000
#181818
Fail
h3 男M1.18:13.0:1
#000000
#181818
Fail
h3 黑丝1.18:13.0:1
#000000
#181818
Fail
title 玩物社区 - 调…1.32:14.5:1
#000000
#222222
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
91 headings
PASS
91 headings
Info::
Single H1 present
  • H1 热门SM调教视频合集与精选资源
  • H2 当前最热
  • H3 玩物直播温柔酷女王调教皮鞋白袜踩贱
  • H3 莉莉丝女王 首调ATM母畜续集双视角狠虐
  • H3 套路直播三三女王调教开发素人技师
  • H3 贱绿帽伺候夫妻主 舔逼含枪看老婆被操到喷水
  • H3 sm调教 推特重口凋教大神 不当人玩法真可怕 暴力调教女m
  • H3 职场菜鸟沦为ol私有物 办公室极致调教 黄金圣水窒息坐脸
  • H3 主动提出街头掠食者角色扮演 被擒获捆绑后把痛苦变成快感
  • H3 全家沦陷被抢走 禁忌母女共侍巨根 嫩穴被爆操 绝顶高潮求原谅
  • H2 最近更新
  • H3 玩物直播子熙女王调教强制坐脸窒息
  • H3 玩物直播缈缈女王调教脏鞋白袜踩踏场
  • H3 玩物直播小婷女王调教恋足喝洗脚水羞辱踩踏
  • H3 阴环乳环女m露娜塞着跳蛋自慰 跪着狂舔我脚趾 爽到喷汁抖个不停
  • H3 光头男m吃主人的口水 等待女王的黄金圣水调教
  • H3 日系家庭主妇的玉足调教家奴的自我修养 被无套猛操到高潮
  • H3 莱克西贝尔调教女王 被无套猛操到高潮失控彻底沉沦
  • H3 极品黑丝少妇与猛男深夜户外野战肛交调教 3d动画
  • H2 直播回放
  • H3 套路直播甜甜女王调教新素人开发
  • H3 不知名美女女王 挑战纯sp 300鞭狠抽
  • H3 凉子女王调教 短发女王红绿灯寸止榨精羞辱早泄废物
  • H3 套路直播暴主s女王调教继续调狗
  • H3 冰诺女王情侣奴奴下奴暴打犯贱中集
  • H3 玩物直播于于鱼网调学姐早泄训练
  • H3 玩物直播元宵sama女王调教新人妹妹首秀生涩调狗
  • H3 玩物直播梦梦女王调教骑马裸足狂舔圣水
  • H2 国产sm
  • H3 黑皮裤女王大腿绞脖 床上木乃伊保鲜膜窒息锁喉
  • H3 精神小妹调教肥猪男M 强制舔脏鞋底白袜玉足
  • H3 淳朴学妹和母狗学姐惨遭男友玩弄调教视频流出
  • H3 黑丝女王马桶视角坐脸 黄金热屎直接拉你嘴里
  • H3 高冷御姐铁笼圈养饥渴贱奴 爬行跪舔黑丝美腿皮鞭重度凌辱
  • H3 她们穿着白衬衫的修长美腿交叠着施力 脚心用力压住棒身来回摩擦
  • H3 黑丝女王高跟狠踩男奴肉棒 丝足足交寸止折磨到他哀求喷射
  • H3 sm调教捆绑被绳子捆住手腕的巨乳黑丝女人
  • H2 日韩sm
  • H3 享受两位日本女主调教责罚的男奴，残酷榨精后强迫全部吞下
  • H3 女王上海妖姬台湾微S众女王变态虐日本贱狗 鞭踹踩脸
  • H3 我被倒吊深喉狠操 整张脸被巨屌操到口水狂喷滴得到处都是 鼻涕眼泪全流下来
  • H3 韩国母狗自愿肛奴调教 各种道具玩弄 爆菊到强制高潮 喷射不停
  • H3 白裙肉丝女王坐脸男奴 室内翘臀压脸足趾塞嘴
  • H3 清纯女儿的惩罚时刻 束缚下的亲密sm感官博弈
  • H3 日本网黄 参加射精耐力锦标赛 双人轮番蹂躏鸡吧榨取浓精
  • H3 韩国母狗调教 肛门拳交训练 60厘米超长玩具顶胃插肛 一步到位
  • H2 欧美sm
  • H3 女M双手捆绑塞口球 双腿高吊大屌打桩猛干骚逼喷水
  • H3 纹身花腿四爱女王霸气调教 携手素人闺蜜 暴力虐阳捆绑快感
  • H3 女王椅上撸管男奴 胶带捆椅强制榨精五次
  • H3 熟女被缚承受打屁股阴蒂泵与阴道夹强力刺激连续五次高潮极乐
  • H3 甜狐姐渔网袜嫩脚把鸡巴夹得死紧猛足交 精液全涂满她渔网脚背
  • H3 女王水晶贞操锁手撸射精 精液倒酒杯强制男M吞咽Slave
  • H3 另类真空吸乳捆绑调教 冰冷的针刺乳房缝合阴道
  • H3 BDSM欧美巨乳女友被轻度SM调教 白虎穴肿胀不已 变成一只好色的母狗
  • H2 动漫sm
  • H3 ｓｍ動画 抖M侠 颜玥之章 贱狗颜玥被女王按倒狂扇耳光
  • H3 エロ動画 sm Lunara天使协议机械败北与触手调教
  • H3 OVA千鹤酱开发日记2 优等生椎名千鹤被教员月野无套狂操开发
  • H3 可爱勇者妹妹冒险归来 被我按倒从后面狂插骚穴 操到翻白眼全身抽搐
  • H3 一个不能告诉任何人的秘密 love sm巨乳剧情
  • H3 pinkerton极品肉体 掰开腿猛干 顶满肉穴 浪叫喷水 身体抽搐
  • H3 小区肉便器巨乳人妻被各种肉棒调教成性奴多人轮番操肉逼
  • H3 帆刈叶乐园终焉 极品肉体 掰开腿猛干 顶满肉穴 浪叫喷水
  • H2 调教av
  • H3 河北彩花Re:start 中文字幕成熟性感POV第一视角主动中出-part2
  • H3 cmc-293 变态老师的喜欢事物 制服肉便器前女友调教 萌波铃
  • H3 我是社长夫人特别助理 让新进员工回头的调教情事
  • H3 bban-454 森泽佳奈日本淫乱女同 虐待调教中文字幕
  • H3 寂寞情深超会玩 多具自慰炮击插逼喷水 后调教男公狗止寸射精玩弄
  • H3 平时是个死板认真的眼镜经理社员没想到竟然是m性感店的女王大人
  • H3 mane-016 完全m男化飞行生活 美女空姐来调教 佐佐木明希
  • H3 看似普通的中年家政妇 其实是女王气质的超级痴女
  • H2 AI成人短剧
  • H3 色情短剧 脑机03 接口一接上就自动开做 研究博士被按在实验台 内射算数据采集
  • H3 求佛被日AI短剧 高冷女网红寺庙求佛被神秘力量控制 当场被日到腿软求饶 这反差谁顶得住
  • H3 AI成人短剧 50元买断人妻02 系统扫描锁定电梯少妇 五十块操嫩穴 潮吹算赠品
  • H3 AI成人短剧 三国龙起06 回到三国 茶室里把男主勾上床 茶还没凉人已经在做
  • H3 AI成人短剧 我的岳母苏沛真04 岳母在厨房勾引被按在台面后入抽插
  • H3 AI成人短剧 深夜潜入女大学生宿舍03 潜入后被按在宿舍床上后入抽插
  • H3 AI成人短剧 拼逼逼06 绿帽女友在旁边看着我和她闺蜜做 内射完她还没挪开眼
  • H3 野生缅北01 AI成人短剧 高薪骗进园区后 她成了谁的禁脔 看完后背发凉
  • H2 精选合集
  • H3 白袜
  • H3 走绳绳艺
  • H3 恋足舔脚
  • H3 野生缅北
  • H3 踩踏
  • H3 母狗
  • H3 男M
  • H3 黑丝
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: - H3: "白袜" - H3: "踩踏" - H3: "母狗"
Got: 3 ≤2-char heading(s)
Info::
61 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: 61 all-caps heading(s)
A
Alt Text Quality
3 of 135 images have issues
PASS
3 of 135 images have issues
Warning::
3 image(s) with generic alt text
Info::
132 image(s) with good alt text
135 images 132 good alt text 3 generic
IssueCount
generic3 image(s)
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 13 form control(s)
PASS
1 input-semantic issue(s) across 13 form control(s)
Info::
2 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">.
A+
Document Language
Lang attribute set to "zh-Hans"
PASS
Lang attribute set to "zh-Hans"
Info::
<html lang="zh-Hans"> is set and valid
Got: zh-Hans
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
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 109 visible text node(s) render at >= 12 CSS pixels
PASS
All 109 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 页面未找到 - 玩物社区 ✓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 94/100 — 1 failing, 22 passed
PASS
94

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.hidden > div.fixed > div.pl-3 > button.dx-pwa-close div.hidden > div.fixed > div.pl-3 > button.dx-pwa-close

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.

○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●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
○Deprecated ARIA roles were not used
○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
○`[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
○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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○`<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
○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