A Web for Everyone by Horton, Sarah -- Read -- Imperial Library of Trantor

Start with purpose and goals Design for clarity and simplicity Think “accessibility first” Make templates accessible, too Choose an accessibility strategy

Who Is Responsible for Clear Purpose? Summary Profile: Simple and Usable with Giles Colborne

Simplicity is good science and good interface design. Simple designs put complexity in its place. Observe real people to learn what’s needed. Designing for multiple devices supports accessibility.

CHAPTER 4 Solid Structure: Built to Standards

How Solid Structure Supports Accessibility How to Create a Solid Structure

Code content to be machine-readable Code to standards Use standard web technologies Organize code for clarity and flow Use stylesheets to separate content and presentation Use semantic markup for content

Who Is Responsible for a Solid Structure? WCAG 2.0 and Solid Structure Summary Profile: Accessibility Standards with Mike Paciello

An early commitment to people and technology. Beginning to explore accessible electronic documents. Markup languages bring meaning to electronic documents. A pioneer for web accessibility. Helping set standards for web accessibility.

CHAPTER 5 Easy Interaction: Everything Works

How Easy Interaction Supports Accessibility Designing for Easy Interaction

Identify and describe interactive elements Use basic HTML codes correctly Use WAI-ARIA for complex elements Use features of the technology platform Provide accessible instructions and feedback Support keyboard interaction

Provide a logical tab order Don’t require point-and-click interaction Show which element has keyboard focus Don’t trap keyboard focus

Make controls large enough to operate easily Let users control the operation of the interface Design for contingencies Allow users to request more time

Who Is Responsible for Easy Interaction? WCAG 2.0 and Easy Interaction Summary Profile: Accessible Interaction with Derek Featherstone

People are the starting point. Best accessibility techniques are constantly changing. Technical remediation can help make interaction accessible. Integrated accessibility produces the best outcomes. Tools help teams integrate accessible components. The most influential tool for accessibility is clear purpose. Solutions come from different places.

CHAPTER 6 Helpful Wayfinding: Guides Users

How Helpful Wayfinding Supports Accessibility How to Design Helpful Wayfinding

Create consistent cues for orientation and navigation Present things that are the same in the same way Differentiate things that are different Provide orientation cues Provide clear landmarks within the page Provide alternative ways to navigate

Who Is Responsible for Wayfinding? WCAG 2.0 and Helpful Wayfinding Summary Profile: Coding Accessibility with Steve Faulkner

Elements of an accessible user interface. An accessibility API needs more than HTML. WAI-ARIA fills the gaps. HTML5, ARIA, or both? Advice for project teams.

CHAPTER 7 Clean Presentation: Supports Meaning

How Clean Presentation Supports Accessibility How to Design for Clean Presentation

Design simply Minimize distracting clutter Design for customization of the display Support customization through the browser Design content for easy comprehension Use color contrast to separate foreground from background Use visual and semantic space Provide enough space between lines of text Use clean typography

Who Is Responsible for Clean Presentation? WCAG 2.0 and Clean Presentation Summary Profile: Responsive Design with Ethan Marcotte

Balancing control and flexibility through responsive design. Redesigning the Boston Globe website. Ahead: More opportunities for responsiveness.

CHAPTER 8 Plain Language: Creates a Conversation

How Plain Language Supports Accessibility How to Design for Plain Language

Write for your audience Follow plain language guidelines for writing content Support users through their tasks Structure the whole page for scanning and understanding Write sentences and paragraphs for easy scanning Write helpful links Use language your audience is familiar with or provide definitions Provide plain language summaries of complex content Don’t rely on readability formulas Usability test your content

Who Is Responsible for Plain Language? WCAG 2.0 and Plain Language Summary Profile: Universal Plain Language with Ginny Redish

Plain language is important for accessibility. Design projects need content people.

CHAPTER 9 Accessible Media: Supports All Senses

How Accessible Media Supports Accessibility When I hear and see it, health information makes more sense. How to Design for Accessible Media

Don’t use only color to communicate meaning Provide instructions without relying on visual cues Describe the content or meaning of images Provide captions and descriptions for video Format captions to enhance meaning Provide alternatives to time-based media Use dynamic elements carefully Make presentations accessible

Who Is Responsible for Accessible Media? WCAG 2.0 and Accessible Media Summary Profile: Accessible Media with Larry Goldberg

Integrated technology as the tipping point. Becoming part of the process. Enhancing media with accessible features. Making text from audio. Partnering with transcription software. Adding captioning to the web media production workflow. Looking ahead for accessible media.

CHAPTER 10 Universal Usability: Creates Delight

How Universal Usability Supports Web Accessibility How to Design for Universal Usability

Design for exploration and discovery

Design for direct manipulation Disclose the right things at the right time Give rewards Support beginners and experts

Create a conversation

Layer information Tell a story

Be informative and helpful

Provide an overview Give instructions at the right time, in the right place

Practice usability for accessibility

Do usability testing Include people with disabilities in usability work

Who Is Responsible for Universal Usability? Summary Profile: Toward Universal Usability with Ben Shneiderman

We are making progress toward universal usability. Universal usability is about satisfying experiences. Expecting to be successful in our use of technology. Strategies for delivering universally usable experiences. Building awareness and expertise in the profession.

CHAPTER 11 In Practice: An Integrated Process

Making Accessibility the Way You Do Business Making a Commitment to Accessibility Assessing What’s Needed for an Integrated Practice

Evaluate the current site Identify ways to allocate resources Identify opportunities to integrate accessibility into current processes Assess current knowledge and readiness

Supporting an Integrated Practice

Set policies and develop training Choose content and development tools that support accessibility Create a style guide and media library Include people with disabilities

Provide tools and assistive technology for ongoing evaluation

Toolbars Assistive technology

Make accessibility part of site maintenance Summary Profile: Design Education with Valerie Fletcher

The state of accessibility and universal design. Education is a catalyst for change. Building a curriculum in universal design and accessibility. Accessibility guidelines set the baseline. Great examples inspire great designs.

CHAPTER 12 The Future: Design for All

What a Web for Everyone Looks Like What We Need to Do to Get There

Get out in front with web accessibility Build awareness and understanding of more diverse people Get support for accessibility into mainstream products Make accessibility part of how we think Don’t launch until it’s accessible

Now, to the Future

APPENDIX A Accessible UX Principles and Guidelines APPENDIX B WCAG 2.0 Cross-Reference

People First: Designing for Differences Clear Purpose: Well-Defined Goals Solid Structure: Built to Standards Easy Interaction: Everything Works Helpful Wayfinding: Guides Users Clean Presentation: Supports Meaning Plain Language: Creates a Conversation Accessible Media: Supports All Senses Universal Usability: Creates Delight Summary: WCAG Requirements in Order

APPENDIX C More Reading

Chapter 1: A Web for Everyone

Design Principles Books on Web Accessibility

Chapter 2: People First

User Research and Personas Disability Demographics and User Research About Assistive Technology Personas of People with Disabilities

Chapter 3: Clear Purpose Chapter 4: Solid Structure

Web and Accessibility Standards Code Validators

Chapter 5: Easy Interaction Chapter 6: Helpful Wayfinding Chapter 7: Clean Presentation Chapter 8: Plain Language

Plain Language Guidelines Writing for Different Audiences

Chapter 9: Accessible Media

Writing Alternative Text Captions and Multimedia Accessibility

Chapter 10: Universal Usability

Usability Testing

Chapter 11: Integrated Process

Planning and Project Management Accessibility Evaluation Toolbars to Check Accessibility Screen Readers and Screen Magnifiers for Windows Tools to Evaluate Flash and Other Rich Internet Applications

Chapter 12: The Future

Index ACKNOWLEDGMENTS ABOUT THE AUTHORS Footnotes

People First: Designing for Differences Solid Structure: Built to Standards Easy Interaction: Everything Works Plain Language: Creates a Conversation Universal Usability: Creates Delight In Practice: an Integrated Process

← Prev
Back
Next →

← Prev
Back
Next →