Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 7 REVIEW 4 FIX

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

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 Present

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

Landmark Structure

Action

1 landmarks

REVIEW

1 landmarks

<main> landmark present

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.

Page Structure — as a screen reader sees it

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

Alt Text Quality

Action

6 of 264 images have issues

REVIEW

6 of 264 images have issues

6 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image(s) with alt text over 125 characters

4 decorative image(s) correctly marked

252 image(s) with good alt text

264 images 252 good alt text 4 decorative 6 missing

Issue	Count
missing	6 image(s)
too long	2 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

Link & Button Quality

105 issue(s) across 191 links and 110 buttons

REVIEW

105 issue(s) across 191 links and 110 buttons

1 link(s) open in new tab without warning

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

Got: https://youtube.com/watch?v=3KcO2M_RQvo

105 button(s) with no accessible text

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

Got: button.btn (#165 on page); button.btn (#172 on page); button.btn (#177 on page); button.btn (#181 on page); button.mr-2 (#369 on page); button (#383 on page); button (#393 on page); button (#403 on page); button (#413 on page); button (#423 on page) (+95 more)

190 link(s) with descriptive text

191 links

0 empty

0 generic text

1 new tab

105 empty buttons

Element	Text	Issue	Suggested Fix
https://youtube.com/watch?v=3KcO2M_RQvo	YoutubeThe Most Viewed Cube on…	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
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

195 links and buttons have descriptive text

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

https://youtube.com/watch?v=3KcO2M_RQvo

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.btn (#165 on page); button.btn (#172 on page); button.btn (#177 on page); button.btn (#181 on page); button.mr-2 (#369 on page); button (#383 on page); button (#393 on page); button (#403 on page); button (#413 on page); button (#423 on page) (+95 more)

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

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

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 Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Expand

1.15:1

#000000

#171507

needs 3.0:1 (large text)

32px · top of page (header area)

h1 your mind

1.18:1

#000000

#1A1809

needs 3.0:1 (large text)

32px · top of page (header area)

h2 Discover the gems of the web,

1.27:1

#000000

#221F0A

needs 3.0:1 (large text)

24px · above the fold

h2 personalized to you.

1.30:1

#000000

#252108

needs 3.0:1 (large text)

24px · above the fold

title Mix — Expand your mind

1.20:1

#000000

#241703

needs 4.5:1 (normal text)

16px · top of page (header area)

div Join

1.31:1

#000000

#23220C

needs 4.5:1 (normal text)

16px · above the fold

span 171,286

1.40:1

#000000

#2B270D

needs 4.5:1 (normal text)

16px · above the fold

div Curators today

1.40:1

#000000

#29280F

needs 4.5:1 (normal text)

16px · above the fold

div or continue with...

1.43:1

#000000

#2C290E

needs 4.5:1 (normal text)

16px · above the fold

span Start Exploring

1.33:1

#000000

#2D2102

needs 4.5:1 (normal text)

16px · above the fold

span Youtube

1.24:1

#000000

#281A02

needs 4.5:1 (normal text)

16px · above the fold

p The Most Viewed Cube on YouTube #shorts

1.27:1

#000000

#2B1C03

needs 4.5:1 (normal text)

16px · mid-page

div +75 liked this

1.18:1

#000000

#251403

needs 4.5:1 (normal text)

16px · mid-page

div Tags

1.19:1

#000000

#251503

needs 4.5:1 (normal text)

16px · mid-page

span YouTube: Tool Tips

1.45:1

#000000

#342806

needs 4.5:1 (normal text)

16px · mid-page

span DIY

1.28:1

#000000

#241F0A

needs 4.5:1 (normal text)

16px · mid-page

span Hobbies

1.19:1

#000000

#1C1908

needs 4.5:1 (normal text)

16px · mid-page

span Home Improvement

1.25:1

#000000

#251C05

needs 4.5:1 (normal text)

16px · mid-page

span Lifehacks

1.10:1

#000000

#111006

needs 4.5:1 (normal text)

16px · mid-page

span Oddly Satisfying

1.06:1

#000000

#0B0B05

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Expand	1.15:1	3.0:1	#000000	#171507	Fail
h1 your mind	1.18:1	3.0:1	#000000	#1A1809	Fail
h2 Discover the gems of…	1.27:1	3.0:1	#000000	#221F0A	Fail
h2 personalized to you.	1.30:1	3.0:1	#000000	#252108	Fail
title Mix — Expand your …	1.20:1	4.5:1	#000000	#241703	Fail
div Join	1.31:1	4.5:1	#000000	#23220C	Fail
span 171,286	1.40:1	4.5:1	#000000	#2B270D	Fail
div Curators today	1.40:1	4.5:1	#000000	#29280F	Fail
div or continue with...	1.43:1	4.5:1	#000000	#2C290E	Fail
span Start Exploring	1.33:1	4.5:1	#000000	#2D2102	Fail
span Youtube	1.24:1	4.5:1	#000000	#281A02	Fail
p The Most Viewed Cube…	1.27:1	4.5:1	#000000	#2B1C03	Fail
div +75 liked this	1.18:1	4.5:1	#000000	#251403	Fail
div Tags	1.19:1	4.5:1	#000000	#251503	Fail
span YouTube: Tool Tips	1.45:1	4.5:1	#000000	#342806	Fail
span DIY	1.28:1	4.5:1	#000000	#241F0A	Fail
span Hobbies	1.19:1	4.5:1	#000000	#1C1908	Fail
span Home Improvement	1.25:1	4.5:1	#000000	#251C05	Fail
span Lifehacks	1.10:1	4.5:1	#000000	#111006	Fail
span Oddly Satisfying	1.06:1	4.5:1	#000000	#0B0B05	Fail

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

Action

Score 77/100 — 4 failing, 16 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
div.pointer-events-auto > div.flex > div.flex > button.p-3 `div.pointer-events-auto > div.flex > div.flex > button.p-3`
div.pointer-events-auto > div.flex > div.flex > button `div.pointer-events-auto > div.flex > div.flex > button`
div.flex > div.flex > div.group > button.flex `div.flex > div.flex > div.group > button.flex`
div.flex > div.flex > div.group > button.flex `div.flex > div.flex > div.group > button.flex`
div.pointer-events-auto > div.flex > div.flex > button `div.pointer-events-auto > div.flex > div.flex > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.pointer-events-none > div.flex > div.pointer-events-auto > button.mr-2 `div.pointer-events-none > div.flex > div.pointer-events-auto > button.mr-2`
div.pointer-events-auto > div.flex > div.flex > button.p-3 `div.pointer-events-auto > div.flex > div.flex > button.p-3`
div.pointer-events-auto > div.flex > div.flex > button `div.pointer-events-auto > div.flex > div.flex > button`
div.flex > div.flex > div.group > button.flex `div.flex > div.flex > div.group > button.flex`
div.flex > div.flex > div.group > button.flex `div.flex > div.flex > div.group > button.flex`
div.pointer-events-auto > div.flex > div.flex > button `div.pointer-events-auto > div.flex > div.flex > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`

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.

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
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`
div.flex > a.btn > div.-m-1 > button `div.flex > a.btn > div.-m-1 > button`

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●Links have a discernible name

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[accesskey]` values are unique

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

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

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

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

○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

○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

2 headings

PASS

2 headings

Single H1 present

H1 Expand your mind
H2 Discover the gems of the web, personalized to you.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#g-recaptcha-response-100000	textarea	(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

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