Last updated
Dec 8, 2007
<span class="reviewer vcard" id="reviewer-vcard">
<span class="fn">George Ornbo</span>
</span>
<span class="type">product</span>
<img src="/images/articles/just-ask.png" alt="Just Ask- Integrating Accessibility Throughout Design" class="right" />
<h3 class="fn">Just Ask- Integrating Accessibility Throughout Design</h3>
<p>Author: Shawn Lawton Henry</p>
<p>Published: February 2007</p>
<p>ISBN:1430319526</p>
<p><a href="http://www.amazon.com/Just-Ask-Integrating-Accessibility-Throughout/dp/1430319526">Buy from Amazon</a></p>
<img src="/images/books/three_stars.gif" title="Three out of Five" alt="Three out of Five" width="124" height="30" />
<span class="rating">3</span>
<p>This review is based on the <a href="http://www.uiaccess.com/accessucd/">free online version</a> of Just Ask</p>
<h3>Accessibility through design</h3>
<p>Just Ask- Integrating Accessibility Throughout Design is not a book that will teach you how to create an Accessible site. In fact there is not one line of code. It is more of a theoretical book and outlines frameworks to test your site and integrate accessibility into your design process. The book advises:</p>
<blockquote>
<p>Designing for accessibility doesn't require a whole new design process; it generally involves only minor adjustments to your existing design process.</p>
</blockquote>
<p>Just Ask shows you how to make those minor adjustments with some sound advice. </p>
<h3>Well referenced</h3>
<p>The book is meticulously referenced throughout allowing the reader to look up standards and recommended documents. As a developer at times I was looking for more interpretation of things like WCAG. Indeed advice is given that standards should be interpreted and tested with users rather than followed to the letter. It would have been great to have some examples of this. The book is certainly theoretical rather than technical.</p>
<h3>Users, personas, scenarios</h3>
<p>The section on Accessibility in User Centered Design is an excellent framework. First you profile your user groups, then create personas and finally scenarios of tasks to be completed. For me this formalised processes that I follow, but it is an excellent resource to refer to.</p>
<h3>Usability testing</h3>
<p>Perhaps the most useful section for me was Usability Testing. It outlines in great detail how to set up and run a usability test.</p>
<p>Overall Just Ask is a detailed well referenced theoretical book. For anyone wanting to implement accessibility into a project, or conduct usability testing it provides excellent frameworks. I suspect many projects simply don't have the time or budget to implement many of the recommendations in the book. Steve Krug's book <a href="/journal/book_review_dont_make_me_think_steve_krug/">Don't Make Me Think</a> for example takes account that the average project probably does not have a big budget. For me it I would have liked more attention being given to smaller projects. That said I will still incorporate as much of the excellent advice I can into my design process. </p>
Have an update or suggestion for this article? You can edit it here and send me a pull request.
Using HashiCorp Vault with LDAP
How to use HashiCorp Vault to setup an LDAP backed secret store with read-only access for users in groups and read-write access for specific users
Linux and Unix xargs command tutorial with examples
Tutorial on using xargs, a UNIX and Linux command for building and executing command lines from standard input. Examples of cutting by character, byte position, cutting based on delimiter and how to modify the output delimiter.
Copy a file in Go
How to copy a file in Go. The ioutil package does not offer a shorthand way of copying a file. Instead the os package should be used.