Skip to content
https://51.la

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
6
REVIEW
6
PASS
1
INFO
0
Checks
13
1 PASS 6 REVIEW 6 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-6uprnh
404 Page Quality Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://51.la/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://51.la/manifest.json

Manifest contains invalid JSON.

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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No contentinfo (footer) landmark
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 MAIN CONTENTINFO (missing!)

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
Heading Hierarchy
Action
21 headings, 1 skip(s)
REVIEW
21 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 App移动统计
  • H2 App移动统计
  • H2 全新「屏幕录制」功能上线
  • H2 全新【屏幕录制】功能上线
  • H2 信赖升级 - 51LA荣获网站安全认证
  • H2 信赖升级!
  • H2 51LA荣获网站安全认证
  • H2 51.LA网站统计
  • H2 51.LA网站统计
  • H4 免费、易用、专业的网站数据统计与营销分析平台 skipped
  • H2 51.LA灵雀应用监控平台
  • H2 51.LA灵雀应用监控平台
  • H2 与用户共建知识社区
  • H2 与用户共建知识社区
  • H2 我们的产品
  • H2 我们的产品
  • H2 丰富的解决方案,覆盖千行百业
  • H2 丰富的解决方案,覆盖千行百业
  • H2 合作伙伴
  • H2 合作伙伴
  • H2 友情链接

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

C
Alt Text Quality
Action
6 of 59 images have issues
REVIEW
6 of 59 images have issues
Critical::
6 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
5 decorative image(s) correctly marked
Info::
48 image(s) with good alt text
59 images 48 good alt text 5 decorative 6 missing
IssueCount
missing6 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 App移动统计20.41:13.0:1
#000000
#FAFCFD
Pass
h2 App移动统计20.44:13.0:1
#000000
#FBFCFD
Pass
h2 全新「屏幕录…20.44:13.0:1
#000000
#FBFCFD
Pass
h2 全新【屏幕录…20.44:13.0:1
#000000
#FBFCFD
Pass
h2 信赖升级 - 51LA…20.44:13.0:1
#000000
#FBFCFD
Pass
h2 信赖升级!20.44:13.0:1
#000000
#FBFCFD
Pass
h2 51LA荣获网站安…20.44:13.0:1
#000000
#FBFCFD
Pass
h2 51.LA网站统计20.44:13.0:1
#000000
#FBFCFD
Pass
h2 51.LA网站统计20.44:13.0:1
#000000
#FBFCFD
Pass
h2 51.LA灵雀应用监…20.44:13.0:1
#000000
#FBFCFD
Pass
h2 51.LA灵雀应用监…20.44:13.0:1
#000000
#FBFCFD
Pass
h2 与用户共建20.44:13.0:1
#000000
#FBFCFD
Pass
h2 与用户共建20.44:13.0:1
#000000
#FBFCFD
Pass
h2 我们的产品20.44:13.0:1
#000000
#FBFCFD
Pass
h2 我们的产品20.44:13.0:1
#000000
#FBFCFD
Pass
h2 丰富的解决方…20.44:13.0:1
#000000
#FBFCFD
Pass
h2 丰富的解决方…20.44:13.0:1
#000000
#FBFCFD
Pass
h2 合作伙伴20.44:13.0:1
#000000
#FBFCFD
Pass
h2 合作伙伴20.44:13.0:1
#000000
#FBFCFD
Pass
h2 友情链接4.31:13.0:1
#717887
#FBFCFD
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.

B
Lighthouse Accessibility Audits
Score 84/100 — 4 failing, 18 passed
REVIEW
84

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 > section.section > div.btn > button
立即注册 div.register-now > div.h5-inner > a > button.register-btn
Copyright © 2002-2026 广州有啦网络科技有限公司 div#footbar > div.footbar > div.footbar-copyright > div

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
免费、易用、专业的网站数据统计与营销分析平台 div.section > div.header-content > div.banner-text > h4.index-animate

These are opportunities to improve keyboard navigation in your application.

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.section__evaluate-content > div.section > div.item-left > img div.section__evaluate-content > div.section > div.item-left > img
div.section__evaluate-content > div.section > div.item-left > img div.section__evaluate-content > div.section > div.item-left > img
div.section__evaluate-content > div.section > div.item-left > img div.section__evaluate-content > div.section > div.item-left > img

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

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
幻灯片切换至索引 3 div.el-carousel > ul.el-carousel__indicators > li.el-carousel__indicator > button.el-carousel__button
幻灯片切换至索引 4 div.el-carousel > ul.el-carousel__indicators > li.el-carousel__indicator > button.el-carousel__button
幻灯片切换至索引 5 div.el-carousel > ul.el-carousel__indicators > li.el-carousel__indicator > button.el-carousel__button

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-*]` 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
Buttons have an accessible name
`[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
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
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
Document has a main landmark.
`[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
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
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
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+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback