Newsletter Archives - July 2012

News

Web Accessibility Training - Advanced Session

Join us for 2 days of advance, hands-on training August 29-30, 2012 in beautiful Logan, Utah.

Accessibility Summit 2012

The third annual Accessibility Conference will feature WebAIM's Jared Smith and other accessibility experts Sep. 25, 2012.

Convention on the Rights of Persons with Disabilities progress

This landmark legislation is going before congress for ratification this week.

Tips and Resources

Using ARIA in HTML5

Steven Faulkner's unofficial draft of a static, practical approach to ARIA for web developers.

Practical Web Accessibility Testing Tools

Glenda Sims outlines several very useful tools for web accessibility testing.

The Captcha monster: Automatic Website Captcha Code Filler

An easy-to-use Firefox add-on is designed to ensure that those with disabilities don't have to worry about deciphering Captcha codes.

W3C HTML and WHATWG HTML 'split' effect on HTML Accessibility?

The politics of HTML5 has resulted in a separation of working groups. The Paciello Group Blog explores how this change may affect web accessibility.

Achieving Online Accessibility (Yes, You Can!)

Helpful tips for developers feeling overwhelmed by accessibility issues.

Why Keyboard Accessibility isn't the Same Thing as Screen Reader Accessibility

Bryan Garaventa discusses that in order to be accessible, a website must be fully accessible to keyboard users, have proper textual equivalents for screen reader users, and be intuitive.

Quick Tip: Layout Tables

Tables in HTML are intended for tabular data. Although using tables for page layout is not considered best practice, this typically has minimal impact on accessibility, as long as two primary guidelines are kept in mind. First, do not use any markup that is typically used to identify data tables. This includes table headers (<th>), <caption>, and <summary>. These tags are often used by a screen reader to detect the presence of a data table, which is read very differently. Second, the reading and navigation order of layout table content (based on the source code order) must be logical and intuitive (e.g., typically the same as the visual order).

WebAIM E-mail Discussion List

Subscribe to the WebAIM E-mail Discussion List

View the Discussion List Archives

Selected recent threads