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 4 REVIEW 6 FIX

Landmark Structure

Action

8 landmarks

FIX

8 landmarks

No <main> landmark found

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

8 <nav> landmark(s) found

8 of 8 <nav> elements are unlabeled

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

No banner (header) landmark

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

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

Link & Button Quality

Action

11 issue(s) across 96 links and 8 buttons

FIX

11 issue(s) across 96 links and 8 buttons

3 link(s) with no accessible text

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

Got: /; /commissioning; /

1 link(s) open in new tab without warning

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

Got: https://plutowski.pl

8 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.ww_submenu_toggle (#179 on page); button.ww_submenu_toggle (#253 on page); button.pswp__button (#1373 on page); button.pswp__button (#1374 on page); button.pswp__button (#1375 on page); button.pswp__button (#1376 on page); button.pswp__button (#1383 on page); button.pswp__button (#1384 on page)

92 link(s) with descriptive text

96 links

3 empty

0 generic text

1 new tab

8 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
/commissioning	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
https://plutowski.pl	Plutowski.pl	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

92 links and buttons have descriptive text

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

/; /commissioning; /

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://plutowski.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

Icon-only buttons need an aria-label so screen readers can announce them.

button.ww_submenu_toggle (#179 on page); button.ww_submenu_toggle (#253 on page); button.pswp__button (#1373 on page); button.pswp__button (#1374 on page); button.pswp__button (#1375 on page); button.pswp__button (#1376 on page); button.pswp__button (#1383 on page); button.pswp__button (#1384 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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

8 navigation landmark(s) detected

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

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.

Tap Target Adequacy

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

REVIEW

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

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

Favicon & Branding

Action

11 icon(s) detected

REVIEW

11 icon(s) detected

favicon.ico present at site root

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

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 2 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title ATEX Flow Service \| …	20.29:1	4.5:1	#000000	#FBFBFB	Pass
span Write a message >>	20.29:1	4.5:1	#000000	#FBFBFB	Pass
span Request Service >>	12.79:1	4.5:1	#000000	#C9CACB	Pass
span Home	5.76:1	4.5:1	#000000	#80878C	Pass
span About Us	8.94:1	4.5:1	#000000	#A2AAB3	Pass
span Commissioning	8.80:1	4.5:1	#000000	#A0A9B1	Pass
span Installation	6.04:1	4.5:1	#000000	#7F8B96	Pass
span Service & Maintenanc…	7.39:1	4.5:1	#000000	#949AA0	Pass
span Water Pomp	20.47:1	4.5:1	#000000	#FCFCFC	Pass
span Fuel and Chemical In…	20.47:1	4.5:1	#000000	#FCFCFC	Pass
span Food and Pharmaceuti…	20.47:1	4.5:1	#000000	#FCFCFC	Pass
span Hygienic Valve Servi…	20.47:1	4.5:1	#000000	#FCFCFC	Pass
span Service in ATEX Zone	20.47:1	4.5:1	#000000	#FCFCFC	Pass
span Decommissioning & Di…	20.47:1	4.5:1	#000000	#FCFCFC	Pass
span Service Warranty	20.47:1	4.5:1	#000000	#FCFCFC	Pass
span Terms of Service	20.47:1	4.5:1	#000000	#FCFCFC	Pass
span Contact	20.47:1	4.5:1	#000000	#FCFCFC	Pass
span Home	20.47:1	4.5:1	#000000	#FCFCFC	Pass
span About Us	20.47:1	4.5:1	#000000	#FCFCFC	Pass
span Commissioning	20.47:1	4.5:1	#000000	#FCFCFC	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.

Lighthouse Accessibility Audits

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

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.gv_gallery > div.gv_panelWrap > div.gv_panel > a `div.gv_gallery > div.gv_panelWrap > div.gv_panel > a`
div#element_128 > div#element_128_content > div.ww_image_wrapper > a `div#element_128 > div#element_128_content > div.ww_image_wrapper > 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
Go to the form >> `div.ww_text_wrapper > p#element_158_text_3 > span > a.custom_link`

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

●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-hidden="true"]` elements do not contain focusable descendents

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

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

●Identical links have the same purpose.

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

○Buttons have an accessible name

○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

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

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

A+

Heading Hierarchy

46 headings

PASS

46 headings

Single H1 present

H3 CUSTOM SERVICE
H3 AGREEMENTS
H3 PRODUCTION DOWNTIME
H3 DISCLAIMER
H3 8-MONTH POST-SERVICE WARRANTY
H3 UNSUCCESSFUL / ABORTED
H3 SERVICE VISITS
H3 If service execution becomes impossible due to site factors or conditions beyond the service provider’s control, we will strive to find an immediate workaround. However, site call-out costs may stil
H3 FORMAL SERVICE ORDERS
H3 TRANSPARENT SERVICE
H3 PRICING
H3 EQUIPMENT CLEANLINESS
H3 & DECONTAMINATION
H3 WORK AREA PREPARATION
H3 SERVICE REQUEST
H3 DISPLACEMENT PUMPS
H3 CENTRIFUGAL PUMPS
H3 OTHER EQUIPMENT
H2 What industrial equipment do we support?
H3 Verification and start-up of fluid handling equipment strictly aligned with design, technical standards, and safety compliance.
H3 Expert assembly and mounting of process pumps, hygienic valves, and specialized fluid systems.
H4 Compliant Decommissioning & Asset Disposal
H3 Disassembly, recycling and
H3 the proper decommissioning of machinery, pumps, valves, and other technical equipment.
H4 Routine Servicing & Diagnostic Inspections
H3 Full-scope diagnostic, preventive maintenance, and emergency repair services backed by an 8-month warranty.
H1 Industrial Pump Repair, Maintenance & Installation
H2 COMMISSIONING
H3 System Start-Up
H3 & Commissioning
H4 Professional verification and seamless start-up for process pumps and fluid handling systems
H2 INSTALLATION
H3 Precision Equipment
H3 Installation
H4 Expert mounting and assembly of industrial pumps, hygienic valves, and process lines
H2 SERVICE & MAINTENANCE
H3 Comprehensive
H3 Service & Repairs
H4 Full-scope diagnostics, preventive maintenance, and rapid emergency repairs for maximum uptime
H2 DECOMMISSIONING & DISPOSAL
H3 Compliant Asset Decommissioning
H4 Safe disassembly, eco-friendly recycling, and certified disposal of industrial machinery
H2 COMMISSIONING
H3 System Start-Up
H3 & Commissioning
H4 Professional verification and seamless start-up for process pumps and fluid handling systems

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

2 heading(s) are over 120 characters -- likely a misformatted paragraph

Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 198 chars - H3: 127 chars

Got: 2 >120-char heading(s)

22 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: 22 all-caps heading(s)

Alt Text Quality

1 of 29 images have issues

PASS

1 of 29 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

26 decorative image(s) correctly marked

2 image(s) with good alt text

29 images 2 good alt text 26 decorative 1 missing

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

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "pl"

PASS

Lang attribute set to "pl"

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

Got: pl

Tabindex Anti-Patterns

0 positive, 2 -1-on-focusable

PASS

0 positive, 2 -1-on-focusable

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Mobile-Readable Font Sizes

All 135 visible text node(s) render at >= 12 CSS pixels

PASS

All 135 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: ATEX Flow Service | Pumps, Hygienic Valves & Homogenizers

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name ATEX Flow Service | Pumps, Hygienic Valves & Homogenizers ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name ATEX Flow Service | Pumps, Hygienic Valves & Homogenizers Display Mode standalone Theme Color #4A4A4A Background Color #ffffff Icons 8 icon(s)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

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.

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