39
Web Accessibility - why we are still here? Dr Vladimir Tomberg Senior Research Fellow Tallinn University 24 November 2016 Riga Accessibility Meetup 1

My talk at Riga 2016 Web Accessibility Meetup

Embed Size (px)

Citation preview

Page 1: My talk at Riga 2016 Web Accessibility Meetup

1

Web Accessibility - why we are still here?

Dr Vladimir TombergSenior Research Fellow

Tallinn University

24 November 2016Riga Accessibility Meetup

Page 2: My talk at Riga 2016 Web Accessibility Meetup

2

Accessibility is a law•Banks, energy providers and public bodies should be

subject to web accessibility rules;• Just a third of the 761,000 public sector websites in

the EU currently conform to "international web-accessibility standards“;

Source: http://www.out-law.com

Page 3: My talk at Riga 2016 Web Accessibility Meetup

3

EU Directive on the accessibility of public sector bodies' websites•Organizations whose websites would be subject to

the new rules would have one year from the introduction of the new laws to ensure that new content added to their sites complies with the new rules;•They would have three years within which to adapt

existing content and five years if that content is "live audio“

28 Feb 2014

Source: http://www.out-law.com

Page 4: My talk at Riga 2016 Web Accessibility Meetup

4

Web accessibility is nicely standardized

Page 5: My talk at Riga 2016 Web Accessibility Meetup

5

WCAG 2.0•Web Content Accessibility Guidelines ─ guidelines

and techniques for making websites and web applications accessible to people with disabilities;

•WCAG consist of 4 principles and 12 guidelines and many success criteria

Page 6: My talk at Riga 2016 Web Accessibility Meetup

6

Principles•At the top are four principles (POUR) that provide

the foundation for Web accessibility: • Perceivable;

• Operable;

• Understandable;

• Robust

Page 7: My talk at Riga 2016 Web Accessibility Meetup

7

Guidelines•Guidelines are under the principles; •The 12 guidelines provide the basic goals that

authors should work toward in order to make content more accessible to users with different disabilities

Page 8: My talk at Riga 2016 Web Accessibility Meetup

8Image: http://www.projectrics.org

Page 9: My talk at Riga 2016 Web Accessibility Meetup

9

Success Criteria•For each guideline, testable success criteria are

provided to allow WCAG 2.0 to be used;• In order to meet the needs of different groups and

different situations, three levels of conformance are defined: •A (lowest), •AA, and •AAA (highest).

Page 11: My talk at Riga 2016 Web Accessibility Meetup

11

WAI-ARIA•Accessible Rich Internet Applications Suite – a

framework for adding attributes to web documents in order to make actionable elements accessible to people using assistive technology

Page 12: My talk at Riga 2016 Web Accessibility Meetup

12

Different input devices

Page 13: My talk at Riga 2016 Web Accessibility Meetup

13

Challenges for accessibility

1. Awareness2. Responsibility

3. Avoiding Ignorance

Page 14: My talk at Riga 2016 Web Accessibility Meetup

14

Challenges for accessibility1. Awareness (Education, empathy modeling)

Image courtesy to http://err.ee

Page 15: My talk at Riga 2016 Web Accessibility Meetup

15

Challenges for accessibility1. Awareness2. Responsibility

Page 16: My talk at Riga 2016 Web Accessibility Meetup

16

Typical training requirements for different professional roles

Executive Manager

Middle Manager

Software & Hardware Developer

Designer Reviewer & Tester

(QA)

Marketing & Communication

Human Resources

User Interfaces S O D D O S S

User-Centred Design S O O D D O S

Assistive Technology S S O D D S S

Web Applications S O D D D S S

Summary (S) Overview (O) Details (D)

Page 17: My talk at Riga 2016 Web Accessibility Meetup

17

Challenges for accessibility

1. Awareness2. Responsibility 3. Avoiding Ignorance

For whom is this ramp?

Page 18: My talk at Riga 2016 Web Accessibility Meetup

18

I guess that is the only one possible answer

Page 19: My talk at Riga 2016 Web Accessibility Meetup

19

Measuring awareness on accessibility standardsA study

Page 20: My talk at Riga 2016 Web Accessibility Meetup

20

Demographic distribution

• 92 Participants • 16 countries

Page 21: My talk at Riga 2016 Web Accessibility Meetup

21

Industry

Public Sector

Academia (university, etc.)

Startup

Self-employed

Industry (Insurance, Baking, Consulting, etc.)

Other

Software company

0 10 20 30 40 50 60 70

Page 22: My talk at Riga 2016 Web Accessibility Meetup

22

Job

Mobile Developer

Project Manager

Technical Lead

Back-end Developer

Application Developer

Senior Back-end Developer

Senior Front-end Developer

Other

Front-end Developer

Interaction Designer

0 5 10 15 20 25 30 35 40

Page 23: My talk at Riga 2016 Web Accessibility Meetup

23

Measuring Awareness

Page 24: My talk at Riga 2016 Web Accessibility Meetup

24

Do you consider yourself aware about accessibility issues on the Web?

I am expert in this field I know quite much about it

I don't know anything about it

I know something, but not so much

0

10

20

30

40

50

60

Page 25: My talk at Riga 2016 Web Accessibility Meetup

25

Writing accessible code enables me to produce higher quality software

Strongly Agree Agree Neither agree nor disagree

Disagree Strongly Disagree0

5

10

15

20

25

30

35

Page 26: My talk at Riga 2016 Web Accessibility Meetup

26

I am aware of what are the WCAG & WAI ARIA specifications

WCAG WAI ARIA

22

70

Yes No

32

60

Yes No

Page 27: My talk at Riga 2016 Web Accessibility Meetup

27

Measuring Responsibility

Page 28: My talk at Riga 2016 Web Accessibility Meetup

28

My colleagues always use accessibility standards and guides in their work

Strongly Agree Agree Neither agree nor disagree

Disagree Strongly Disagree0

5

10

15

20

25

30

Page 29: My talk at Riga 2016 Web Accessibility Meetup

29

Most of developers I know, consider no real necessary in use of accessible technologies

Strongly Agree Agree Neither agree nor disagree

Disagree Strongly Disagree0

5

10

15

20

25

30

35

Page 30: My talk at Riga 2016 Web Accessibility Meetup

30

Do you use sometimes WCAG guidelines in your projects?

17

15

Yes No

Page 31: My talk at Riga 2016 Web Accessibility Meetup

31

What was a purpose for you to use WCAG? 

I think that it is important

It was a project requirement from a client

It is standard practice of our development process

It is regulated by national law

0 1 2 3 4 5 6 7 8 9

Page 32: My talk at Riga 2016 Web Accessibility Meetup

32

Do you use sometimes WAI ARIA guidelines in your projects?

8

14

Yes No

Page 33: My talk at Riga 2016 Web Accessibility Meetup

33

Ignorance

Page 34: My talk at Riga 2016 Web Accessibility Meetup

34

It is very time consuming task to learn about accessible technologies

Strongly Agree Agree Neither agree nor disagree

Disagree Strongly Disagree0

5

10

15

20

25

30

35

Page 35: My talk at Riga 2016 Web Accessibility Meetup

35

Using accessibility standards increases need for communications among developers

Strongly Agree Agree Neither agree nor disagree

Disagree Strongly Disagree0

5

10

15

20

25

30

35

40

Page 36: My talk at Riga 2016 Web Accessibility Meetup

36

My organization provides libraries that already contain required accessible markup in code

Strongly Agree Agree Neither agree nor disagree

Disagree Strongly Disagree0

5

10

15

20

25

30

Page 37: My talk at Riga 2016 Web Accessibility Meetup

37

Participate in my study, please!

https://goo.gl/60rp2d

Page 38: My talk at Riga 2016 Web Accessibility Meetup

38

Global Accessibility Awareness Day

Every 3th Thursday of May

http://www.estchi.org/gaad/

Page 39: My talk at Riga 2016 Web Accessibility Meetup

39

Thank you!Email: [email protected]