Practical Web Inclusion and Accessibility: A Comprehensive Guide to Access Needs

Inhaltsverzeichnis des Buches

• Cover
• Front Matter
• 1. The Accessibility Problem
• Facing accessibility head on
• The state of accessibility today
• Why is it important now?
• Competitive advantages
• Why approach accessibility in a disability-driven way?
• Notes
• 2. Blindness
• Screen reader software
• Perceive, navigate, and interact
• Using ARIA
• Applying ARIA attributes
• aria-live
• aria-label
• aria-hidden
• Support
• HTML5 implicit mapping
• 3. Low Vision and Colour Blindness
• Magnification
• Horizontal scrolling
• Tracking
• Text overflow
• Testing zoom
• Responsive web design
• Preventing zoom
• Point of regard
• Navigation
• Accessible text
• Relative units
• Stop using pixels
• Screen sizes
• Raise your base font size
• Line height
• Letter spacing
• Font choice
• Contrast ratio
• Colour blindness
• Different types of colour blindness
• Links
• Testing
• Conclusion
• Notes
• 4. Motor Disabilities
• Keyboard-only navigation
• Tabindex
• Focus styles
• Accessible overlays
• Pointer-based gestures
• Large hit areas
• Pointer cancellation
• Voice to text
• Support for all motor-impaired users
• Short timeouts
• Provide shortcuts
• Motion actuation
• Autofill
• Conclusion
• Notes
• 5. Deafness and hard of hearing
• Subtitles vs closed captioning
• Caption actions
• Helping all users
• Which should I apply?
• <track> element
• WebVTT files
• vtt layout
• Different formats
• Styling subtitles
• Positioning
• Future features
• <audio> tag and captions
• Closed caption buttons
• YouTube
• Accessible subtitle/caption content
• Summarising audio and video content
• Unexpected or Automatic Audio
• Linear Layouts
• Servicing customers without a telephone
• Providing alternatives
• Text relays
• Conclusion
• Notes
• 6. Cognitive Impairments
• Defining Cognitive Impairments
• Language comprehension
• Plain English
• Word choice
• TL;DR’s
• Clear iconography
• Avoiding complex pages
• Complex layouts
• Complex experiences
• Breadcrumbs
• Hierarchical
• Historical
• Sitemaps
• Autocomplete
• “Strict” search
• “Fuzzy” matching
• Types of “fuzzy” searching
• Which should I use?
• Conclusion
• Notes
• 7. Mental Health
• Dark patterns
• Dark pattern: Complicated journeys and dead ends
• Dark pattern: Forced urgency
• Dark pattern: “Sneak into basket”
• Dark pattern: Confirm shaming
• Dark pattern: Bait and switch
• Communication anxiety
• Reach users where they feel comfortable
• Familiar integrations
• Conclusion
• Notes
• 8. Imagery
• Images
• Background images
• Text in images
• Text in responsive images
• Colour in images
• Videos
• Should you do it?
• Reducing movement
• Parallax
• Iconography
• <img> tag
• Sprites
• Windows High Contrast Mode
• SVG
• Conclusion
• Notes
• 9. Communication
• Accessible email
• Highlight actions
• Testing
• Understanding email support
• Attachments
• One-click action buttons
• No-reply email addresses
• You’re going to annoy your users
• Good uses of email
• Communicating with users directly
• Identifying access needs
• How to pass on information effectively
• Use plain language
• Set expectations
• After communication
• Accessibility champions
• Conclusion
• Notes
• 10. New Technologies
• Smart devices
• Voice assistants
• How do they understand us?
• How do smart devices help accessibility?
• How much can you interact with the Web on them?
• Disability-driven design
• Sesame
• smartphone
• Microsoft adaptive controller
• Support for offline customers
• Telephony software
• Fallbacks
• Impact on accessibility
• Artificial Intelligence
• Providing automatic video captioning
• Providing human-level language translation
• Providing information about images
• Providing information about a user’s surroundings
• Making speech recognition even more inclusive
• Providing catered content for users
• Providing automatic summaries of text
• Conclusion
• Notes
• 11. Tools and QA
• Tools
• General
• Blindness
• Low vision
• Colour blindness
• Deaf and hard of hearing
• Cognitive impairments
• Mental health
• Communication
• Automating your accessibility testing
• AccessLint
• Pa11y
• A11y machine
• AATT
• WAVE evaluation tool
• Auditing an existing site
• Aesthetics
• Content
• Communication
• Ease of use
• Settings
• Specifics
• Conclusion
• Notes
• 12. Conclusion
• Questions you should ask yourself
• How can I engage more with users with different access needs?
• Should I ask for help?
• Should I build everything myself?
• What can I do to engage others in accessibility?
• Takeaways
• Robles vs Domino’s Pizza
• Final words
• Notes
• Index
• Back Matter