Download to read offline
Uploaded byAdy Stokes
Accessibility Assumptions and Arguments AADays
The document discusses common misconceptions about accessibility, emphasizing that it is not only about disability but about inclusion for all users. It addresses assumptions such as accessibility being costly or complicated and presents arguments for why accessibility is essential for removing barriers and enhancing user experience. It also provides practical tips for implementing accessibility standards, such as testing websites and using inclusive design principles.
More Related Content
Similar to Accessibility Assumptions and Arguments AADays
Accessibility Assumptions and Arguments AADays
- 1. Accessibility: Assumptions & Arguments Ady Stokes @CricketRulz Agile& Automation Days 2018 linkedin.com/in/adystokes/ thebigtesttheory.com slideshare.net/adystokes/presentations
- 2. Accessibility, Assumptions &Arguments Agile and Automation Days 2018 2nd Assumption: • Accessibility issues only affect a small number of users Ady Stokes @CricketRulz thebigtesttheory.com
- 3. Accessibility, Assumptions &Arguments Agile and Automation Days 2018 • Glasses or contact lenses wearer • Zoomed in • None traditional keyboard or mouse • Used a device with only one hand Ady Stokes @CricketRulz thebigtesttheory.com
- 4. Accessibility, Assumptions &Arguments Agile and Automation Days 2018 • Glasses make text accessible/readable • Zoom (to 200%) is a Web Content Accessibility Guideline • none traditional keyboards and mouse are assistive technologies • Using with only one hand is a situational incapacity Ady Stokes @CricketRulz thebigtesttheory.com
- 5. 1st Assumption: Accessibility = Disability Accessibility, Assumptions& Arguments Agile and Automation Days 2018 Ady Stokes @CricketRulz thebigtesttheory.com
- 6. Accessibility, Assumptions &Arguments Agile and Automation Days 2018 Ady Stokes @CricketRulz thebigtesttheory.com The Reality is: Accessibility = Inclusion
- 7. Ady Stokes @CricketRulzthebigtesttheory.com • Microsoft Inclusive Design Toolkit Accessibility, Assumptions & Arguments Agile and Automation Days 2018
- 8. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Common Assumptions • Accessibility is costly • It affects a small number of users • It is only for people with disabilities • It is very complicated
- 9. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Accessibility is costly inclusivedesignprinciples.org
- 10. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Accessibility is costly
- 11. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 It affects a small number of users • There are estimated to be over 30 million blind and partially sighted people in geographical Europe • There are four times as many partially sighted people • 37 % of the EU-28 population aged 15 and over reported (moderate or severe) physical or sensory limitations Figures from European Blind Union and Eurostat
- 12. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 It affects a small number of users • 55 million adults between 15 and 65 years of age have literacy difficulties and are 'functionally illiterate.’ that’s 1 in 5 EU figures from eli-net.eu, ELINET Symposium 2018
- 13. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 It is only for people with disabilities
- 14. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Accessible to all Quadrants Understandable Content • Simple Language • No acronyms • No all capital words • Clear instructions
- 15. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Accessible to all Quadrants Inclusive Language • Optional title / gender • Empathy and respect • Everyone / Folks • They Them
- 16. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Accessible to all Quadrants Usability • Intuitive • Ergonomic • Uncomplicated • Clean and simple
- 17. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Accessible to all Quadrants Web Content Accessibility Guidelines Compliant • AA / AAA • Accessibility • Keyboard only use • Consistent headings
- 18. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Accessible to all Quadrants
- 19. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Using language that assumes who the users are or how they engage with the content is an accessibility issue
- 20. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 shouldIuseacarousel.com July 2013 http://shouldiuseacarousel.com/
- 21. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 It is very complicated • Small steps
- 22. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Arguments – Against Accessibility is hard
- 23. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Arguments – For Accessibility is hard for users
- 24. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Arguments – For The right thing to do
- 25. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Arguments – For Removes barriers to information and products, increasing profits and reputation
- 26. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Arguments – For The right thing to do
- 27. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Arguments – For Regulations and Fines mitigation
- 28. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018
- 29. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Alt-Text – remember this?
- 30. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Format Pictures for Alt Text
- 31. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Tips for tomorrow – Testing •Test your site using only a keyboard •Check images have alternative text •Check your links say where they take you
- 32. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Tips for tomorrow – Start talking about •Inclusive design •Accessibility •Empathy and inclusion •(ideally be an advocate for all)
- 33. Ady Stokes @CricketRulzthebigtesttheory.com Accessibility, Assumptions & Arguments Agile and Automation Days 2018 Tips for tomorrow – Start learning •Heydon Pickering •inclusive-components.design blog and book “He teaches you how to cater to every possible user (you never thought of) in witty and clever ways.” — Zell Liew, learnjavascript.today
- 34. Accessibility: Assumptions & Arguments Ady Stokes @CricketRulz Agile& Automation Days 2018 linkedin.com/in/adystokes/ thebigtesttheory.com Thank you for listening See next page for links to accessibility and inclusive design resources
- 35. Resources • https://inclusivedesignprinciples.org/ • https://www.microsoft.com/design/inclusive/ •http://www.karlgroves.com/2013/09/05/the-6-simplest-web- accessibility-tests-anyone-can-do/ • https://the-pastry-box-project.net/anne-gibson/2014-july-31 accessible personas • http://www.webaxe.org/ • https://wave.webaim.org/ testing tool, also as browser extensions • https://w3c.github.io/wcag21/guidelines/ web content accessibility guidelines • Many, many more resources available, you just have to go looking
Editor's Notes
- #3 We begin with the second biggest assumption I’ve encountered. Accessibility only affects a small number of users. And I think I know the reason I’d like to begin by asking for your indulgence and joining me in a very quick experiment You don’t have to, but as this is quite integral to this talk it could all go a bit wobbly if you don’t, so no pressure… Please stand if you are able or raise a hand. When up. Sit down if you answer yes to any of the following questions If they wear glasses or contact lenses when working with screens, using a phone, tablet Ever used zoom on a computer, laptop or mobile device A none traditional keyboard or vertical mouse Had to use a mobile phone one handed because you were carrying something Used a phone on a bus, train or in a car To all those now sitting, would any one consider themselves an accessibility user? I would, as there’s an adaption to the software or the environment for you to enable access
- #4 Please stand if you are able or raise a hand. When up. Sit down if you answer yes to any of the following questions If they wear glasses or contact lenses when working with screens, using a phone, tablet Ever used zoom on a computer, laptop or mobile device A none traditional keyboard or vertical mouse Had to use a mobile phone one handed because you were carrying something Used a phone on a bus, train or in a car To all those now sitting, would any one consider themselves an accessibility user? I would, as there’s an adaption to the software or the environment for you to enable access
- #5 Multiple issues can cause shaky hands including illness and disability But so can anxiety and other neurological issues So can alcohol So can being on a bus or train Anyone ever hit the wrong button on a phone screen? Generally this is because there’s little or no gap between them Padding is simple, looks better and adds accessibility for many situations
- #6 So lets talk about accessibility and the most common assumption I come across in conversations, writing, blogs etc. Accessibility = Disability. There are a lot of reasons for this. Some I’m aware of and I’m sure some I’m not. But it’s my belief that the number one reason for this is the only time we are talking about accessibility, is when we talk about the Web Content Accessibility Guidelines and whether our ‘thing’ complies or not. Sometimes this is a companies policy but more often it’s a client requirement, and that’s a shame. Used the right way, in the right context. Adherence to the guidelines in our software, in combination with a few other things can make everything better than it was, for little to no extra cost, and make us feel better about ourselves, while earning more money
- #7 So lets take a second and consider what should we mean when we talk about accessibility related matters? Definitely ensuring users with disabilities can access and use our products and services.
- #8 Hopefully you are realising that Accessibility is not just about people with disabilities There are lots of reasons people need to use software in unideal situations So lets look at some common assumptions
- #9 The most common accessibility assumptions. Let’s work our way through them
- #10 It can be if you only think about it at the end Using inclusive design and its principles is the simplest way forward for new projects
- #11 Barclays created this nice graphic based on the principles of inclusive design As you can see there’s nothing earth shattering here
- #12 Not everyone reads content Lots of people have issues hitting buttons, illness, disability on a bus Content that is understood by all needs to be targeted
- #13 Not everyone reads content Lots of people have issues hitting buttons, illness, disability on a bus Content that is understood by all needs to be targeted
- #14 As shown at the start it can cover a lot more than just disabilities but there are a few other things to consider if we want to make things truly inclusive Location, signal, screen size, old browsers, rural locations, low battery
- #15 Understandable content: average reading ages are lower than you would expect Usability: Simple is best. Carousels are hard for keyboard and screen readers and don’t deliver the benefits you expect (http://shouldiuseacarousel.com/) NEXT
- #16 Understandable content: average reading ages are lower than you would expect Usability: Simple is best. Carousels are hard for keyboard and screen readers and don’t deliver the benefits you expect (http://shouldiuseacarousel.com/) NEXT
- #17 Understandable content: average reading ages are lower than you would expect Usability: Simple is best. Carousels are hard for keyboard and screen readers and don’t deliver the benefits you expect (http://shouldiuseacarousel.com/) NEXT
- #18 Understandable content: average reading ages are lower than you would expect Usability: Simple is best. Carousels are hard for keyboard and screen readers and don’t deliver the benefits you expect (http://shouldiuseacarousel.com/) NEXT
- #19 Understandable content: average reading ages are lower than you would expect Usability: Simple is best. Carousels are hard for keyboard and screen readers and don’t deliver the benefits you expect (http://shouldiuseacarousel.com/) NEXT
- #20 Understandable content: average reading ages are lower than you would expect Not everyone is a Mr or Mrs. Folks rather than guys; Hours not man hours; Cleaner not cleaning lady Usability: Simple is best. Carousels are hard for keyboard and screen readers and don’t deliver the benefits you expect (http://shouldiuseacarousel.com/) NEXT
- #21 Usability: Simple is best. Carousels are hard for keyboard and screen readers and don’t deliver the benefits you expect (http://shouldiuseacarousel.com/) Jared Smith WEBAim director Source code says, ‘every time you use a carousel a kitten dies’
- #22 Using inclusive design takes the big bang out of accessibility, especially on new projects But not everyone will be starting from scratch. What about existing sites and application? While the new WCAG guidelines have been updated to include more areas such as mobile going step by step can give you wins. Don’t try to look at everything at once. Start small. Can you do everything using only a keyboard? Do all your images have alternate text defined? Is the new ‘thing’ you are about to add aligned with existing stuff and consistent? Remove that carosel!
- #23 Accessibility is not just about people with disabilities There are lots of reasons people need to use software in unideal situations So lets look at some common assumptions
- #24 Accessibility is not just about people with disabilities There are lots of reasons people need to use software in unideal situations So lets look at some common assumptions
- #26 Accessibility is not just about people with disabilities There are lots of reasons people need to use software in unideal situations So lets look at some common assumptions
- #27 Accessibility is not just about people with disabilities There are lots of reasons people need to use software in unideal situations So lets look at some common assumptions
- #28 Target $6 million fine for no Alt-Text Multiple instances of law-suits pertaining to accessibility issues
- #29 Don’t be like these folks. We can and must do better! American Disabilities Act lawsuits growing https://nrf.com/blog/ada-website-lawsuits-growing-problem-retailers
- #30 As you begin your learning journey of accessibility
- #31 You can do this on Facebook, Twitter, for presentations, PDFs as well as website images.
- #34 Can’t recommend Heydon’s blog and book highly enough