Wednesday, November 30, 2011

Web Accessibility: Contrast

This is part of a continuing series of web accessibility tips for IT personnel, web managers and web development groups. These tips can be used to review current website accessibility and to utilize in developing new websites with the hope of improving web accessibility for everyone.

Determining whether there is enough color contrast between text and background can be difficult. WCAG 2.0 has contrast guidelines at both level AA and level AAA and a complex formula for determining a contrast ratio. Large text (over 14 point bold) requires slightly less contrast than 'normal' text.There are many tools, such as WebAIM's color contrast checker that can generate this contrast ratio and give immediate feedback whether the contrast is sufficient. Simply enter a foreground and background color to see the results. Users of the Firefox web browser can use the Colorzilla add-on too easily select color values from within the web page.

Wednesday, November 23, 2011

Web Accessibility: Text Size and Zoom

This is part of a continuing series of web accessibility tips for IT personnel, web managers and web development groups. These tips can be used to review current website accessibility and to utilize in developing new websites with the hope of improving web accessibility for everyone.

Content must remain readable and understandable when text size or page zoom is set to at least 200% or twice the default size. While it is optimal to decrease the likelihood of horizontal scrollbars or changes in visual design or document layout at these settings, readability and understandability are most critical to accessibility. This can be tested by selecting Control + (or Command + on a Mac) in your web browser or by increasing the text size under the View menu.

Wednesday, November 16, 2011

Web Accessibility: Robustness

This is part of a continuing series of web accessibility tips for IT personnel, web managers and web development groups. These tips can be used to review current website accessibility and to utilize in developing new websites with the hope of improving web accessibility for everyone.

Robustness addresses the technology implications of accessibility. It requires following web standards (e.g., valid HTML and CSS), creating content/functionality that works across various user agents (web browsers and assistive technologies), ensuring compatibility with various hardware (such as mobile devices), and considering present, future, and older technologies. While it does not mean that a web site must be compatible with all present, future, or former technologies, it does suggest that consideration be given to ensure accessibility to the broadest range of technologies feasible.

Thursday, November 10, 2011

Free Webinar: A Holiday AT Buying Guide

picture of wrapped giftRegister now and join us Nov. 17th to learn about adaptive gizmos, gadgets and practical ideas that make great gifts for people of all ages this holiday season. We will be going over both low-tech, less expensive devices to more high-tech and expensive gadgets. The webinar will include a range of mainstream devices (items that may not be specifically designed as AT) and others will be actual AT products. WATAP's AT Specialists will explore devices for people with a range of functional needs and abilities that will make great small gift ideas to fabulously wrapped presents with a bow. Please join WATAP and the Washington Access Fund on November 17th, from 10:00am-11:15am for a gift guide webinar on assistive technology. To register for this free webinar, please send an email to Leann at leann@washingtonaccessfund.org, or by phone at (206) 328-5116 or TTY (888) 494-4775.

Wednesday, November 9, 2011

Web Accessibility: Cognitive Disabilities

This is part of a continuing series of web accessibility tips for IT personnel, web managers and web development groups. These tips can be used to review current website accessibility and to utilize in developing new websites with the hope of improving web accessibility for everyone.

The number of people with cognitive disabilities is greater than the number people with all other disabilities combined. Cognitive disabilities are complex and vary greatly. Recommendations for those with cognitive disabilities share much overlap with general usability recommendations, however, the impact of poor usability and understandability can have a much more significant impact on those with cognitive disabilities. Care should be taken to ensure optimal functionality and understandability of web content by those with cognitive or learning disabilities.

Post-Test Survey: National Test of Emergency Alert System

On November 9, 2011, the Federal Communications Commission conducted a national test of the Emergency Alert System (EAS) over television and radio. The Rehabilitation Engineering Research Center for Wireless Technologies (Wireless RERC) is conducting a survey of people with visual and hearing impairment in order to understand the effectiveness and accessibility of EAS.
Please take a few minutes to complete the post-EAS-test survey.

The survey can be found at: https://www.surveymonkey.com/s/Post-EAS-Test
If you need assistance completing the survey, please contact Salimah LaForce at 404-894-8297 or salimah.laforce@cacp.gatech.edu.

All participants will be entered into a drawing for a $100 Amazon gift card. The drawing will be held on November 15, 2011; the winner will be contacted privately.

Wednesday, November 2, 2011

Web Accessibility: Alternative Versions

This is part of a continuing series of web accessibility tips for IT personnel, web managers and web development groups. These tips can be used to review current website accessibility and to utilize in developing new websites with the hope of improving web accessibility for everyone.

Building one version of a site that is highly accessible is the best approach to accessibility. Providing alternative versions or directing users to accessible or mobile versions of a site can be interpreted a segregation and separation, particularly if the content and functionality is not similar or equivalent to the main site. Statistics show that screen reader users are not likely to use this content anyway. A good site has full accessibility built in naturally, thus removing the need for alternative versions.