Name: Accessibility for Everyone
ISBN: 9781937557621

Laura Kalbag

You make the web more inclusive for everyone, everywhere, when you design with accessibility in mind. Let Laura Kalbag guide you through the accessibility landscape: understand disability and impairment challenges; get a handle on important laws and guidelines; and learn how to plan for, evaluate, and test accessible design. Leverage tools and techniques like clear copywriting, well-structured IA, meaningful HTML, and thoughtful design, to create a solid set of best practices. Whether you’re new to the field or a seasoned pro, get sure footing on the path to designing with accessibility.

Accessibility for Everyone

Jaydee (she/her)

Ill start with some definitions. Accessibility in the physical world is the degree to which an environment is usable by as many people as possible. Web accessibility is the degree to which a website is usable by as many people as possible. We can think about both kinds of accessibility as forms of incusion.

Universal design is a concept coined by architect Ronald L. Mace, founder of the Center for Universal Design. After contracting polio at age nine, Mace useda wheelchair for most of his life. He had to be carried up and down stairs to attend classes, and his wheelchair didn't fit through the doors of public restrooms. Mace's experiences led him to study architecture, and later specialize in accessibility. He considered universal design an evolution of accessible design: y Universal design is the design of products and environments to be usable by all people, to the greatest extent possible, without the need for adaptation or specialized design.

The distinction between universal and accessible design is subtle but important. Accessible design considers the needs of people with disabilities. So, for example, accessible design might result in a building having a wheelchair ramp attached to its far side, as an afterthought. It might not be convenient for people using wheelchairs, and it's unlikely to be used by people who find it faster to use the stairs, but at least there's some form of access (FIG 1.3). On the other hand, universal design considers the needs of a diverse human population. Universal design might result in a building with a combined ramp and stairs, opening access to all and forcing no one to go out of their way to choose one option or the other (FIG 1.4).

Throughout this book, I take a universal design approach to accessibility wherever possible. Universal web accessibility helps us create sites that are usable by the widest, most diverse audi- ence, rather than creating bolt-on solutions that might benefit one group at the expense of another. (But I won't always use the terms "universal design" or universal web accessibility" because they're a bit of a mouthful.)

Empathy in design is far easier when we work in diverse teams. Diversity comes from a range of ages, abilities, eth- nicities, socio-economic classes, personal backgrounds, gen- ders, education levels, and many more characteristics which give each of us a unique experience of the world. Spending meaningful time with people whose experiences differ from our own can help us develop a greater understanding of each other's needs. The greater capacity a team has for understand- ing their audience, the more likely they are to solve that audi- ence's problems.

Believing we know what's best for others, despite our diifer- ing needs, can also result in a patronizing and incorrect solu- tion (sometimes referred to as colonial design"). For example, sometimes when developers first learn about screen readers, they provide additional instructions and cues in text that only visible to screen readers. They're trying to be helpful, but these additional instructions on how to use the interface are usually unnecessary, disruptive and distracting for people who just want to get to the page content.

Screen readers don't just benefit those with visual impair- ments. Some people can consume information more comfort- ably and conveniently by hearing text rather than reading it. For example, many people prefer audiobooks over reading, and sighted users with learning difficulties may prefer screen readers for reading lengthy amounts of text aloud. Screen readers also enable people to engage in other activi- ties while listening-such as driving while listening to an SMS text message. As the web starts finding its way into more mobile systems, we're likely to come across more use cases like this.

 In this book, I talk about people who have disabilities, rather than people who are disabled. When we're designing for the web, thinking of the person before the disability helps us focus audience rather than create a false separation between"people without disabilities" and "people with disabilities." 

TYPES OF DISABILITY Five main areas of disability affect our use of the web: visual impairments, auditory impairments, motor impairments, cog- nitive impairments, and vestibular disorders and seizures.

Cognitive dificulties are incredibly diverse, and the way peo- ple interact with web content will vary depending on their condition. Cognitive issues that are particularly relevant to the web include:

 • Memory: difficulties remembering the task one is trying to accomplish, or where one is within a site.

 •  Attention: difficulty focusing on large amounts of informa- tion, or any information for prolonged periods. 

• Problem-solving: difficulty processing information, particu- larly if the content on the page is not what's expected. · 

 • Text processing: difficulty understanding text, and difficulty expressing understanding through speech and language.

 • Math processing: difficulty understanding mathematical concepts and symbols, such as telling the time or distinguish- ing quantities, money, and pricing.

 •  Visual processing: difficulty interpreting visual information, or understanding visual representatios of real-world objects (such as icons)

INCORPORATING ACCESSIBILITY FROM the beginning is almost always easier, more effective, and less expensive than making accessibility improvements as a separate project. 

an ma In fa s hs C Web accessibility is the responsibility of everyone who has a hand in the design of a site. Design includes all of the decisions we make when we create a productnot just the pretty bits, but the decisions about how it works and who it's for. This means everybody involved in the project is a designer of some sort. 

At the beginning of a project, you'l need to make many deci- sions that will have an impact on accessibility efforts and approaches, including:

 . What is the purpose of your product? . Who are the target audiences for your product? What are . What are the goals and tasks that your product enables the . What is the experience your product should provide for each • How can accessibility be integrated during production? their needs, restrictions, and technology preferences? user to complete? combination of user group and user goal? • Which target platforms, browsers, operating systems and assistive technologies should you test the product on?

And since accessibility begins with accessible content, the content management system (CMS) you choose is incredibly important. A good CMS should enable the content creator to produce content in a way that's accessible to both the creator and the consumer. 

Hendren asks, "What technology are you using that's not assistive?" Our keyboards and mice assist us in communicating with a computer. Our headphones enable us to hear audio in our own spaces without disrupting those around us. Our phones give us the knowledge of the entire web in our pockets. Technology enables us all, and can give usa better experience of the world around us.

To improve the experience for everyone, we can focus on the usability of the web across four broad parameters: 

 3. Motor: make it easy to interact with. 

4. Cognitive: make it easy to understand.

The problem is that using "click here" as the language for your links renders the links meaningless for those with screen readers as well as those without. Descriptive linking, instead, helps links make sense out of context, and provides users with a sense of where the link will take themn or what will happen after they click. “Read the full article" is a lot more descriptive than “Click here." Descriptive linking also helps simplify your writing. "To get in contact with our team, click here" can be simplified to "Get in contact with our team." Or: "Last week we posted a review of Murder in The Clouds. You can read that review here" can be simplified to Last week we posted a review of Murder in The Clouds."

In other contexts, acronyms can be okay-even necessary. For example, if you started talking about "Hypertext Markup Language and Cascading Style Sheets," fewer web industry folks would understand you than if you said HTML and CSS." Just in case, it's best to incude the meaning of the acronym or abbreviation the first time you use it on a page: "We make websites using Hypertext Markup Language (HTML) and Cas- cading Style Sheets (CSS). HTML gives our content structure; CSS gives it style." 

Jason Santa Maria's On Web Typography (http://bkaprt.com/ afe/o4-o4/) and Richard Rutter's recent Web Typography (http:/ bkaprt.com/afe/o4-os/) both contain a wealth of information on choosing fonts and arranging type. As with general usability, thoughtful typography will benefit everyone.

While we aim for high contrast for the majority of visitors, if the contrast between text and background is too high, the text can appear to dance on screen. High-contrast text is particularly problematic for people with a dyslexic condition called scotopic sensitivity syndrome (SSS). People with SSS find that high-con- trast text appears to shimmer or wobble on the screen.

"You make the web more inclusive for everyone, everywhere, when you design with accessibility in mind. Let Laura Kalbag guide you through the accessibility landscape: understand disability and impairment challenges; get a handle on important laws and guidelines; and learn how to plan for, evaluate, and test accessible design. Leverage tools and techniques like clear copywriting, well-structured IA, meaningful HTML, and thoughtful design, to create a solid set of best practices. Whether you're new to the field or a seasoned pro, get sure footing on the path to designing with accessibility." -- Publisher's description

Maria Luiza

Great book on accessibility on the web. Very light and easy to read. Great insights.

Accessibility for Everyone

Reviews

Highlights