Presentation given by Jonathan Hassell (Accessibility Editor, Digital Curriculum for BBC New Media) and Giles Colborne (Director, cx partners) at BSI accessibility event in 2005.
Covers: what are 'reasonable steps' to ensure your site is accessible; comparison of 'blind following of standards & conformance badges' approach to accessibility with user-centred design (based on ISO 9421-12 standards for measuring usability and ISO 13407 user-centred design process); comparison of cost-benefits of various usability & accessibility testing methods to assure your site meets your users' needs.
08448380779 Call Girls In Greater Kailash - I Women Seeking Men
Â
2005: Accessibility: which site production standards and testing methods will give maximum return on investment
1. What standards do you need to meet for your
site to be accessible?
Which methods will give maximum ROI?
Dr Jonathan Hassell Giles Colborne
Accessibility Editor, Digital Curriculum Director,cxpartners
BBC New Media President,UK UPA
Presentation to
BSI Accessibility conference
12/11/2011 11/12/2011 7/7/05 v0.19
jonathan.hassell@bbc.co.uk
2. What weâll be talking about
⢠Accessibility and âreasonablenessâ
⢠Common approach (stereotyped) vs. our suggested approach (UCD)
⢠Standards:
â Is there an accepted Industry Standard?
â Other standards/guidelines and codes of practice
â Rolling your own
⢠Testing:
â Test it and put a badge on it
â automated vs. manual testing
â self-check v audit
â acceditation
â accessible v usable
⢠User-Centred Design
â ISO Standards for measuring usability & UCD process
â Testing methods â cost vs. benefits
⢠Case studies
â Case study â testing wireframes
â Case study â tables (guidelines vs. results of testing)
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 22
Š BBC 2005
3. Accessibility and âreasonablenessâ
⢠DDA:
â 1999: aim to prevent discrimination against disabled people for 'goods
and servicesâ
â code of practice (2002) clarification to specifically include
websites, within the provision of 'goods and services'
â DDA requires âreasonableâ steps to ensure websites are accessible to a
disabled audience
⢠So what is âreasonableâ?
â depends on the size of your site, budget for site, size of organisationâŚ
â need to be clear who the site is for, and how you are going to support
different groups of users to use the siteâŚ
â some accessibility features are more expensive than othersâŚ
â ROI: make sure the money you spend actually makes a difference
⢠But for legal guidanceâŚ
see talk on Accessibility & The Law
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 33
Š BBC 2005
4. Common approach (stereotyped)âŚ
⢠you get your technical people to read some
guidelines
⢠they decide what they can do and do it
⢠they test it with an automated accessibility
checker
⢠they put a badge on the site to let people know
they checked it (so it must be accessible)
⢠you breathe a sigh of relief that youâre not going
to be sued (you hope)
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 44
Š BBC 2005
5. Purpose of accessibility
⢠Always keep in mindâŚ
⢠the purpose of
accessibility is to
make things easier for
all of your (clientâs)
audience â start and
end with them in
mindâŚ
⢠the internet can be a great
enabler for disabled people if
you use it right
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 55
Š BBC 2005
6. Our suggested approach (UCD)âŚ
⢠you work out who is going to use the site
⢠you get (reps of) your users in to capture their requirements
⢠you form a policy based on which of those requirements your site
can reasonably support
⢠you produce the site against standards/guidelines
⢠but you also get those users to test the site
â preferably iteratively, as you go
⢠so when it goes live, youâre sure itâs accessible to those users you
have decided you can support
â and, as a side-effect, you breathe a sigh of relief that youâre not going to
be sued
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 66
Š BBC 2005
7. Background: accessibility is a partnership
to make a website
accessible, you need all of
the following to work
together:
Website creators
Assistive technology creators
(e.g. Freedom
Scientific, ReadPlease)
Operating system creators
(e.g. Microsoft, Apple)
Disability assessment
agencies
(e.g. AbilityNet, RNIB)
Browser creators
(e.g. Microsoft, Opera)
comms via W3C-WAIâŚ
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 77
Š BBC 2005
8. Standards:
Is there an accepted industry standard?
⢠legal answer = no
⢠but in practiceâŚ
â see W3Câs WAI guidelines:
⢠WCAG â technical guidelines for site
developers
â v1⌠v2
⢠ATAG â guidelines for creation of site maintenance
tools (incl. CMSs)
⢠UAAG â guidelines for browser, OS, assistive
technology manufacturers
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 88
Š BBC 2005
9. Standards:
other standards, guidelines, codes of practice
⢠InternationalâŚ(W3C)
⢠vs NationalâŚ
â PAS 78: Guide to good practice in designing accessible websites
⢠vs Organisational (roll your own)âŚ
â e.g. BBCâs @ http://bbc.co.uk/guidelines/newmedia/accessibility
â Cabinet Officeâs Guidelines for UK government websites
â IBMâs @ http://www-306.ibm.com/able/guidelines/
â can be useful but be careful when doing thisâŚ
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 99
Š BBC 2005
10. How to change the culture of your production
teams / clients â awareness, motivation
⢠Start with your staff⌠then go to your clientsâŚ
⢠Make it personal: ⢠Make it real:
â get an external
agency to do a survey â send all your staff on an
of your siteâs Accessibility Awareness
accessibility, including course
video-taping of real
users using the site â provide background &
â See the Accessibility motivation for staff & clients
Study of bbc.co.uk for (DDA etc.)
inspiration (available â provide experience of
from:
http://www.bbc.co.uk/ assistive technologies
commissioning/bbci/w â show the videos of real users
ebsites.shtml) having problems using the site
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 10
10
Š BBC 2005
11. How to channel buy-in into producing a
better site â standards & guidelines
⢠create/identify accessibility standards & guidelines for your sites
â good start: WAI or the BBC Accessibility Standards (from
http://www.bbc.co.uk/commissioning/newmedia/websites.shtml)
â make sure your standards support your / your clientsâ audiences and production
processes â get your staff to create them
â be pragmatic - for each standard considerâŚ
⢠is it âreasonableâ?
⢠benefit: does it actually help disabled audiences?
â does it hinder other audiences?
⢠cost: what aspects of production does it affect?
⢠communicate them well to staff
⢠provide a group/someone who can answer specific accessibility questions
as they crop up in practice
⢠whenever possible, encode the standards in your production tools, so that
staff cannot get things wrong
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 11
11
Š BBC 2005
12. Testing: check it and put a badge on it
⢠DIY - check your conformance
yourself and award yourself a
badgeâŚ
⢠Use an automated site
validation tool and use the
badge it awards youâŚ
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 12
12
Š BBC 2005
13. Testing:
Automated vs. manual testingâŚ
⢠automated tools can be useful
⢠BUTâŚ
⢠listen to real people, rather than
automated tools/checklists
âThese tools are like spell-checkers; you wouldnât send out
a spell-checked document that wasnât manually proof-
read as wellâ
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 13
13
Š BBC 2005
14. Testing: Self-check vs. audit
⢠are you really experienced enough to do
it?
⢠would you be able to tell the difference
between:
â a problem which is a limitation of a
screenreader, or
â a problem which is your siteâs problemâŚ
⢠get in an expertâŚ
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 14
14
Š BBC 2005
15. Testing: what accreditation could you
get from the experts?
⢠currently no UK government recognised
accreditation (quality mark) scheme for website
accessibility
⢠What you can apply for now:
â See it Right mark (between WCAG A and AA)
⢠Forthcoming:
â EuroAccessibility Consortium
(http://www.euroaccessibility.org/)
â supportEAM (http://support-eam.org/)
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 15
15
Š BBC 2005
16. Testing: user-testing
- accessible vs. usable
⢠test with disabled users
â many options:
recruit & adminster yourself => ask a lab to do it for you
⢠a site can be âaccessibleâ but impossible to use
â which is no use to anyone (incl. your non-disabled users)
⢠use user/accessibility testing to pick up your usability
problems too
â include disabled users in your wider user-testing panel rather
than just do accessibility testing
⢠and make sure you plan in time to act on the resultsâŚ
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 16
16
Š BBC 2005
18. ISO 9421-12: Measuring usability
Satisfaction Effectiveness
Efficiency
Identify key tasks
Identify key disabled audiences
How well can your disabled users complete tasks on your web site?
19. ISO 9421-12: Measuring usability
Effectiveness
Satisfaction
Efficiency
How often can disabled users complete each task?
- Task completion rate
How well can they complete each task?
- Degree of completion
- Error rates
20. ISO 9421-12: Measuring usability
Satisfaction Effectiveness
Efficiency
How much effort does it take to complete each task?
- Number of keystrokes / clicks
- Time taken
- Pauses
21. ISO 9421-12: Measuring usability
Satisfaction
Effectiveness
Efficiency
Is user satisfied with the experience
- What is an appropriate experience?
- Different for education, banking, buying CDs, entertainment
- Does the experience fit with your brand values?
- Perceived efficiency
- Perceived effectiveness
22. ISO 9421-12: Measuring usability
Effectiveness
Satisfaction
Efficiency
Different systems need a different balance of these elements
Web sites are often self-service
Effectiveness and satisfaction dominate measures of web site usability
23. ISO 9421-12: Measuring usability
Effectiveness
Satisfaction
Efficiency
But for disabled users, efficiency becomes a massive problem
Improving accessibility can be about improving efficiency for disabled
users
24. ISO 9421-12: Measuring usability
45
40
35
30
25
20
15
10
5
0
Effectiveness Efficiency Satisfaction
Measures are only meaningful when you compare them
So measure at least twice
For instance
- Proposed site versus competitors
- Proposed site versus current site
25. Usability testing methods
Quality of data
User testing
Remote testing
User reviews / interviews
Expert walkthrough
Heuristics
Testing with assistive technologies
Automated testing
Cost
26. ISO 13407: The user centred design process
Plan user
Produce
centred
prototype Success!
design
s
activities
Test
Specify solutions
goals with
users
Specify
context
of use
27. Can you really test wireframes?
Exterior
Menu for exterior features -
link to other zones
Drag the mouse to spin the car.
Labels zoom forward and back
Feature 1 Click on label to explore
Feature 2
feature
Click on action nav to order
brochure
Performance
Image of car
Interior
360 spin
Feature 3
AcmeCar jingle
Test drive | Brochure | Downloads Acme
None
28. Can you really test wireframes
Main nav
Sub nav (features)
Call to action
Feature 1
Feature 2
Main nav
Interior
Exterior
Performance
Performance
Content Main content
Sub nav
Interior
Feature 1 Logo
Feature 2
Feature 3
Feature 3
Test drive | Brochure | Downloads AcmeCar
Logo
Call to action
29. Case study: user-testing vs. slave to
guidelinesâŚ
⢠e.g. tablesâŚ
â WAI level 1 requires HTML
labelling of all table cells
â butâŚ
⢠user-testing reveals this
doesnât produce âbetter tablesâ
for screenreader browsing
⢠this requires knowledge of
special table-browsing mode in
JAWS
â tables are actually more usable
for screenreader users if they
are âlinearâ
⢠which is WAI level 2
â example: BBC weather site
⢠before⌠and after
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 29
29
Š BBC 2005
30. Other useful additions to your site
provide accessibility
information/help:
â include information on:
⢠browser/OS settings
⢠assistive technologies
â or link toâŚ
⢠BBC & AbilityNetâs forthcoming My
Web My Way
(http://www.bbc.co.uk/accessibility/)
ask for accessibility
feedback:
â to further inform your
understanding of how people
really use your website
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 30
30
Š BBC 2005
31. Thanks for listening
Any questionsâŚ
Contacts:
jonathan@hassellinclusion.com
giles.colborne@cxpartners.co.uk
12/11/2011 jonathan.hassell@bbc.co.uk
07/07/05 jonathan@hassellinclusion.com 31
31
Š BBC 2005