Swift A11y

Scan a page for accessibility problems and run fifteen testing tools, right beside it. Nothing leaves your browser.

Swift A11y finds accessibility problems on the page you are looking at, and gives you the fifteen tools to check what a scan cannot. Press the toolbar button (or Alt+Shift+S) and Swift A11y opens right beside the page. SCAN THIS PAGE One button runs three accessibility engines on the page as you see it: signed in, mid-flow, menu open. axe-core, IBM Equal Access and Siteimprove Alfa are packaged inside the extension and run in your browser. When two or three engines flag the same element for the same WCAG criterion, they become one finding, so you read each problem once. - Open results: every issue grouped by where it is on the page, with its severity, WCAG criterion, selector, markup and a screenshot of the element. - Copy as ticket: one issue as Markdown, ready to paste into a tracker or chat. - Download results: every issue as a CSV file. - Your newest 50 scans stay in this browser, under Recent scans. THEN TEST BY HAND After a scan, each tool says whether you still need it for this page: "3 found" (the scan found issues it covers, one click shows just those), "Optional", or "By hand" (a scan cannot zoom, press Tab or listen). Fifteen tools become a short list. THE FIFTEEN TOOLS - Page Basics: title, language, blocked zoom, timed refresh, frames, autoplaying media, duplicated ids. - Contrast: every piece of text with its contrast ratio, worst first. - Reflow: at a narrow width or 400 percent zoom, what scrolls sideways, sticks out or is cut off. - Text Spacing: applies the required text spacing in one click, then lists what broke. - Target Size: controls too small to tap, with the spacing exception worked out. - Headings: the heading outline a screen reader announces, boxed on the page. - Landmarks: the page's regions, nested as the page nests them, and content outside all of them. - Read Aloud Order: the page in the order a screen reader reads it, numbered on the page. - Tables: every table with its name, size and what looks wrong. - Forms: every field with its label, required state, description and error. - Links and Buttons: every link and button with its role, name and state. - Same Component?: controls that look alike but are named or built differently. - Images: every image with a thumbnail and what is announced for it. - Focus Trail: follows keyboard focus and names each stop. - Announcements: a running log of what a screen reader is told while you use the page. Each tool reports what a screen reader would announce, not just what the markup says. Problems are things that are wrong; judgement calls are marked "to check". Running a tool again turns it off and leaves the page as it was. NOTHING LEAVES YOUR BROWSER The extension makes no network requests. It has no server, no account, no analytics. Scans are kept in the extension's own storage in your browser and are deleted when you remove it. The tools never show, store or copy what you typed in a form field. PERMISSIONS, AND WHY - activeTab: work on the tab you are looking at, only after you press the button. No access to other tabs or sites. - scripting: put the scan engines or the chosen tool, files inside the extension, into that tab. - sidePanel: show the panel beside the page. No host permissions, no script that runs on every page, nothing downloaded or run from the internet. LIMITS Browsers do not let extensions run on their own pages, the extension stores or the built-in PDF viewer; the panel says so. For local files, turn on "Allow access to file URLs" in the extension's settings. Open source under the MIT licence. For IT teams, a one-page note lists every permission and how to check it: https://swifta11y.com/for-it-teams