Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

10 PASS 5 REVIEW 9 FIX

Alt Text Quality

Action

5 of 42 images have issues

FIX

5 of 42 images have issues

5 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

5 image-in-link without alt text

An image inside a link with no alt creates an empty link.

4 decorative image(s) correctly marked

33 image(s) with good alt text

42 images 33 good alt text 4 decorative 5 missing

Issue	Count
missing	5 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Mobile Keyboard & Autofill

Action

7/7 eligible field(s) missing autocomplete or inputmode

FIX

7/7 eligible field(s) missing autocomplete or inputmode

3 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" name="email" id="reg-email">, <input type="email" name="email" id="log-email">, <input type="email" name="email" id="reset-email">

4 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email, search.

Got: <input type="email" name="email" id="reg-email">, <input type="email" name="email" id="log-email">, <input type="email" name="email" id="reset-email">, <input type="search" name="q" id="rbxMobileSearchInput">

Tap Target Adequacy

Action

36 tap target(s) too small or too close together

FIX

36 tap target(s) too small or too close together

36 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Mobile-Readable Font Sizes

Action

52% of visible text renders at >= 12 CSS px (154 below threshold)

FIX

52% of visible text renders at >= 12 CSS px (154 below threshold)

154 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 9.0px ("Głosuję"); <span> 10.4px ("Autor:"); <a> 10.4px ("Admin"); <span> 10.4px ("Sklep:"); <a> 10.4px ("Revolut").

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

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 404 ✓Page Title 404 Not Found ✓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

5 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 5 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

14 landmarks

REVIEW

14 landmarks

<main> landmark present

5 <nav> landmark(s) found

1 of 5 <nav> elements are unlabeled

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

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

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

Heading Hierarchy

26 headings, 1 skip(s)

REVIEW

26 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 CASHBACK + KODY RABATOWE
H2 Jak działa cashback na Rabatex?
H3 16
H3 1002
H3 (empty)
H2 Popularne na społeczności
H2 Dołącz do Revolut i zgarnij 100 zł!
H2 Grand Theft Auto VI (Xbox Series X/S oraz PS5) - Taniej w G2A + Cashback
H2 Jak działa Allegro Smart? Czy warto?
H2 MULTIPROMOCJA - Im więcej wybierasz, tym więcej zyskujesz!
H2 Zgarnij Rabat 60 zł
H2 Kod rabatowy 10% na wszystkie modele
H2 Dedykowany kod rabatowy na wszystko w sklepie - 20%
H2 Kupon na 20% oszczędności
H2 Kod rabatowy 10%
H2 Kup 3+ produkty, cło pokryte! Dostawa darmowa
H2 Najczęstsze pytania
H2 10 zł na start dla każdego
H5 Udostępnij okazję skipped
H2 Rejestracja na Rabatex
H2 Witaj ponownie!
H2 Witaj ponownie!
H2 Menu użytkownika
H2 Popularne sklepy
H2 Popularne na społeczności
H2 Znajdź coś dla siebie

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Link & Button Quality

Action

8 issue(s) across 238 links and 45 buttons

REVIEW

8 issue(s) across 238 links and 45 buttons

8 link(s) with no accessible text

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

Got: #; #; #; #; https://facebook.com/rabatexpl; https://instagram.com/rabatexpl/; https://tiktok.com/@rabatexpl; https://x.com/rabatexpl

5 link(s) open in new tab without warning

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

Got: https://leadgroup.pl; #; #; #; #

225 link(s) with descriptive text

238 links

8 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://facebook.com/rabatexpl	(empty)	empty	Add link text or aria-label
https://instagram.com/rabatexpl/	(empty)	empty	Add link text or aria-label
https://tiktok.com/@rabatexpl	(empty)	empty	Add link text or aria-label
https://x.com/rabatexpl	(empty)	empty	Add link text or aria-label
https://leadgroup.pl	Logo Leadgroup	new tab	Add '(opens in new tab)' to text
#	Facebook	new tab	Add '(opens in new tab)' to text
#	X	new tab	Add '(opens in new tab)' to text
#	Telegram	new tab	Add '(opens in new tab)' to text
#	Whatsapp	new tab	Add '(opens in new tab)' to text
/przekierowanie-cashback/allegro?u=	Allegro	img no alt	Add alt attribute to the image
/przekierowanie-cashback/pyszne?u=	Pyszne.pl	img no alt	Add alt attribute to the image
/przekierowanie-cashback/esky?u=	eSky	img no alt	Add alt attribute to the image
/przekierowanie-cashback/aliexpress?u=	AliExpress	img no alt	Add alt attribute to the image
/przekierowanie-cashback/kinguin?u=	Kinguin	img no alt	Add alt attribute to the image

270 links and buttons have descriptive text

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

#; #; #; #; https://facebook.com/rabatexpl; https://instagram.com/rabatexpl/; https://tiktok.com/@rabatexpl; https://x.com/rabatexpl

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://leadgroup.pl; #; #; #; #

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

Action

8 icon(s) detected

REVIEW

8 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Score 83/100 — 4 failing, 23 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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Załóż konto i odbierz 10 zł Wybierz sposób rejestracji `aside#rabatexMobileCta > div.accordion-item > div#rabatexMobileCtaTitle > div.accordion-button`

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
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
Zarejestruj przez Facebook `div.accordion-body > div.g-1 > div.col-12 > a.btntopheader`

These are opportunities to improve the legibility of your content.

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
div.container > div.align-items-center > div.col-12 > a.hero-store-item `div.container > div.align-items-center > div.col-12 > a.hero-store-item`
div.container > div.align-items-center > div.col-12 > a.hero-store-item `div.container > div.align-items-center > div.col-12 > a.hero-store-item`
div.container > div.align-items-center > div.col-12 > a.hero-store-item `div.container > div.align-items-center > div.col-12 > a.hero-store-item`
div.container > div.align-items-center > div.col-12 > a.hero-store-item `div.container > div.align-items-center > div.col-12 > a.hero-store-item`
div.container > div.align-items-start > div.col-6 > a `div.container > div.align-items-start > div.col-6 > a`
div.container > div.align-items-start > div.col-6 > a `div.container > div.align-items-start > div.col-6 > a`
div.container > div.align-items-start > div.col-6 > a `div.container > div.align-items-start > div.col-6 > a`
div.container > div.align-items-start > div.col-6 > a `div.container > div.align-items-start > div.col-6 > a`

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
0 Skomentuj `article.community-deal > div.community-deal-body > div.community-actions > a.community-comment`
Udostępnij `article.community-deal > div.community-deal-body > div.community-actions > button.community-share`
#akcja promocyjna `div.community-deal-body > div.community-actions > span > a`
Udostępnij `article.community-deal > div.community-deal-body > div.community-actions > button.community-share`
#gta `div.community-deal-body > div.community-actions > span > a`
#ps5 `div.community-deal-body > div.community-actions > span > a`
#grand theft auto `div.community-deal-body > div.community-actions > span > a`
#pre-order `div.community-deal-body > div.community-actions > span > a`
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
0 Skomentuj `article.community-deal > div.community-deal-body > div.community-actions > a.community-comment`
#allegro smart `div.community-deal-body > div.community-actions > span > a`
#jak kupić na allegro `div.community-deal-body > div.community-actions > span > a`
#smart `div.community-deal-body > div.community-actions > span > a`
0 Skomentuj `article.community-deal > div.community-deal-body > div.community-actions > a.community-comment`
Udostępnij `article.community-deal > div.community-deal-body > div.community-actions > button.community-share`
#pitbu `div.community-deal-body > div.community-actions > span > a`
#odzież sportowa `div.community-deal-body > div.community-actions > span > a`
#ubrania `div.community-deal-body > div.community-actions > span > a`
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
0 Skomentuj `article.community-deal > div.community-deal-body > div.community-actions > a.community-comment`
#kod rabatowy `div.community-deal-body > div.community-actions > span > a`
#venezianico `div.community-deal-body > div.community-actions > span > a`
#kod rabatowy zegarki `div.community-deal-body > div.community-actions > span > a`
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
0 Skomentuj `article.community-deal > div.community-deal-body > div.community-actions > a.community-comment`
#sekrecik `div.community-deal-body > div.community-actions > span > a`
#kod rabatowy -20% `div.community-deal-body > div.community-actions > span > a`
0 Skomentuj `article.community-deal > div.community-deal-body > div.community-actions > a.community-comment`
#czasnajedzenie `div.community-deal-body > div.community-actions > span > a`
#pysznejedzenie `div.community-deal-body > div.community-actions > span > a`
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
0 Skomentuj `article.community-deal > div.community-deal-body > div.community-actions > a.community-comment`
Udostępnij `article.community-deal > div.community-deal-body > div.community-actions > button.community-share`
#kod promocyjny `div.community-deal-body > div.community-actions > span > a`
Zgłoś `article.community-deal > div.community-deal-body > div.community-actions > button.community-report`
Zooplus cashback `body.d-flex > div.container > div.mb-5 > a`

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

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

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●All heading elements contain content.

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

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

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

○Uses ARIA roles only on compatible elements

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

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

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

1 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "16"

Got: 1 ≤2-char heading(s)

1 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 1 all-caps heading(s)

A+

Form Accessibility

All 7 controls labeled

PASS

All 7 controls labeled

7 control(s) properly labeled

7 controls

7 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#reg-email	email	Adres e-mail	for/id
#reg-password	password	Powtórz Hasło	for/id
#reg-password	password	Powtórz Hasło	for/id
#log-email	email	Adres e-mail	for/id
#log-password	password	Hasło	for/id
#reset-email	email	Adres e-mail	for/id
#rbxMobileSearchInput	search	Szukaj wpisów	aria-label

A+

Form Input Types

7 form control(s) checked, no type mismatches

PASS

7 form control(s) checked, no type mismatches

No input-type mismatches detected

Form Input Quality

1 input-semantic issue(s) across 7 form control(s)

PASS

1 input-semantic issue(s) across 7 form control(s)

3 password field(s) missing or with invalid `autocomplete`

Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="haslo">, <input type="password" name="re-haslo">, <input type="password" name="haslo">.

A+

Document Language

Lang attribute set to "pl"

PASS

Lang attribute set to "pl"

<html lang="pl"> is set and valid

Got: pl

A+

Tabindex Anti-Patterns

4 explicit tabindex attribute(s) checked, no anti-patterns

PASS

4 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

A+

Color Contrast (Screenshot)

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 CASHBACK + KODY RABA…	15.68:1	3.0:1	#000000	#F1DAD0	Pass
h2 Jak działa cashback…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Popularne na społec…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Najczęstsze pytania	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 10 zł na start dla …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Rejestracja na Rabat…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Witaj ponownie!	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Witaj ponownie!	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Menu użytkownika	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Popularne sklepy	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Popularne na społec…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Znajdź coś dla sie…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 1002	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Rabatex - Cashback i…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Katalog sklepów	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Społeczność	20.22:1	4.5:1	#000000	#FFFAF3	Pass
a Zaloguj się	20.22:1	4.5:1	#000000	#FFFAF3	Pass
a Zarejestruj się	17.44:1	4.5:1	#000000	#F7E7DE	Pass
div Kupujesz jak zawsze.	15.68:1	4.5:1	#000000	#F1DAD0	Pass
span Część pieniędzy …	15.68:1	4.5:1	#000000	#F1DAD0	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.

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