Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Challenging Accessibility Assumptions: Screen Readers

Challenging Accessibility Assumptions: Screen Readers

Webinar for Knowbility's 2021 Accessibility Series

If you don’t understand accessibility and how it affects your project, you’re setting the stage for budget overruns, missed deadlines and unfulfilled requirements. Challenge your assumptions and learn how role-based accessibility can lead to more efficient and effective projects!

With a focus on screen readers, learn where accessibility fits into the project life cycle and when, as well as who is responsible for accessibility decisions.

Emily Lewis

June 13, 2021
Tweet

More Decks by Emily Lewis

Other Decks in Business

Transcript

  1. 2021 Accessibility Series • February 22 • 10-11:30am Central
    Challenging Accessibility
    Assumptions: Screen Readers
    #AccessibilitySeries

    View full-size slide

  2. • Email:
    [email protected]
    • LinkedIn:
    www.linkedin.com/in/emilyplewis
    • Twitter:
    @emilylewis
    Connect!

    View full-size slide

  3. Digital Project Management

    View full-size slide

  4. Managers
    Team Leads
    Directors
    Coordinators
    Owners
    Executives
    Who’s Responsible?

    View full-size slide

  5. Lack of support from the top
    Misunderstandings about requirements
    Poor hiring and outsourcing
    Projects over budget
    Missed milestones, late launches
    Accessibility fades over time
    Developers are struggling
    Stakeholders are confused
    Challenges & Risks

    View full-size slide

  6. Accessibility Leaders

    View full-size slide

  7. • Screen reader user experience
    • What accessibility is
    • When, where and how accessibility fits into the project life cycle
    • Who is responsible for accessibility
    • How much accessibility is built into web trends
    Assumptions

    View full-size slide

  8. • What is accessibility?
    • Why does it matter?
    • Where does it fit into the project lifecycle?
    • Who is responsible for accessibility?
    Become Informed

    View full-size slide

  9. What Is Accessibility?

    View full-size slide

  10. It’s About People

    View full-size slide

  11. Can people with disabilities get the
    same information, perform the same
    interactionsand function as others
    with comparable ease?

    View full-size slide

  12. Assumption #1
    Why people use screen readers

    View full-size slide

  13. “Screen reader users are blind”
    “Only people who have trouble seeing need a screen reader”
    Also Known As (AKA)

    View full-size slide

  14. • Blind
    • Low vision
    • Cognitive disabilities
    • Learning disabilities
    • Help with small print in
    documents that can’t be scaled
    • Prefer audio over text
    Screen Reader Users
    Web Accessibility Perspectives Videos:
    www.w3.org/WAI/perspective-videos

    View full-size slide

  15. Assumption #2
    How people use screen readers

    View full-size slide

  16. “Screen reader users don’t use the keyboard”
    “Why does a screen reader user need to use a mouse?”
    AKA

    View full-size slide

  17. • Mouse
    • Keyboard
    • Switch
    • Screen magnification
    • Resizing/zooming
    • Braille displays
    Screen Reader Software

    View full-size slide

  18. Assumption #3
    Who your users are

    View full-size slide

  19. “Our users are only interested in wheelchair access”
    “We don’t have blind customers”
    ”People with disabilities don’t visit our website”
    AKA

    View full-size slide

  20. • 9.8 million US adults with more than one disability
    • Consumer needs are varied
    Adults with One or More Functional Disabilities — United States, 2011–2014:
    www.cdc.gov/mmwr/volumes/65/wr/mm6538a1.htm
    Diversity

    View full-size slide

  21. • $490 billion total disposable income
    • Consumer loyalty
    A Hidden Market: The Purchasing Power of Working-Age Adults With
    Disabilities: www.air.org/system/files/downloads/report/Hidden-Market-
    Spending-Power-of-People-with-Disabilities-April-2018.pdf
    Purchasing Power

    View full-size slide

  22. Assumption #4
    WCAG is enough

    View full-size slide

  23. “WCAG means we are accessible”
    “We are WCAG compliant and safe from lawsuits”
    AKA

    View full-size slide

  24. • Provides a path towards accessibility
    • Incorporated in legislation across the world
    • Defines the bare minimum for accessibility
    Important Standards

    View full-size slide

  25. Can people with disabilities get the
    same information, perform the same
    interactionsand function as others
    with comparable ease?

    View full-size slide

  26. Neil Lenane
    Talent Acquisition/Diversity and Inclusion Leader
    Progressive Insurance
    If you do not intentionally include,
    you unintentionally exclude.

    View full-size slide

  27. • 69% of online shoppers with access needs leave sites due to difficulties
    • 75% will pay more for an item on an accessible website
    • 86% only shop on sites they know to be free of barriers
    The Click-Away Pound Report 2019:
    www.clickawaypound.com/downloads/cap19final0502.pdf
    Don't Leave Money on the Table

    View full-size slide

  28. • 6 times more costly during development than during design
    • 15 times more costly during testing
    How much do bugs cost to fix during each phase of the SDLC?
    www.synopsys.com/blogs/software-security/cost-to-fix-bugs-during-each-
    sdlc-phase
    Improve Efficiency

    View full-size slide

  29. • More than 11,000 ADA Title III Lawsuits in 2019
    • Litigation is expensive and damages reputations
    ADA Title III Lawsuits Hit Another All-Time High in 2019:
    www.hrdive.com/news/ada-title-iii-lawsuits-hit-another-all-time-high-in-
    2019/573393
    Reduce Legal Risk

    View full-size slide

  30. Assumption #5
    Accessibility for screen readers is
    enough

    View full-size slide

  31. “We added ARIA”
    “We tested with JAWS”
    AKA

    View full-size slide

  32. • Diverse screen reader users
    • Misunderstanding barriers
    Inclusive Accessibility

    View full-size slide

  33. • No impact on keyboard or mouse
    • No ARIA is better than bad ARIA
    The WebAIM Million:
    webaim.org/projects/million/#aria
    The Truth About ARIA

    View full-size slide

  34. Assumption #6
    Where accessibility fits in the
    project lifecycle

    View full-size slide

  35. “The developers are taking care of accessibility”
    AKA

    View full-size slide

  36. • Discovery
    • Planning
    • Content strategy
    • Information architecture
    • Copywriting and editing
    • User experience design
    • Visual design
    • Front-end development
    • Back-end development
    • Content entry
    • Quality assurance
    • Maintenance
    All Phases

    View full-size slide

  37. • Executive / C Suite
    • Project / Product Managers
    • Content Strategists / Information
    Architects
    • Copywriters / SMEs / Content
    Authors
    • Designers
    • Front-end Developers
    • Back-end / CMS Developers
    • Quality Assurance
    • Contractors / Vendors
    Role-based Accessibility

    View full-size slide

  38. Collaboration

    View full-size slide

  39. • Owner/Executive: budget, hiring
    • Project manager: communication,
    resource
    • Vendor: 3rd-party transcription
    • Content author: support transcription
    • Designer: look and feel
    • Developer: code
    • QA: testing
    Captions for Video
    WCAG 1.2.2 Captions (Prerecorded):
    www.w3.org/WAI/WCAG21/Understanding/captions-prerecorded.html

    View full-size slide

  40. Assumption #7
    Who is responsible for
    accessibility decisions

    View full-size slide

  41. “The developers know the standards”
    “Our tech team lead has the final say”
    AKA

    View full-size slide

  42. Primary Decision-maker
    • Content author
    Alt Text for Images
    Secondary Decision-maker
    • Visual designer
    Contributor
    • Manager
    WCAG 1.1.1 Non-text content:
    www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html

    View full-size slide

  43. Assumption #8
    Web trends are accessible

    View full-size slide

  44. “Google does it”
    “Bootstrap says it’s accessible”
    AKA

    View full-size slide

  45. • Carousels that don’t provide context for screen reader users
    • Media without alternative content
    • Form controls that can’t be used with the keyboard
    Be Informed, Double-check

    View full-size slide

  46. “… it should be perfectly possible to create websites and applications with
    Bootstrap that fulfill WCAG 2.0 (A/AA/AAA), Section 508 and similar
    accessibility standards and requirements.”
    Bootstrap Accessibility:
    getbootstrap.com/docs/4.0/getting-started/accessibility
    Read the Fine Print

    View full-size slide

  47. Assumption #9
    It’s all or nothing

    View full-size slide

  48. “We don’t have time to factor in accessibility”
    “It’s too expensive to make it accessible”
    AKA

    View full-size slide

  49. • Start small, stay focused
    • High-priority, high-impact
    • Role-based accessibility
    • Stay informed
    Make it part of your plan

    View full-size slide