Skip to content
https://home.pl

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: App
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name App ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗
Name App Icons 6 icon(s)
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::
2 navigation landmark(s) detected
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 2 <nav> element(s)
Back to Top
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.
B
Landmark Structure
37 landmarks
REVIEW
37 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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

B
Heading Hierarchy
20 headings
REVIEW
20 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Stwórz stronę WWW
  • H2 Otwórz atrakcyjny sklep
  • H2 – nawet w 30 minut!
  • H2 Hosting dla WordPressa z AI
  • H2 Stwórz stronę WWW
  • H2 Otwórz atrakcyjny sklep
  • H2 – nawet w 30 minut!
  • H2 Hosting dla WordPressa z AI
  • H2 Stwórz stronę WWW
  • H2 Otwórz atrakcyjny sklep
  • H2 – nawet w 30 minut!
  • H2 Czego potrzebujesz, żeby zacząć
  • H2 Znajdź idealny adres dla swojego biznesu
  • H2 Znajdź idealny adres dla swojego biznesu
  • H2 Zarezerwuj przestrzeń dla swojej strony
  • H2 Zarezerwuj przestrzeń dla swojej strony
  • H2 Zbudujemy stronę, jakiej potrzebujesz
  • H2 Zbudujemy stronę, jakiej potrzebujesz
  • H2 Zrób pierwszy krok, a my pomożemy z kolejnymi
  • H2 Zrób pierwszy krok, a my pomożemy z kolejnymi

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title home.pl - podana strona nie istnieje ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
19 icon(s) detected
REVIEW
19 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::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A
Alt Text Quality
2 of 128 images have issues
PASS
2 of 128 images have issues
Warning::
2 image(s) with generic alt text
Info::
37 decorative image(s) correctly marked
Info::
89 image(s) with good alt text
128 images 89 good alt text 37 decorative 2 generic
IssueCount
generic2 image(s)
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id=":R1bac7csm:">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#:R1bac7csm:text(Wpisz poszukiwany adres)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" id=":R1bac7csm:">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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)
ElementRatioRequiredFGBGResult
h2 Stwórz stronę WWW8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Otwórz atrakcyjny s…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 – nawet w 30 minut…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Hosting dla WordPres…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Stwórz stronę WWW8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Otwórz atrakcyjny s…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 – nawet w 30 minut…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Hosting dla WordPres…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Stwórz stronę WWW8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Otwórz atrakcyjny s…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 – nawet w 30 minut…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Czego potrzebujesz, …8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Znajdź idealny adre…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Znajdź idealny adre…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Zarezerwuj przestrze…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Zarezerwuj przestrze…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Zbudujemy stronę, j…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Zbudujemy stronę, j…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Zrób pierwszy krok,…8.57:13.0:1
#000000
#A1A6AC
Pass
h2 Zrób pierwszy krok,…8.57:13.0:1
#000000
#A1A6AC
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
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 27 passed
PASS
91

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
div > div.sc-1ju0p0f-0 > div > div.rah-static div > div.sc-1ju0p0f-0 > div > div.rah-static
div > div.sc-1ju0p0f-0 > div > div.rah-static div > div.sc-1ju0p0f-0 > div > div.rah-static

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.sc-e37j8p-0 > div.sc-e37j8p-0 > div.sc-1lkt62-0 > button.sc-1k63jdr-0 div.sc-e37j8p-0 > div.sc-e37j8p-0 > div.sc-1lkt62-0 > button.sc-1k63jdr-0
div.sc-u6u06y-0 > div.bg-surface-input-default > div.-ml-px > button.uds-focus-outline div.sc-u6u06y-0 > div.bg-surface-input-default > div.-ml-px > button.uds-focus-outline

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.

○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
●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 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
●No element has a `[tabindex]` value greater than 0
●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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`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
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback