extension ExtPose

WAVE Evaluation Tool

CRX id

jbbplnpkjmmeebjpijfedlgcdilocofh-

Description from extension meta

Evaluate web accessibility within the Chrome browser.

Image from store WAVE Evaluation Tool
Description from store WAVE is a web accessibility evaluation tool developed by WebAIM.org. It provides visual feedback about the accessibility of your web content by injecting icons and indicators into your page. No automated tool can tell you if your page is accessible, but WAVE facilitates human evaluation and educates about accessibility issues. All analysis is done entirely within the Chrome browser allowing secure valuation of intranet, local, password protected, and other sensitive web pages. To run a WAVE report, simply click on the WAVE icon to the right of your browser address bar, or select "WAVE this page" from the context menu. WAVE errors align with WCAG 2.1 failures. The WAVE interface facilitates human evaluation of many other aspects of accessibility and Web Content Accessibility Guidelines and Section 508 compliance. Version 3.0.9 (July 2020) includes numerous bug fixes, improved accessibility, and improved color contrast checking including fewer false positives and expanded contrast checking for form inputs.

Latest reviews

  • (2023-03-08) Jared Reid: This does not work. I was unable to highlight anything after making sure it was enabled with permissions, and trying it in both an updated Chrome and Edge browser separately. Nothing gets highlighted or saved, even on a Google search page.
  • (2023-01-13) Teri Brooks: I added a bunch of similar extensions and none of them worked properly, or they only provided some info but required you to sign up to get the "full" experience. But this one is fantastic and provides all the details I need in an easy to understand layout. It finds stuff that other extensions missed, and it's quick and doesn't slow down the browser. Being able to toggle between showing the styles or hiding them is a nice touch. My only issue is that by using this extension, I give them permission to read my browser history. What on earth do they need that for? That's a bit of a concern.
  • (2022-10-25) Tony Langford: It's a pretty useful tool, but there are some annoyances that make it hard to work with: 1) On the details pane you can check and uncheck the type of errors/warnings to show, we are doing our first round of testing an improvements and so want to focus on just Errors/Contrast Errors. But these settings do not persist, each page it's open extension, details tab, uncheck all these warning/aria sections.... allow these settings to persist please! 2) It's static. We have a React JS UI. The page is changing as the user uses it, the extension however only looks at the page at the point the extension loads. So you have to turn it off, wait for the page to reload, make sure its back at the new state you want it, and then turn it back on.... Just takes far too long. 3) It messes up styles, things get shifted off the page which makes it difficult to see certain problems
  • (2022-08-03) Ermes Mox: Slow, old, with a lot of issues. It's time to update and improve this tool.
  • (2022-05-25) Mitchell Christensen: Great tool. Thank you for providing such a useful tool for accessibility
  • (2022-05-21) Rocky Kev: Used this to update and ensure accessibility for hundreds of sites.
  • (2022-02-09) Kim Tan: Can't seem to get it to work on the latest version of chrome :(
  • (2022-02-02) Ferran Buireu: Fácil de usar y con reportes detallados.
  • (2021-12-20) Arron D: This used to work for local html files. It no longer does? Edit: You need to enable file access in the extension settings. This is an extremely helpful tool.
  • (2021-11-23) James Kuffner: The wave results sits over part of the web page being assessed and therefore any errors on the page are hidden by the results. Desaturate page resizes the page to fit next to the wave results which is great and the normal view should do the same.
  • (2021-11-05) Ryan: Useful tool, and at an unbeatable price point of 'free'. But there's no way to output errors - even a raw txt file with error type and the line of code would be fine, not looking for anything fancy. UI is tucked off to one side, so once you have more than a handful of errors it's very easy to get lost in a sea of repetitive and small error indicators. Crashes Chrome not infrequently when making use of the Code view with styles turned on.
  • (2021-10-25) Marcelo Quintino da Silva: Not a good tool. The UI is poor and confusing. The results can sometimes overlay the page content makin impossible to find the problem. It does not refresh/reassess the page when you navigate thru the websites.
  • (2021-08-02) Freddy Jey: It's great but it misses a very important feature: The ability to simply rerun the accessiblity check without having to reload the full web app. It becomes very cumbersome to test all combinations of your app state when you have to reload the web app every time you want to rerun a test.. It would be nice if the sidebar simply had a "RECHECK" button.
  • (2020-10-27) Dario Alpern: According to https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html , an inactive button has no contrast requirement, but the tool shows a Very Low Contrast error in an inactive button in my Web site. This appears to be an error in this Chrome extension.
  • (2020-10-12) Amity Web: This is great, I found it when I was blocked from their website due to limits, I didn't know this existed Its much faster than using their website. The only issue I have, which would gain it 5 stars if this was addressed, is when you navigate to a new page or refresh the page the tool is not enabled again, you have to click the plugin icon every time, so it can be annoying. Ideally it should have an enable permanent feature so it will stay active and check pages as you navigate a site or refresh pages. That would be ideal. Thanks
  • (2020-08-03) Adam Reece: Room for improvement. Very annoying that every page that gets validated you have to deselect all of the valid aspects. When this is turned off it should remain off. -- We need to know what to fix, not what's already good.
  • (2020-02-08) Atoall web accessibility tool for billion disabled: Your domain names are 1 language, in the world of 200 languages, Apply https://Atoall.com/ on your websites big government departments are using it check https://mhrd.gov.in you can see icon of Atoall with FaceBook, Twitter, YouTube icon.
  • (2020-01-07) Rob Wise: This app has recently been updated and I have to say that it has brought massive improvements in the UX and performance of the tool. It's much more impressive than it was a year or so ago, and it has a lot more features packed in. It's important to note that genuine accessibility is not just a checkbox- making your site useful without javascript is not a trivial task, and really has to be done with a human touch. However this tool is an excellent first step in pointing out the basics. Developers note, sometimes things like debug overlays (like django/flask ones) can get warnings flagged and hidden which makes them sometimes hard to find- but there's nothing this tool can do about that- it's inspecting the entire window.
  • (2019-12-10) Darren Sweet (Sweet Life Adventure): Recently I have used many different accessibility checkers, all are useful but many are not efficient to use. Wave shows me clearly what the issues are, shows me markers visually on my own page and provides a clear description of the issue and what to do about it.
  • (2019-11-28) Remi Dijoux: bof
  • (2019-11-22) Andreas Schieferbein: As a fullstack developer, this is the first time that the topic "Accessibility and UIs (React/Spa)" comes into contact. A cover of Specs is to be considered, this Tool makes the entrance into this not quite simple topic for me clearly easier. My thanks go to the developers, very useful.
  • (2019-11-04) Andy Layman: Where did the ability to filter down to WCAG AA 2.0 go? What standard is the new redesign using as the "default"?
  • (2019-11-01) Daryl Knight: The new update is really useful. It breaks the page layout less than the old version, explains what's wrong - WHY it's important and how to fix it. Thank you.
  • (2019-10-30) Alex O'Connell: Something JUST broke the extension, we use it daily at work here, and today I went to use it and its now broken
  • (2019-10-30) Josh V: The update looks so much nicer, good job! I ran into an issue where I needed to test locally and couldn't use my normal tools, and after finding this Wave plugin I don't need to any more!
  • (2019-10-23) Luke Pennings: Clunky; and nearly always points out non-issues with very little direction on where they are originating. You would only use this if you are a QA person for basic HTML and you need to get by not knowing any code at all.
  • (2019-09-25) Colleen LeMasters: This proved to be a very handy tool for assessing web accessibility but I wish I knew to what standard it was being measured... WCAG 2.0? A? AA? If that was added, it would be extremely helpful. Bonus points if we could select the level at which we tested.
  • (2019-09-20) Felina: Is WAVE up to date with WCAG 2.1?
  • (2019-08-22) Dan Paguirigan: A lot of false positives.
  • (2019-05-10) Austin Powell: It is a powerful and useful tool for sure. It takes a little time to figure out the interface and be able to determine what it is telling you. It also slows down the browser quite a bit when it is in use. But again, it is very in depth and beneficial when testing a11y. Give it a try and see if it's abundant information is worth the learning curve and performance slowdown.
  • (2019-04-30) Jay Fortner: Gives a report but you can't do anything with the report items. You can click on stuff and maybe it'll take you to the element it's referencing but most likely not.
  • (2019-04-02) M KSHR: 幾つかの「アクセシビリティ・チェックツール」を試しましたが、最も分かりやすくエラーを表示してくれます。(テストするページの画面にエラーやその他のアイコンが表示される。そのアイコンを押すと問題箇所のHTMLが表示される。視覚的に理解しやすい) ローカル環境でテストできる(テスト環境でテストできる) HTMLの書き方をもっとシビアにチェックしてくれるともっと使いやすくなる。
  • (2019-03-26) julio cesar martinez zarate: Excelente... Gracias
  • (2019-01-12) Víctor Sagal: Excelente para evaluar accesibilidad web en línea con el cumplimiento de las pautas WCAG de la W3C, también se puede usar su versión web para el mismo cometido.
  • (2018-10-22) Amanda Calvert: This is a great tool. My only suggestion is that you give us a way to download the results. I use this tool for sites that take human interaction to navigate the site where I can't use my automated tool. I would love to be able to download the results to send to my IT team.
  • (2018-10-16) Patricia Acosta: Excelente herramienta
  • (2018-05-12) Kishan Kock: Confusing user interface, and shows some webpages as nothing more than raw HTML when trying to evaluate, even if the page follows W3 spec immaculately.
  • (2018-02-28) Andreas Poloczek: Diese Erweiterung gehört zum Standardwerkzeug eines jeden Webdevelopers oder Webdesigners. Prüft und visualisiert technische Umsetzungsfehler in Bezug auf barrierefreie Webseitengestaltung und sensibilisiert auch den in die Jahre gekommen Routineabarbeiter…
  • (2018-02-22) Angel L: Continues to work great when your site was not planned with accessibility in mind. The contrast errors are sometimes off when trying to edit in the tool, but not wrong. Tried aXe extension and it broke this tool. Stay away from aXe. Stick with Wave!!!
  • (2018-02-09) Magnus W: It would be great if it could display the webpage as it would actually by understood by a screen reader, for example removing all elements with aria-hidden="true". I can only get it to mark them, but that's not quite the same.
  • (2018-01-31) Arturo Estrada: Very helpful for checking AA compliance
  • (2017-12-06) DP Bhatt: Awesome tool.
  • (2017-11-10) Ashwin Mekala: awesome tool! used for our company website.
  • (2017-07-20) Angus Grant: Hi Having spent some time doing some research into accessibility i find this tool more confusing than helpful. Firstly this tool appears not to cater for dynamically applied Javascript changes which is an important aspect of most sites that exist out there these days... (unless I am missing something) Secondly it appears to complain about links that contain no text but, already have a title attribute with a text description. In my tests with screen readers they where able to read the title attribute so why is is marking it as an important error that a link has no text when it has a title attribute? ie what is wrong with this: <a href="https://twitter.com/WeAreIngenta" title="Link to the sites Twitter feed"><i class="fa fa-twitter fa-lg pull-right"></i></a>
  • (2017-07-03) Keitel Jovin: I really like this one the first minute I use it. I'm improving my website SEO after I evaluate it from online evaluators. But the problem is I wanted to evaluate the progress I'm making at Development environment. So this tool is perfect for that. I would give 5/5 +1 (bonus)!
  • (2017-03-23) Jennifer Little: I find this tool amazing for quickly accessing the quality and accessibility of my websites. It's easy to make sure inputs are correctly labelled, images have alt text, and headings are ordered logically. Good HTML structure benefits everyone!

Statistics

Installs
600,000 history
Category
Rating
4.1197 (142 votes)
Last update / version
2024-09-20 / 3.2.7.2
Listing languages
en-US

Links