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 5 REVIEW 6 FIX

Landmark Structure

Action

3 landmarks

FIX

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Heading Hierarchy

1 headings

REVIEW

1 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Join creators

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Link & Button Quality

1 issue(s) across 9 links and 15 buttons

REVIEW

1 issue(s) across 9 links and 15 buttons

1 link(s) with no accessible text

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

Got: #cover-section

2 link(s) open in new tab without warning

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

Got: /app/help; /app/help

6 link(s) with descriptive text

9 links

1 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#cover-section	(empty)	empty	Add link text or aria-label
/app/help	support	new tab	Add '(opens in new tab)' to text
/app/help	Support	new tab	Add '(opens in new tab)' to text

21 links and buttons have descriptive text

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

#cover-section

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.

/app/help; /app/help

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

15 icon(s) detected

REVIEW

15 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, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

h2 Join

1.03:1

#000000

#060403

needs 3.0:1 (large text)

24px · bottom of viewport

h2 creators

1.03:1

#000000

#060403

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Join	1.03:1	3.0:1	#000000	#060403	Fail
h2 creators	1.03:1	3.0:1	#000000	#060403	Fail
title Boosty.to - a place …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Main	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Showcase	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span How it works	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Features	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span How to use	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Sign up	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Log in	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div More than 500,000 cr…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Your talent	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div is worth money	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div The best way to earn…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div with your audience a…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Start Your Page	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Telegram integration	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Transfer content fro…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Telegram	15.26:1	4.5:1	#000000	#DFDBD8	Pass
div in one click	9.37:1	4.5:1	#000000	#AFADA9	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 80/100 — 4 failing, 18 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.

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
LOG IN `div#topMenu > div.TopMenu-scss--module_right_x5-iO > div > button.BaseButton-scss--module_button_RKC5I`
Start Your Page `div.CoverSection-scss--module_innerWrapper_TP-nD > div.CoverSection-scss--module_info_KBA8I > div > button.BaseButton-scss--module_button_RKC5I`
Telegram `div.TelegramBotBanner-scss--module_root_WbMLK > div.TelegramBotBanner-scss--module_left_eRDrI > div.TelegramBotBanner-scss--module_title_sFZSm > span.TelegramBotBanner-scss--module_telegram_-DgOd`
No need to repost content. Set up forwarding from your channel, and posts will … `div.TelegramBannerSection-scss--module_root_cigvg > div.TelegramBotBanner-scss--module_root_WbMLK > div.TelegramBotBanner-scss--module_left_eRDrI > div.TelegramBotBanner-scss--module_description_3OuYE`
Have questions? Contact support. `div > section.FaqSection-scss--module_root_h85Dr > div.FaqSection-scss--module_titleBox_qDpGa > div.FaqSection-scss--module_description_xyKWn`
support `section.FaqSection-scss--module_root_h85Dr > div.FaqSection-scss--module_titleBox_qDpGa > div.FaqSection-scss--module_description_xyKWn > a.FaqSection-scss--module_descriptionLink_Y3gsZ`
Start Your Page `footer.Footer-scss--module_root_lW052 > div.Footer-scss--module_innerWrapper_0RyRr > section.Footer-scss--module_section_29rUi > button.BaseButton-scss--module_button_RKC5I`

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
RU EN `div#topMenu > div.TopMenu-scss--module_right_x5-iO > div.LanguageSelector-scss--module_container_AY-Jp > select.LanguageSelector-scss--module_select_dYPzE`

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.MainLanding-scss--module_root_4ruex > div#topMenu > div.TopMenu-scss--module_left_CmDbu > a.TopMenu-scss--module_logo_b9-Pe `div.MainLanding-scss--module_root_4ruex > div#topMenu > div.TopMenu-scss--module_left_CmDbu > a.TopMenu-scss--module_logo_b9-Pe`

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

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`

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

○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

○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

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

Alt Text Quality

All 62 images OK

PASS

All 62 images OK

1 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

60 image(s) with good alt text

62 images 60 good alt text 1 decorative

Issue	Count
too long	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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