Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 1 REVIEW 7 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Lighthouse Accessibility Audits

Action

Score 54/100 — 8 failing, 11 passed

FIX

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.04.22发布 `section.bg-white > div.flex-box > a.pro-item > span.release-time`
预约直播 `div.flex-box > a.pro-item > span.pl8 > span.live`
2026.04.21发布 `section.bg-white > div.flex-box > a.pro-item > span.release-time`
2026.04.21发布 `section.bg-white > div.flex-box > a.pro-item > span.release-time`
评测 `li.pics > a > p.tags > span.blue`
2小时前 `li.pics > a > p.tags > span.time`
评测 `li.pics > a > p.tags > span.blue`
19小时前 `li.pics > a > p.tags > span.time`
2026年04月22日 19点00分 `div.flex-box > a.live-list-item > span.tips > span.time`
评测 `li.pics > a > p.tags > span.blue`
11小时前 `li.pics > a > p.tags > span.time`
评测 `li.pics > a > p.tags > span.blue`
11小时前 `li.pics > a > p.tags > span.time`
评测 `li.pics > a > p.tags > span.blue`
12小时前 `li.pics > a > p.tags > span.time`
查看榜单 `div.product-list > div > div.list-header > a.look-rank`
评测 `li.pics > a > p.tags > span.blue`
12小时前 `li.pics > a > p.tags > span.time`
评测 `li.pics > a > p.tags > span.blue`
11小时前 `li.pics > a > p.tags > span.time`
545.3万次播放 `li.swiper-slide > a.relative > div.detail-text > span.time`
1.5万次播放 `li.swiper-slide > a.relative > div.detail-text > span.time`
评测 `li.pics > a > p.tags > span.blue`
22小时前 `li.pics > a > p.tags > span.time`
评测 `li.pics > a > p.tags > span.blue`
04.17 `li.pics > a > p.tags > span.time`
评测 `li.pics > a > p.tags > span.blue`
04.20 `li.pics > a > p.tags > span.time`
10回答 `div.hot-ask-list > div.asks-content > a.asks-content-title > div.num`
6回答 `div.hot-ask-list > div.asks-content > a.asks-content-title > div.num`
评测 `a.flex-box > div.detail-text > p.tags > span.blue`
04.18 `a.flex-box > div.detail-text > p.tags > span.time`
评测 `a.flex-box > div.detail-text > p.tags > span.blue`
04.17 `a.flex-box > div.detail-text > p.tags > span.time`
评测 `li.pics > a > p.tags > span.blue`
61 `li.pics > a > p.tags > span.comment-num`
04.17 `li.pics > a > p.tags > span.time`
点击加载更多 `body > section.bg-white > div.load-more`
网站经营者信息公示 `body > footer.pl16 > div.bottom-breads > a.info-link`

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

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
body > img `body > 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.global-page-header > div.side-box > a.iconfont `body > header.global-page-header > div.side-box > a.iconfont`
body > section.bg-white > a.rili-title `body > section.bg-white > a.rili-title`
body > section.bg-white > div.jingxuan-section > a.icon `body > section.bg-white > div.jingxuan-section > a.icon`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
最新报价产品排行性能天梯免费众测攒机广场 `body > section.bg-white > ul.sites-nav`
影驰RTX 5070 Ti《识质存在》测试：4K画质拉满体验赛博养娃评测 2 2小时前再战超轻量级雷柏VT0/VT3s Air MAX电竞鼠标刷新… `body > section.bg-white > ul.news-list`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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`

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
vivo300拍照片有什么优势 10回答 `ul.news-list > div.hot-ask-list > div.asks-content > a.asks-content-title`

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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●Input buttons have discernible text.

●Form elements have associated labels

●Document has a `<title>` element

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Heading elements appear in a sequentially-descending order

●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

○`[aria-*]` attributes match their roles

○`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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted 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

○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

○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 a valid value for its `[lang]` attribute

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<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.

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title ��ʵ�ҳ��ѱ�ɾ��򲻴��... ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 503 Service Temporarily Unavailable

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

No links or buttons

PASS

No links or buttons

No links or buttons on this page

0 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

A+

Color Contrast (Screenshot)

3 text elements analyzed, 0 fail WCAG AA

PASS

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

3 pass

Show all checked elements (3)

Element	Ratio	Required	FG	BG	Result
h1 503 Service Temporar…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title 503 Service Temporar…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
center openresty	21.00:1	4.5:1	#000000	#FFFFFF	Pass

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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.