Explore >> Select a destination
|
You are here 
|
marcysutton.com | ||
| | | | |
dht.is
|
|
| | | | | WebAIM has been conducting surveys on web accessibility for years (see WebAIM projects), including a survey of Screen Reader users since 2009. The latest survey was published in September 2019. I encourage everyone to read through their results and analysis as it won't take long, but here are the four key insights I found. Note: Numbers rounded to the nearest full number. #1 - The technology landscape for screen readers is fragmented, but usage is not. A predominant number of users rely only on a handful of platforms and technologies. More is always better when it comes to testing, but given the scarcity of time, talent, and treasure, I would expect the best ROI by prioritizing the following list: | |
| | | | |
scribnasium.com
|
|
| | | | | By Riley Major, 2018-04-26. I attended the JavaScriptMN Meetup last night (video). Due perhaps to the larger attendance, it was on the 9th floor of the Olson building rather than the more common 6th floor meeting space. After plugs for sponsors Twilio, TrackJS, and FrontEnd Masters, Kelly Heikkil | |
| | | | |
iainbean.com
|
|
| | | | | Automated tools like Lighthouse are great, but if you want to really understand accessibility, you'll need to get your hands dirty. | |
| | | | |
a11y-style-guide.com
|
|
| | | Style guide and pattern library promoting accessible components and WCAG compliance criteria | ||
