Accessible Open SourceSoftware

                   

                   

Accessibility is a user experience…

Standards and laws help us get there but are not an end in themselves

                   

                   

Definition

Accessibility means all users – including those with disabilities – can get the same information and perform the same functions

                   

                   

Official Disabilities

• Visual (including blind, low vision, and color blind)

• Hearing

• Motor/Physical

• Speech

• Cognitive Learning

                   

                   

Addressing disability access

…also improves access in these conditions:

• Low bandwidth

• Old Browser

• Missing Plugins

• No Speakers

• Small Display (pda, mobile phone)

• Noisy Environment … and more

                   

                   

Techniques:

1. Alternatives to images – image attribute alt=“description goes here”

• Active images (links) MUST have meaningful alt text

• Illustrative images require judgement• Spacer images MUST have empty alt

alt=“”

                   

                   

Techniques, cont

2. Navigation, including within each page

• All functions must be keyboard accessible• Use structural tags as intended :

– h1, h2 to indicate page outline– list markup for lists

                   

                   

Techniques, cont

3. Emerging best practice for dynamic, scripted content found on:

• WAI-ARIA Roadmap (web)

• IAccessible2 (applications)

With background and links on the Codeathon wiki

                   

                   

Experienced Accessibility folks

• Sharron Rush

• CharlesChen

• Kelsey Ruger (available by phone)

Let us help!