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

Link & Button Quality

Action

4 issue(s) across 48 links and 5 buttons

FIX

4 issue(s) across 48 links and 5 buttons

2 link(s) with no accessible text

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

Got: https://l.messenger.com/l.php?u=http%3A%2F%2Fitunes.apple.com%2Fapp%2Fid45463…; https://l.messenger.com/l.php?u=https%3A%2F%2Fmarket.android.com%2Fdetails%3F…

3 link(s) open in new tab without warning

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

Got: https://www.facebook.com/privacy/policy; https://messenger.com/policy/cookies; https://www.facebook.com/policies/?ref=pf

2 button(s) with no accessible text

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

Got: button._8orf (#251 on page); button._8org (#258 on page)

43 link(s) with descriptive text

48 links

2 empty

0 generic text

3 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://l.messenger.com/l.php?u=http%3A%…	(empty)	empty	Add link text or aria-label
https://l.messenger.com/l.php?u=https%3A…	(empty)	empty	Add link text or aria-label
https://www.facebook.com/privacy/policy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://messenger.com/policy/cookies	Cookie Policy	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/policies/?ref=p…	Terms	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

46 links and buttons have descriptive text

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

https://l.messenger.com/l.php?u=http%3A%2F%2Fitunes.apple.com%2Fapp%2Fid45463…; https://l.messenger.com/l.php?u=https%3A%2F%2Fmarket.android.com%2Fdetails%3F…

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

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

https://www.facebook.com/privacy/policy; https://messenger.com/policy/cookies; https://www.facebook.com/policies/?ref=pf

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

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

button._8orf (#251 on page); button._8org (#258 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.

Homepage link present on 404 page

404 Page Quality Default 404 Page

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

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 ✗

Landmark Structure

Action

4 landmarks

REVIEW

4 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

Favicon & Branding

Action

6 icon(s) detected

REVIEW

6 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

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

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

Name present: Messenger

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name Messenger ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode browser ✗

Name Messenger Display Mode browser Icons 5 icon(s)

Lighthouse Accessibility Audits

Score 84/100 — 3 failing, 19 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.

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
header#u_0_0_JH > div._1-l5 > div._8otc > button._8orf `header#u_0_0_JH > div._1-l5 > div._8otc > button._8orf`

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._2kzy > div._2tqd > span#messenger_markerting_android_button > a `div._2kzy > div._2tqd > span#messenger_markerting_android_button > 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

●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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

○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

4 headings

PASS

4 headings

Multiple H1 headings (4 found)

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

H1 Useful
H1 Social duplicate H1
H1 Expressive duplicate H1
H1 A place for meaningful conversations duplicate H1

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

A+

Alt Text Quality

All 4 images OK

PASS

All 4 images OK

2 decorative image(s) correctly marked

2 image(s) with good alt text

4 images 2 good alt text 2 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#email	text	Email address or phone number	aria-label
#pass	password	Password	aria-label
#u_0_0_En	checkbox		none

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
h1 Useful	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Social	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Expressive	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 A place for meaningf…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Messenger	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Features	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Show up for your fam…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Build community with…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Let your personality…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Privacy and safety	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div For developers	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Help Centre	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Messenger helps you …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Log In	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Forgotten password?	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Keep me signed in	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span © Meta 2026	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Privacy Policy	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Cookie Policy	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Terms	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.

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