Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 1 REVIEW 6 FIX

404 Error Page

Action

HTTP 401, custom page

FIX

HTTP 401, custom page

Unexpected status code: HTTP 401

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

Got: HTTP 401

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 401 ✗Page Title Making sure you're not a bot! ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Missing

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

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

2 landmarks

REVIEW

2 landmarks

<main> landmark present

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

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

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 Oh noes!

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 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+

Link & Button Quality

6 links, 0 buttons — all OK

PASS

6 links, 0 buttons — all OK

6 link(s) with descriptive text

6 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

6 links and buttons have descriptive text

A+

Color Contrast (Screenshot)

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

13 pass

Show all checked elements (13)

Element	Ratio	Required	FG	BG	Result
h1 Oh noes!	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Oh noes!	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Access Denied: error…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Go home	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Protected by	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a BotStopper	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p From	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Techaro	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p . Made with ❤️ i…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Unsplash \|	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Help Center	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a support@unsplash.com	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Imprint	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 92/100 — 4 failing, 26 passed

PASS

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

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
Go to Land O'Lakes, Inc.'s profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_cigqnl9au_ > a.link-dYuCfx`
Go to Karolina Grabowska's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34hanl9au_ > a.link-dYuCfx`
figure > div.container-lWLQXW > div.defaultOverlay-iwU1pC > a.link-GVbnGZ `figure > div.container-lWLQXW > div.defaultOverlay-iwU1pC > a.link-GVbnGZ`
Go to Haoli Chen's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34hqnl9au_ > a.link-dYuCfx`
Go to Pana K's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34ianl9au_ > a.link-dYuCfx`
Go to Denis's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34iqnl9au_ > a.link-dYuCfx`
Go to Allison Saeng's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34janl9au_ > a.link-dYuCfx`
figure > div.container-lWLQXW > div.defaultOverlay-iwU1pC > a.link-GVbnGZ `figure > div.container-lWLQXW > div.defaultOverlay-iwU1pC > a.link-GVbnGZ`
Go to Dmytro Koplyk's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34jqnl9au_ > a.link-dYuCfx`
Go to Microsoft Copilot's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_cikanl9au_ > a.link-dYuCfx`
Go to Denis's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34kqnl9au_ > a.link-dYuCfx`
Go to Chris Weiher's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34lanl9au_ > a.link-dYuCfx`
Go to Andrej Lišakov's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34lqnl9au_ > a.link-dYuCfx`
figure > div.container-lWLQXW > div.defaultOverlay-iwU1pC > a.link-GVbnGZ `figure > div.container-lWLQXW > div.defaultOverlay-iwU1pC > a.link-GVbnGZ`
Go to Alexander Mass's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34manl9au_ > a.link-dYuCfx`
Go to Alvan Nee's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34mqnl9au_ > a.link-dYuCfx`
Go to Chris Weiher's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34nanl9au_ > a.link-dYuCfx`
Go to Land O'Lakes, Inc.'s profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_cinqnl9au_ > a.link-dYuCfx`
Go to Andrej Lišakov's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34oanl9au_ > a.link-dYuCfx`
figure > div.container-lWLQXW > div.defaultOverlay-iwU1pC > a.link-GVbnGZ `figure > div.container-lWLQXW > div.defaultOverlay-iwU1pC > a.link-GVbnGZ`
Go to Clay Banks's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34oqnl9au_ > a.link-dYuCfx`
Go to Alvan Nee's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34panl9au_ > a.link-dYuCfx`
Go to De an Sun's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34pqnl9au_ > a.link-dYuCfx`
Go to Resource Database's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34qanl9au_ > a.link-dYuCfx`
figure > div.container-lWLQXW > div.defaultOverlay-iwU1pC > a.link-GVbnGZ `figure > div.container-lWLQXW > div.defaultOverlay-iwU1pC > a.link-GVbnGZ`
Go to Intricate Explorer's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34qqnl9au_ > a.link-dYuCfx`
Go to Microsoft Copilot's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_ciranl9au_ > a.link-dYuCfx`
Go to Maximilian Bungart's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34rqnl9au_ > a.link-dYuCfx`
Go to Aaron Burden's profile `figure > div.userLinkContainer-MPKvy1 > span#base-ui-_R_34sanl9au_ > a.link-dYuCfx`

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
Land O'Lakes, Inc. `div.userLinkContainer-MPKvy1 > span#base-ui-_R_cigqnl9au_ > div.infoContainer-KVyf_x > a.name-bimlc4`
Repicturing Rural ↗ `span#base-ui-_R_cigqnl9au_ > div.infoContainer-KVyf_x > div.secondaryLabel-I7Ce7f > a.secondaryLabelLink-s9A8xZ`
Karolina Grabowska `div.userLinkContainer-MPKvy1 > span#base-ui-_R_34hanl9au_ > div.infoContainer-KVyf_x > a.name-bimlc4`
Allison Saeng `div.userLinkContainer-MPKvy1 > span#base-ui-_R_34janl9au_ > div.infoContainer-KVyf_x > a.name-bimlc4`
Microsoft Copilot `div.userLinkContainer-MPKvy1 > span#base-ui-_R_cikanl9au_ > div.infoContainer-KVyf_x > a.name-bimlc4`
Your AI Companion ↗ `span#base-ui-_R_cikanl9au_ > div.infoContainer-KVyf_x > div.secondaryLabel-I7Ce7f > a.secondaryLabelLink-s9A8xZ`
Andrej Lišakov `div.userLinkContainer-MPKvy1 > span#base-ui-_R_34lqnl9au_ > div.infoContainer-KVyf_x > a.name-bimlc4`
Land O'Lakes, Inc. `div.userLinkContainer-MPKvy1 > span#base-ui-_R_cinqnl9au_ > div.infoContainer-KVyf_x > a.name-bimlc4`
Repicturing Rural ↗ `span#base-ui-_R_cinqnl9au_ > div.infoContainer-KVyf_x > div.secondaryLabel-I7Ce7f > a.secondaryLabelLink-s9A8xZ`
Andrej Lišakov `div.userLinkContainer-MPKvy1 > span#base-ui-_R_34oanl9au_ > div.infoContainer-KVyf_x > a.name-bimlc4`
Resource Database `div.userLinkContainer-MPKvy1 > span#base-ui-_R_34qanl9au_ > div.infoContainer-KVyf_x > a.name-bimlc4`
Microsoft Copilot `div.userLinkContainer-MPKvy1 > span#base-ui-_R_ciranl9au_ > div.infoContainer-KVyf_x > a.name-bimlc4`
Your AI Companion ↗ `span#base-ui-_R_ciranl9au_ > div.infoContainer-KVyf_x > div.secondaryLabel-I7Ce7f > a.secondaryLabelLink-s9A8xZ`

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.

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
Photos `nav.wrapper-wjgLhe > div.cluster-zM_HK3 > div.group-fYx1cB > button#base-ui-_R_1olau_`

○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

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

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

●Form elements have associated labels

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

●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

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

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

●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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

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

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

○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

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

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

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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Image elements do not have `[alt]` attributes that are redundant text.

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

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