We want people to fix the issues we find in an accessibility audit. That gets harder when the finding is in a spreadsheet and the issue is somewhere on the website.
Our manual audits often include 80 to 100 findings. We include the page, component, impact and suggested fix, but a team still has to move between the spreadsheet and website to find the exact element. We built a bookmarklet to make that part easier.
Why finding the issue can take time
Spreadsheets are useful because they hold a lot of information. They also separate each finding from the page where it happens.
Screenshots help, but they do not always show enough context. A page may have changed, the same component may appear more than once, or someone may return to the audit months later.
Putting findings back on the website
The bookmarklet is a saved browser link that opens the audit beside the live page. It adds numbered, colour-coded markers without changing the website. Your team runs it while reviewing the audit.
The panel groups findings with markers, page-level findings and findings it cannot locate on the current page. The last group helps when the website has changed since testing.
What each finding includes
Select a marker or finding to see the audit details:
- Finding ID and title, WCAG success criterion and level or expert observation, impact level, priority, and test method.
- Affected pages and component, disabilities affected, and teams for the fix.
- Description, steps to recreate, why it matters, suggested fixes, code examples, resources, and screenshots when available.
Moving through the audit
On each page, you can review the findings that apply there or select a marker to open one. Previous finding and Next finding move through the full audit. Findings for the same component stay together.
For repeated patterns, one marker shows the audited example. If a finding has a matching rule, the viewer can also outline similar elements as suggestions to review. These are kept separate from the verified findings.
Why we made it
The spreadsheet remains the audit record. The bookmarklet uses the same information but puts it back on the page, so a team can understand the issue before starting the fix.
We're starting to include it with audits where it helps.