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 4 REVIEW 9 FIX

Alt Text Quality

Action

18 of 44 images have issues

FIX

18 of 44 images have issues

18 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

7 image-in-link without alt text

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

26 image(s) with good alt text

44 images 26 good alt text 18 missing

Issue	Count
missing	18 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

Link & Button Quality

Action

19 issue(s) across 69 links and 7 buttons

FIX

19 issue(s) across 69 links and 7 buttons

8 link(s) with no accessible text

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

Got: https://www.facebook.com/profile.php?id=61577349563696; https://www.youtube.com/@JXDEco-Packaging; zan:global name='web_attr_10' /; https://www.instagram.com/ecofashion.pack?igsh=MWs5eWtod2NsbWxtbg%3D%3D&utm_s…; https://www.facebook.com/profile.php?id=61577349563696; https://www.youtube.com/@JXDEco-Packaging; https://www.linkedin.com/company/shenzhen-jiuxinda-jxd-packaging-co-ltd/about…; https://www.instagram.com/ecofashion.pack?igsh=MWs5eWtod2NsbWxtbg%3D%3D&utm_s…

9 link(s) with generic text

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

Got: /blog/how-to-source-reliable-biodegradable-bags-manufacturers-for-custom-orders ("Read More"); /blog/custom-packaging-bags-a-complete-buyer-s-guide-for-smooth-sourcing ("Read More"); /blog/eco-friendly-apparel-packaging-smart-packaging-solutions-for-modern-clo… ("Read More"); /blog/choosing-the-right-packaging-bags-for-products ("Read More"); /blog/how-plastic-bags-for-packaging-products-enhance-brand-visibility ("Read More"); /blog/biodegradable-bags-which-packaging-solution-is-best-for-your-brand ("Read More"); /blog/how-to-choose-the-right-biodegradable-plastic-bags-manufacturer-for-you… ("Read More"); /blog/custom-product-packaging-bags-sustainable-options-for-eco-conscious-brands ("Read More"); /blog/how-to-choose-the-right-biodegradable-bags-manufacturers-for-your-brand ("Read More")

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.btn (#252 on page); button.btn (#254 on page)

52 link(s) with descriptive text

69 links

8 empty

9 generic text

0 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/profile.php?id=…	(empty)	empty	Add link text or aria-label
https://www.youtube.com/@JXDEco-Packagin…	(empty)	empty	Add link text or aria-label
zan:global name='web_attr_10' /	(empty)	empty	Add link text or aria-label
https://www.instagram.com/ecofashion.pac…	(empty)	empty	Add link text or aria-label
../products/	Logistics	img no alt	Add alt attribute to the image
../products/	Clothing & Branding	img no alt	Add alt attribute to the image
../products/	Household Appliance	img no alt	Add alt attribute to the image
../products/	Beauty & Personal Care	img no alt	Add alt attribute to the image
../products/	Hardware Accessories	img no alt	Add alt attribute to the image
../products/	Consumer Electronics	img no alt	Add alt attribute to the image
/blog/how-to-source-reliable-biodegradab…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: How To Source Reliable Biodegradable Bags Manufacturers For Custom Orders
/blog/custom-packaging-bags-a-complete-b…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Custom Packaging Bags A Complete Buyer S Guide For Smooth Sourcing
/blog/eco-friendly-apparel-packaging-sma…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Eco Friendly Apparel Packaging Smart Packaging Solutions For Modern Clothing Brands
/blog/choosing-the-right-packaging-bags-…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Choosing The Right Packaging Bags For Products
/blog/how-plastic-bags-for-packaging-pro…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: How Plastic Bags For Packaging Products Enhance Brand Visibility
/blog/biodegradable-bags-which-packaging…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Biodegradable Bags Which Packaging Solution Is Best For Your Brand
/blog/how-to-choose-the-right-biodegrada…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: How To Choose The Right Biodegradable Plastic Bags Manufacturer For Your Business
/blog/custom-product-packaging-bags-sust…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Custom Product Packaging Bags Sustainable Options For Eco Conscious Brands
/blog/how-to-choose-the-right-biodegrada…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: How To Choose The Right Biodegradable Bags Manufacturers For Your Brand
https://www.facebook.com/profile.php?id=…	(empty)	empty	Add link text or aria-label
https://www.youtube.com/@JXDEco-Packagin…	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/shenzhe…	(empty)	empty	Add link text or aria-label
https://www.instagram.com/ecofashion.pac…	(empty)	empty	Add link text or aria-label
https://wa.me/+8618025497165?text=hello	WhatsApp Us	img no alt	Add alt attribute to the image
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

57 links and buttons have descriptive text

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

https://www.facebook.com/profile.php?id=61577349563696; https://www.youtube.com/@JXDEco-Packaging; zan:global name='web_attr_10' /; https://www.instagram.com/ecofashion.pack?igsh=MWs5eWtod2NsbWxtbg%3D%3D&utm_s…; https://www.facebook.com/profile.php?id=61577349563696; https://www.youtube.com/@JXDEco-Packaging; https://www.linkedin.com/company/shenzhen-jiuxinda-jxd-packaging-co-ltd/about…; https://www.instagram.com/ecofashion.pack?igsh=MWs5eWtod2NsbWxtbg%3D%3D&utm_s…

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.

/blog/how-to-source-reliable-biodegradable-bags-manufacturers-for-custom-orders ("Read More"); /blog/custom-packaging-bags-a-complete-buyer-s-guide-for-smooth-sourcing ("Read More"); /blog/eco-friendly-apparel-packaging-smart-packaging-solutions-for-modern-clo… ("Read More"); /blog/choosing-the-right-packaging-bags-for-products ("Read More"); /blog/how-plastic-bags-for-packaging-products-enhance-brand-visibility ("Read More"); /blog/biodegradable-bags-which-packaging-solution-is-best-for-your-brand ("Read More"); /blog/how-to-choose-the-right-biodegradable-plastic-bags-manufacturer-for-you… ("Read More"); /blog/custom-product-packaging-bags-sustainable-options-for-eco-conscious-brands ("Read More"); /blog/how-to-choose-the-right-biodegradable-bags-manufacturers-for-your-brand ("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

Icon-only buttons need an aria-label so screen readers can announce them.

button.btn (#252 on page); button.btn (#254 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Lighthouse Accessibility Audits

Action

Score 61/100 — 8 failing, 13 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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > section.team > div.carousel-container > button.btn `body > section.team > div.carousel-container > button.btn`
body > section.team > div.carousel-container > button.btn `body > section.team > div.carousel-container > button.btn`

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.con-pro > a > div.con-pro-item > img.product-img `div.con-pro > a > div.con-pro-item > img.product-img`
div.con-pro > a > div.con-pro-item > img.product-img `div.con-pro > a > div.con-pro-item > img.product-img`
div.con-pro > a > div.con-pro-item > img.product-img `div.con-pro > a > div.con-pro-item > img.product-img`
div.con-pro > a > div.con-pro-item > img.product-img `div.con-pro > a > div.con-pro-item > img.product-img`
div.con-pro > a > div.con-pro-item > img.product-img `div.con-pro > a > div.con-pro-item > img.product-img`
div.con-pro > a > div.con-pro-item > img.product-img `div.con-pro > a > div.con-pro-item > img.product-img`
div.container > div.about-content > div.about-img > img `div.container > div.about-content > div.about-img > img`
div.carousel-container > div.carousel-track > div.carousel-item > img `div.carousel-container > div.carousel-track > div.carousel-item > img`
div.carousel-container > div.carousel-track > div.carousel-item > img `div.carousel-container > div.carousel-track > div.carousel-item > img`
div.carousel-container > div.carousel-track > div.carousel-item > img `div.carousel-container > div.carousel-track > div.carousel-item > img`
div.carousel-container > div.carousel-track > div.carousel-item > img `div.carousel-container > div.carousel-track > div.carousel-item > img`
div.carousel-container > div.carousel-track > div.carousel-item > img `div.carousel-container > div.carousel-track > div.carousel-item > img`
div.carousel-container > div.carousel-track > div.carousel-item > img `div.carousel-container > div.carousel-track > div.carousel-item > img`
div.carousel-container > div.carousel-track > div.carousel-item > img `div.carousel-container > div.carousel-track > div.carousel-item > img`
div.carousel-container > div.carousel-track > div.carousel-item > img `div.carousel-container > div.carousel-track > div.carousel-item > img`
footer > div.container > div.footeco > img `footer > div.container > div.footeco > img`
div.custor > a > div.custorimg > img `div.custor > a > div.custorimg > 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.headertop > div.container > div.topsr > a `div.headertop > div.container > div.topsr > a`
div.headertop > div.container > div.topsr > a `div.headertop > div.container > div.topsr > a`
div.headertop > div.container > div.topsr > a `div.headertop > div.container > div.topsr > a`
div.headertop > div.container > div.topsr > a `div.headertop > div.container > div.topsr > a`
div.footer-content > div.footer-column > div.social-links > a `div.footer-content > div.footer-column > div.social-links > a`
div.footer-content > div.footer-column > div.social-links > a `div.footer-content > div.footer-column > div.social-links > a`
div.footer-content > div.footer-column > div.social-links > a `div.footer-content > div.footer-column > div.social-links > a`
div.footer-content > div.footer-column > div.social-links > a `div.footer-content > div.footer-column > div.social-links > 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.

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
Inquire About Customization `body > section.custom-service > div.container > label.trigger-btn`
WhatsApp Us `footer > div.custor > a > div.custorwq`

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
Logistics `div.con-pro > a > div.con-pro-item > h5`

These are opportunities to improve keyboard navigation in your application.

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
div.headertop > div.container > div.topsr > a `div.headertop > div.container > div.topsr > a`
div.headertop > div.container > div.topsr > a `div.headertop > div.container > div.topsr > a`

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●ARIA attributes are used as specified for the element's role

●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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

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

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

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

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

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

1 <nav> landmark(s) 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

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

Heading Hierarchy

Action

44 headings, 1 skip(s)

REVIEW

44 headings, 1 skip(s)

No H1 heading found

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

Heading level skipped: H2 → H5 (missing H3)

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

H2 Our Advantages
H3 End-to-end Production
H3 Independent R&D University Cooperation
H3 Certified Standard Factory
H3 OEM&ODM Service
H2 Packaging Bag Application Industry
H5 Logistics skipped
H5 Clothing & Branding
H5 Household Appliance
H5 Beauty & Personal Care
H5 Hardware Accessories
H5 Consumer Electronics
H2 One-stop Eco-friendly Packaging Bag Customization Service
H3 PE Tote Bag
H3 Facial Cleansing Cloths CPE Frosted Drawstring Bag
H3 Clothing CPE Frosted Drawstring Bag
H3 Biodegradable Vacuum Bag
H3 Recyclable PE Eyewear Flat Bag
H3 Recyclable PE Eyewear Bone bag
H3 Eyewear Biodegradable Bags
H3 Toothbrushes Biodegradable Bag
H2 About Us
H3 16 Years of Custom Eco-Friendly Packaging Bag Production
H4 6000㎡
H4 15+
H4 2000+
H2 Our Team
H2 Frequently Asked Questions
H2 Company News
H3 How to Source Reliable Biodegradable Bags Manufacturers for Custom Orders
H3 Custom Packaging Bags: A Complete Buyer’s Guide for Smooth Sourcing
H3 Eco Friendly Apparel Packaging: Smart Packaging Solutions for Modern Clothing Brands
H3 Choosing the Right Packaging Bags for Products
H3 How Plastic Bags for Packaging Products Enhance Brand Visibility
H3 Biodegradable Bags: Which Packaging Solution Is Best for Your Brand?
H3 How to Choose the Right Biodegradable Plastic Bags Manufacturer for Your Business
H3 Custom Product Packaging Bags: Sustainable Options for Eco-Conscious Brands
H3 How to Choose the Right Biodegradable Bags Manufacturers for Your Brand
H2 Need Custom Packaging Bags?
H3 JXD Eco-packaging Bag
H3 Quick Links
H3 Contact Us
H2 message online
H3 Cookie Usage Notice

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

Form Accessibility

Action

6 of 6 controls have issues

REVIEW

6 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="checkbox" id="message-toggle">

5 control(s) rely on placeholder only

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

Got: <input type="text" name="attr_5" id="attr_5">; <input type="email" name="attr_7" id="attr_7">; <input type="text" name="attr_10" id="attr_10">; <textarea id="attr_8">; <input type="text" name="vertify">

6 controls

0 labeled

5 placeholder only

1 unlabeled

Control	Type	Label	Method
#attr_5	text	(Please enter your name)	placeholder only
#attr_7	email	(Please enter your email)	placeholder only
#attr_10	text	(Please enter your phone number e.g.,（+1）-555-1234- 5555)	placeholder only
#attr_8	textarea	(Please enter message)	placeholder only
vertify	text	(verification code)	placeholder only
#message-toggle	checkbox	(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

Tap Target Adequacy

2 tap target(s) too small or too close together

REVIEW

2 tap target(s) too small or too close together

2 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

A+

Heading Text Quality

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

PASS

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

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

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 "attr_10" should use type="tel" (currently type="text")

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

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"

PASS

Lang attribute set to "en"

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

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Mobile-Readable Font Sizes

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

PASS

All 125 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

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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)

Element	Ratio	Required	FG	BG	Result
h2 Our Advantages	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h2 Packaging Bag Applic…	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h2 One-stop Eco-friendl…	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h2 About Us	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h2 Our Team	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h2 Frequently Asked Que…	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h2 Company News	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h2 Need Custom Packagin…	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h2 message online	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h3 End-to-end Productio…	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h3 Independent R&D Uni…	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h3 Certified Standard F…	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h3 OEM&ODM Service	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h3 PE Tote Bag	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h3 Facial Cleansing Clo…	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h3 Clothing CPE Frosted…	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h3 Biodegradable Vacuum…	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h3 Recyclable PE Eyewea…	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h3 Recyclable PE Eyewea…	19.82:1	3.0:1	#000000	#F3FAF6	Pass
h3 Eyewear Biodegradabl…	19.82:1	3.0:1	#000000	#F3FAF6	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.