87
Ho w t o Impr ove Y ouPr oject’s A ccessibility Without Go in g Crazy Eric Eggert [email protected] yatil W3C/Web Accessibility Initiative

DrupalCamp Vienna 2015

Embed Size (px)

Citation preview

Page 1: DrupalCamp Vienna 2015

How to Improve Your Project’s Accessibility

Without Going CrazyEric Eggert

[email protected] • yatil W3C/Web Accessibility Initiative

Page 2: DrupalCamp Vienna 2015
Page 3: DrupalCamp Vienna 2015
Page 4: DrupalCamp Vienna 2015
Page 5: DrupalCamp Vienna 2015

– w3.org/accessibility

The Web is fundamentally designed to work for all  people, whatever their hardware, software,

language, culture, location, or physical or mental ability. When the Web meets this goal, it is accessible to people with a diverse range of

hearing, movement, sight, and cognitive ability.

Page 6: DrupalCamp Vienna 2015

Accessibility: Make sure that People with disabilities can effectively interact with the Web

Page 7: DrupalCamp Vienna 2015

– Aaron Gustafson (Foreword in: Sarah Horton. “A Web for Everyone.”)

“On the web, every decision I make can have a profound effect on hundreds of thousands (if not millions) of people’s lives. I can make checking into

a flight a breeze, or I can make it a living hell.

That’s a lot of power. And to quote Stan Lee: ‘With great power comes great responsibility.’”

Page 8: DrupalCamp Vienna 2015

>1 billion Persons with some form

of disability

— WHO Report 2011

Page 9: DrupalCamp Vienna 2015

15% Persons with some form

of disability

— WHO Report 2011

Page 10: DrupalCamp Vienna 2015

@dstorey

Page 11: DrupalCamp Vienna 2015

Q: How do People With Disabilities

Use the web?

Page 12: DrupalCamp Vienna 2015

Browser Web Content

Page 13: DrupalCamp Vienna 2015

Browser Web Content

Assistive tech

Page 14: DrupalCamp Vienna 2015

Zoom

Page 15: DrupalCamp Vienna 2015

Pinch Out by Julie Muckensturm from the Noun Project

Page 16: DrupalCamp Vienna 2015
Page 17: DrupalCamp Vienna 2015

Braille

Page 18: DrupalCamp Vienna 2015

customizations

Page 19: DrupalCamp Vienna 2015

Captions

Page 20: DrupalCamp Vienna 2015

Resource: How People with

Disabilities Use the Web

w3.org/WAI/intro/people-use-web/

Page 21: DrupalCamp Vienna 2015

Q: Accessibility sounds complicated.

Page 22: DrupalCamp Vienna 2015

Q: How do I start with Accessibility?

Page 23: DrupalCamp Vienna 2015

Designers Content creators

Developers

Page 24: DrupalCamp Vienna 2015
Page 25: DrupalCamp Vienna 2015
Page 26: DrupalCamp Vienna 2015
Page 27: DrupalCamp Vienna 2015
Page 28: DrupalCamp Vienna 2015
Page 29: DrupalCamp Vienna 2015

Resource: Tips for getting started with web accessibility

w3.org/WAI/gettingstarted/tips/

Page 30: DrupalCamp Vienna 2015

Q: How do I make sure my website is accessible?

Page 31: DrupalCamp Vienna 2015

Resource: Web Content

Accessibility Guidelines (WCAG) 2.0

w3.org/TR/WCAG/

Page 32: DrupalCamp Vienna 2015

Principles: Perceivable

Operable Understandable

Robust

Page 33: DrupalCamp Vienna 2015

Perceivable: Text Alternatives

Page 34: DrupalCamp Vienna 2015

<button> <span class="icon icon-pencil"> </span>

</button>

Page 35: DrupalCamp Vienna 2015

<button title="Edit"> <span class="icon icon-pencil"> </span>

</button>

Page 36: DrupalCamp Vienna 2015

<button title="Edit"> <span class="icon icon-pencil-kaput“> </span>

</button>

Page 37: DrupalCamp Vienna 2015
Page 38: DrupalCamp Vienna 2015

ImageS

Page 39: DrupalCamp Vienna 2015

<button> <img src="pencil.png" alt="Edit"> </button>

Page 40: DrupalCamp Vienna 2015

<button> <img src="pencil.svg" alt="Edit"> </button>

Page 41: DrupalCamp Vienna 2015

Resource: Image Tutorial

w3.org/WAI/tutorials/images/

Page 42: DrupalCamp Vienna 2015

Resource: Web Accessibility

Tutorials

w3.org/WAI/tutorials/

<aside>

Page 43: DrupalCamp Vienna 2015

Page structure (Draft) Menus (Draft)

images Tables forms

carousels (Draft)

</aside>

Page 44: DrupalCamp Vienna 2015

Visible text labels

Page 45: DrupalCamp Vienna 2015

<button> <span class="icon icon-pencil"> </span> Edit

</button>

Page 46: DrupalCamp Vienna 2015

Perceivable: Color Contrast

Page 47: DrupalCamp Vienna 2015

Operable: usable with a Keyboard

Page 48: DrupalCamp Vienna 2015

Operable: Proper headings

F labels

Page 49: DrupalCamp Vienna 2015

Understandable: Page language

Page 50: DrupalCamp Vienna 2015

Understandable: Consistent Navigation

Page 51: DrupalCamp Vienna 2015

Robust: Compatibility

Page 52: DrupalCamp Vienna 2015

Q: How do I make sure my Backend is accessible?

Page 53: DrupalCamp Vienna 2015

Resource: Authoring Tools

Accessibility Guidelines (ATAG) 2.0

w3.org/TR/ATAG/

Page 54: DrupalCamp Vienna 2015

part A: Make the authoring tool user interface accessible

part B: Support the production of

accessible content

Page 55: DrupalCamp Vienna 2015

part A: Make the authoring tool user interface accessible

Page 56: DrupalCamp Vienna 2015

principle A.1: Authoring tool user

interfaces follow applicable accessibility

guidelines

Page 57: DrupalCamp Vienna 2015

principle A.2: Editing-views are

perceivable

Page 58: DrupalCamp Vienna 2015

principle A.3: Editing-views are

Operable

Page 59: DrupalCamp Vienna 2015

Guideline A.3.1: Provide keyboard access

to authoring features

Page 60: DrupalCamp Vienna 2015

Guideline A.3.2: Provide authors with

enough time

Page 61: DrupalCamp Vienna 2015

Guideline A.3.4: Enhance navigation and

editing via content structure

Page 62: DrupalCamp Vienna 2015

principle A.4: Editing-views are understandable

Page 63: DrupalCamp Vienna 2015

Guideline A.4.1: Help authors avoid and

correct mistakes

Page 64: DrupalCamp Vienna 2015

Guideline A.4.2: Document the user

interface, including all accessibility features

Page 65: DrupalCamp Vienna 2015

part B: Support the production

of accessible content

Page 66: DrupalCamp Vienna 2015

principle B.1: Fully automatic

processes produce accessible content

Page 67: DrupalCamp Vienna 2015

principle B.2: Authors are supported

in producing accessible content

Page 68: DrupalCamp Vienna 2015

Guideline B.2.3: Assist authors with managing

alternative content for non-text content

Page 69: DrupalCamp Vienna 2015

Guideline A.2.4: Assist authors with accessible templates

Page 70: DrupalCamp Vienna 2015

principle B.3: Authors are supported in

improving the accessibility of existing content

Page 71: DrupalCamp Vienna 2015

Guideline B.3.1: Assist authors in

checking for accessibility problems

Page 72: DrupalCamp Vienna 2015

Guideline B.3.2: Assist authors in

repairing accessibility problems

Page 73: DrupalCamp Vienna 2015

principle B.4: Authoring tools promote

and integrate their accessibility features

Page 74: DrupalCamp Vienna 2015

Q: How do I make sure that the experience is

accessible?

Page 75: DrupalCamp Vienna 2015

You achiEve the best results when…

Page 76: DrupalCamp Vienna 2015

Accessibility is not an afterthought

Page 77: DrupalCamp Vienna 2015

Makes the backend easy to use

Page 78: DrupalCamp Vienna 2015

No need to rebuild

Page 79: DrupalCamp Vienna 2015

Accessibility is an opportunity

Page 80: DrupalCamp Vienna 2015

Reach more people

Page 81: DrupalCamp Vienna 2015

makes your website easy(er) to understand

Page 82: DrupalCamp Vienna 2015

consistent layout H Navigation

Page 83: DrupalCamp Vienna 2015

Accessibility is A creative outlet

Page 84: DrupalCamp Vienna 2015

Produce the best video player UI

Page 85: DrupalCamp Vienna 2015

Take the available data and do something no one

expects

Page 86: DrupalCamp Vienna 2015
Page 87: DrupalCamp Vienna 2015

thank you. Eric Eggert

W3C/Web accessibility initiative [email protected] & @yatil

Fonts: Goodlife (Sans Condensed, Brush, Serif, Serif Bold), Aleo, Source code pro