Accessibility Statement

1. Commitment

Tools for Stupid Wizards is meant to be usable by everyone, including people who browse with a screen reader, a keyboard only, voice control, a screen magnifier, or a browser zoomed well past 100%. Accessibility is treated as part of whether a tool works at all, not as an extra pass at the end.

2. The standard this site aims for

The target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the W3C. That is the benchmark United States courts and the Department of Justice look to when judging whether a website is accessible under the Americans with Disabilities Act, and it is also the reference standard behind Section 508 and the European EN 301 549. This site aims to conform to it, and the sections below describe how far that has actually got.

3. What is in place

These are specific, checkable things rather than a general promise:

• Keyboard access. Every tool can be operated with Tab, Shift+Tab, Enter, Space, and the arrow keys. Nothing traps keyboard focus.
• Visible focus. Whatever you are focused on carries a high contrast purple outline, so you can always see where you are.
• Skip link. A "Skip to main content" link is the first thing focused on every page, so you do not have to tab past the header each time.
• Labelled controls. Every input, textarea, slider, colour picker, and checkbox has a programmatic name. Placeholder text is never the only label.
• Named previews. The canvas each tool draws into is exposed as an image with a description, rather than as an unlabelled blank to a screen reader.
• Landmarks and headings. Each page has header, main, and footer landmarks and a single H1, with headings in order, so screen reader users can jump around.
• Reduced motion. The drifting pixel stars, the bobbing wizard, the cursor companion, and the panel animations all stop if your operating system is set to reduce motion.
• Text and zoom. Layouts reflow to 400% zoom and down to a 320 pixel wide viewport without horizontal scrolling or lost content.
• Contrast. Body text and interface text are checked against the 4.5:1 minimum, and large text and interface borders against 3:1.
• Target size. Interactive controls are at least 24 by 24 CSS pixels, which is the WCAG 2.2 minimum.
• High contrast mode. Borders and focus rings are preserved when Windows High Contrast or forced colours is switched on.
• No time limits, no flashing. Nothing on the site expires, auto-advances, or flashes more than three times a second.

4. Known limitations

Being straight about the gaps, because a statement that claims perfection is worth nothing:

• The tools produce images. The output of every generator is a picture, and a picture is inherently visual. The controls that build it are accessible and the preview is described, but the finished PNG cannot be read out. If you download one to use elsewhere, add your own alt text wherever you post it.
• Pixel fonts. The display typeface is a pixel font, chosen for the look of the site. It is used for headings, labels, and buttons but never for long body copy, and it can be resized and zoomed like any other text. If it is hard for you to read, tell me and I will look at the balance again.
• Fine positioning. A few tools let you nudge elements around the canvas. Those controls work by keyboard, but they are still easier with a pointer, and that is an area I want to improve.
• Third-party pages. The Buy Me a Coffee page and any other site linked from here are outside my control and are governed by their own accessibility practices.

This site has been assessed by the person who develops it, using keyboard testing, screen reader spot checks, and automated tooling. It has not had a formal third-party audit.

5. Why there is no accessibility overlay

This site deliberately does not use an accessibility overlay, toolbar, or widget, the kind that drops a floating accessibility button onto a page and promises instant compliance. Those products sit on top of the page without fixing the underlying markup that assistive technology actually reads, many screen reader users report that they interfere with the software they already run, and installing one has not stopped businesses from being sued. Fixing the HTML directly is slower and it is the thing that actually works.

6. Tell me about a barrier

If any part of this site stops you doing something, I want to hear about it, and you do not need to explain why or prove anything.

• Use the contact form, which is keyboard and screen reader operable.
• If the form itself is the problem, leave a message on the Buy Me a Coffee page, which does not require the form.

Tell me the page you were on, what you were trying to do, and what got in the way. Include your browser and any assistive technology if you know it, though it is fine if you do not. I aim to acknowledge reports within 5 business days and to give you either the fix or a timeline for it. Reports are handled by the person who builds and runs the site.

If you need something on this site in a different format, ask through the same channels and I will work out an alternative with you.

7. How this is kept up

Accessibility is checked when a new tool is added and when an existing one changes, and the whole site is reviewed periodically. This statement is updated when the site changes or when a review turns something up, and the date at the top reflects the last review.

8. If you are not satisfied

If you report a barrier and are not happy with the response, you can raise it with the U.S. Department of Justice Civil Rights Division, which handles complaints under the Americans with Disabilities Act. I would rather hear from you first and fix it, but that route is open to you either way.