zdashamber: painting - a frog wearing a bandanna (Default)
Madeline the Edifying ([personal profile] zdashamber) wrote in [community profile] accessibility_fail2015-12-29 08:39 am
Entry tags:

Web Accessibility slides

I'm going to give a five-minute presentation tomorrow evening on basic web accessibility (what to do re: designing and developing a website)... Here are the slides: https://slides.com/madelinebernard/webaccessibility

I'm interested in taking feedback on it, if you have any!
adrian_turtle: (Default)

[personal profile] adrian_turtle 2015-12-30 04:02 am (UTC)(link)
Who is your audience? Are you speaking to developers who might otherwise think accessibility doesn't matter? Or developers who think accessibility might be a nice feature if it wasn't so hard to implement? Or developers who are really careful about being accessible to one users with a particular disability and need to understand that isn't "universal" design? Or frustrated users with disabilities (like us) who use websites but may or may not design them? Or managers who set specifications for company websites?

The jargon page doesn't seem to add much, for such a short presentation. Are you defining the terms because they are used in the references you point people to, on the last slide? If they're defined on those websites, you don't need to define them before sending people there.

I like the graphic about what causes the most accessibility problems. I'm not a web designer, but I'd find it helpful if there was a more explicit connection between that and the other information. Doing this html thingee avoids that problem people complain about. Maybe it's all obvious to people who work in the field. Some of it is stuff I can make sense of, but it would be a lot clearer if it were organized as "this is what's a problem for screen readers" and "that's a problem for keyboard accessibility" and "this other thing is a problem for photosensitivity."