Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 2 REVIEW 7 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

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

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

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 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Lighthouse Accessibility Audits

Action

Score 63/100 — 5 failing, 8 passed

FIX

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Connects with over 1 billion users `div.banner > div.banner__bd > div.banner__desc_wrap > p.banner__desc`
Provides chats, calls, and more `div.banner > div.banner__bd > div.banner__desc_wrap > p.banner__desc`
iOS `div.banner__bd > div.banner__download > a.banner__download-item > span`
Android `div.banner__bd > div.banner__download > a#android_download > span`
macOS `div.banner__bd > div.banner__download > a.banner__download-item > span`
Windows `div.banner__bd > div.banner__download > a.banner__download-item > span`
Weixin `div.banner > div.lang_change > div.lang-switcher > a.lang-switcher__brand`
English `div.lang_change > div.lang-switcher > button.lang-switcher__trigger > span`
Copyright © 2012-2026 WeChat. All Rights Reserved. `div.footer-wrp > div.footer > div.footer__bd > div.footer__copyright`

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

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
Terms of Service `div.footer > div.footer__bd > div.footer__links > a`
Acceptable Use Policy `div.footer > div.footer__bd > div.footer__links > 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-hidden="true"]` is not present on the document `<body>`

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Document has a `<title>` element

●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

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

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

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

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○Heading elements appear in a sequentially-descending order

○`<html>` element has a valid value for its `[lang]` attribute

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

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

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

A+

Alt Text Quality

1 of 3 images have issues

PASS

1 of 3 images have issues

1 image(s) with generic alt text

2 image(s) with good alt text

3 images 2 good alt text 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

16 links, 1 buttons — all OK

PASS

16 links, 1 buttons — all OK

14 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://mac.weixin.qq.com/en; https://apps.microsoft.com/detail/xpfckbrnfzq62g; https://weixin.qq.com; https://newsroom.wechat.com/; https://safety.wechat.com/en_US; https://cs.help.wechat.com/hc/en-us; https://weixin.qq.com/; https://www.wechat.com/en/contact_us.html; /en/service_terms.html; /en/privacy_policy.html (+4 more)

2 link(s) with descriptive text

16 links

0 empty

0 generic text

14 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://mac.weixin.qq.com/en	macOS	new tab	Add '(opens in new tab)' to text
https://apps.microsoft.com/detail/xpfckb…	Windows	new tab	Add '(opens in new tab)' to text
https://weixin.qq.com	Weixin	new tab	Add '(opens in new tab)' to text
https://newsroom.wechat.com/	Newsroom	new tab	Add '(opens in new tab)' to text
https://safety.wechat.com/en_US	Safety Center	new tab	Add '(opens in new tab)' to text
https://cs.help.wechat.com/hc/en-us	Help Center	new tab	Add '(opens in new tab)' to text
https://weixin.qq.com/	Weixin Version	new tab	Add '(opens in new tab)' to text
https://www.wechat.com/en/contact_us.htm…	Contact Us	new tab	Add '(opens in new tab)' to text
/en/service_terms.html	Terms of Service	new tab	Add '(opens in new tab)' to text
/en/privacy_policy.html	Privacy Policy	new tab	Add '(opens in new tab)' to text
/en/acceptable_use_policy.html	Acceptable Use Policy	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/wechatapp	Facebook	new tab	Add '(opens in new tab)' to text
https://x.com/Weixin_WeChat	X	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/teamwec…	LinkedIn	new tab	Add '(opens in new tab)' to text

3 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://mac.weixin.qq.com/en; https://apps.microsoft.com/detail/xpfckbrnfzq62g; https://weixin.qq.com; https://newsroom.wechat.com/; https://safety.wechat.com/en_US; https://cs.help.wechat.com/hc/en-us; https://weixin.qq.com/; https://www.wechat.com/en/contact_us.html; /en/service_terms.html; /en/privacy_policy.html (+4 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

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
title WeChat - Connects wi…	7.35:1	4.5:1	#000000	#2AAE67	Pass
p Connects with over 1…	7.35:1	4.5:1	#000000	#2AAE67	Pass
p Provides chats, call…	7.35:1	4.5:1	#000000	#2AAE67	Pass
span iOS	7.35:1	4.5:1	#000000	#2AAE67	Pass
span Android	7.35:1	4.5:1	#000000	#2AAE67	Pass
span macOS	7.35:1	4.5:1	#000000	#2AAE67	Pass
span Windows	7.35:1	4.5:1	#000000	#2AAE67	Pass
a Weixin	7.35:1	4.5:1	#000000	#2AAE67	Pass
span English	7.35:1	4.5:1	#000000	#2AAE67	Pass
a Newsroom	7.35:1	4.5:1	#000000	#2AAE67	Pass
a Safety Center	7.35:1	4.5:1	#000000	#2AAE67	Pass
a Help Center	7.35:1	4.5:1	#000000	#2AAE67	Pass
div Download Android Ver…	7.35:1	4.5:1	#000000	#2AAE67	Pass
span Google Play	7.35:1	4.5:1	#000000	#2AAE67	Pass
span Weixin Version	7.35:1	4.5:1	#000000	#2AAE67	Pass
a Contact Us	7.35:1	4.5:1	#000000	#2AAE67	Pass
a Terms of Service	7.35:1	4.5:1	#000000	#2AAE67	Pass
a Privacy Policy	7.35:1	4.5:1	#000000	#2AAE67	Pass
a Acceptable Use Polic…	7.35:1	4.5:1	#000000	#2AAE67	Pass
div Copyright © 2012-20…	7.35:1	4.5:1	#000000	#2AAE67	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.