Accessibility statement.

What this aims at

The target is WCAG 2.2 level AA — the same standard public institutions are held to. In practice that means a few concrete things: content readable at low contrast sensitivity, operable with a keyboard alone, enlargeable without losing text, and understandable without relying on colour or movement.

I do not claim full conformance, because that would not be honest without an external audit. I claim what has been checked and fixed, and I list what has not.

What is in place

• The page structure is marked up: header, navigation, main content and footer are separate landmarks a screen reader can jump between.
• The first element on every page is a skip link that takes you past the menu.
• Everything is operable by keyboard, and the focused element has a clear outline rather than the browser's barely-visible default.
• Text contrast is at least 4.5:1 in both the light and dark theme. The light palette was darkened to get there.
• Light and dark themes; the site follows your system setting and lets you override it.
• When your system asks for reduced motion, movement is switched off — including the animation on the homepage photograph.
• Images carry alternative text, and purely decorative images are deliberately marked empty so a screen reader skips them.
• Touch targets are at least 24px, including the small footer links.
• The page language is declared in the markup, separately for the Polish and English versions.
• Text enlarges to 200% and the window narrows to 320px without losing content or scrolling sideways.
• There is no flashing content, no autoplaying audio, and no carousel that moves on its own.
• There is no contact form — contact is by email and phone, so there are no fields, labels or error messages to negotiate.

How this is checked

Automatically: with axe-core, run across every page type (home, services, guides, work, contact, documents, local page) in both themes, at desktop and phone widths.

Manually: a keyboard-only pass, a check that focus is visible, text enlarged to 200%, and the window narrowed to 320px.

This is a self-assessment, not an external audit. Automated tools catch some problems, not all of them — which is why a report from you is worth more than another test run.

What still falls short

• The 404 page renders in a simplified framework shell: no menu, no footer and no declared language. If you land on an address that does not exist, return via the logo or szramuk.pl. I am working on it.
• Alternative text on project screenshots is limited to the project name. It does not describe the layout in the image — the project itself is described in the text beside it.
• There has been no external audit and no testing with people who actually use screen readers. That is the difference between “tested with a tool” and “checked in practice”.
• The admin area at /admin is out of scope for this statement — it is not part of the public site and one person uses it.

Report a problem

If something cannot be reached or cannot be read, tell me: web@szramuk.pl or +48 518 102 029. I usually reply within one business day.

Helpful but not required: the address of the page, what you are using (browser, screen reader, magnification) and what should have happened. If a fix will take longer, I will get you the information another way — by email or over the phone — so you are not waiting on a deployment.

Legal note

I am not a public-sector body under the Polish Act of 4 April 2019 on the digital accessibility of public bodies' websites and mobile applications, so this statement is voluntary and is not a declaration under that act.

I publish it because accessibility is part of what I consider a properly built website — and because the sites I build for clients are checked the same way.