Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 REVIEW 6 FIX

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 44/100 — 6 failing, 6 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
更多专题 `div.index-part1 > div.slider-wrap > div.more-zt-link > a`
更多 `div#app > div.index-part1 > div.news-more > a`
更多 `div#app > div.index-part5 > div.index-media-top > a`

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
div.wap-nav-bar > div.wap-nav-bar__right > span.nav-search > img `div.wap-nav-bar > div.wap-nav-bar__right > span.nav-search > img`
div.wap-nav-bar > div.wap-nav-bar__right > span.ch-nav > img `div.wap-nav-bar > div.wap-nav-bar__right > span.ch-nav > img`
div.van-swipe__track > div.van-swipe-item > a > img `div.van-swipe__track > div.van-swipe-item > a > img`
div.van-swipe__track > div.van-swipe-item > a > img `div.van-swipe__track > div.van-swipe-item > a > img`
div.van-swipe__track > div.van-swipe-item > a > img `div.van-swipe__track > div.van-swipe-item > a > img`
div.van-swipe__track > div.van-swipe-item > a > img `div.van-swipe__track > div.van-swipe-item > a > img`
div.van-swipe__track > div.van-swipe-item > a > img `div.van-swipe__track > div.van-swipe-item > a > img`
div#app > div.index-part2 > a > img `div#app > div.index-part2 > a > img`
div.van-grid-item > div.van-grid-item__content > div.van-grid-item__icon-wrapper > img `div.van-grid-item > div.van-grid-item__content > div.van-grid-item__icon-wrapper > img`
div.van-grid-item > div.van-grid-item__content > div.van-grid-item__icon-wrapper > img `div.van-grid-item > div.van-grid-item__content > div.van-grid-item__icon-wrapper > img`
div.van-grid-item > div.van-grid-item__content > div.van-grid-item__icon-wrapper > img `div.van-grid-item > div.van-grid-item__content > div.van-grid-item__icon-wrapper > img`
div.van-grid-item > div.van-grid-item__content > div.van-grid-item__icon-wrapper > img `div.van-grid-item > div.van-grid-item__content > div.van-grid-item__icon-wrapper > img`
div.van-grid-item > div.van-grid-item__content > div.van-grid-item__icon-wrapper > img `div.van-grid-item > div.van-grid-item__content > div.van-grid-item__icon-wrapper > img`
div.van-grid-item > div.van-grid-item__content > div.van-grid-item__icon-wrapper > img `div.van-grid-item > div.van-grid-item__content > div.van-grid-item__icon-wrapper > img`
div.wap-footer-units > div.list > a > img `div.wap-footer-units > div.list > a > 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
div.wap-swipe > div.van-swipe__track > div.van-swipe-item > a `div.wap-swipe > div.van-swipe__track > div.van-swipe-item > a`
div.wap-swipe > div.van-swipe__track > div.van-swipe-item > a `div.wap-swipe > div.van-swipe__track > div.van-swipe-item > a`
div.wap-swipe > div.van-swipe__track > div.van-swipe-item > a `div.wap-swipe > div.van-swipe__track > div.van-swipe-item > a`
div.wap-swipe > div.van-swipe__track > div.van-swipe-item > a `div.wap-swipe > div.van-swipe__track > div.van-swipe-item > a`
div.wap-swipe > div.van-swipe__track > div.van-swipe-item > a `div.wap-swipe > div.van-swipe__track > div.van-swipe-item > a`
body > div#app > div.index-part2 > a `body > div#app > div.index-part2 > a`

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.

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`

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

●Document has a `<title>` element

●Links are distinguishable without relying on color.

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●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

○Deprecated ARIA roles were not used

○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

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

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

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

○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

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found (没有找到访问的页面) ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

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