Accessibility statement

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across the site, including the tools. We test with keyboard-only use, automated checks and screen readers, and fix problems as we find them.

What works today

• Keyboard. Every tool can be used without a mouse. The drop zones are real buttons that open your device’s file picker, so you never have to drag and drop. Settings use standard form controls with visible focus outlines.
• Before/after slider. The comparison divider is a slider: focus it and use the arrow keys (5% steps), Home and End.
• Crop, blur and watermark boxes. Focus a box and move it with the arrow keys (Shift for bigger steps); Alt with the arrow keys resizes it. The crop tool also has exact number fields, and the blur tool has an “Add area” button and a list of areas.
• Status updates. Progress such as “7 of 12 files done” and results are announced through a polite live region, no more than once every two seconds during batches.
• Not color alone. Savings, warnings and errors are shown with text and icons as well as color, and color pairs are chosen for at least 4.5:1 contrast for text in both light and dark themes.
• Motion. Animations are short and decorative. If your system asks for reduced motion, they are switched off.
• Zoom and reflow. Pages reflow from 320 px wide phones to very wide monitors and work at 200% zoom.
• QR codes. The preview has a text description of what the code contains, and the scan check results are a list read in order.

Known limits

• Image previews show the picture itself; their text alternative describes the file and its size rather than what the photo shows, because the tools can’t know that.
• Drawing a new blur area by dragging needs a pointer; keyboard users can add an area with the button and then move and resize it.
• Content in third-party ads is outside our control.

Feedback

If something doesn’t work for you, email hello@pixwrench.com with the page, what you were trying to do and the browser and assistive technology you use. We treat accessibility problems as bugs and aim to reply within five working days.

This statement was prepared on October 8, 2026 and is reviewed when tools change.