Accessibility statement.

What this aims at

The target is WCAG 2.2 level AA. 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.
• In the checked views, the keyboard reaches the main content, opens and closes the menu, and operates questions, checklists and form fields. The focused control has a visible outline.
• Automated checks of the sampled views in light and dark themes found no text-contrast rule violations. This does not replace readability testing with people who have low vision.
• Light and dark themes; the site opens in light mode by default. You can change it with the theme button, and the choice is remembered in this browser.
• The system’s reduced-motion preference disables motion effects. Homepage images do not rotate automatically on arrival: you can select one or explicitly start and pause rotation. These controls also work with reduced motion enabled.
• 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.
• The checked pages fit a 320px-wide window. Representative views were also checked with text doubled in size, without page-wide horizontal scrolling or clipping visible content.
• There is no flashing content, no autoplaying audio, and no carousel that moves on its own.
• The contact form has labels bound to their fields, autocomplete hints, and status messages announced to a screen reader rather than signalled by a border colour alone.

How this is checked

Review on 12 September 2026: axe-core across all 21 editorial page types in both languages (42 URLs), at 320px in the dark theme. The homepage, project index, case study, contact and 404 pages were checked too.

Representative home, service, quote, guide, project index, case study, contact and 404 views were checked at 1440px in both themes. Keyboard operation, visible focus and doubled text size were checked separately. Normal pages and the corrected skip link on the 404 page passed these automated checks without detected violations.

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

• With JavaScript enabled, the 404 page has a header, main content, footer and working skip link. In the checked production version, its content does not appear with JavaScript disabled. This affects unknown URLs and missing projects in both languages; you can go directly to the homepage or enable JavaScript.
• Alternative text on project screenshots uses short view titles. It does not convey every visual detail or transcribe all text in the capture; a written description of the project is provided alongside 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.