Main actions to improve accessibility in open source projects, OW2con16, Paris.

18
IMPROVE ACCESSIBILITY IN YOUR ORGANIZATION ARMONY ALTINIER

Transcript of Main actions to improve accessibility in open source projects, OW2con16, Paris.

Page 1: Main actions to improve accessibility in open source projects, OW2con16, Paris.

IMPROVE ACCESSIBILITY IN YOUR ORGANIZATION

ARMONY ALTINIER

Page 2: Main actions to improve accessibility in open source projects, OW2con16, Paris.

INTRODUCTION

Introduction

Accessibility as a Process

Compliance &Accessibility

ReasonableAccommodation

Conclusion

>

Page 3: Main actions to improve accessibility in open source projects, OW2con16, Paris.

3

Outline

▶ Accessibility as a Process

▶ Compliance & Accessibility

▶ Reasonable Accommodation

Page 4: Main actions to improve accessibility in open source projects, OW2con16, Paris.

ACCESSIBILITY AS A PROCESS

Introduction

Accessibilityas a Process

Compliance &Accessibility

ReasonableAccommodation

Conclusion

>

Page 5: Main actions to improve accessibility in open source projects, OW2con16, Paris.

5

The Role of the Accessibility Manager

▶ Accessibility Manager : Accountable for theAccessibility on the Organization

• R.A.C.I. → makes the final decision, not doing thejob

Page 6: Main actions to improve accessibility in open source projects, OW2con16, Paris.

6

The 3 steps of the Accessibility Process

▶ Diagnostic

▶ Repare

▶ Improve

Page 7: Main actions to improve accessibility in open source projects, OW2con16, Paris.

7

Digital Accessibility,a Never-ending process

▶ The major importance of NRT –Non‑Regression Testing for Accessibility!

• Use Accerciser or other tools

Page 8: Main actions to improve accessibility in open source projects, OW2con16, Paris.

COMPLIANCE & ACCESSIBILITY

Introduction

Accessibility as a Process

Compliance &Accessibility

ReasonableAccommodation

Conclusion

>

Page 9: Main actions to improve accessibility in open source projects, OW2con16, Paris.

9

“Accessibility Supported”

▶ The WCAG Definition:“supported by users' assistive technologies aswell as the accessibility features in browsersand other user agents”

▶ P.O.U.R.

• Perceivable

• Operable

• Understandable

• Robust

Source: https://www.w3.org/TR/WCAG20/

Page 10: Main actions to improve accessibility in open source projects, OW2con16, Paris.

10

Accessibility Non‑Compliance = Bug

▶ “Universal Design”

• A bug for one person must be considered as a bugfor everyone

▶ Know your product, adopt the user viewpoint

• Identify showstoppers

Page 11: Main actions to improve accessibility in open source projects, OW2con16, Paris.

REASONABLE ACCOMMODATION

Introduction

Accessibility as a Process

Compliance &Accessibility

ReasonableAccommodation

Conclusion

>

Page 12: Main actions to improve accessibility in open source projects, OW2con16, Paris.

12

Inclusion, a Human Right

“Discrimination on the basis of disability”includes denial of reasonable accommodation

Page 13: Main actions to improve accessibility in open source projects, OW2con16, Paris.

13

“Reasonable accommodation”, the UN Definition

“Reasonable accommodation” meansnecessary and appropriate modification andadjustments not imposing a disproportionateor undue burden, where needed in a particularcase, to ensure to persons with disabilities theenjoyment or exercise on an equal basis withothers of all human rights and fundamentalfreedoms

Source : CRPD – http://ur1.ca/ps31g

Page 14: Main actions to improve accessibility in open source projects, OW2con16, Paris.

14

Prioritizing axes

▶ 2 axes:

• User impact: “necessary and appropriate”

• Cost: "not imposing a disproportionate or undueburden”

Page 15: Main actions to improve accessibility in open source projects, OW2con16, Paris.

15

The 4 Priority Fields of Digital Accessibility

Page 16: Main actions to improve accessibility in open source projects, OW2con16, Paris.

CONCLUSION

Introduction

Accessibility as a Process

Compliance &Accessibility

ReasonableAccommodation

Conclusion>

Page 17: Main actions to improve accessibility in open source projects, OW2con16, Paris.

17

3 Key Points

▶ Insource Digital Accessibility as one of your Organization Process

▶ Ckeck small, check often, never stop

▶ Identify the Core functionalities of your product,on the user’s side, make them work for all

Page 18: Main actions to improve accessibility in open source projects, OW2con16, Paris.

18

It’s OK if you try and fail

Source: https://www.flickr.com/photos/107892497@N03/10722810504