eaccessibility - part 2_ppt slides text

8/10/2019 EAccessibility - Part 2_PPT Slides Text

1/5

Slide 1: The Copy Collective

e-Accessibility Part 2 Monica Seeber

Slide 2. What am I talking about?

1.

Web Accessibility National Transition Strategysee Part 1

2. Introducing WCAG 2.0see Part 1

3. WCAG 2.0 Level AA requirements

4.

Applying WCAG 2.0 to digital copy

5. Resources

Slide 3. Operable

The second principle.

Slide 4. Keyboard Accessible

Operable

2.1 Make all functionality 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 cant do it ourselves.

Slide 5. Enough Time

Operable

2.2 Provide users enough time to read and use the content

2.2.1*

2.2.2*

* These criteria can only be met through design. We can tell the graphic designer/web developer


Slide 6. Seizures

Operable

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

2.3.1*



Slide 7. Navigable

Operable


2/5

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 cant do it ourselves.

Slide 8. Writing Navigation Content

Navigation content must be informativeand concise

Navigation content can be:

page titles

links

headings and labels

Examples:

Understanding SC 2.4.2



Page or Document Title

Headings and Subheadings

Link text

Table Headers and Captions

Slide 9. Understandable

The third principle.

Slide 10. Readable

Heres a shocker: Plain English is not a success criteria. You should use it anyway because its Best

Practice and all-round good manners.

Slide 11. Predictable

Understandable

3.2 Make Web pages appear and operate in predictable ways


3/5

3.2.1*

3.2.2*

3.2.3 AA*

3.2.4 AA*



Slide 12. 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 cant do it ourselves.

Slide 13. Writing Input Assistance

Input Assistance content must be specificand helpful

Input Assistance content can be:

error identification

labels or instructions

suggestions

Examples:



Understanding SC 3.3.310 Tips on Writing Hero-worthy Error Messages

Usable and Accessible Form Validation and Error Recovery

Slide 14. Robust

The fourth (and final!) principle.

Slide 15. Compatible

Robust
http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-identified.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-suggestions.htmlhttp://blog.teamtreehouse.com/10-tips-on-writing-hero-worthy-error-messageshttp://localhost/var/www/apps/conversion/tmp/scratch_3/Forms/%20http/::webaim.org:techniques:formvalidation:http://localhost/var/www/apps/conversion/tmp/scratch_3/Forms/%20http/::webaim.org:techniques:formvalidation:http://localhost/var/www/apps/conversion/tmp/scratch_3/Forms/%20http/::webaim.org:techniques:formvalidation:http://blog.teamtreehouse.com/10-tips-on-writing-hero-worthy-error-messageshttp://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-suggestions.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-identified.html


4/5

4.1 Maximise compatibility with current and future user agents, including assistive

technologies.

4.1.1*

4.2.2*



Slide 16. 4. Applying WCAG 2.0 to digital copy

Infographic shows Word, Excel PowerPoint, forms and PDF icons.

NB: VA has worked with Microsoft and WCAG 2.0 requirements on office documents.

Slide 17. 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

Slide 18. Word

6.

Use true heading styles

7.

Use true numbered and bulleted lists8. Use true columns

9.

Place images in line with text

10.

Include table of content for long documents (auto is preferable)

Slide 19. Excel

11.Give each worksheet a descriptive title

12.

Provide brief instructions in the first cell of each worksheet

13.Describe the contents of charts in text and present the same data in a table

14.Choose colours with a contrast ratio of at least 4.5:1 and use additional visual cues

Slide 20. PowerPoint

14. Give each slide a title

16. Use built-in slide layouts

17. Provide captions and text transcript for multimedia content

18. Avoid excessive use of slide transitions and text animations

Slide 21. Forms

19.

Provide labels for fields via Help Text

20.

Identify required fields21.Describe expected format and values


5/5

22.

Place section breaks before and after the form and only enforce protection on the section

containing the form

Slide 22. PDF

PDF documents are considered web content and must comply with WCAG 2.0 whichincludes 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

Slide 23. 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 Evaluation Tool

TCC Writing for the Web training

Fangs Screen Reader Emulator

ChromeShades

WAT for IE

Legislation

Australian Human Rights Commission

Web Accessibility National Transition Strategy

eaccessibility - part 2_ppt slides text

Documents