Home › Accessibility
Accessibility statement
Last reviewed: 1 February 2026. Target: WCAG 2.2, level AA.
An address filter is not much use if the thing explaining it cannot be read. These commitments apply to the site and to the documents the service produces.
1. What has been done
- Semantic landmarks, one
h1per page and a heading order that does not skip. - Every interactive control reachable and operable by keyboard, with a visible focus ring that is not the browser default alone.
- A skip link as the first item in the tab order.
- Text and background combinations checked against 4.5:1 for body copy and 3:1 for large display type. The palette was chosen with that in mind rather than afterwards.
- Alt text on every meaningful graphic,
aria-hiddenon purely decorative ones, and each illustration described in a sentence rather than labelled "image". - Form fields with real labels — placeholders never stand in for one — plus inline error text tied to the field.
- Layout tested down to 320 pixels wide and at 200% zoom, reflowing without horizontal scrolling.
- Motion kept short and suppressed under
prefers-reduced-motion. - No content that exists only on hover, and no carousel.
2. Known gaps
Being specific is more useful than a claim of full compliance, so:
- Illustrations are SVG art, not photographs. Their descriptions are written by the operator, and a more natural description would be better in places.
- The accessible name of the mobile menu button is "Open menu" and is not updated to "Close menu" while open; it is announced as an expanded state instead.
- Alias examples are shown as monospaced strings that a screen reader may read character by character.
- The cookie banner sits over page content rather than moving it, so the bottom of a page can be briefly obscured on very short viewports.
- The checkout is a demonstration and its confirmation appears by script; after a real processor is wired in, the same screen needs re-testing with a screen reader.
3. The service itself
The audit document is delivered as plain, structured text with headings rather than as a PDF of screenshots. It is written to be read aloud. On request it can be sent as a tagged PDF, as a large-print version, or dictated in a short call.
The diagnostic can run entirely by e-mail. A voice call is offered, not required. Where a task needs a change inside an account, the instructions are numbered, one action per line.
4. Reporting a barrier
Write to hello@lasikiewicz.com with "Accessibility" in the subject line, or use the contact form. Say where it happened and what you expected. A screenshot helps but is not required.
- Acknowledged within one business day.
- A fix or a dated plan within ten business days.
- Where a site barrier blocks a purchase, the trial can be opened by e-mail instead.
5. Standards and review
WCAG 2.2 AA is the target, which also satisfies the substance of the AODA information and communication requirements for an organisation of this size. The site is re-tested with keyboard only, at 200% zoom, and with VoiceOver after any structural change. This statement is reviewed each February, and review notes are kept.
It is an honest assessment rather than an audit badge: no third-party certification has been bought.
See also the privacy policy and terms.