I hear you. We spent a lot of time making the tools accessible and we learned a lot during that period. Now we're ready to go further and start adding more accessibility tools in the nearer future. Currently I am conducting user testing on validating some of these and see how they make the most sense to roll out. A few of the things brewing are high contrast simulation, source order viewer for CSS Grids and a few more. The great thing is that everyone in the Chromium project is on board with that and there are quite a few things brewing. Mathias Bynens of the Chrome team for example lately added simulation for different colour deficits to the rendering pane and it was great to see that.
Specifically what are you missing? What would be a game changer in that space to you?
It's say a real game changer would be a "screen reader emulator", meaning emulating how a screen reader would read a page, be it Voice Over, NVDA, Talk Back... But that would be nearly impossible, I think, because it would basically mean implement those screen readers in the DevTools 😅
Other things that I'd like to see:
emulate other accessibility-related media queries, like prefers-reduced-motion or forced-colors (after it will be implemented, that is!);
a fully fledged and reactive accessibility tree explorer (meaning that changes in the DOM are reflected in the tree... and viceversa): the current one is a bit disappointing;
in the Elements panel, decorator badges near the Elements highlighting accessibility problems (like low contrasts, missing labels, insufficient distance between interactive areas, etc.), maybe linking to WCAG references and best practice to solve the issue;
an emulator for various types of dyslexia? Kind of hard to imagine, though...
prefers-reduced-motion is already in the Developer tools as part of the rendering pane. I've documented the feature here and forced-colors is what is currently in user testing - you should be able to play with it soon in Edge Canary.
Interesting ideas about the elements panel, we've been pondering things like that. For now, you can also check the experiment that shows webhint results in the issues panel. As you may know webhint is a linter of web content that flags up all kind of accessibility and compatibility problems.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I hear you. We spent a lot of time making the tools accessible and we learned a lot during that period. Now we're ready to go further and start adding more accessibility tools in the nearer future. Currently I am conducting user testing on validating some of these and see how they make the most sense to roll out. A few of the things brewing are high contrast simulation, source order viewer for CSS Grids and a few more. The great thing is that everyone in the Chromium project is on board with that and there are quite a few things brewing. Mathias Bynens of the Chrome team for example lately added simulation for different colour deficits to the rendering pane and it was great to see that.
Specifically what are you missing? What would be a game changer in that space to you?
Thank you for your answer!
It's say a real game changer would be a "screen reader emulator", meaning emulating how a screen reader would read a page, be it Voice Over, NVDA, Talk Back... But that would be nearly impossible, I think, because it would basically mean implement those screen readers in the DevTools 😅
Other things that I'd like to see:
prefers-reduced-motionorforced-colors(after it will be implemented, that is!);Keep up with the great job!
prefers-reduced-motionis already in the Developer tools as part of therendering pane. I've documented the feature here andforced-colorsis what is currently in user testing - you should be able to play with it soon in Edge Canary.Interesting ideas about the elements panel, we've been pondering things like that. For now, you can also check the experiment that shows webhint results in the issues panel. As you may know webhint is a linter of web content that flags up all kind of accessibility and compatibility problems.