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

Landmark Structure

Action

2 landmarks

FIX

2 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

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

404 Error Page

Action

HTTP 429, bare page

FIX

HTTP 429, bare page

Unexpected status code: HTTP 429

Expected HTTP 404 but received 429. This may confuse search engine crawlers.

Got: HTTP 429

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

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 ✗

Link & Button Quality

1 issue(s) across 24 links and 0 buttons

REVIEW

1 issue(s) across 24 links and 0 buttons

1 link(s) with no accessible text

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

Got: /

3 link(s) open in new tab without warning

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

Got: https://l.threads.com/?u=https%3A%2F%2Fhelp.instagram.com%2F769983657850450&e=AT5QkAh9QE7PJT_2oe6dbPWG5--HQuyp9Yjktc6MqIipGvA5RWkXrs4IEeKEdywsAoMHK03ynCooCAs9Y7Bt3Vscue9sP6l4GcvXV-HMZY7n25UVWCA; https://l.threads.com/?u=https%3A%2F%2Fhelp.instagram.com%2F515230437301944&e=AT5QkAh9QE7PJT_2oe6dbPWG5--HQuyp9Yjktc6MqIipGvA5RWkXrs4IEeKEdywsAoMHK03ynCooCAs9Y7Bt3Vscue9sP6l4GcvXV-HMZY7n25UVWCA; https://l.threads.com/?u=https%3A%2F%2Fhelp.instagram.com%2F1896641480634370%2F&e=AT5QkAh9QE7PJT_2oe6dbPWG5--HQuyp9Yjktc6MqIipGvA5RWkXrs4IEeKEdywsAoMHK03ynCooCAs9Y7Bt3Vscue9sP6l4GcvXV-HMZY7n25UVWCA

20 link(s) with descriptive text

24 links

1 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
https://l.threads.com/?u=https%3A%2F%2Fh…	Threads Terms	new tab	Add '(opens in new tab)' to text
https://l.threads.com/?u=https%3A%2F%2Fh…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://l.threads.com/?u=https%3A%2F%2Fh…	Cookies Policy	new tab	Add '(opens in new tab)' to text

20 links and buttons have descriptive text

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

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://l.threads.com/?u=https%3A%2F%2Fhelp.instagram.com%2F769983657850450&e=AT5QkAh9QE7PJT_2oe6dbPWG5--HQuyp9Yjktc6MqIipGvA5RWkXrs4IEeKEdywsAoMHK03ynCooCAs9Y7Bt3Vscue9sP6l4GcvXV-HMZY7n25UVWCA; https://l.threads.com/?u=https%3A%2F%2Fhelp.instagram.com%2F515230437301944&e=AT5QkAh9QE7PJT_2oe6dbPWG5--HQuyp9Yjktc6MqIipGvA5RWkXrs4IEeKEdywsAoMHK03ynCooCAs9Y7Bt3Vscue9sP6l4GcvXV-HMZY7n25UVWCA; https://l.threads.com/?u=https%3A%2F%2Fhelp.instagram.com%2F1896641480634370%2F&e=AT5QkAh9QE7PJT_2oe6dbPWG5--HQuyp9Yjktc6MqIipGvA5RWkXrs4IEeKEdywsAoMHK03ynCooCAs9Y7Bt3Vscue9sP6l4GcvXV-HMZY7n25UVWCA

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

Favicon & Branding

9 icon(s) detected

REVIEW

9 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 16 fail WCAG AA

REVIEW

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

4 pass 16 fail WCAG AA

title Threads

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · top of page (header area)

div Log in

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · top of page (header area)

span Home

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · top of page (header area)

span authortembersapphire

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · top of page (header area)

span 13h

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · above the fold

span Replying to

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · above the fold

span @thequeen.krys

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · above the fold

span Yesterday my cousin asked me how come I …

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · above the fold

span sierracascadia

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · above the fold

span We are going to have to fight our asses …

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · above the fold

span annerollins23

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · above the fold

span 16h

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · above the fold

span Picked up groceries, started putting the…

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · above the fold

span jansen_patty

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · mid-page

span 19h

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · mid-page

span This hotel in Prague is different. Oppos…

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title Threads	2.45:1	4.5:1	#000000	#4C4C4C	Fail
div Log in	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span Home	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span authortembersapphire	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span 13h	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span Replying to	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span @thequeen.krys	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span Yesterday my cousin …	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span sierracascadia	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span We are going to have…	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span annerollins23	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span 16h	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span Picked up groceries,…	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span jansen_patty	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span 19h	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span This hotel in Prague…	2.45:1	4.5:1	#000000	#4C4C4C	Fail
span feministajones	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span adhd threads	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 16h	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Friends	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 87/100 — 3 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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Get the full app experience Unlock more features and see what people are talkin… `div.x1uvtmcs > div.__fb-light-mode > div.x1cy8zhl > div.x1n2onr6`

These are opportunities to improve the usage of ARIA in your application which 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
11h `time.x1rg5ohu > span.html-span > abbr > span`
16h `time.x1rg5ohu > span.html-span > abbr > span`
16h `time.x1rg5ohu > span.html-span > abbr > span`
Replying to @authorlmbennett `div > div.x1gslohp > span.x1lliihq > span.x1lliihq`
@authorlmbennett `div.x1gslohp > span.x1lliihq > span.x1lliihq > span`
asia.nikkei.com `div.xcrlgei > div.x6s0dn4 > span.x1lliihq > span.x1lliihq`
Unlock more features and see what people are talking about right now. `div.x1qjc9v5 > div.x1fmog5m > div.x6s0dn4 > span.x1lliihq`

These are opportunities to improve the legibility of your content.

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#viewport `head > meta#viewport`

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

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

●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

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

●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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

○Buttons have an accessible name

○`<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 an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

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

○Form elements have associated labels

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

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 Home

A+

Alt Text Quality

All 6 images OK

PASS

All 6 images OK

6 image(s) with good alt text

6 images 6 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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.