Accessibility Report — WCAG & EAA audit 제작자: Plainwork
Scan any page against WCAG 2.2, then export an accessibility report your client can actually read. Nothing leaves your browser.
확장 메타 데이터
스크린샷
정보
Turn an accessibility test into a document you can send.
The free tools that check a page for accessibility problems — axe, WAVE, Lighthouse — are built for developers, and they show you developer output. If a client has just asked whether their site is compliant, you cannot forward them a list of rule identifiers.
This extension runs the same class of test, then writes the result in plain English and lays it out as a report: what is wrong, who it shuts out, what to do about it, and which part of the standard it relates to. One click to save it as a PDF.
WHAT YOU GET
· A scan of any page against WCAG 2.2 level AA — the standard named by the European Accessibility Act, and the reference point in US accessibility litigation
· Every finding written in ordinary language, not rule identifiers
· A report laid out to be read by a client, not a build system
· Code locations for whoever does the fixing, which you can leave out of the client's copy
· Findings that a machine cannot settle, listed separately and honestly
WHAT IT WILL NOT TELL YOU
Automated testing finds roughly a third of accessibility problems. It reliably catches what a machine can measure — contrast, missing labels, tap target size. It cannot judge whether alt text is accurate, whether a page still makes sense read aloud in order, or whether someone can get through a checkout using only a keyboard.
So this extension will not tell you a page is compliant, and it does not sell "lawsuit protection". Tools that made those claims have been penalised for it. What it gives you is an accurate, readable starting point, with the parts a person still has to check marked as exactly that.
THREE SEPARATE LISTS, NOT ONE INFLATED NUMBER
· Findings — failures against WCAG 2.2 AA. These are the headline count.
· Also worth fixing — long-established good practice that is not, strictly, a WCAG failure. Counted separately, so the headline number stays true.
· Needs a person to check — cases the test could not settle either way.
NOTHING LEAVES YOUR BROWSER
The test runs on the page in front of you, inside your own browser. Page content, addresses and results are never transmitted. There is no server. No analytics, no tracking, no account, no email required.
The only time the extension contacts the internet at all is if you enter a licence key, and permission for that is requested at that moment — not at install.
FREE AND LICENSED
Everything above is free, including the PDF.
A licence adds your own name and your client's name to the report and removes our sign-off from the footer. That is the whole difference. No findings are withheld from the free version.
Built on axe-core, the open-source rules engine maintained by Deque Systems. Independent product; not affiliated with Deque, the W3C, or any regulator. Not legal advice.
The free tools that check a page for accessibility problems — axe, WAVE, Lighthouse — are built for developers, and they show you developer output. If a client has just asked whether their site is compliant, you cannot forward them a list of rule identifiers.
This extension runs the same class of test, then writes the result in plain English and lays it out as a report: what is wrong, who it shuts out, what to do about it, and which part of the standard it relates to. One click to save it as a PDF.
WHAT YOU GET
· A scan of any page against WCAG 2.2 level AA — the standard named by the European Accessibility Act, and the reference point in US accessibility litigation
· Every finding written in ordinary language, not rule identifiers
· A report laid out to be read by a client, not a build system
· Code locations for whoever does the fixing, which you can leave out of the client's copy
· Findings that a machine cannot settle, listed separately and honestly
WHAT IT WILL NOT TELL YOU
Automated testing finds roughly a third of accessibility problems. It reliably catches what a machine can measure — contrast, missing labels, tap target size. It cannot judge whether alt text is accurate, whether a page still makes sense read aloud in order, or whether someone can get through a checkout using only a keyboard.
So this extension will not tell you a page is compliant, and it does not sell "lawsuit protection". Tools that made those claims have been penalised for it. What it gives you is an accurate, readable starting point, with the parts a person still has to check marked as exactly that.
THREE SEPARATE LISTS, NOT ONE INFLATED NUMBER
· Findings — failures against WCAG 2.2 AA. These are the headline count.
· Also worth fixing — long-established good practice that is not, strictly, a WCAG failure. Counted separately, so the headline number stays true.
· Needs a person to check — cases the test could not settle either way.
NOTHING LEAVES YOUR BROWSER
The test runs on the page in front of you, inside your own browser. Page content, addresses and results are never transmitted. There is no server. No analytics, no tracking, no account, no email required.
The only time the extension contacts the internet at all is if you enter a licence key, and permission for that is requested at that moment — not at install.
FREE AND LICENSED
Everything above is free, including the PDF.
A licence adds your own name and your client's name to the report and removes our sign-off from the footer. That is the whole difference. No findings are withheld from the free version.
Built on axe-core, the open-source rules engine maintained by Deque Systems. Independent product; not affiliated with Deque, the W3C, or any regulator. Not legal advice.
리뷰어 0명이 0점으로 평가함
권한 및 데이터
추가 정보
- 부가 기능 링크
- 버전
- 0.1.1
- 크기
- 200.36 KB
- 최근 업데이트
- 2일 전 (2026년 9월 4일)
- 관련 카테고리
- 라이선스
- All Rights Reserved
- 개인정보처리방침
- 이 부가 기능에 대한 개인정보처리방침 읽기
- 버전 목록
- 모음집에 추가