Monica Seeber

e-Accessibility Part 2

What am I talking about?

1.  Web Accessibility National Transition Strategy – see Part 1

2.  Introducing WCAG 2.0 – see Part 1 3.  WCAG 2.0 Level AA requirements 4.  Applying WCAG 2.0 to digital copy 5.  Resources

Operable

§  The second principle.

Keyboard Accessible

Operable  

2.1  Make  all  func2onality  

available  from  a  keyboard  

2.1.1  ✪  2.1.2  ✪  

✪ These criteria can only be met through design. We can tell the graphic designer/web developer about them, but we can’t do it ourselves.

Enough Time

Operable  2.2  Provide  users  

enough  2me  to  read  and  use  content    

2.2.1  ✪  2.2.2  ✪  

✪ These criteria can only be met through design. We can tell the graphic designer/web developer about them, but we can’t do it ourselves.

Seizures

Operable  

2.3  Do  not  design  content  in  a  way  that  is  known  to  cause  seizures  

2.3.1  ✪  

✪ These criteria can only be met through design. We can tell the graphic designer/web developer about them, but we can’t do it ourselves.

Navigable

Operable  

2.4  Provide  ways  to  help  users  navigate,  find  content,  and  determine  where  

they  are  

2.4.1  ✪���2.4.2  

2.4.3  ✪  2.4.4  ✪  

2.4.5  AA  ✪  2.4.6  AA  ✪  2.4.7  AA  ✪  

✪ Some of these criteria can only be met through design. We can tell the graphic designer/web developer about them, but we can’t do it ourselves.

Writing Navigation Content Navigation content must be informative and concise.

Navigation content can be: •  page titles •  links •  headings and labels Examples: Understanding SC 2.4.2 Understanding SC 2.4.4 Understanding SC 2.4.6 Page or Document Title Headings and Subheadings Link Text Table Headers and Captions

Understandable

§  The third principle.

Readable

Understandable  3.1  Make  text  

content  readable  and  understandable  

3.1.1  ✪���3.1.2  AA  ✪  

✪ These criteria can only be met through design. We can tell the graphic designer/web developer about them, but we can’t do it ourselves.

Here’s a shocker: Plain English is not a success

criteria. You should use it anyway because

it’s Best Practice and all-round good manners.

Predictable

Understandable  3.2  Make  Web  pages  appear  and  operate  in  predictable  ways  

3.2.1  ✪���3.2.2  ✪���

3.2.3  AA  ✪���3.2.4  AA  ✪  

✪ These criteria can only be met through design. We can tell the graphic designer/web developer about them, but we can’t do it ourselves.

Input Assistance

Understandable   3.3  Help  users  avoid  and  correct  mistakes  

3.3.1  ✪���3.3.2  ✪���

3.3.3  AA  ✪���3.3.4  AA  ✪  

✪ Some of these criteria can only be met through design. We can tell the graphic designer/web developer about them, but we can’t do it ourselves.

Writing Input Assistance Input Assistance content must be specific and helpful.

Input Assistance content can be: •  error identification •  labels or instructions •  suggestions Examples: Understanding SC 3.3.1 Understanding SC 3.3.2 Understanding SC 3.3.3 10 Tips on Writing Hero-worthy Error Messages Usable and Accessible Form Validation and Error Recovery

Robust

§  The fourth (and final!) principle.

Compatible

Robust  

4.1  Maximize  compa2bility  with  current  and  future  

user  agents,  including  assis2ve  technologies.  

4.1.1  ✪���4.2.2  ✪  

✪ These criteria can only be met through design. We can tell the graphic designer/web developer about them, but we can’t do it ourselves.

4. Applying WCAG 2.0 to digital copy

Word  

Excel  

PowerPoint  

Forms  

PDF  

For all office documents

1.  Provide alternative text for images 2.  Identify the column headers of

tables 3.  Avoid complex tables 4.  Avoid text boxes 5.  Avoid excessive use of blank

characters, lines and cells

Word

6. Use true heading styles 7.  Use true numbered and bulleted

lists 8. Use true columns 9.  Place images in line with text 10. Include table of content for long

documents (auto is preferable)

Excel

6.  Give each worksheet a descriptive title 7.  Provide brief instructions in the first

cell of each worksheet 8.  Describe the contents of charts in text

and present the same data in a table 9.  Choose colours with a contrast ratio of

at least 4.5:1 and use additional visual cues

PowerPoint

6. Give each slide a title 7.  Use built-in slide layouts 8.  Provide captions and text transcript

for multimedia content 9.  Avoid excessive use of slide

transitions and text animations

Forms

6.  Provide labels for fields via Help Text 7.  Identify required fields 8.  Describe expected format and values 9.  Place section breaks before and after

the form and only enforce protection on the section containing the form

PDF §  PDF documents are considered “web content”

and must comply with WCAG 2.0 which includes 23 techniques specific to PDFs.

§  PDF is not considered an accessible format by the Australian Human Rights Commission □  An alternative format optimised for accessibility is

required World Wide Web Access: Disability Discrimination Act Advisory Notes ver 4.0 (2010) – section 2.4.2 See also: PDF files

5. Resources

WCAG  2.0  WCAG  2.0  Contents  

michaelgaigg.com  

AccessAbility  

Web  Accessibility  In  Mind  

Digital  copy  

Vision  Australia  

ADOD  Project  

Tools  Web  Accessibility  Evalua2on  Tool  

TCC  Wri2ng  for  the  Web  training  

Fangs  Screen  Reader  Emulator  

ChromeShades  

WAT  for  IE  

Legisla2on  Australian  Human  Rights  Commission  

Web  Accessibility  Na2onal  Transi2on  Strategy