Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 6 REVIEW 4 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

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

✗ favicon.ico Missing

✓ PNG Icons Present

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

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.

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

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

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 7 controls have issues

REVIEW

2 of 7 controls have issues

2 control(s) without accessible label

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

Got: <input type="submit">; <input type="submit">

5 control(s) properly labeled

7 controls

5 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
email	email		none
pass	password		none
input	search		none
#_r_o_	text	Email address or phone number	none
#_r_s_	password	Password	none
input	submit	(none)	none
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

Link & Button Quality

2 issue(s) across 54 links and 2 buttons

REVIEW

2 issue(s) across 54 links and 2 buttons

2 link(s) open in new tab without warning

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

Got: https://www.facebook.com/recover/initiate?ars=royal_blue_bar; https://www.facebook.com/recover/initiate?ars=royal_blue_bar

2 button(s) with no accessible text

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

Got: input[type="submit"] (#243 on page); input[type="submit"] (#1034 on page)

52 link(s) with descriptive text

54 links

0 empty

0 generic text

2 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/recover/initiat…	Forgotten account?	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/recover/initiat…	Forgotten password?	new tab	Add '(opens in new tab)' to text
<input>	(empty)	empty	Add button text or aria-label
<input>	(empty)	empty	Add button text or aria-label

52 links and buttons have descriptive text

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

https://www.facebook.com/recover/initiate?ars=royal_blue_bar; https://www.facebook.com/recover/initiate?ars=royal_blue_bar

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.

input[type="submit"] (#243 on page); input[type="submit"] (#1034 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

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.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

a Terms

4.35:1

#000000

#0866FF

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Video	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Facebook video \| Fac…	19.43:1	4.5:1	#000000	#F6F6F6	Pass
title Facebook video	19.43:1	4.5:1	#000000	#F6F6F6	Pass
span Log in	19.43:1	4.5:1	#000000	#F6F6F6	Pass
span Log in	19.26:1	4.5:1	#000000	#F5F5F5	Pass
a Forgotten account?	19.06:1	4.5:1	#000000	#F3F4F4	Pass
span Home	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Live	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Reels	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Shows	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Explore	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Privacy	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Terms	4.35:1	4.5:1	#000000	#0866FF	Fail
a Advertising	11.57:1	4.5:1	#000000	#9CC2FF	Pass
a Ad choices	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Cookies	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span More	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Video	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Home	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Live	18.26:1	4.5:1	#000000	#EFEFEF	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 89/100 — 4 failing, 22 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

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body#app-body > iframe#sem_pixel_iframe `body#app-body > iframe#sem_pixel_iframe`

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.m > div.m > div.m > a `div.m > div.m > div.m > a`
div.m > div.m > div.m > a `div.m > div.m > div.m > 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

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
Mary Lovett Fowler `div.m > div.m > div.m > div.m`
Mary Lovett Fowler `div.m > div.m > div.native-text > span.f2`
1.7M `div.m > div.m > div.m > div.m`
Myo `div.m > div.m > div.m > div.m`
Myo `div.m > div.m > div.native-text > span.f2`
40K `div.m > div.m > div.m > div.m`
Bangladesh Pratidin Entertainment `div.m > div.m > div.m > div.m`
Bangladesh Pratidin Entertainment `div.m > div.m > div.native-text > span.f2`
619,637 reactions `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
div.m > div.m > div.native-text > span.f2 `div.m > div.m > div.native-text > span.f2`
4,751 reactions `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
div.m > div.m > div.native-text > span.f2 `div.m > div.m > div.native-text > span.f2`
43,559 reactions `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
div.m > div.m > div.native-text > span.f2 `div.m > div.m > div.native-text > span.f2`
981,433 reactions `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
div.m > div.m > div.native-text > span.f2 `div.m > div.m > div.native-text > span.f2`
226,588 reactions `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
div.m > div.m > div.native-text > span.f2 `div.m > div.m > div.native-text > span.f2`
289,082 reactions `div.m > div.m > div.m > div.m`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
󱛻 22M 󱝍 `div.m > div.m > div.m > div.m`
󱛻 8.2M 󱝍 `div.m > div.m > div.m > div.m`
󱛻 7.5M 󱝍 `div.m > div.m > div.m > div.m`
Mary Lovett Fowler `div.m > div.m > div.m > div.m`
Myo `div.m > div.m > div.m > div.m`
Bangladesh Pratidin Entertainment `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`
Tap to open profile page `div.m > div.m > div.m > div.m`

○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

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

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

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○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

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

○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

3 headings

PASS

3 headings

Multiple H1 headings (2 found)

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

H1 Video
H1 Video duplicate H1
H2 Popular videos

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 8 images OK

PASS

All 8 images OK

8 image(s) with good alt text

8 images 8 good alt text

All images have appropriate alt text.

A+

Dark Mode Support

Full dark mode support

PASS

Full dark mode support

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: light

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 light ✓Dark theme-color #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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