Skip to content
https://art.pl

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
7
REVIEW
1
PASS
5
INFO
0
Checks
13
5 PASS 1 REVIEW 7 FIX
D
Alt Text Quality
Action
3 of 12 images have issues
FIX
3 of 12 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
9 image(s) with good alt text
12 images 9 good alt text 3 missing
IssueCount
missing3 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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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
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
No dark mode signals
FIX
No dark mode signals
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 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.

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::
1 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 1 <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.
D
Lighthouse Accessibility Audits
Action
Score 66/100 — 5 failing, 10 passed
FIX
66

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
Sprzedaż domen z rozszerzeniem art.pl już trwa! div.premium-info-wrapper > div.premium-info-wrapper-inner > div.premium-info-wrapper-inner__box > h4
art.pl div.premium-info-wrapper-inner > div.premium-info-wrapper-inner__box > h4 > a
Pospiesz się, dołącz do TWÓRCÓW! Bądź art.pl, twórz z art.pl! Nie przegap swoje… div.premium-info-wrapper > div.premium-info-wrapper-inner > div.premium-info-wrapper-inner__box > p
art.pl div.premium-info-wrapper-inner > div.premium-info-wrapper-inner__box > p > a
art.pl div.premium-info-wrapper-inner > div.premium-info-wrapper-inner__box > p > a
art.pl div.premium-info-wrapper-inner > div.premium-info-wrapper-inner__box > p > a
Cokolwiek tworzysz, pokaż się jak ARTYSTA! div.premium-info-wrapper > div.premium-info-wrapper-inner > div.premium-info-wrapper-inner__box > h5

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
lab.art.pl div.banner-inner > div.banner-info > p > a

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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.footer-wrapper-inner > div.footer-wrapper-inner__menu > div.footer-wrapper-inner-col1 > img div.footer-wrapper-inner > div.footer-wrapper-inner__menu > div.footer-wrapper-inner-col1 > img
div.footer-wrapper-inner > div.footer-wrapper-inner-col4 > a > img div.footer-wrapper-inner > div.footer-wrapper-inner-col4 > a > img
div.footer-wrapper-inner > div.footer-wrapper-inner-col4 > a > img div.footer-wrapper-inner > div.footer-wrapper-inner-col4 > a > img

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
Regulamin div.footer-wrapper-inner-col2 > ul > li > a
Polityka prywatności div.footer-wrapper-inner-col2 > ul > li > 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>`
●Buttons have an accessible name
●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.
●Document has a `<title>` element
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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 a valid value for its `[lang]` attribute
○`<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.
○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.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title An Error Occurred: Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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

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

A+
Heading Hierarchy
14 headings
PASS
14 headings
Info::
Single H1 present
  • H1 Twoja domena w art.pl
  • H2 Dla kogo jest art.pl
  • H3 czym jest
  • H2 art.pl to domena charakteryzująca TWÓRCÓW, których ambicją jest być MISTRZEM w swojej kategorii:
  • H3 To domena dla osób prawnych/instytucji, które reprezentują KREATYWNOŚĆ.
  • H2 LABORATORIUM FOTOGRAFII PROFESJONALNEJ - lab.art.pl
  • H3 Planujesz wystawę, chcesz udekorować swój dom, biuro lub jakąkolwiek przestrzeń, potrzebujesz wielkoformatowych wydruków na witryny sieci sklepów? Zajrzyj do nas! Mamy bogata ofertę szytą na
  • H2 Bez żadnych kruczków wykup hosting w Kru.pl
  • H3 Poszukujesz hostingu? Hosting biznes za 0 zł!!! Użyj kodu: ART2023
  • H2 Jesteś specem od DIGITAL MARKETINGU?
  • H3 Oto tu idealne miejsce na reklamę Twoich usług. Twórcy wszelkich kategorii potrzebują dziś wsparcia DIGITAL MARKETINGU.
  • H3 Rozważasz domenę PREMIUM?
  • H4 Sprzedaż domen z rozszerzeniemart.pl już trwa!
  • H5 Cokolwiek tworzysz, pokaż się jak ARTYSTA!
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" name="q">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
qtext(wpisz tutaj poszukiwaną domenę _)placeholder only

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

<input type="text" name="q">

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
h1 Twoja domena w art.p…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dla kogo jest art.pl21.00:13.0:1
#000000
#FFFFFF
Pass
h2 LABORATORIUM FOTOGRA…18.73:13.0:1
#000000
#F5F1F1
Pass
h2 Bez żadnych kruczk…18.73:13.0:1
#000000
#F5F1F1
Pass
h2 Jesteś specem od DI…18.73:13.0:1
#000000
#F5F1F1
Pass
h3 czym jest21.00:13.0:1
#000000
#FFFFFF
Pass
h3 To domena dla osób …18.73:13.0:1
#000000
#F5F1F1
Pass
h3 Planujesz wystawę, …18.73:13.0:1
#000000
#F5F1F1
Pass
h3 Poszukujesz hostingu…18.73:13.0:1
#000000
#F5F1F1
Pass
h3 Oto tu idealne miejs…18.73:13.0:1
#000000
#F5F1F1
Pass
h3 Rozważasz domenę P…18.73:13.0:1
#000000
#F5F1F1
Pass
title Bank domen ART.PL21.00:14.5:1
#000000
#FFFFFF
Pass
a Cennik21.00:14.5:1
#000000
#FFFFFF
Pass
a Domeny premium21.00:14.5:1
#000000
#FFFFFF
Pass
a FAQ21.00:14.5:1
#000000
#FFFFFF
Pass
a Kontakt21.00:14.5:1
#000000
#FFFFFF
Pass
span Logowanie21.00:14.5:1
#000000
#FFFFFF
Pass
span Mój koszyk21.00:14.5:1
#000000
#FFFFFF
Pass
button Wyszukaj domenę21.00:14.5:1
#000000
#FFFFFF
Pass
p Jest dla tych wszyst…21.00:14.5:1
#000000
#FFFFFF
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.

Send Feedback