/explore
|
You are here 
|
cssence.com | ||
| | | | |
sayansivakumaran.com
Looking at some minimal codepens that demonstrate how browsers distinguish between "real" and "fake" tables for accessibility. |
|
| | | | | ||
| | | | |
www.trevorlasn.com
Detect CSS feature support and provide smart fallbacks with @supports |
|
| | | | | ||
| | | | |
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: |
|
| | | | | ||
| | | | |
blog.pope.tech
Learn how to do screen reader, keyboard, and zoom manual testing. |
|
| | | |||
