IBM Equal Access Accessibility Checker
A web browser extension for checking accessibility issues
Total ratings
4.88
(Rating count:
16)Review summary
These summaries are automatically generated weekly using AI based on recent user reviews.
Chrome Web Store does not verify user reviews, so some user reviews may be inaccurate,
spammy, or outdated. Pros
- Highly effective for conducting accessibility scans.
- Identifies violations and provides fix suggestions.
- Convenient feature to store scans into a single file.
- User-friendly interface with straightforward guidelines.
- Works well with WCAG 2.1AA standards.
Cons
- Issues with rendering errors when scanning for WCAG 2.2AA.
- Crashes reported after running multiple scans.
- Problems generating blank HTML reports.
- Inconsistencies in Excel report data analysis.
- Not functional for some users after the May 2022 update.
Most mentioned
- Love this tool for conducting accessibility scans.
- Great tool, very precise.
- Problems with Excel reporting.
- Last update caused functionality issues.
- Different tabs for tool usage are confusing.
Upgrade to see all 13 reviews
User reviews
Recent rating average:
4.50
All time rating average:
4.88
Upgrade to see all 13 reviews
Rating filters
5 star 4 star
3 star
2 star
1 star
| Date | Author | Rating | Lang | Comment |
|---|---|---|---|---|
| 2024-02-15 |  | | en | Dustin at Sparkbox did an independent review: Conclusion - 🏆 Highly Recommend (24/28 stars) I recommend watching his cool video (17 mins) of the review. You can see the full "professional" report at https://sparkbox.com/foundry/ibm_equal_access_evaluation_tool_website_accessibility_audit_website_accessibility_checker |
| 2024-08-16 |  | | en | Very nice tool, Previously I have used for WCAG2.1AA it works very sooth and perfect result for me. but facing problem this time, for WCAG2.2AA showing rendering error when scanning, if any workaround for the same please let me know... Thank you!! |
| 2024-08-09 |  | | en | Love this tool for conducting accessibility scans. The ability to store scans into a single file is so convenient and saves a lot of time. However, I recently ran into an issue where I was running my 60th page scan when it appeared that the checker crashed and I received the equivalent of a skull and crossbones. Are there limits on how many scans can be run and saved? Are there browser settings that should be adjusted if you know you need to run a large set of scans? Is there a way to recover the file that was being built when this happens? |
| 2023-12-05 |  | | ||
| 2022-11-22 |  | | Love this tool. It's the first thing I use when evaluating a web application to see how accessible it is. It will not only identify the violations & highlight them in the DOM, but will also provide fix suggestions as well as links on where to learn more. | |
| 2022-11-22 |  | | en | Love this tool. It's the first thing I use when evaluating a web application to see how accessible it is. It will not only identify the violations & highlight them in the DOM, but will also provide fix suggestions as well as links on where to learn more. |
| 2022-05-31 |  | | With the last update in May 2022, doesn’t work form for chrome, I trying to do some scans but is impossible | |
| 2022-05-31 |  | | en | With the last update in May 2022, doesn’t work form for chrome, I trying to do some scans but is impossible |
| 2022-05-05 |  | | I can't generate report as HTML document. HTML document is blank :( | |
| 2022-03-18 |  | | Great Tool, very precise. I only have a problem regarding the excel report. With these settings (last deployment / WCAG 2.1) it often happens that the % elements without violations is lower than the % elements without violations or items to review. I would like to understand how to analyze this data. Is this a bug or does it refer to different parameters? which of the two is more reliable for my settings? Many Thanks |
Upgrade to see all 13 reviews