Accessibility statement.

The standard I aim at

Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. I believe this site substantially meets it, with the specific exceptions listed further down. That belief comes from my own testing, not from an independent audit, and I would rather say so than imply a certificate I do not have.

What has actually been done

• Real document structure. One h1 per page and headings that descend without skipping a level, so a screen-reader user can navigate by heading rather than by scrolling.
• Keyboard operable throughout. Every link, button, theme toggle and FAQ accordion works without a mouse, in a sensible order, with no keyboard traps.
• Visible focus. A two-pixel focus ring with an offset, on both themes — not the outline removed for tidiness, which is the most common accessibility failure on designed sites.
• A skip link to main content, as the first focusable element on every page.
• Contrast checked against AA in both the night and day themes, rather than eyeballed.
• Descriptive alt text on content images, and decorative artwork — the cursor, the background field, the arrow glyphs beside link text — marked so assistive technology skips it rather than reading it aloud.
• Reduced motion respected. If your system asks for less movement, the scroll effects, parallax and 3D are cut back. The walkthrough also carries its own motion switch.
• It works without JavaScript. Every page renders and reads as a document if scripts fail or are blocked.
• Text resizes. The type scale is relative, so browser zoom and larger default font sizes work rather than breaking the layout.
• No third-party embeds to inherit somebody else’s accessibility problems from.

Where it falls short

Known and honest, rather than discovered by you:

• The custom pointer. On a desktop with a mouse, the system cursor is hidden and replaced by a drawn mark. It tracks accurately, but if you rely on a large or high-contrast system cursor, this overrides it. It is disabled entirely on touch devices and when reduced motion is requested — but it should also respect a forced-colours preference, and it does not yet.
• The walkthrough is a demonstration. That page is deliberately an experience, with WebGL and scroll-driven motion. It degrades to a readable document if 3D fails or reduced motion is set, but it is the least conventional page here. Everything it demonstrates is described in plain text on the services pages.
• The home page is a scroll sequence. It reveals panels as you move through it. Without JavaScript it renders as a plain document, but it is a longer and more effortful read than the document pages.
• Not independently audited. No third party has verified any of the above.

If something blocks you

Tell me and I will fix it, and I would rather hear about it than not. Email info@littlemandev.com or call or message +960 797 5770. Say what page it was, what you were trying to do, and what you use to browse if you are willing to.

I will acknowledge within a few working days. If something is a genuine barrier rather than a rough edge, it gets fixed ahead of whatever else I had planned. If you need information from a page you cannot use, ask and I will send it in a format that works for you.

Why this page exists

Accessibility is listed as part of every build I quote, and institutional clients are entitled to ask whether that is real. A statement that only listed successes would not answer the question, which is why the shortcomings are on the same page.