Kevin Marks
Well, details is in chrome and safari so you have android and iOS covered. The fallback is to show all the expanded content, which is more ok on IE and Firefox as they’re on big screens mainly
Here’s a bit of convergent evolution: Hugo’s script is similar to what I wrote about recently.
He also raises a point that Kevin mentioned:
I would like to investigate on the
details
andsummary
elements as they are basically a native implementation for content toggles.
For some reason details
never got much browser love, even though it’s clearly paving a well-trodden cowpath.
Well, details is in chrome and safari so you have android and iOS covered. The fallback is to show all the expanded content, which is more ok on IE and Firefox as they’re on big screens mainly
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.
Manu’s book is available to pre-order now. I’ve had a sneak peek and I highly recommend it!
You’ll learn how to build common patterns written accessibly in HTML, CSS, and JavaScript. You’ll also start to understand how good and bad practices affect people, especially those with disabilities.
Another handy accessibility testing tool that can be used as a bookmarklet.
This is good advice:
Write alternative text as if you’re describing the image to a friend.
I just attended this talk from Heydon at axe-con and it was great! Of course it was highly amusing, but he also makes a profound and fundamental point about how we should be going about working on the web.
Business, sustainability, and inclusivity.
Separate your concerns.
Aiming for originality and creativity in alt text.
Adding `alt` text to uploaded images.
Making the moral argument.