What we aim for
We aim for PowerLens to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We haven’t had it independently audited yet, so this statement is our own assessment.
What works today
- Keyboard: the workspace’s tools are buttons and menus you can reach with the keyboard, and the main actions have shortcuts (see keyboard shortcuts).
- Screen readers: buttons have names, the toolbar and menus use the matching roles, and the change counter and comparison results are announced as they change.
- Not colour alone: changes are marked with a bar and a position as well as colour, and the list of changes gives each change’s words and counts in text.
- Light, dark and low contrast: PowerLens follows your system theme or the one you pick, and a low contrast mode drops borders and lines.
- Zoom and small screens: the pages reflow on narrow screens and at high zoom; on a phone the workspace shows one column.
- Motion: the workspace and the guides respect your system’s reduce motion setting.
Known limitations
- Picture comparisons are visual. The changed areas are counted and can be stepped through, but what changed inside a picture isn’t described in words.
- Audio comparisons show the recordings as pictures; the transcript is the best way to follow them with a screen reader.
- The replicas in the guides are simplified pictures of the workspace. The step text next to them says the same thing in words.
- How accessible an exported PDF or document is depends partly on the original document’s structure.
Feedback
If something in PowerLens is hard to use with your setup, please tell us through the project’s issue tracker, with the page, your browser and any assistive technology you use. We read every report and try to fix problems quickly.