Skip to content
https://honor.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
36
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
F
Heading Hierarchy
Action
62 headings, 2 skip(s)
FIX
62 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
12 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 HONOR 香港 - HONOR 智能手機
  • H5 關於HONOR skipped
  • H5 最新活動
  • H2 (empty)
  • H3 AI| 2億像素AI超清人像
  • H2 (empty)
  • H3 AI| 2億像素AI超清人像
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H3 AI| 世一輕薄，唯一旗艦
  • H2 (empty)
  • H3 AI| 2億像素AI超清人像
  • H2 (empty)
  • H3 AI| 2億像素AI超清人像
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H3 AI| 世一輕薄，唯一旗艦
  • H2 (empty)
  • H3 AI| 視夜新視野
  • H2 (empty)
  • H2 所有產品
  • H3 HONOR 600 Pro
  • H3 HONOR 600 Pro
  • H3 HONOR MagicBook Art 14 2025
  • H3 HONOR Pad X8b
  • H3 HONOR Watch Fit
  • H3 HONOR Earbuds Open
  • H3 HONOR 600 Pro
  • H3 HONOR 600 Pro
  • H3 HONOR 600
  • H3 HONOR 600 Lite
  • H3 HONOR X6d 5G
  • H3 HONOR X5c Plus
  • H3 HONOR MagicBook Art 14 2025
  • H3 HONOR MagicBook Art 14 2025
  • H3 HONOR MagicBook Art 14
  • H3 HONOR Pad X8b
  • H3 HONOR Pad X8b
  • H3 HONOR MagicPad3
  • H3 HONOR Pad 10
  • H3 HONOR Pad X9a
  • H3 HONOR Pad X8a
  • H3 HONOR Watch Fit
  • H3 HONOR Watch Fit
  • H3 HONOR Watch 5 Ultra
  • H3 HONOR Watch 5
  • H3 HONOR Watch 4 Pro
  • H3 HONOR Band 9
  • H3 HONOR Earbuds Open
  • H3 HONOR Earbuds Open
  • H3 HONOR Earbuds 3 Pro
  • H2 HONOR 最新活動
  • H3 HONOR MWC 2026
  • H2 HONOR科技，引領未來
  • H1 HONOR duplicate H1
  • H3 關於HONOR skipped
  • H3 產品
  • H3 購買渠道
  • H3 服務支援
  • H3 软件和应用程式

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
Alt Text Quality
Action
11 of 314 images have issues
FIX
11 of 314 images have issues
Critical::
10 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
1 image(s) with generic alt text
Info::
223 decorative image(s) correctly marked
Info::
80 image(s) with good alt text
314 images 80 good alt text 223 decorative 1 generic 10 missing
IssueCount
missing10 image(s)
generic1 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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-pkluft
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
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://honor.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://honor.com/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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation
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.
C
Landmark Structure
Action
No landmarks
REVIEW
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present

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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input id="footer-hide-data">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputtext(Type your search keyword here)placeholder only
#footer-hide-datainput(none)none

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

<input id="footer-hide-data">

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

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
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Lighthouse Accessibility Audits
Action
Score 73/100 — 8 failing, 23 passed
REVIEW
73

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
HONOR 600 Pro 購買 了解更多 HONOR MagicBook Art 14 2025 購買 了解更多 HONOR Pad X8b 了解更多… div.product-list-new > div.products-list-new > div.new-products-list > div.new-product-list

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
HONOR MagicBook Art 14 2025 購買 了解更多 div.productNew-container > div.productNew-list_swiper > div.swiper-wrapper > div.swiper-slide
HONOR Pad X8b 了解更多 div.productNew-container > div.productNew-list_swiper > div.swiper-wrapper > div.swiper-slide
HONOR Watch Fit 了解更多 div.productNew-container > div.productNew-list_swiper > div.swiper-wrapper > div.swiper-slide
HONOR Earbuds Open 購買 了解更多 div.productNew-container > div.productNew-list_swiper > div.swiper-wrapper > div.swiper-slide

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.html-text > div.hk-add-newNotes > ul.notes-warper > li

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
關於HONOR div.footer_wrap > div.footer_content > div.footer_content_list > h3.navigation-title

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.product-content > div.product-content-warp > h3.new-home-banner-content-slogan > img.ai-star div.product-content > div.product-content-warp > h3.new-home-banner-content-slogan > img.ai-star
div.product-content > div.product-content-warp > h3.new-home-banner-content-slogan > img.ai-star div.product-content > div.product-content-warp > h3.new-home-banner-content-slogan > img.ai-star
div.key-product-content-box > div.key-product-content-top > h3.desolate-des > img.ai-star div.key-product-content-box > div.key-product-content-top > h3.desolate-des > img.ai-star

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.new-home-banner-comp > div.new-home-banner-wrap > div.image-background > a div.new-home-banner-comp > div.new-home-banner-wrap > div.image-background > a
HONOR Watch 5 Ultra div.product-content > div.product-content-warp > div.image-background > a
HONOR MagicBook Art 14 2025 div.product-content > div.product-content-warp > div.image-background > a
div.new-home-banner-comp > div.new-home-banner-wrap > div.image-background > a div.new-home-banner-comp > div.new-home-banner-wrap > div.image-background > a
div.new-home-banner-comp > div.new-home-banner-wrap > div.image-background > a div.new-home-banner-comp > div.new-home-banner-wrap > div.image-background > a
HONOR Watch 5 Ultra div.product-content > div.product-content-warp > div.image-background > a
HONOR MagicBook Art 14 2025 div.product-content > div.product-content-warp > div.image-background > a
div.new-home-banner-comp > div.new-home-banner-wrap > div.image-background > a div.new-home-banner-comp > div.new-home-banner-wrap > div.image-background > a
HONOR 600 Pro div.productNew-wrapper > div.productNew-slide > div.productNew-bgWrapper > a.product-img_group
HONOR MagicBook Art 14 2025 div.swiper-wrapper > div.swiper-slide > div.productNew-bgWrapper > a.product-img_group
HONOR Pad X8b div.swiper-wrapper > div.swiper-slide > div.productNew-bgWrapper > a.product-img_group
HONOR Watch Fit div.swiper-wrapper > div.swiper-slide > div.productNew-bgWrapper > a.product-img_group
HONOR Earbuds Open div.swiper-wrapper > div.swiper-slide > div.productNew-bgWrapper > a.product-img_group
HONOR MWC 2026 div.swiper-slide > div.activity-content > div.activity-more-img > a.more_link
HONOR AI 影像大師 div.swiper-slide > div.activity-content > div.activity-more-img > a.more_link
HONOR AI div.swiper-slide > div.activity-content > div.activity-more-img > a.more_link
div#cookie_notices > div.cookie_notices > div.cookie_notices_button > a.btn-close div#cookie_notices > div.cookie_notices > div.cookie_notices_button > a.btn-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.

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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●ARIA input fields have accessible names
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
A+
Color Contrast (Screenshot)
20 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.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 HONOR 香港 - HONOR…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 HONOR21.00:13.0:1
#000000
#FFFFFF
Pass
h2 所有產品21.00:13.0:1
#000000
#FFFFFF
Pass
h2 HONOR 最新活動21.00:13.0:1
#000000
#FFFFFF
Pass
h2 HONOR科技，引領…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 | 2億像素AI超清…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 | 2億像素AI超清…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 | 世一輕薄，唯…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 | 2億像素AI超清…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 | 2億像素AI超清…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 | 世一輕薄，唯…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 | 視夜新視野21.00:13.0:1
#000000
#FFFFFF
Pass
h3 HONOR 600 Pro21.00:13.0:1
#000000
#FFFFFF
Pass
h3 HONOR 600 Pro21.00:13.0:1
#000000
#FFFFFF
Pass
h3 HONOR MagicBook Art …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 HONOR Pad X8b21.00:13.0:1
#000000
#FFFFFF
Pass
h3 HONOR Watch Fit21.00:13.0:1
#000000
#FFFFFF
Pass
h3 HONOR Earbuds Open21.00:13.0:1
#000000
#FFFFFF
Pass
h3 HONOR 600 Pro21.00:13.0:1
#000000
#FFFFFF
Pass
h3 HONOR 600 Pro21.00:13.0: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.

Send Feedback