February 2015 Newsletter

News

WebAIM Web Accessibility Training

WebAIM's next open training will be held May 19-20 in Logan, Utah.

International Technology and Persons with Disabilities Conference

WebAIM staff will be presenting the following sessions at the CSUN conference:

  • Introduction to ARIA and HTML5 - Pre-conference Workshop - Tuesday, March 3 at 9am-12pm
  • Do We Need To Change the Web Accessibility Game Plan (Redux)? - Wednesday, March 4 at 1:20pm
  • WebAIM's Web Accessibility Practitioner and User Surveys: Data and Trends - Thursday, March 5 at 8am
  • WAVE - API, Toolbars, and Rule Builder - Thursday, March 5 at 9am
  • Screen Reader Web Accessibility Face-Off II — No Holds Barred - Thursday, March 5 at 3:20pm

Proposed Section 508/255 guidelines published

After clearing another hurdle, the proposed updates to the Section 508 technical guidelines are available online.

Harvard and M.I.T. Are Sued Over Lack of Closed Captions

Advocates for the deaf filed federal lawsuits saying both universities violated antidiscrimination laws by failing to provide closed captioning.

Resources

Keyboard Accessibility with the Space Bar

Keyboard accessibility is critical for your users that depend on voice recognition, onscreen keyboards, screen readers, ergonomic accessories, and your power users that prefer to avoid grabbing the mouse for every task.

Advanced ARIA Tip #2: Accessible modal dialogs

One question that came up more and more in recent months is how to create an accessible modal dialog with WAI-ARIA.

Flipboard – React Canvas Accessibility

Flipboard announced that they are using HTML5 canvas to improve performance on mobile devices. This has accessibility ramifications.

The Unbearable Inaccessibility of Slideshows

Slideshow. Slider. Carousel. Whatever you call them, they’re ubiquitous on organizational home pages across the web. And almost all of them are inaccessible.

Accessibility Originates With UX: A BBC iPlayer Case Study

Henny Swan provides a case study of user experience driving accessibility decisions.

Layout Tables Tip

A quick tip for ensuring that layout tables are not read a data tables by screen readers.

Quick Tip: Line Length

Pages should be designed so the line length, the number of characters that appear per line, should be neither too short nor too long. Anything more than around 80 characters can introduce reading difficulties in scanning from the end of a line of text to the beginning of the next line. Short line lengths also introduce difficulty and vertical scrolling. The width of the body area of a web page should be constructed to ensure that lines of text are constrained to both minimum and maximum lengths across both small (such as mobile devices) and large screen resolutions.

WebAIM E-mail Discussion List

Subscribe to the WebAIM E-mail Discussion List

View the Discussion List Archives

Selected recent threads: