Skip to content
https://link.space

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Warning::
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

F
404 Error Page
Action
HTTP 503, bare page
FIX
HTTP 503, bare page
Warning::
Unexpected status code: HTTP 503
Expected HTTP 404 but received 503. This may confuse search engine crawlers.
Got: HTTP 503
Warning::
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 503 ✗Page Title 503 Service Temporarily Unavailable ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
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
title Streamlabs: Free Live Streaming & Record…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
div Popup heading
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
p All-in-one live streaming software
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
span English
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a English
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a العربية
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Español
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Português (Brazil)
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Русский
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Français
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Türkçe
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Deutsch
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Português
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a 日本語
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a 简体中文 (Simplified)
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a Italiano
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a Indonesian
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a 한국어
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a Język polski
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a Čeština
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title Streamlabs: Free Liv…1.00:14.5:1
#000000
#000000
Fail
div Popup heading1.00:14.5:1
#000000
#000000
Fail
p All-in-one live stre…1.00:14.5:1
#000000
#000000
Fail
span English1.00:14.5:1
#000000
#000000
Fail
a English1.00:14.5:1
#000000
#000000
Fail
a العربية1.00:14.5:1
#000000
#000000
Fail
a Español1.00:14.5:1
#000000
#000000
Fail
a Português (Brazil)1.00:14.5:1
#000000
#000000
Fail
a Русский1.00:14.5:1
#000000
#000000
Fail
a Français1.00:14.5:1
#000000
#000000
Fail
a Türkçe1.00:14.5:1
#000000
#000000
Fail
a Deutsch1.00:14.5:1
#000000
#000000
Fail
a Português1.00:14.5:1
#000000
#000000
Fail
a 日本語1.00:14.5:1
#000000
#000000
Fail
a 简体中文 (Simpli…1.00:14.5:1
#000000
#000000
Fail
a Italiano1.00:14.5:1
#000000
#000000
Fail
a Indonesian1.00:14.5:1
#000000
#000000
Fail
a 한국어1.00:14.5:1
#000000
#000000
Fail
a Język polski1.00:14.5:1
#000000
#000000
Fail
a Čeština1.00:14.5:1
#000000
#000000
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.

A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 29 passed
PASS
92

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.landing-hero > div.landing-hero__inner > div.landing-hero__figure > img.landing-hero__sp div.landing-hero > div.landing-hero__inner > div.landing-hero__figure > img.landing-hero__sp
section.landing-page__tool-cards > div.landing-page__tool-cards--container > div.ab-tool-card > img.ab-tool-card__image section.landing-page__tool-cards > div.landing-page__tool-cards--container > div.ab-tool-card > img.ab-tool-card__image
section.landing-page__tool-cards > div.landing-page__tool-cards--container > div.ab-tool-card > img.ab-tool-card__image section.landing-page__tool-cards > div.landing-page__tool-cards--container > div.ab-tool-card > img.ab-tool-card__image
section.landing-page__tool-cards > div.landing-page__tool-cards--container > div.ab-tool-card > img.ab-tool-card__image section.landing-page__tool-cards > div.landing-page__tool-cards--container > div.ab-tool-card > img.ab-tool-card__image
div.landing-page__sections > section.landing-section > div.landing-section__image > img.landing-section__image--slobs div.landing-page__sections > section.landing-section > div.landing-section__image > img.landing-section__image--slobs
div.landing-page__sections > section.landing-section > div.landing-section__image > img div.landing-page__sections > section.landing-section > div.landing-section__image > img
div.landing-page__sections > section.landing-section > div.landing-section__image > img div.landing-page__sections > section.landing-section > div.landing-section__image > img
div.landing-page__sections > section.landing-section > div.landing-section__image > img div.landing-page__sections > section.landing-section > div.landing-section__image > img
div.landing-page__sections > section.landing-section > div.landing-section__image > img div.landing-page__sections > section.landing-section > div.landing-section__image > img
section.ultra-landing__compare-plans > div.ultra-product-grid > div.product-card > img.product-card__image section.ultra-landing__compare-plans > div.ultra-product-grid > div.product-card > img.product-card__image
section.ultra-landing__compare-plans > div.ultra-product-grid > div.product-card > img.product-card__image section.ultra-landing__compare-plans > div.ultra-product-grid > div.product-card > img.product-card__image
section.ultra-landing__compare-plans > div.ultra-product-grid > div.product-card > img.product-card__image section.ultra-landing__compare-plans > div.ultra-product-grid > div.product-card > img.product-card__image
section.ultra-landing__compare-plans > div.ultra-product-grid > div.product-card > img.product-card__image section.ultra-landing__compare-plans > div.ultra-product-grid > div.product-card > img.product-card__image
section.call-to-action-section > div.call-to-action-section__inner > div.call-to-action-section__image > img.landing-page__call-to-action--mobile section.call-to-action-section > div.call-to-action-section__inner > div.call-to-action-section__image > img.landing-page__call-to-action--mobile

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Press for Accessibility for blind people who use screen readers div#INDquickAccess > ul > li > button.INDshortcutBtn
Press for Accessibility menu div#INDquickAccess > ul > li > button

These are opportunities to improve keyboard navigation in your application.

○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[accesskey]` values are unique
●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
●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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`button`, `link`, and `menuitem` elements 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
○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.
○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.
○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.

Send Feedback