UKOLN is supported by: From Web Accessibility to Web Adaptability Techshare 2009 conference, 17 September 2009 Brian Kelly UKOLN University of Bath Bath,

UKOLN is supported by:

From Web Accessibility to Web Adaptability

Techshare 2009 conference, 17 September 2009

Brian KellyUKOLNUniversity of BathBath, UK

http://www.ukoln.ac.uk/web-focus/events/conferences/techshare-2009/

This work is licensed under a Attribution-NonCommercial-ShareAlike 2.0 licence (but note caveat)

Acceptable Use PolicyRecording/broadcasting of this talk, taking photographs, discussing the content using email, Twitter, blogs, etc. is permitted providing distractions to others is minimised.

Tag for del.icio.us ‘techshare2009'

Email:[email protected]:http://twitter.com/briankelly/

Blog:http://ukwebfocus.wordpress.com/

About This TalkThis talk:

• Reviews limitations of WAI’s approaches to ‘universal accessibility’

• Describes development of a holistic approach to accessibility, developed for learning and cultural heritage contexts

• Introduces recent work on bringing previous work together under a ‘Web Adaptability’ framework

Intr

oduc

tion

Accompanying Paper

Talk based on “From Web accessibility to Web adaptability” paper by Brian Kelly, Liddy Nevile, Sotiris Fanou, Ruth Ellison, Lisa Herrod and David Sloan published in Disability and Rehabilitation: Assistive Technology journal, July 2009 Vol. 4, Issue. 4

Note: Due to copyright restrictions, access to this paper is restricted until July 2010

Accompanying PaperSummary of ideas provided in accompanying blog post on UK Web Focus blog

Definition“All people are disabled in some circumstances … disability is a social construct not an attribute of an individual. In particular, resource accessibility is an attribute of the matching, or otherwise, of a resource to a user’s individual needs and preferences, not an attribute of a resource” (my emphasis)

Convention on the Rights of Persons with Disabilities, United Nations. <http://www.un.org/disabilities/default.asp?navid=12&pid=150>

Note difference to WAI model which is based on resource attributes (the resource and the tools used to create & view the resource – WCAG, ATAG & UAAG)

6

The WAI ModelWAI has been tremendously successful in raising awareness of Web accessibility & providing guidelines.WAI guidelines are based on:

• WCAG (Web Content …)• ATAG (Authoring Tools ..)• UAAG (User Agents …)

Simple model to grasp. But is it appropriate for the future? Does it reflect:

• Differing definitions of accessibility• Diversity of users & user environments• Diversity of Web usage• Real-world technical environment and developments• Real-world political, cultural & economic contexts

WA

I App

roac

h

7

Limitations Of The WAI ModelThis model:

• Requires all three components to be implemented in order for the WAI vision to be achieved

• Is of limited use to end users who have no control over browser or authoring tools developments

• Is confusing – as many think WCAG is WAIHow does this model address:

• Delays in full conformance?• Real-world challenges in deploying new software

(issues of inertia, testing, costs, …)• Real world complexities

Is there a plan B in case this model fails to ever take off?Is it desirable to base legal requirements on an unproven theoretical framework? What if evidence reveals flaws in model?

WA

I App

roac

h

8

WCAG ConformancePage authors can only follow WCAG guidelines. Several surveys carried out using automated tools (which gives upper limit on accessibility)

• DRC report, 2004: 19% A, 0.6% AA conformance based on 1,000 UK Web sites

• UK Universities surveys (UKOLN, 2002, 2004): 43%/58% A, 2%/6% AA based on 160+ Web sites

Note that these figures aren’t of accessible Web site, only conformance with automated tests

ImplicationsThese low conformance levels can indicate:

• Organisations don't care• Guidelines are difficult to implement• Guidelines are inappropriate, misleading, wrong, …

WA

I App

roac

h

RNIB’s Alternative Approach“Greenwood also said that there was "no chance at all" of all public sector websites achieving a Level AA rating by December 2009, as set out in 'Delivering inclusive web sites'. …The RNIB … largely positive about the report's findings, claiming that the figures do not necessarily represent a widespread lack of accessibility. … a new additional qualitative assessment system [commissioned by RNIB] …136 councils (33%) rated by RNIB as satisfactory or excellent [8% according to WCAG]”

e-Access Bulletin, March 2009

Alte

rnat

ive

App

roac

h

10

Nitpicking?“This is just nit-picking! WCAG is valuable – don’t knock it!”WCAG is valuable, but we need to:

• Build a robust framework for the future• Reflect on experiences gained since 1999• Avoid dangers of inappropriate case law being set

Nightmare ScenarioCase taken to court in UK.Defence lawyers point out ambiguities & inconsistencies.Case lost, resulting in WCAG’s relevance being diminished.

WA

I App

roac

h

Today’s ScenarioWCAG AA is too difficult to achieve so organisations fail to deploy Web solutions.

11

Holistic Approach

1 Developing A Holistic Approach For E-Learning Accessibility, Canadian Journal of Learning and Technology, 2004, Vol. 30, Issue 3

This approach reflects an emphasis on blended learning (rather than just e-learning)

Kelly, Phipps & Swift1 developed a holistic framework for e-learning accessibilityThe framework:

• Focusses on the needs of the learner

• Requires accessible learning outcomes, not necessarily e-learning resources

An

Alte

rnat

ive

App

roac

h

12

Previous Work (1)Following on from first paper, a framework for applying WCAG in the real world (of flawed browsers, limited resources, etc) described at W4A 2005.

e.g. WAI model flawed due to poor take-up of ATAG & UAAG, so need for pragmatic advice

13

Previous Work (2)Application of our work in a wider context (e.g. cultural resources) described at W4A 2007.Paper:

• Prioritised people, policies & processes, rather than the resources

• Introduced the stakeholder model

• Coined the term ‘Accessibility 2.0’ to describe this approach

14

Universal Accessibility? Normal Cancer

The Great Masturbator by Salvador Dali (1929)

The Duck-RabbitCRAFT BREWERY

Note these aren’t edge cases for educational institutions, cultural heritage organisations, …

15

WAI LimitationsLimitations of WAI guidelines have been acknowledged (my emphasis):

“However, we recognize that standards are slow, and technology evolves quickly in the commercial marketplace. Innovation brings new customers and solidifies relationships with existing customers; Web 2.0 innovations also bring new types of professionals to the field, ones who care about the new dynamic medium. As technologies prove themselves, standardizing brings in the universality of the benefit, but necessarily follows this innovation. Therefore, this paper acknowledges and respects Web 2.0, discussing the issues and real world solutions.”

Accessibility of Emerging Rich Web Technologies: Web 2.0 and the Semantic Web. Cooper, M. W4A 2007

An

Alte

rnat

ive

App

roac

h

16

WCAG In ContextWCAG 2.0 states that Web resources must be:

• Perceivable • Operable• Understandable • Robust

But this should apply after we’ve decided what our purposes our, rather than constraining what we can or can’t do:

“Super Cally Go Ballistic, Celtic Are Atrocious”:Not universally understandable, not universally accessible, culturally-specific … but witty

Legislation: “take reasonable measure ..” Is bankrupting your company reasonable? Is failing to satisfy your user community reasonable? Is not providing resources reasonable?

17

Second LifeA video clip shows Judith, a user with cerebral palsy, using Second Life with a headwand.

“Do you think that this will be a really useful tool for people who are unable to get around, who have problems of mobility in real life?” “Yes, because you can have friends without having to go out and physically find them”.

The danger is that organisations will ban SL as they feel if fails to comply with accessibility guidelines.

Accessibility 2.0

18

Accessibility 2.0Need to build on WAI’s successes, whilst articulating a more sophisticated approach. Accessibility 2.0:

• User-focussed: It’s about satisfying user’s needs• Rich set of stakeholders: More than the author

and the user• Always beta: Accessibility is a process, not a

destination – we are always learning• Flexibility: There’s not just a single solution • Diversity: There is diversity in society’s views of

accessibility (e.g. widening participation, not universal accessibility)

• Blended solutions: Focus on ‘accessibility’ and not just ‘Web accessibility’

Accessibility 2.0

An

Alte

rnat

ive

App

roac

h

19

Accessible Web in Context

Web

WCAG+ATAG+UAAG=universal accessibility

• Motherhood and apple pie?

• Demonstrably flawed after 10 yearse.g. Lilley: “99.99999% of the Web was invalid HTML. W3C pretended that didn’t exist.”

• So 99.99999% of Web isn’t WCAG AA conformant!

The Pixel of Perfection

WAI.

20

Kevin Kelly

21

A Fresh Look At AccessibilityWe acknowledge that:

• Not everything on the Web will ever be accessible• Accessibility may not cross cultural, linguistic,

national and discipline boundaries• An individual does not need a universally

accessible resource; rather s/he wants a resource which is accessible to them

• Different communities may have different needs• Same person may have different needs at

different times and places• Let’s not talk about the accessibility of a resource• We find the term ‘inclusivity’ and ‘inclusive

approaches’ more useful than ‘accessible to people with disabilities’

An

Alte

rnat

ive

App

roac

h

Web AdaptabilityWe Adaptability term embraces such diversity and challenges:

• Solutions• Policies• Levels of resources• Definitions of disability, accessibility, …• Stakeholders and their varied requirements,

priorities, pressures, … • Change: technologies, policies, learning,

evidence, …• …

22

Web

Ada

ptab

ility

Alternative to a one-size-fit-all approach

Web Adaptability FrameworkThe framework embraces:

• The intended use of the service• The intended audience• The available resources• Technical innovations• Organisational policies• Definitions of accessibility• …

23

To avoid adaptability meaning doing whatever you fancy (e.g. IE-only sites) the adaptation needs to be implemented with context of a legal framework, reasonable measures, reputation management, social responsibility, …

Web

Ada

ptab

ility

Putting The User FirstThe way we were:

24

The

rule

s

The

solu

tion

The

user

Example“UK Government requires all government Web sites to comply with WCAG AA”

The context

The

user

Opt

imal

so

lutio

n

The

guid

elin

es

Where we should be:

Example• Involve user in design

process• Recognise the context• Then seek to apply

guidelines

Web

Ada

ptab

ility

25

Who’s Using These Approaches? (1)

Public library example:• Talk at national Public Library event (May 2004)• “And here’s a Flash-based game we’ve developed.

Easy to do, and the kids love it”• “What about accessibility?”• “Oh, er. We’ll remove it before the new legislation

becomes into force”Blended approach:

• “What’s the purpose of the game?”• “To keep kids amused for 10 mins, while parents

get books”• “How about building blocks or a bouncy castle as

an alternative? This is an alternative approach to problem, which doesn’t focus on disabilities”

Web

Ada

ptab

ility

26

Who’s Using These Approaches? (2)

Tate’s i-Map project: early example of an award-winning approach to providing access to paintings for visual impaired users

• It used Flash …

• … to allow users to ‘participate’ in the creation of the painting

Note this work was described in an award-winning paper on “Implementing A Holistic Approach To E-Learning Accessibility” paper by Kelly, Phipps and Howell (ALT-C, 2005)

Who’s Using These Approaches? (3a)

Videoing and audio recording and publishing is now cheap due to consumer products, network effect, ... Is it better to publish the video & audio now:

• Enhances impact or ides & diversity enriches access• Without resource, won’t be able to exploit future

technological innovation, crowd-sourcing, … Or suppress publication as this can infringe WCAG?

Web

Ada

ptab

ility

Who’s Using These Approaches? (3b)

Slidecast (slides and synched audio) of rehearsal of this talkBenefits:

• Backup in case I lose my voice, travel delays, …

• Delegates can view after event

• Can be shared with others

• Richer than slides on their own

• Enhances accessibility

But is it WCAG compliant?Should it be deleted in order to enhance WCAG-rating?

A Challenge For You!You have:

• An institutional repository• An open access policy, which encourages take-up by

others of your research reports and data & teaching & learning resources

But:• Research papers are in non-conformant PDFs &

learning resources are mostly PowerPoints & other proprietary formats.

What do you do:• Mandate use of HTML in repositories?• Switch off services until workflow issues resolved?• Or something else?

29

Web

Ada

ptab

ility

Web Adaptability approach:• Welcomes WCAG as valuable

set of guidelinesBut we:

• Feel standardisation based on resource characteristics is flawed

We:• Encourage standardisation of

mature and proven (evidence–based) solutions

• Welcome standardisation of processes

• Feel BSI PAS 78 provides a good basis for further work

What About Standards?

31

ConclusionsThis talk:

• Explores limitations of current approaches• Suggests alternative approaches

There’s a need:• For accessibility researchers & policy makers to

gather evidence on proposed solutions to accessibility

• To explore ways in which changes in our understandings can be adopted and deployed

Future work:• Need to critique the critique• Need to develop better models for change control• Need to learn from the past

32

QuestionsQuestions are welcome