I guess this domain name is why our local developmemnt environments stopped working.
Anyway, it’s a web interface onto Lighthouse (note that it has the same bugs as the version of Lighthouse in Chrome). Kind of like webhint.io.
So my observation is that 80% of the subject of accessibility consists of fairly simple basics that can probably be learnt in 20% of the time available. The remaining 20% are the difficult situations, edge cases, assistive technology support gaps and corners of specialised knowledge, but these are extrapolated to 100% of the subject, giving it a bad, anxiety-inducing and difficult reputation overall.
Another handy accessibility testing tool that can be used as a bookmarklet.
This is a great succinct definition of progressive enhancement:
Progressive enhancement is a web development strategy by which we ensure that the essential content and functionality of a website is accessible to as many users as possible, while providing an improved experience using newer features for users whose devices are capable of supporting them.
Firefox as the asphyxiating canary in the coalmine of the web.
Using progressive enhancement means your users will be able to do what they need to do if any part of the stack fails.
What a terrific short guide to sensible web development!
- Start with HTML
- Using interactive elements
- Adding the extras
- Building more complex services
- Testing your service
- Do not assume users turn off CSS or JavaScript
- Case studies and related guides
It’s not just about finding the issues—it’s about finding the issues at the right time.
How I’m letting people know they can install The Session to their home screens.
Debugging an error message.
How do we let people know what the web can do?
What’s the worst that could happen?