extension ExtPose

Accessibility Developer Tools

CRX id


Description from extension meta

(Deprecated.) Accessibility audit and element properties.

Image from store Accessibility Developer Tools
Description from store This extension is deprecated, and will be removed from the Chrome Web Store at a future date. As an alternative to the functionality provided by this extension, please check out the built-in Accessibility audits in the Lighthouse Audits panel in Chrome DevTools, the new accessibility debugging tools in the Elements panel, and/or the the aXe extension by Deque Systems.

Latest reviews

  • (2019-05-18) Дима Фомин: tt
  • (2019-03-19) Ning Cao: good
  • (2019-02-04) TSQ USA: very good
  • (2018-08-19) Arturo Sanz: This is an awesome tool. It's a pity it won't be here for long. I would have paid for this extension.
  • (2018-06-01) Ashwini Shankar H S: This is really good. I still would love to see this instead of lighthouse tool on chrome.
  • (2018-05-25) hung quan: rát thic tiện ích này
  • (2018-02-28) Andreas Poloczek: Praktisch - gehört, neben aXe und WAVE Evaluation Tool zum Standard-Repertoire von Erweiterungen für barrierfreie Webseitengestaltung.
  • (2018-02-06) Radu Bretean: Can this extension be used with a SPA? Because each time I click analyze it loads my page, which is not what I want. I want to see accessibility issues on current elements on the page, don't reload the url because is nothing on the first page, only a menu.
  • (2018-01-31) Walter Robbins: it's great
  • (2017-12-13) LT Lê Tiến: good
  • (2017-11-29) Works ok, But it should show the current standard evaluated
  • (2017-11-17) A _: When test is performed target device always turn into mobile view (Nexus 5X) even if it is removed from emulation list. How can it be changed?
  • (2017-10-12) John Alexis Guerra Gomez: Did this extension stop working with lighthouse on Chrome 61+? The audit tab has been kidnapped by lighthouse, which is ok, but only tests for mobile....
  • (2017-09-21) Biel B.: It would be great to know exactly which standard it is hoping to test for, WCAG20? When test is performed target device always turn into Nexus 5X. How can it be changed?
  • (2017-08-14) Early Weaver: I'm trying to view all may facebook games, old and new, but for some reason I can't!
  • (2017-08-10) Richard Lockwood: Very helpful tool but unfortunately not compatible with Chrome 60. Chrome 60's built-in Lighthouse tool cannot audit the current page state (and is also much much slower).
  • (2017-04-11) Gary Miller: Doesn't work. Adds an icon to the top of chrome, but it does not scan the page I'm on and there is nothing in the menus or settings to activate it. A waste of my time.
  • (2017-02-06) Jeremy S: Downloaded it, then it opened automatically to the url on my active tab. Used all of my 5 free URLS so I couldn't actually see if it worked. Totally sucker move on my part, maybe, or maybe they're just not interested in having you try it as it is really a FOR SALE app.
  • (2016-12-06) Eugenia Lemberg: The feature to export the logs - i could not find it could you implement summary report to export or save as
  • (2016-11-16) Eduardo Paixão: Ótimo :D
  • (2016-03-24) Massimiliano Bolognesi: Molto utile!
  • (2016-03-02) Arjan Noordende: This extension gives a reasonable idea of the issues on a page, but it would be great to know exactly which standard it is hoping to test for, WCAG20? Please clarify and, better yet, refer to the standard's documentation rather than your own documentation. In addition: - Warning about a tel: href in an anchor (AX_TEXT_04). It is perfectly obvious that this is a telephone number link and should not generate this warning. - Controls should have labels (AX_TEXT_01) does not take into account the Placeholder attribute, voiding the need for a label - The tests did not pick up on a checkbox that did not have any text asssociated with it - Some explanations in the documents are stubs only. But again, it's a good starting point.
  • (2015-11-24) jihey youn: 대박
  • (2015-08-02) Chaitanya Vankadaru: gud
  • (2015-07-06) Roger Somazzi: I tested a single privacy policy page offered by one of our applications and found 2 items I believe any auditor, manual or automated should catch: 1. This page was missing an <h1>, instead beginning with a single <h2>. Why does this auditor not test for basic page structure? Accessibility requires a single, and present, <h1> to assist in landmark navigation of content. 2. I saw a test for generic link text (i.e. "Click Here". Although the test does catch English translated generic strings, it does not for Spanish, which tells me there is no support outside en-us. Is this intended?
  • (2015-04-26) Сергей Лидмаэстро: ПОЛЁТ НОРМАЛЬНЫЙ!
  • (2015-03-11) Aditya Kalra: Just what you want to test accessibility and performance


60,000 history
4.1 (144 votes)
Last update / version
2018-03-04 / 3.0.1
Listing languages