Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 3 REVIEW 7 FIX

Mobile Keyboard & Autofill

Action

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

FIX

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

1 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="email">

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

Got: <input type="email" name="email" id="email">

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 ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

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 Missing

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

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

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

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

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

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

Mobile-Readable Font Sizes

97% of visible text renders at >= 12 CSS px (2 below threshold)

REVIEW

97% of visible text renders at >= 12 CSS px (2 below threshold)

2 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: <a> 10.9px ("Nasze funkcje"); <a> 10.9px ("Skontaktuj się").

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA 2 pass AA only

h1 Deals Brokers

1.53:1

#000000

#352B28

needs 3.0:1 (large text)

32px · above the fold · over background image/gradient

h2 Kluczowe funkcje

1.02:1

#000000

#030401

needs 3.0:1 (large text)

24px · bottom of viewport

h2 O firmie

1.02:1

#000000

#030401

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Najczęstsze pytania

1.02:1

#000000

#030401

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kontakt

1.02:1

#000000

#030401

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Co zyskujesz?

1.78:1

#000000

#3F3537

needs 3.0:1 (large text)

19px · mid-page · over background image/gradient

h3 Zapytania handlowe

1.02:1

#000000

#030401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Zestawienie ofert

1.02:1

#000000

#030401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Więcej czasu na handel

1.02:1

#000000

#030401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Pełny kontekst oferty

1.02:1

#000000

#030401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Powiadomienia

1.02:1

#000000

#030401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Od zapytania do domknięcia

1.02:1

#000000

#030401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Misja

1.02:1

#000000

#030401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Wartości

1.02:1

#000000

#030401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Szybkie linki

1.02:1

#000000

#030401

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Informacje prawne

1.02:1

#000000

#030401

needs 3.0:1 (large text)

19px · bottom of viewport

title Deals Brokers — dealsbrokers.pl

1.88:1

#000000

#393C38

needs 4.5:1 (normal text)

16px · top of page (header area)

a Start

4.16:1

#000000

#6E6F6D

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

3 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Deals Brokers	1.53:1	3.0:1	#000000	#352B28	Fail
h2 O projekcie	4.30:1	3.0:1	#000000	#92684B	Pass
h2 Kluczowe funkcje	1.02:1	3.0:1	#000000	#030401	Fail
h2 O firmie	1.02:1	3.0:1	#000000	#030401	Fail
h2 Najczęstsze pytania	1.02:1	3.0:1	#000000	#030401	Fail
h2 Kontakt	1.02:1	3.0:1	#000000	#030401	Fail
h3 Co zyskujesz?	1.78:1	3.0:1	#000000	#3F3537	Fail
h3 Zapytania handlowe	1.02:1	3.0:1	#000000	#030401	Fail
h3 Zestawienie ofert	1.02:1	3.0:1	#000000	#030401	Fail
h3 Więcej czasu na han…	1.02:1	3.0:1	#000000	#030401	Fail
h3 Pełny kontekst ofer…	1.02:1	3.0:1	#000000	#030401	Fail
h3 Powiadomienia	1.02:1	3.0:1	#000000	#030401	Fail
h3 Od zapytania do domk…	1.02:1	3.0:1	#000000	#030401	Fail
h3 Misja	1.02:1	3.0:1	#000000	#030401	Fail
h3 Wartości	1.02:1	3.0:1	#000000	#030401	Fail
h3 Szybkie linki	1.02:1	3.0:1	#000000	#030401	Fail
h3 Informacje prawne	1.02:1	3.0:1	#000000	#030401	Fail
title Deals Brokers — de…	1.88:1	4.5:1	#000000	#393C38	Fail
a Start	4.16:1	4.5:1	#000000	#6E6F6D	Fail
a O projekcie	5.93:1	4.5:1	#000000	#8D8783	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.

A+

Heading Hierarchy

21 headings

PASS

21 headings

Single H1 present

H1 Deals Brokers FMCG Networking
H2 O projekcie
H3 Co zyskujesz?
H2 Kluczowe funkcje
H3 Zapytania handlowe
H3 Zestawienie ofert
H3 Więcej czasu na handel
H3 Pełny kontekst oferty
H3 Powiadomienia
H3 Od zapytania do domknięcia
H2 O firmie
H3 Misja
H3 Wartości
H2 Najczęstsze pytania
H3 Czy potrzebuję instalacji na komputerze?
H3 Jak zostać dostawcą?
H3 Jak zacząć kupować na platformie?
H3 Jak uzyskać dostęp do panelu?
H2 Kontakt
H3 Szybkie linki
H3 Informacje prawne

A+

Heading Text Quality

All 21 heading(s) have substantive, well-formed text

PASS

All 21 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 5 controls labeled

PASS

All 5 controls labeled

5 control(s) properly labeled

5 controls

5 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#imie	text	Imię i nazwisko	for/id
#email	email	E-mail	for/id
#temat	select	Temat	for/id
#wiadomosc	textarea	Wiadomość	for/id
#zgoda_rodo	checkbox	Wyrażam zgodę na kontakt w sprawie zapytania oraz przetwarzanie danych podanych w formularzu.	for/id

A+

Link & Button Quality

16 links, 9 buttons — all OK

PASS

16 links, 9 buttons — all OK

16 link(s) with descriptive text

16 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

25 links and buttons have descriptive text

A+

Form Input Types

5 form control(s) checked, no type mismatches

PASS

5 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

5 form control(s) checked, no input-semantic issues

PASS

5 form control(s) checked, no input-semantic issues

All form input semantics look correct

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

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

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

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 25 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.

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
Slajd 1 `body > header#start > div.container > button.wskaznik-slajdu`
Slajd 2 `body > header#start > div.container > button.wskaznik-slajdu`
Slajd 3 `body > header#start > div.container > button.wskaznik-slajdu`

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Slajdy banera `body > header#start > div.container`

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.

○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

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

●Select elements have associated label elements.

●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

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

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

○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

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

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