Useful links roundup

24 Ways: CSS for Accessibility by Ann McMeekin is a nice set of CSS tips that would make a good handout or class discussion.

Six Tech Predictions for 2008 from Web Worker Daily is a quick and interesting read.

Bad Timing is Eric Meyer’s look at the flip side of the suit Opera brought against Microsoft in Europe this week.

 Why Accessibility? Because it’s Our Job by brothercake argues, “If we call ourselves professionals, we owe it to our clients, their clients, and ourselves, to do our job properly. A chef must care about health, a builder must care about safety, and we must care about accessibility.”

WCAG 2.0 ready for review and comment

The Web Content Accessibility Guidelines (WCAG) Working Group wants you to
review the second WCAG 2.0 Last Call Working Draft published on December 11,
2007. WCAG 2.0 deals with how to make Web sites, applications, and other
content accessible to people with disabilities. Submit any comments by February 1, 2008. WCAG Quick Reference will help you review.

Event: California Web Accessibility Conference

The 3rd Annual California Web Accessibility Conference (CalWAC 3)! is scheduled for January 14-16 at California State University at Long Beach. This is a joint project of CSU/LB and Knowbility. The registration and conference lineup are available on the Knowbility.org site.

Speaking of the lineup, it’s a perfect mix of male and female, with names like Molly Holzschlag, Derek Featherstone, Sharron Rush, and Jim Thatcher leading a pack of expert accessibility trainers.

Technorati Tags: ,

Tagging a PDF

If you own Adobe’s CS3 suite, Acrobat 8 Professional was bundled with the product. To buy it separately costs $449, but if you own an older version of the full Acrobat software, you can upgrade for $159. If you are interested in making your PDFs capable of use by screenreaders or small screens where the content must reflow to fit the screen, you need to use a structured document with tags added. Tags can only be added to a document with a full version of Acrobat, the Adobe Reader isn’t capable of doing this.

I’m using Acrobat 8 Professional to demo these steps. Older versions of the full Acrobat software can also tag documents.

sidebar shows no tags availableOpen the PDF in Acrobat. You can tell if there are any tags already in the file by looking at the tags sidebar. In this example, there are no tags yet.

Use the Acrobat menu to add tags to your document.

add tags using the Advanced menu

In the Advanced menu, select Accessibility > Add Tags to Document.

a recogntion report

The first screen that opens in the tags sidebar is a Recognition Report, which points out some of the missing accessibility information. Take a good look at what you’re missing here. You’ll need to address each item to make the PDF document usable and accessible for the small screen and screen readers.. Then select the tag icon on the far left side of the sidebar to move on to the tags category.

the added tags are listed in the sidebar

The complete list of tags and figures are given in the tags sidebar. Each one can be individually opened to examine.

select the item's properties to edit

To make changes in Figures, first highlight the figure you want to edit in the document window. It will be highlighted in the tags panel. Use right-click or ctrl-click to select the Properties menu for the item.

edit properties in the touch up dialog

The Touch Up Properties dialog opens. Here you can add alt text and other accessiblility features.

edit tags in the touch up dialog

Selecting any tag in the tag sidebar and going to the tag’s properties will allow you to change any inappropriately labeled tags.

When you save and close the document, the Recognition Report will disappear, but you will still have access to the Tags sidebar when you reopen the document. If you want the information, you can run various accessibility reports using the Advanced menu.

If possible, get someone with a PDA or screen reader to check your file for problems.

Review: Design Accessible Web Sites

Summary: A good resource


get this book at Amazon.com

Design Accessible Web Sites: 36 Keys to Creating Content for All Audiences and Platforms

Rating: 4/5

This book, by Jeremy J Sydik, is from the Pragmatic Bookshelf series (2007). It covers the full range of accessibility topics from basics such as introductions to the various types of disabilities to more complex topics such as scripts, accessible Flash, and understanding the guidelines.

I particularly like the Ten Principles for Web Accessibility in this book. The second principle, my favorite, is “Your users’ technologies are capable of sending and receiving text. That’s about all you’ll ever be able to assume.”

There are simple, no-nonsense descriptions and tips for testing, alt text, semantic HTML, captioning, tagging PDFs, scripting, and accessibility laws the world over. This book, in many ways, follows the same contents as Web Accessibility: Web Standards and Regulatory Compliance, but in a less pedantic and lighter way. You don’t get as much depth, but you do get a serviceable reference that would be good to have around.

A roundup of useful links

Jim Thatcher has revised and updated his tutorial on how to comply with Section 508. It’s a ten section course in accessibility. JimThatcher.com

Project Seven has a free tutorial on Q Tabs, or navigation tabs with scalable graphics. The tutorial includes downloadable files and graphics. PVII Q Tabs

The New York Times (NYT) has embraced the blogosphere with its Blogrunner section. The NYT cherry picks from blogs it considers accurate or authoritative and displays them collected by topic. One such topic is technology. NYT Blogrunner: Technology A personal favorite post from the Technology blogs is New Classroom War: Teachers vs. Technology.

An article by Milissa Tarquini at Boxes and Arrows takes on the myth of above the fold design and thoroughly blasts it into oblivion. Blasting the Myth of the Fold

A new and discounted deal on Mac software each day. You save money and you learn about the newest Mac apps. MacZOT

Accessiblity and AJAX

In Accessibility and Usability issues with AJAX, Joe Dolson provides a think piece detailing the issues and solutions for accessibility and AJAX. This analysis is useful information for anyone using or teaching AJAX.

This is not a technical article. You will not learn how to code AJAX by reading this; either in an accessible and usable fashion or otherwise. This is a conceptual article. It will run through basic user-interface issues with AJAX (and other rich media). These are the reasons that AJAX functionality can be a problem for users — if you consider these issues carefully during development, it should greatly enhance the usability of your end product.