Design Accessible Web Sites
New book on accessibility ...
"It’s good to see more books on Web accessibility being published. More books means different authors and different writing approaches, and a greater chance of there being a book available that suits different people.
I mention this because to some people, words such as standards, regulations, or compliance are huge turn-offs that make them effectively stop listening. Maybe Design Accessible Web Sites will sit better with that crowd, since the author, Jeremy Sydik, presents the information in a gentler way, without getting overly hung up on checkpoints and accessibility guidelines.
I think it’s a very good approach. There isn’t much sense in slavishly following recommendations just to tick checkboxes without knowing what the benefit is. And I’ve been seeing quite a bit of that lately…
It seems that often when a client requires their website to be accessible, the task of making sure it is accessible is handed over to a back-end developer who also happens to be the only one on the project who has any sort of knowledge of front-end development. But that developer is very rarely aware of what makes a website accessible, so they turn to checking points off the WCAG checklists and checking checkboxes in whichever IDE they are using. And that often leads to badly implemented accessibility, like the issues I mentioned a while ago in Overdoing accessibility." (Continued via 456 Berea Street) [Usability Resources]
"It’s good to see more books on Web accessibility being published. More books means different authors and different writing approaches, and a greater chance of there being a book available that suits different people.
I mention this because to some people, words such as standards, regulations, or compliance are huge turn-offs that make them effectively stop listening. Maybe Design Accessible Web Sites will sit better with that crowd, since the author, Jeremy Sydik, presents the information in a gentler way, without getting overly hung up on checkpoints and accessibility guidelines.
I think it’s a very good approach. There isn’t much sense in slavishly following recommendations just to tick checkboxes without knowing what the benefit is. And I’ve been seeing quite a bit of that lately…
It seems that often when a client requires their website to be accessible, the task of making sure it is accessible is handed over to a back-end developer who also happens to be the only one on the project who has any sort of knowledge of front-end development. But that developer is very rarely aware of what makes a website accessible, so they turn to checking points off the WCAG checklists and checking checkboxes in whichever IDE they are using. And that often leads to badly implemented accessibility, like the issues I mentioned a while ago in Overdoing accessibility." (Continued via 456 Berea Street) [Usability Resources]
Design Accessible Web Sites: 36 Keys to Creating Content for All Audiences and Platforms
Check-out more books at Usernomics.
0 Comments:
Post a Comment
<< Home