Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 8 REVIEW 5 FIX

Heading Hierarchy

Action

33 headings, 2 skip(s)

FIX

33 headings, 2 skip(s)

No H1 heading found

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H5 (missing H4)

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

H5 One-Stop Custom Signage
H5 Durable Outdoor Craftsmanship
H5 OEM Custom Service
H3 Check our main categories
H6 Metal Precision Logo Signs skipped
H6 Premium Metal Letters
H6 Acrylic LED Mini Letters & Nameplates
H6 LED Neon Signs & American Style Signs
H6 Full-Color Custom Logos
H6 Mirror Multi-Layer Shapes & Letters
H6 LED Backlit Letters
H6 LED Borderless Stainless Steel Illuminated Letters
H6 LED floor cover structure for illuminated letters
H6 Vintage Bulb Decorative Letter Signs
H6 Infinite Mirror LED Channel Letters
H6 Outdoor 3D Landscape Letters
H5 Acrylic LED Mini Letters & Nameplates
H5 Acrylic LED Mini Letters & Nameplates
H5 LED Neon Signs & American Style Signs
H5 LED Neon Signs & American Style Signs
H3 Custom LED 3D Signage & Metal Logo Factory
H3 Custom Brand Signage Solutions
H5 Acrylic LED Mini Letters & Nameplates skipped
H5 Metal Precision Logo Signs
H5 Metal Precision Logo Signs
H5 Metal Precision Logo Signs
H5 Premium Metal Letters
H5 Premium Metal Letters
H5 Premium Metal Letters
H5 Premium Metal Letters
H2 Guangzhou Hongbo Signage Co., Ltd.
H3 Sign up for our newsletter to explore our latest signage works
H4 Navigation

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

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Tabindex Anti-Patterns

Action

0 positive, 60 -1-on-focusable

FIX

0 positive, 60 -1-on-focusable

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

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.

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 ✗

Landmark Structure

Action

5 landmarks

REVIEW

5 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

No <nav> landmark found

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

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

Form Accessibility

2 of 6 controls have issues

REVIEW

2 of 6 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="email" name="your-email" id="2daf7c7-your-name">

4 control(s) properly labeled

6 controls

4 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
s	text	Find product	aria-label
input	submit	Search	aria-label
s	text	Enter your search	aria-label
input	submit	Search	aria-label
#2daf7c7-your-name	email	(✉ Your e-mail address)	placeholder only
input	submit	(none)	none

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

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.

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

Link & Button Quality

Action

6 issue(s) across 210 links and 3 buttons

REVIEW

6 issue(s) across 210 links and 3 buttons

5 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #; https://hongbosign.com/wp-content/uploads/2026/07/11cad9dc3f9793d7239f42c214a…; https://hongbosign.com/wp-content/uploads/2026/07/13ee475e0f0d97c75c28debda74…; https://hongbosign.com/wp-content/uploads/2026/07/21f409161d0a571d5b4e37139a0…; https://hongbosign.com/wp-content/uploads/2026/07/9918ce1d3b1f0b9c0b95b5128fe…

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://hongbosign.com/about-us/ ("Read more")

204 link(s) with descriptive text

210 links

5 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#	(empty)	empty	Add link text or aria-label
https://hongbosign.com/product-category/…	Metal Precision Logo Signs	img no alt	Add alt attribute to the image
https://hongbosign.com/product-category/…	Premium Metal Letters	img no alt	Add alt attribute to the image
https://hongbosign.com/product-category/…	Acrylic LED Mini Letters & Nam…	img no alt	Add alt attribute to the image
https://hongbosign.com/product-category/…	LED Neon Signs & American Styl…	img no alt	Add alt attribute to the image
https://hongbosign.com/product-category/…	Full-Color Custom Logos	img no alt	Add alt attribute to the image
https://hongbosign.com/product-category/…	Mirror Multi-Layer Shapes & Le…	img no alt	Add alt attribute to the image
https://hongbosign.com/product-category/…	LED Backlit Letters	img no alt	Add alt attribute to the image
https://hongbosign.com/product-category/…	LED Borderless Stainless Steel…	img no alt	Add alt attribute to the image
https://hongbosign.com/product-category/…	LED floor cover structure for …	img no alt	Add alt attribute to the image
https://hongbosign.com/product-category/…	Vintage Bulb Decorative Letter…	img no alt	Add alt attribute to the image
https://hongbosign.com/product-category/…	Infinite Mirror LED Channel Le…	img no alt	Add alt attribute to the image
https://hongbosign.com/product-category/…	Outdoor 3D Landscape Letters	img no alt	Add alt attribute to the image
https://hongbosign.com/about-us/	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: About Us
https://hongbosign.com/wp-content/upload…	(empty)	empty	Add link text or aria-label
https://hongbosign.com/wp-content/upload…	(empty)	empty	Add link text or aria-label
https://hongbosign.com/wp-content/upload…	(empty)	empty	Add link text or aria-label
https://hongbosign.com/wp-content/upload…	(empty)	empty	Add link text or aria-label

207 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

#; https://hongbosign.com/wp-content/uploads/2026/07/11cad9dc3f9793d7239f42c214a…; https://hongbosign.com/wp-content/uploads/2026/07/13ee475e0f0d97c75c28debda74…; https://hongbosign.com/wp-content/uploads/2026/07/21f409161d0a571d5b4e37139a0…; https://hongbosign.com/wp-content/uploads/2026/07/9918ce1d3b1f0b9c0b95b5128fe…

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

https://hongbosign.com/about-us/ ("Read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

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 #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 4 fail WCAG AA

REVIEW

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

16 pass 4 fail WCAG AA 2 pass AA only

div ● PROFESSIONAL SUPPORT

3.10:1

#000000

#6B5A16

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

div ● Specialized in manufacturing metal s…

1.15:1

#000000

#0A1527

needs 4.5:1 (normal text)

16px · above the fold

div ● OEM manufacturing factory

1.19:1

#000000

#0C192C

needs 4.5:1 (normal text)

16px · above the fold

div ● PROFESSIONAL SUPPORT

1.23:1

#000000

#101C32

needs 4.5:1 (normal text)

16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Guangzhou Hongbo Sig…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Check our main categ…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Custom LED 3D Signag…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Custom Brand Signage…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sign up for our news…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Home - Guangzhou Hon…	17.11:1	4.5:1	#000000	#DBE9FF	Pass
div ● FREE SHIPPING ON…	14.25:1	4.5:1	#000000	#F1D367	Pass
div ● SHIPPING WITHIN …	13.24:1	4.5:1	#000000	#FFC501	Pass
div ● PROFESSIONAL SUP…	3.10:1	4.5:1	#000000	#6B5A16	Fail
div ● Specialized in m…	1.15:1	4.5:1	#000000	#0A1527	Fail
div ● OEM manufacturin…	1.19:1	4.5:1	#000000	#0C192C	Fail
div ● PROFESSIONAL SUP…	1.23:1	4.5:1	#000000	#101C32	Fail
span ✕	4.71:1	4.5:1	#000000	#6F7886	Pass
span No results	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a See all results	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span ✕	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span No results	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a See all results	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Whishlist	5.54:1	4.5:1	#636971	#FFFFFF	Pass
div Products	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.

Lighthouse Accessibility Audits

Score 88/100 — 4 failing, 27 passed

REVIEW

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
All Types of Sign Products Available `div.mcb-column-inner > div.mfn-icon-box > div.desc-wrapper > div.desc`
Weatherproof & Long Service Life `div.mcb-column-inner > div.mfn-icon-box > div.desc-wrapper > div.desc`
Flexible Orders for Wholesale `div.mcb-column-inner > div.mfn-icon-box > div.desc-wrapper > div.desc`
© 2026 Guangzhou Hongbo Signage Co., Ltd. All Rights Reserved \| Privacy Policy … `div.mcb-wrap-inner > div.column > div.mcb-column-inner > div.desc`
Privacy Policy `div.column > div.mcb-column-inner > div.desc > a`
Terms of Service `div.column > div.mcb-column-inner > div.desc > a`

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
Metal Precision Logo Signs `a.mfn-banner-box > div.banner-desc > div.banner-wrapper > h6.title`
Acrylic LED Mini Letters & Nameplates `ul.products > li.mfn-product-li-item > div.mfn-li-product-row > h5.title`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.mcb-wrap-inner > div.column > div.mcb-column-inner > a.mfn-icon-box `div.mcb-wrap-inner > div.column > div.mcb-column-inner > a.mfn-icon-box`
dt.gallery-icon > div.image_frame > div.image_wrapper > a `dt.gallery-icon > div.image_frame > div.image_wrapper > a`
dt.gallery-icon > div.image_frame > div.image_wrapper > a `dt.gallery-icon > div.image_frame > div.image_wrapper > a`
dt.gallery-icon > div.image_frame > div.image_wrapper > a `dt.gallery-icon > div.image_frame > div.image_wrapper > a`
dt.gallery-icon > div.image_frame > div.image_wrapper > a `dt.gallery-icon > div.image_frame > div.image_wrapper > a`
div.mfn-footer-stickymenu > ul > li > a `div.mfn-footer-stickymenu > ul > li > 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`

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

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●Form elements have associated labels

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

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○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 type="image">` elements have `[alt]` text

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

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

Heading Text Quality

All 33 heading(s) have substantive, well-formed text

PASS

All 33 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 36 images OK

PASS

All 36 images OK

20 decorative image(s) correctly marked

16 image(s) with good alt text

36 images 16 good alt text 20 decorative

All images have appropriate alt text.

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "s" should use type="search" (currently type="text")

Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

6 form control(s) checked, no input-semantic issues

PASS

6 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 81 visible text node(s) render at >= 12 CSS pixels

PASS

All 81 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

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.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

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