Skip to content
https://interia.pl

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
D
Landmark Structure
Action
30 landmarks
FIX
30 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN (missing!) CONTENTINFO footer

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

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #fff
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 ModePartial Dark Mode
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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Back-to-top link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Heading Hierarchy
Action
28 headings
REVIEW
28 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
3 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H4 Warszawa
  • H2 WYDARZENIA DNIA
  • H2 Okiem Interii
  • H2 Dziś w Interii
  • H2 Piszą dla nas:
  • H2 Dla Ciebie
  • H2 Polecane
  • H2 Sport
  • H2 Sport
  • H2 Biznes
  • H2 Biznes
  • H2 Motoryzacja
  • H2 Piszą dla nas:
  • H2 Styl Życia
  • H2 Technologie Gry
  • H2 Kulinaria
  • H2 Rekomendacje
  • H2 (empty)
  • H2 Popkultura
  • H2 (empty)
  • H2 Porady
  • H2 W wolnym czasie
  • H2 Oferty dnia
  • H2 Gazetki promocyjne
  • H2 Gry online
  • H2 Popularne
  • H2 Ciekawe
  • H2 (empty)

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

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

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 Komunikat - INTERIA.PL ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA 1 pass AA only
span Katowice,
1.28:1
#000000
on
#231E1F
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
i Śląskie
1.28:1
#000000
on
#2B1B1C
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
span Kielce,
3.07:1
#000000
on
#5B5967
needs 4.5:1 (normal text)
16px · mid-page · 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)
ElementRatioRequiredFGBGResult
h2 Piszą dla nas:19.43:13.0:1
#000000
#F6F6F6
Pass
h2 Piszą dla nas:19.43:13.0:1
#000000
#F6F6F6
Pass
title Interia - Polska i …21.00:14.5:1
#000000
#FFFFFF
Pass
span Teraz16.21:14.5:1
#000000
#E2E2E2
Pass
a Warszawa21.00:14.5:1
#000000
#FFFFFF
Pass
a Wyczyść20.48:14.5:1
#000000
#FCFCFD
Pass
span Zlokalizuj mnie19.81:14.5:1
#000000
#F8F8FB
Pass
span Białystok,19.81:14.5:1
#000000
#F8F8FB
Pass
i Podlaskie19.81:14.5:1
#000000
#F8F8FB
Pass
span Bielsko Biała,19.81:14.5:1
#000000
#F8F8FB
Pass
i Śląskie19.81:14.5:1
#000000
#F8F8FB
Pass
span Bydgoszcz,19.81:14.5:1
#000000
#F8F8FB
Pass
i Kujawsko-pomorskie19.81:14.5:1
#000000
#F8F8FB
Pass
span Gdańsk,19.26:14.5:1
#000000
#F5F5F5
Pass
i Pomorskie19.26:14.5:1
#000000
#F5F5F5
Pass
span Gorzów Wlk.,19.26:14.5:1
#000000
#F5F5F5
Pass
i Lubuskie4.82:14.5:1
#000000
#7B787C
Pass
span Katowice,1.28:14.5:1
#000000
#231E1F
Fail
i Śląskie1.28:14.5:1
#000000
#2B1B1C
Fail
span Kielce,3.07:14.5:1
#000000
#5B5967
Fail

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.

B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 20 passed
REVIEW
82

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
Bardzo dobre div.weather-alert > a.weather-alert__info > div.text > span
INTERIA Z MADRYTU li.news-li > a.listitem-a > div.listitem-img-wrapper > span.tile-label
3 615,77 ul.stock > li.header-li > a.header-a > span.value
-0,67% ul.stock > li.header-li > a.header-a > span.growth
59 585,86 ul.stock > li.header-li > a.header-a > span.value
0,40% ul.stock > li.header-li > a.header-a > span.growth
49 490,03 ul.stock > li.header-li > a.header-a > span.value
0,69% ul.stock > li.header-li > a.header-a > span.growth
4,6207 ul.stock > li.header-li > a.header-a > span.value
0,00% ul.stock > li.header-li > a.header-a > span.growth
4,2440 ul.stock > li.header-li > a.header-a > span.value
ZIELONA INTERIA li.news-li > a.listitem-a > div.listitem-img-wrapper > span.tile-label
MUST BE THE MUSIC ul.header-ul > li.header-li > a.header-a > span.header-span
Copyright: div.footer-item > ul.footer-ul > li.footer-li > span
INTERIA.PL div.footer-item > ul.footer-ul > li.footer-li > a.footer-a
1999-2026 div.footer-item > ul.footer-ul > li.footer-li > span
naszych partnerów reklamowych (1018) form.rodo-popup > div.rodo-popup-content > p > a
PRZYPOMNIJ PÓŹNIEJ body > form.rodo-popup > div.rodo-popup-content > button.rodo-popup-later
USTAWIENIA PRYWATNOŚCI body > form.rodo-popup > div.rodo-popup-buttons > button.rodo-popup-settings
PRZEJDŹ DO SERWISU body > form.rodo-popup > div.rodo-popup-buttons > button.rodo-popup-agree

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
POWIETRZE div.weather-alert > a.weather-alert__info > div.text > h4

These are opportunities to improve keyboard navigation in your application.

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
li.news-li > a.listitem-a > div.listitem-img-wrapper > img.listitem-img li.news-li > a.listitem-a > div.listitem-img-wrapper > img.listitem-img
li.news-li > a.listitem-a > div.listitem-img-wrapper > img.listitem-img li.news-li > a.listitem-a > div.listitem-img-wrapper > img.listitem-img
li.news-li > a.listitem-a > div.listitem-img-wrapper > img.listitem-img li.news-li > a.listitem-a > div.listitem-img-wrapper > img.listitem-img
li.news-li > a.listitem-a > div.listitem-img-wrapper > img.listitem-img li.news-li > a.listitem-a > div.listitem-img-wrapper > img.listitem-img
ul.news-ul > li.reels-li > a.tile-a > img.tile-img ul.news-ul > li.reels-li > a.tile-a > img.tile-img
ul.news-ul > li.reels-li > a.tile-a > img.tile-img ul.news-ul > li.reels-li > a.tile-a > img.tile-img
ul.news-ul > li.reels-li > a.tile-a > img.tile-img ul.news-ul > li.reels-li > a.tile-a > img.tile-img
ul.news-ul > li.reels-li > a.tile-a > img.tile-img ul.news-ul > li.reels-li > a.tile-a > img.tile-img
ul.news-ul > li.reels-li > a.tile-a > img.tile-img ul.news-ul > li.reels-li > a.tile-a > img.tile-img

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
nav.column-switch > ul.tabbar-ul > li.tabbar-li > a.tabbar-a nav.column-switch > ul.tabbar-ul > li.tabbar-li > a.tabbar-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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[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 use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●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.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`[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
○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
○`<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.
○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
○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 386 images OK
PASS
All 386 images OK
Info::
240 decorative image(s) correctly marked
Info::
146 image(s) with good alt text
386 images 146 good alt text 240 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 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="search">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-inputsearchSzukaj:for/id
inputsearch(Wpisz miejscowość)placeholder only

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

<input type="search">

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
Favicon & Branding
12 icon(s) detected
PASS
12 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Interia
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Interia ✓192×192 icon ✓512×512 icon ✓Start URL /?utm_source=interia_homescreen&utm_medium=skrot_homescreen&utm_campaign=skrot_homescreen&iwa_source=homescreen ✓Display Mode standalone ✓
Name Interia Display Mode standalone Theme Color #fff Background Color #fff Icons 8 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback