4 ms·
I always try my best to make things as accessible as possible by following accessibility standards and semantic elements the best that I can. It is more difficu
by loh 7y ago
I always try my best to make things as accessible as possible by following accessibility standards and semantic elements the best that I can. It is more difficult than one would think though, especially without fully understanding the perspectives of those who need the bit of extra consideration. I'm sure I fall short on many things which would help these people use my software more effectively, but this article provided some interesting insights.
I know there are some checklists and some tools out there which help verify certain accessibility standards (for web applications at least), but does anyone know of a better way to test/verify accessibility without actually getting e.g. someone blind to try things out and provide feedback?
- Ndymium 7y agoPersonally when I write webpages, I turn on VoiceOver on my Mac and run through the page's features. Just doing that usually points me to a few pain points that I can alleviate with ARIA and different HTML structuring choices. For hard mode and possibly better results, close your eyes and only rely on the screen reader.
- loh 7y agoThat makes sense. Actually trying out the accessibility features myself sounds... interesting.
- digitalengineer 7y agoA lot of it is manual, but there is this handy chrome tool to catch the obvious problems: https://chrome.google.com/webstore/detail/wave-evaluation-tool/jbbplnpkjmmeebjpijfedlgcdilocofh https://chrome.google.com/webstore/detail/wave-evaluation-to...