e-Accessibility Part 1 - The Copy Collective International · e-Accessibility Part 1. What am I...

20
Monica Seeber e-Accessibility Part 1

Transcript of e-Accessibility Part 1 - The Copy Collective International · e-Accessibility Part 1. What am I...

Monica Seeber

e-Accessibility Part 1

What am I talking about?

1.  Web Accessibility National Transition Strategy

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

e-Accessibility: More than just a buzz word

Design  for  all  

legisla-on  

disability  

methodology   hardware  

usability  

e-­‐accessibility  

Access for all

Visual   Hearing   Physical   Cogni-ve  

1. Web Accessibility National Transition Strategy

§  Agencies must update all government websites (as specified within scope under the NTS) to WCAG 2.0 conformance •  Level A (Single A) by 31 December 2012 •  Level AA (Double A) by 31 December 2014 •  To claim conformance websites must meet all five WCAG 2.0

conformance requirements.

§  Agencies are encouraged to seek WCAG 2.0 Level AA conformance from the outset, but must still meet the minimum requirements of the NTS (including Level A conformance by December 2012).

Australian Government Web Guide - Accessibility

Relax and let me explain…

Some  very  clever  people  wrote  guidelines  for  

improving  access  to  digital  informa-on.  

The  Federal  Government  decided  it  is  

mandatory  for  all  departments  to  implement  these  

guidelines.  

All  government  departments  –  

Federal,  State  and  Territory  –  must  implement  these  guidelines  by  31  December  2014.    

The guidelines allow for three levels of conformity: 1.  Single A 2.  Double A 3.  Triple A “Single A” is the minimum standard. “Triple A” is the gold standard. “Double A” is the happy-medium.

“Double A” is not a battery size.

2. Introducing WCAG 2.0

World  Wide  Web  Consor-um  

Web  architecture  

Seman-c  Web  

XML  technology  

Web  design  and  applica-ons  

Web  Content  Accessibility  Guidelines  

Web  of  services  

Web  of  devices  

Browsers  and  authoring  tools  

WCAG 2.0 structure

4  Principles  

12  Guidelines  

61  Success  Criteria  

Principles

1.  Perceivable  

2.  Operable  

3.  Understandable  

4.  Robust  

Guidelines Perceivable  

1.1  Provide  text  alterna-ves  for  non-­‐text  content  

1.2  Provide  alterna-ves  for  

-me-­‐based  media  

1.3  Create  content  that  can  be  presented  in  different  ways    

1.4  Make  it  easier  for  users  to  see  and  hear  content    

Operable  

2.1  Make  all  func-onality  

available  from  a  keyboard  

2.2  Provide  users  enough  -me  to  read  and  use  

content  

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

2.4  Provide  ways  to  help  users  

navigate  and  find  content  

Understandable  

3.1  Make  text  content  readable  

and  understandable  

3.2  Make  Web  pages  appear  and  

operate  in  predictable  ways  

3.3  Help  users  avoid  and  correct  

mistakes  

Robust  

4.1  Maximize  compa-bility  with  

current  and  future  soYware  and  hardware  

Success criteria

Single  A   Double  A   Triple  A  

Perceivable   8   5   8  

Operable   9   3   8  

Understandable   5   5   7  

Robust   1   -­‐   -­‐  

TOTAL   23   Single  A  +  13   Double  A  +  23  

Principles of accessibility

Number of Success Criteria

Level of compliance

Double A compliance has a total of 36 Success Criteria

•  1.  Perceivable:  Informa-on  and  user  interface  components  must  be  presentable  to  users  in  ways  they  can  perceive.  Principle  

•  1.1  Text  Alterna>ves:  Provide  text  alterna-ves  for  any  non-­‐text  content  so  that  it  can  be  changed  into  other  forms  people  need,  such  as  large  print,  braille,  speech,  symbols  or  simpler  language.  

Guideline  

•  1.1.1  Non-­‐text  Content:  All  non-­‐text  content  that  is  presented  to  the  user  has  a  text  alterna-ve  that  serves  the  equivalent  purpose,  except  for  the  situa-ons  listed  below.  (Level  A)    

Success  Criteria  

3. WCAG 2.0 Level AA requirements

This is where we come in

Perceivable

§  The first principle.

Text Alternatives

Perceivable   1.1  Text  Alterna-ves     1.1.1  

Non-text content can be: •  charts •  diagrams •  pictures •  animations •  maps •  interactive design

Text alternatives can be: •  text description •  data table •  text transcript

This is related to 1.2 Time-based Media

Writing Text Alternatives

Is  the  content  func-onal?  

Yes   Provide  a  text  alterna-ve  

No   “Hide”  the  content  in  the  background    

Further information: Understanding SC 1.1.1 Image ALT Tag Tips Complex Images

Alternative text must be equivalent and meaningful.

Time-based Media

Perceivable  1.2  Provide  

alterna-ves  for  -me-­‐based  media  

1.2.1  1.2.2  1.2.3  

1.2.4  AA  1.2.5  AA  

Time-based media can be: •  audio-only •  video-only •  live audio content •  synchronised media •  animations

Alternatives can be: •  text transcript •  audio description •  captions •  text description

This is related to 1.1 Text Alternatives

Writing Media Alternatives

Is  the  content  repe--ve?  

Yes   Provide  a  brief  ALT  descrip-on  and  refer  back  to  the  main  text  

No   Provide  a  media  alterna-ve  

Further Information: Understanding SC 1.2.1 Understanding SC 1.2.2 Understanding SC 1.2.3 Understanding SC 1.2.4 Understanding SC 1.2.5 Video Captions and Audio Transcripts

Media alternatives must be accurate and detailed.

Adaptable

Perceivable  

1.3  Create  content  that  can  be  presented  in  different  ways  

1.3.1  ✪  1.3.2  ✪  1.3.3  ✪  

✪ 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.

Adaptable content can be: •  forms •  tables •  schedules •  text reading order

Alternatives can be: •  text directions •  text description •  captions Ø  programmatic cues

Writing Adaptable Alternatives

Further Information: Understanding SC 1.3.1 Creating Accessible Tables Form Design Text Reading Order

Adaptable alternatives must be equivalent and detailed.

This is related to 2.4 Navigable

Distinguishable

Perceivable  

1.4  Make  it  easier  for  users  to  see  and  

hear  content  including  separa-ng  foreground  from  background  

1.4.1  ✪  1.4.2  ✪  

1.4.3  AA  ✪���1.4.4  AA  ✪  1.4.5  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.