accessibility-developer-tools

You are absolutely correct in assuming that having alt-text on the image inside the link is accessible. This is a known bug (https://github.com/Khan/tota11y/issues/1) that comes from upstream (https://github.com/GoogleChrome/accessibility-developer-tool...) and will hopefully be fixed soon. As for your notes on screen-reader text: you can "hide" it by not actually hiding it, but placing it off the side of the page. This will be picked up by screen-readers and will not cause any positioning issues. We use the following snippet all over Khan Academy. Bootstrap 3 uses it as well. .sr-only { border: 0; clip: rect(0,0,0,0); height: 1px; margin: -1px; overflow: hidden; padding: 0; position: absolute; width: 1px; } So I'd like to assure you that your image link is good to g

Good point – unfortunately, it doesn't look like htat's what the plugin here does: https://github.com/Khan/tota11y/blob/952427485a49bde0f498e9d... https://github.com/GoogleChrome/accessibility-developer-tool... Definitely a good feature request

To echo mkozlows, definitely check out axe-core. They recently open-sourced the tool and it's chock full of great a11y testing. At Khan Academy we use Chrome's Accessibility Developer Tools (https://github.com/GoogleChrome/accessibility-developer-tool...) as part of our testing infrastructure. A few of us also have the browser extension to do some manual testing, which is what tota11y is for. tota11y uses Accessibility Developer Tools internally.

Hey Paul, Love the work Alice & co are doing. We're big users of Accessibility Developer Tools (https://github.com/GoogleChrome/accessibility-developer-tool...) at Khan Academy both as part of our automated testing process and now as part of tota11y. Really excited to see it to make its way into DevTools proper! Been rocking the extension for a few months now.