ATIA Webinar - Evaluating Web Accessibility: Developing a Program with Real AT Users

WEBINAR CODE: AT12-WEB18

WEBINAR TITLE: Evaluating Web Accessibility: Developing a Program with Real AT Users

PRESENTER(S): Janet Jendron, Program Coordinator, South Carolina Assistive Technology Program

DATE: Thursday, June 21, 2012

TIME: 3:30 p.m. – 5:00 p.m. Eastern Time

REGISTRATION FEE: $49

Link to Online Registration Form – Registration is now open!!

OVERVIEW: There is no substitute for the use of real, live people evaluating web pages for accessibility and usability! South Carolina has developed and implemented a program, training AT users (and some non-users) to evaluate state agency web sites. We’ll address: training methods, report formats/content, approaches for effective communication with state agency administrators/IT personnel, funding, identifying/training testers, testing tools, program adaptations made along the way, past and future strategies for maximizing the program’s impact, future plans and possibilities, and how components of the program could be replicated by other organizations and in other arenas.

STRAND: Policy - Policy and Implementation

AUDIENCE: Advocates, AT Specialists, Consumers/Individuals with Disabilities, Disability Services, Educators, Family Members, General Interest, Instructional Technologists, IT, Media Specialists, OTs, PTs, SLPs, Professional Development/Training, Rehab Therapists, Social Workers, Visual Impairment Specialists, Vocational Rehabilitation, Wed Designers

LEARNING OBJECTIVES: As a result of this webinar, participants will be able to:

• Describe strategies for training web users (with and without AT) to evaluate web pages for accessibility and usability.
• Describe effective ways to communicate accessibility challenges to state agency administrators and IT personnel.
• Describe elements of a meaningful accessibility report to web designers and state agency administrators.

SPEAKER BIOGRAPHIES: Janet Jendron, Web Accessibility Workgroup Chair, SC Assistive Technology Advisory Committee, administers a Web Testers Program, using people who use assistive technology (and some who don’t) to evaluate agency web pages for accessibility and usability. She facilitates reporting and presentation and consultation with agencies about evaluation results and possible accessibility solutions. She also manages the SC Assistive Technology Program's equipment reuse program, is the web administrator and does public relations for SCATP. She is experienced in non-profit administration in several arenas.

To read more about the webinar, please click on the above title.

To access the CDR Library catalog, please click on this link.

Powerpont Accessibility

PowerPoint Accessibility

* WebAIM: PowerPoint Accessibility - http://www.webaim.org/techniques/powerpoint/
* AccessIT: How do I make my online PowerPoint presentation accessible? - http://www.washington.edu/accessit/articles?1028
* Web Accessibility for All: Creating Accessible PowerPoint Presentations -
* http://www.cew.wisc.edu/accessibility/tutorials/pptmain.htm
* Microsoft PowerPoint, Universally Designed - http://accessproject.colostate.edu/udl/modules/powerpoint/mod_ppt.cfm
* California State University on Powerpoint- http://teachingcommons.cdl.edu/access/docs_multi/MSPPTFaceToFace.shtml
http://teachingcommons.cdl.edu/access/docs_multi/documents/
CreatingAccessiblePowerPointPresentations.pdf

NOTE: To access the Center for Disability Resources Library, click on this link.

Accessibility Tips from ATAP and WebAIM

Link Type Indicators
It is a good idea to inform users when a link goes to non-HTML content (such as a PDF file or Word document). It can be frustrating to activate a link and then realize that the link requires an external program or viewer. An icon (with appropriate alternative text) or text, such as "(PDF)", is sufficient. Because screen reader users commonly navigate by links, it is vital that the link type indicator icon or text be placed within the link, otherwise this information is readily available to sighted users, but not presented in the context of the link for screen reader users.

Accessibility User Testing
Instead of conducting accessibility testing with users with disabilities (asking users to identify accessibility issues), it is almost always more effective to do usability testing (asking users to evaluate overall usability) with users with disabilities. While accessibility testing can be used to identify instances of accessibility – poor alt text here and a missing label there, fixing all significant instances of inaccessibility and non-compliance still might result in a poor experience for users with disabilities. Basic user testing that includes users with disabilities has a focus on the broader user experience with a site, yet still can identify specific accessibility issues. User testing with individuals with disabilities should be part of a broader testing plan that involves compliance checklists, automated tests, manual testing, and assistive technology testing.

Do Not Require Unnecessary Form Data
One of the keys to creating highly accessible forms is to avoid as many errors as possible before the form is submitted. Ensure that forms are as simple and intuitive as possible, and don't require that a field be filled out if the content is not necessary (e.g., a telephone number to subscribe to an email discussion list). Errors can also be prevented by allowing informatoin to be entered in a number of logical formats. For example, allow a telephone number to be formatted: (123)456-7890, 123-456-7890, 123.456.7890, or 1234567890, as long as ten numerals are present. This data can easily be reformatted using scripting or database languages for further usage.

Large Clickable Targets
Some mouse users have may have difficulty with fine motor control, so it is important that clickable targets be sufficiently large. Radio buttons and checkboxes should include properly-associated labels (using the element). Small icons or text, such as previous/next arrows or superscript links for footnotes, should be sufficiently large or combined with adjacent text into a single link.