Design Accessible Web Sites: 36 Keys to Creating Content for All Audiences and Platforms (Pragmatic Programmers)
Format: PDF / Kindle (mobi) / ePub
It's not a one-browser web anymore. You need to reach audiences that use cell phones, PDAs, game consoles, or other "alternative" browsers, as well as users with disabilities. Legal requirements for assistive technologies as well as a wide array of new browsing experiences means you need to concentrate on semantics, alternate access paths, and progressive enhancement.
Give your audience the power to interact with your content on their own terms. It's the right thing to do, and with a $100 billion a year market for accessible content, new laws and new technologies, you can't afford to ignore accessibility.
With this book, you'll learn basic principles and techniques for developing accessible HTML, audio, video, and multimedia content. In addition, you will understand how to apply the principles you learn in this book to new technologies when they emerge.
You'll learn how to:
Use best practices of accessibility to develop accessible web content Build testing into projects to improve results and reduce costs Create high quality alternative representations for your audience Add accessibility features to external media like PDF and Flash Negotiate the terrain of accessibility standards Apply principles of accessiblity to new technologies as they emerge
whether they can be streamlined. • Was the user comfortable with the interface for completing the tasks? It’s interview time. This is your opportunity to find out where the interface was clear to the user and where it felt cumbersome. If you are recording interactions, it may be helpful to ask the tester to work in a speak-aloud fashion, commenting on their actions as they take them (note that this will affect task completion times, however). For an in depth discussion of the issues surrounding
information to separate tracks from different albums. Let’s add 118 A H , < TABLE >, I H ARDLY K NEW Y E ! axis=’albums’ to each album’s title field and axis=’album#’ for each song and see where that takes us:
|Artist||Album Title||Media Format|
for users who can clearly resolve the colors chosen, keying is a valuable tool. The key point is to pick colors that don’t resolve too closely for the colorblind. When colors do behave badly in a colorblindness simulation, we have three options: • Change One of the Conflicting Colors: Clearly, if possible, it is best to change the color scheme to avoid the color conflict entirely. This might still put a considerable burden on the user, however, who may still need to consider different values of
though. While visually impaired users need have text alternatives for images, other users benefit from explanatory imagery. Some developers choose the path of “text-only” versions of their pages. Don’t make this mistake! To do this right, you would need to write alternative text content anyway—you would just be doing it the WET way. Take a look at Don’t Get WET!, on page 57 if you don’t know why that would be a Bad Thing. Act on it! 1. Act Locally. Take the time to add alternate text to your
of low vision may vary widely— some people can use magnification while others might only be able to perceive motion or changes in the level of light. Many low vision users rely on screen magnification solutions, sometimes one included with an operating system but, more commonly, one available from a third party. Third party magnifiers, like ZoomText5 provide higher levels of magnification and reduce pixelation of magni1. 2. 3. 4. 5. http://www.freedomscientific.com/ http://www.yourdolphin.com/