Skip to content
https://mrds365.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
Form Accessibility
Action
4 of 8 controls have issues
FIX
4 of 8 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="number" name="page" id="pageNum">; <select id="languageSelect">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="mobile-search-box-input">; <input type="text" id="input-desktop-control-key">
Info::
4 control(s) properly labeled
8 controls
4 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#friend-siteNameinput网站名称 *for/id
#friend-contactinput联系方式 *for/id
#friend-siteUrlurl网站地址 *for/id
agreementcheckboxnone
#mobile-search-box-inputtext(输入你想要搜索的关键词)placeholder only
#input-desktop-control-keytext(输入你想搜索的关键词...)placeholder only
#pageNumnumber(none)none
#languageSelectselect(none)none

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

<input type="number" name="page" id="pageNum">; <select id="languageSelect">

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" id="mobile-search-box-input">; <input type="text" id="input-desktop-control-key">

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

D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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
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
9 landmarks
REVIEW
9 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 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

C
Mobile Keyboard & Autofill
Action
2/3 eligible field(s) missing autocomplete or inputmode
REVIEW
2/3 eligible field(s) missing autocomplete or inputmode
Warning::
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: numeric, url.
Got: <input type="number" name="page" id="pageNum">, <input type="url" name="url" id="friend-siteUrl">
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 页面不存在 - 每天大赛网 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #000000 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · bottom of viewport
h2 每天大赛(mrds365.com)持续更æ–…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 中国新说唱亚军 新秀 被前妻 ç…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 男网红二蛋和小羊出轨瓜,女å…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 从AV女优到全球DJ 滨崎真绪 人ç…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 黑丝御姐 被巨根轮番深喉侵犯
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 冰城玫姿 灰丝玉足羞辱足交强…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 AI短剧 催眠眼镜 第7集连载 绿å…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 AI短剧母上攻略第21集连载 高内
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 深圳大学校园女神 李婉珺 约ç…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 西安外国语大学大三学姐 余甜…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 语柠柠柠 清纯眼镜妹全裸手指…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 推特黑丝秘书 下班后被老板用…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 推特日本福利姬 浴室湿身狂秀…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 梨落声控舔蜜棒 酥软耳语直击…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 桥本香菜 搭讪微醺少妇酒吧直…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 丝袜美腿足交 挑战赛直播
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 推特极品福利姬 小星 超顶多奅
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 小薰伪娘 身着暴露衣物 户外ç‹…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 思琪 热舞无内翘臀丝足诱惑
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 每天大赛 - 全ç½…1.00:13.0:1
#000000
#000000
Fail
h2 每天大赛(mrds3…1.00:13.0:1
#000000
#000000
Fail
h2 中国新说唱亚内1.00:13.0:1
#000000
#000000
Fail
h2 男网红二蛋和å°…1.00:13.0:1
#000000
#000000
Fail
h2 从AV女优到全球…1.00:13.0:1
#000000
#000000
Fail
h2 黑丝御姐 被巨æ…1.00:13.0:1
#000000
#000000
Fail
h2 冰城玫姿 灰丝ç…1.00:13.0:1
#000000
#000000
Fail
h2 AI短剧 催眠眼é•…1.00:13.0:1
#000000
#000000
Fail
h2 AI短剧母上攻略…1.00:13.0:1
#000000
#000000
Fail
h2 深圳大学校园奅1.00:13.0:1
#000000
#000000
Fail
h2 西安外国语大å­…1.00:13.0:1
#000000
#000000
Fail
h2 语柠柠柠 清纯ç…1.00:13.0:1
#000000
#000000
Fail
h2 推特黑丝秘书 ä…1.00:13.0:1
#000000
#000000
Fail
h2 推特日本福利å§…1.00:13.0:1
#000000
#000000
Fail
h2 梨落声控舔蜜棅1.00:13.0:1
#000000
#000000
Fail
h2 桥本香菜 搭讪å…1.00:13.0:1
#000000
#000000
Fail
h2 丝袜美腿足交 æ…1.00:13.0:1
#000000
#000000
Fail
h2 推特极品福利å§…1.00:13.0:1
#000000
#000000
Fail
h2 小薰伪娘 身着æ…1.00:13.0:1
#000000
#000000
Fail
h2 思琪 热舞无内ç…1.00:13.0:1
#000000
#000000
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.

B
Lighthouse Accessibility Audits
Score 80/100 — 2 failing, 12 passed
REVIEW
80

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.

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.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Chinese English div.warning-flex-box > div.option-container > div.select-dropdown > select#languageSelect

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-hidden="true"]` is not present on the document `<body>`
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●ARIA IDs are unique
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○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.
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○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.
A+
Heading Hierarchy
44 headings
PASS
44 headings
Info::
Single H1 present
  • H1 每天大赛 - 全网热门大赛与爆料更新平台
  • H2 每天大赛(mrds365.com)持续更新热门大赛、网红黑料、明星爆料、反差现场与全网热议内容,聚合高热度话题与热门事件,带来更快、更全的吃瓜体验。
  • H2 中国新说唱亚军 新秀 被前妻 王安冉 实锤出轨嫖娼 人设彻底崩塌
  • H2 男网红二蛋和小羊出轨瓜,女友生理期也疯狂偷情 热搜 HOT
  • H2 从AV女优到全球DJ 滨崎真绪 人生轨迹反差拉满 热搜 HOT
  • H2 黑丝御姐 被巨根轮番深喉侵犯
  • H2 冰城玫姿 灰丝玉足羞辱足交强制榨精调教
  • H2 AI短剧 催眠眼镜 第7集连载 绿帽老公工作忙 人妻主动献身被内射 NTR拉满
  • H2 AI短剧母上攻略第21集连载 高冷妈妈下班回家 儿子洗脚后被主动打飞机到高潮
  • H2 深圳大学校园女神 李婉珺 约炮视频流出 与男友开房大胆录制 白皙娇躯被彻底开发
  • H2 西安外国语大学大三学姐 余甜甜 出租房与男友镜前激战 主动迎合娇喘不止
  • H2 语柠柠柠 清纯眼镜妹全裸手指抠逼揉奶 网红高颜值
  • H2 推特黑丝秘书 下班后被老板用手指挑逗黑丝美足
  • H2 推特日本福利姬 浴室湿身狂秀特写
  • H2 梨落声控舔蜜棒 酥软耳语直击颅内 ASMR助眠
  • H2 桥本香菜 搭讪微醺少妇酒吧直奔家中激战
  • H2 丝袜美腿足交 挑战赛直播
  • H2 推特极品福利姬 小星 超顶多套情趣裸舞诱惑 圆润翘臀无限挑逗
  • H2 小薰伪娘 身着暴露衣物 户外狂撸
  • H2 思琪 热舞无内翘臀丝足诱惑
  • H2 极品福利姬COS 赛马娘 肥臀诱惑欲望爆棚
  • H2 3D动漫大神魔改绝区 零维琳娜 御姐肥臀骑乘调教
  • H2 河南 大学生 郭曼宜 偷情被曝光 床上激情反差女大学生
  • H2 推特白丝福利姬COS 西施 用纤足玩弄榨出浓精
  • H2 泰国女星 Lisa 拉斯维加斯大尺度演出电臀摇摆疯马秀
  • H2 抖音网红 追鼠记 约炮女粉丝黑丝后入视频流出
  • H2 林浩 被日本房东和樱花妹榨精告别阴影
  • H2 四川 美术学院 李琦 白虎高颜值校园性爱合集
  • H2 禅狱 工作室抗拒者系列之二进宫,美女模特美早子铁链束缚皮鞭调教
  • H2 粉牛cc 反差推特视频曝光高颜值少女高潮尖叫
  • H2 枫芙爱 高叉泳衣教室多P被学生轮番操
  • H2 虎牙 御姐 刘钞钞 黑丝大长腿骚舞抖奶
  • H2 Totonito 魔改无职转生保罗双飞莉莉雅塞妮丝每日大赛打桩肥臀
  • H2 黑丝 空姐 跪地挑逗直播刺激
  • H2 JVID 顶级御姐 雨橙 被绳艺调教彻底变成听话娃娃
  • H2 日本少妇街头被尾随偷拍 包臀裙下春光外泄
  • H2 曼曼 原创少妇红丝袜激情打桩肥臀
  • H2 ST站 SelenS 开票直播高潮假屌狂喷湿穴
  • H2 肥臀主播 QWQ4455 大开腿直播浓毛骚气四溢
  • H2 梦乃爱华 AV实战教学教你让女伴高潮连连爽
  • H2 SelenS 直播开票大秀高潮喷涌
  • H2 梦乃爱华 性爱讲师日本AV实战演示教你如何让女伴高潮
  • H3 热门标签
  • H2 这是个成人网站
A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
2 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H2: 152 chars - H2: 154 chars
Got: 2 >120-char heading(s)
Info::
38 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: 38 all-caps heading(s)
A
Alt Text Quality
3 of 40 images have issues
PASS
3 of 40 images have issues
Warning::
3 image(s) with generic alt text
Info::
4 decorative image(s) correctly marked
Info::
33 image(s) with good alt text
40 images 33 good alt text 4 decorative 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 "mobile-search-box-input" should use type="search" (currently type="text")
Field name "mobile-search-box-input" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "contact" should use type="email" (currently type="text")
Field name "contact" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A+
Form Input Quality
8 form control(s) checked, no input-semantic issues
PASS
8 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+
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
No visible text nodes measured on the page
PASS
No visible text nodes measured on the page
Info::
No visible text nodes measured on the page
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::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback