Making Sense of Accessibility

© 2012 Adobe Systems Incorporated. All Rights Reserved.

Making Sense of Accessibility Char James-Tanny | Accessibility Advocate | JTF Associates, Inc. | [email protected]

Maxwell Hoffmann | Adobe Product Evangelist | Twitter @maxwellhoffmann | [email protected]

1

mailto:[email protected]

http://twitter.com/maxwellhoffmann



About Adobe

2

74 Offices in 43 Countries

Corporate Headquarters in San Jose, California

Founded in December 1982

$4.2 billion in revenue in FY2011

More than 10,000 employees

Adobe donates a minimum of 1% of net income to philanthropy

We simplify complicated, inefficient, and expensive workflows. We enable more engaging, compelling content. We drive greater return from digital media and marketing investments.

Presenter

Presentation Notes


Your Webinar Host

Maxwell Hoffmann

Adobe Product Evangelist, Tech Comm Suite

Former Product Manager and Sales Training Director for Frame Technology

15 years in translation industry, working on “whatever documents walked through the door”

Trained over 1,200 people in hands-on, scalable publishing solutions

3


Your Webinar Guest Speaker

Char James-Tanny

More than thirty years of experience in tech comm

Frequently speaks about accessibility, Help authoring concepts, social media, web standards

Primary coordinator for the Boston Accessibility Conference

Microsoft MVP since 2002

4

@charjtf / @helpstuff Copyright 2012 JTF Associates, Inc. 5

Presenter

Presentation Notes

Fifteen percent. One billion people. This is the average number of people worldwide who have a disability, according to estimates from the World Health Organization (WHO). And these people are a part of our audience, the people who read what we write or edit (or tweet or blog).


People with disabilities constitute the nation's largest minority group, and the only group any of us can become a member of at any time.

Disability Funders Network – Disability Stats

and Facts (http://www.disabilityfunders.org/disability-stats-

and-facts)

http://www.disabilityfunders.org/disability-stats-and-facts








Copyright 2011 The AbleGamers Foundation. Used with permission.

Presenter

Presentation Notes

But we typically don’t know a lot about our audience. We can ask people about their technical ability, their domain knowledge, and their familiarity with our product, but rarely do we use a more comprehensive audience analysis, asking questions like: Where are you when you use the content? Are you at home, at work, or traveling? What devices do you use to access content? Desktop, laptop, tablet, smartphone, other? Do you have speakers or headphones? Can you use them? Do you use broadband, dial-up, or 2G/3G/4G? What is your reading level?


Alex E. Proimos. http://www.flickr.com/photos/proimos/4199675334/

Presenter

Presentation Notes

And we can’t ask personal questions that would give us a better idea of our users’ abilities. It’s embarrassing, and in some cases, it’s illegal. For example, what if we could ask: What is your reading level? Do you have issues seeing different colors? Is English your primary or secondary language? (Do you have the same primary language as your users?) But we can use statistics to provide some information. For example: Disabilities increase with age. 0-14: 6%; 15-59: 18%; over 60: 56% 8% are color deficient (primarily males). 50% will be accessing the Internet through mobile devices by 2014 American Sign Language is the third most commonly used language in the United States On average, people spend approximately 11% of their lives with some kind of disability (permanent or temporary).

http://www.flickr.com/photos/proimos/4199675334/

Myths


May Michaely. http://www.flickr.com/photos/maymichaely/3126604121/

Presenter

Presentation Notes

It’s very common to hear someone repeat one of the following myths. Unfortunately, if a myth is repeated often enough, people believe it to be true. As a result, companies don’t think about making their content more accessible. (Some myths are listed with the Twitter name of the person who contributed to my call for myths.)

http://www.flickr.com/photos/maymichaely/3126604121/

http://www.flickr.com/photos/maymichaely/3126604121/

People who are disabled don’t use the Internet. Or work as programmers. Or as astronomers.


Jennison Ascuncion. Photo by William Lawrence.

Sina Bahram. Photo by Michael Francis McCarthy. http://www.flickr.com/photos/sagamiono/4827919176/.

Presenter

Presentation Notes

Many people with disabilities DO use the Internet. Typically, comments refer to people who are blind, sometimes saying, “They can’t see, so we don’t need to fix anything for them.” There’s no way for you to know what disabilities your user, customers, or visitors have. And there are astronomers who are blind. In fact, NASA has hired chemists, computer scientists, mathematicians, and project managers (in addition to an astronomer) who are blind. On a side note: The Museum of Science (MOS) in Boston recently held a workshop called “Creating Museum Media for Everyone”. My friend Sina Bahram attended, and he’s provided links to videos and photos at his website (http://sinabahram.com) that describe how the MOS is creating artifacts that all museums can use to incorporate universal design into their exhibit design process.

http://www.flickr.com/photos/sagamiono/4827919176/



You must create a text-only version of your website for screen readers


Presenter

Presentation Notes

Thanks to cascading style sheets and accessible design, you can create one website that can be used on multiple devices, from large-screen TVs to tablets to smartphones.

Accessible websites are ugly


Presenter

Presentation Notes

Any website can be ugly. Accessible websites tend to have a more structured design, and really attractive accessible websites can be found. (Typically, really busy websites with many headings and images tend to be inaccessible.) Sample: World Glaucoma Association: http://www.globalaigs.org/ (from 2007)

No, they’re not!


Presenter

Presentation Notes

Any website can be ugly. Accessible websites tend to have a more structured design, and really attractive accessible websites can be found. (Typically, really busy websites with many headings and images tend to be inaccessible.) Sample: CSS Zen Garden by CSS Co., Ltd: http://csszengarden.com/?cssfile=/209/209.css&page=0

Sometimes they’re really cool


Presenter

Presentation Notes

Any website can be ugly. Accessible websites tend to have a more structured design, and really attractive accessible websites can be found. (Typically, really busy websites with many headings and images tend to be inaccessible.) Samples: Retro Theater CSS Zen Garden Design by Eric Roge: http://csszengarden.com/?cssfile=/202/202.css&page=1

People who are disabled don’t play games


Copyright 2011-2012. The AbleGamers Foundation. Used with permission.

Presenter

Presentation Notes

If you play multi-player games on the web or through a game console, chances are good that you’ve played with someone who is disabled. AbleGamers (http://www.ablegamers.org) focuses on bringing great accessibility to games so that gamers can enjoy a rich social life. Some accessible games include In The Pit (Xbox, http://marketplace.xbox.com/en-US/Product/In-the-Pit/66acd000-77fe-1000-9115-d80258550113) and Stem Stumper (iTunes and Android, http://www.ananseproductions.com/stemstumper/).

People who are colorblind can’t see colors


From Vision Simulator (http://webexhibits.org/causesofcolor/2.html).

Presenter

Presentation Notes

Those who are colorblind do see colors, but the colors they see are different because their color spectrum is altered (based on their type of color deficiency). Parents start teaching their children about colors before they’re a year old, but kids can’t be tested for color deficiency until they can read and talk. (New tests have been developed to test kids as early as 3, but testing is typically done when they’re 6).

http://webexhibits.org/causesofcolor/2.html

It’s OK to touch a guide dog


Sini Merikallio. http://www.flickr.com/photos/smerikal/5555789969/ Photo by

Char James-Tanny

Presenter

Presentation Notes

It’s only OK to touch a guide dog if their owner has given you permission. Never reach out and touch a guide dog without asking.

http://www.flickr.com/photos/smerikal/5555789969/

http://www.flickr.com/photos/smerikal/5555789969/

People who can’t use a mouse or keyboard don’t use computers. (@SteveBuell)


Photo by Char James-Tanny.

Presenter

Presentation Notes

People who can’t use a mouse (such as those with arthritis) use the keyboard to navigate. People who can’t use a mouse or keyboard use their voice or sip-and-puff devices.

We don’t have any disabled customers


Glenda Watson Hyatt, http://www.doitmyselfblog.com/2010/the-ipad-as-an-affordable-communicator-initial-review/

Photo by Char James-Tanny.

Presenter

Presentation Notes

You can’t ask your customers if they’re disabled. But you can take steps to accommodate anyone who uses your product.

http://www.doitmyselfblog.com/2010/the-ipad-as-an-affordable-communicator-initial-review/
















Accessibility is free. (@nethermind) No, it’s really expensive. (@redcrew)


Michael Francis McCarthy. http://www.flickr.com/photos/sagamiono/4827919176/.

Presenter

Presentation Notes

Neither is true. It can be more expensive to implement accessibility if you wait until the end of the project. And it will cost less if you include accessibility from the beginning of the project. Whitney Quesenbery once referred to an article by the Usability Professionals of America (UPA) and believes that the cost-benefit ratios for usability and accessibility are similar: "The rule of thumb in many usability-aware organizations is that the cost-benefit ratio for usability is $1:$10-$100. Once a system is in development, correcting a problem costs 10 times as much as fixing the same problem in design. If the system has been released, it costs 100 times as much relative to fixing in design." (Gilb, 1988) In addition, see “The Cost of Accessibility” (http://eclecti.ca/the-cost-of-accessibility/) by Sean Yo and “How to Ensure You Pay More for Web Accessibility Than You Should” (http://simplyaccessible.com/article/pay-more/) by Derek Featherstone.


If the page passes an HTML validator, it’s accessible


Presenter

Presentation Notes

Using an HTML validator to verify that your code meets standards is a good first start. However, just because a page is compliant doesn’t mean that it’s also accessible. And pages that don’t pass the validator might be compliant.

If the page works with a screen reader, it’s accessible. (@SteveBuell)


Presenter

Presentation Notes

Again, this is a good first start. But screen readers do more than just read a page: they analyze the structure by making a list of all headings available. (This lets someone using a screen reader scan headings just like sighted people do.) Screen readers also make a list of all links available.

Standards


HTML

CSS

Presenter

Presentation Notes

The World Wide Web Consortium (W3C) maintains standards for the Web, such as HTML and Cascading Style Sheets (CSS). In 1997, when the W3C launched the Web Accessibility Initiative (WAI) (http://www.w3.org/WAI/), Tim Berners-Lee said, “The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.” Through its working groups, the WAI has developed: Authoring Tool Accessibility Guidelines (ATAG) (http://www.w3.org/WAI/intro/atag.php) User Agent Accessibility Guidelines (UAAG) (http://www.w3.org/WAI/intro/uaag.php) Application Rich Internet Applications (WAI-ARIA) (http://www.w3.org/WAI/intro/aria.php) Web Content Accessibility Guidelines (WCAG) (http://www.w3.org/WAI/intro/wcag.php) (You can find links to all WAI standards and guidelines at http://www.w3.org/WAI/guid-tech.html.)

Types of Disabilities

•Vision •Hearing •Speech •Physical/Motor •Learning •Psychiatric •Cognitive • Intellectual


Presenter

Presentation Notes

Disabilities are typically categorized by: Vision (blind, low vision, color deficiency) Hearing (deaf, hard-of-hearing) Speech (speech disorder, language disorder) Physical/Motor (spinal cord injuries, cerebral palsy, muscular dystrophy, multiple sclerosis, arthritis, Parkinson’s Disease) Learning (dyslexia, dyscalculia, autism) Psychiatric (ADD, ADHD, anxiety) Cognitive (traumatic brain injury, epilepsy) Intellectual (Down’s Syndrome)

Qualifying Disabilities

When they occur How they occur How long they last


Presenter

Presentation Notes

Accessibility issues can be qualified by when they occur, how they occur, and how long they last. When they occur Congenital issues exist from birth. Inherited issues are passed through genes from parents to children. At any time (see How they occur) How they occur Accidents Acquired Disease How long they last Temporary disabilities, such as broken bones, last a relatively short period of time. Permanent disabilities last forever. Situational disabilities can affect anyone at any time. For example: If you break the arm you mouse with, you need to learn to mouse with the other hand or you start using keyboard navigation. If you’re taking painkillers or you haven’t had enough sleep (and you’re still trying to work), your cognitive abilities are affected.


In countries with life expectancies over 70 years of age, people spend on average about 8 years, or 11.5 per cent of their life span, living with disabilities.

Disabled World – World Facts and Statistics on

Disabilities and Disability Issues: http://www.disabled-

world.com/disability/statistics/#ixzz1wM3G3pdg

http://www.disabled-world.com/disability/statistics/



Benefits of Accessible Documents and Web Pages


Presenter

Presentation Notes

Back in the 1940s, Jack Fisher was instrumental in getting curb cuts installed in Kalamazoo, Michigan, to help disabled World War II veterans navigate the city. City planners quickly noticed that curb cuts helped more than just wheelchair-bound veterans: people with prostheses and those pushing baby carriages and many more were now able to navigate Kalamazoo’s high curbs. In the same way that curb cuts are valuable to more than just one group, accessible web pages and documents: Improve search engine results. Search engines read the source code (like screen readers do), and clean coding helps improve your ranking. “Google is blind.” Make it more likely that mobile browsers can interpret the content. Restaurants seem to be the biggest offender for mobile browsing. Check your web site in a variety of mobile devices or use an emulator. See “10 Excellent Tools for Testing Your Site on Mobile Devices” (http://sixrevisions.com/tools/10-excellent-tools-for-testing-your-site-on-mobile-devices/) Reduce maintenance costs. The cleaner the code, the easier it is to maintain the site and make future updates. Increase profits. (According to the United States Department of Labor, in 2009, the disability market represents $1 trillion in purchasing power. According to UK Net Guide, the disability market is worth £80 billion annually.) Are the right thing to do. And in some countries, it’s the law.


“Web accessibility is not a legal issue. It’s an equal opportunity issue.”

Rakesh Babu, quoted in To The Blind, The Internet Isn’t Always So

User-Friendly

http://www.webpronews.com/blind-friendly-internet-2012-02





Laws


kcp4911. http://www.flickr.com/photos/29712230@N08/2861478881/

Presenter

Presentation Notes

“Web accessibility is not a legal issue. It’s an equal opportunity issue.” Rakesh Babu, quoted in To The Blind, The Internet Isn’t Always So User-Friendly Anti-discrimination and other disability-specific laws have been passed in 45 countries. The World Wide Web Consortium’s Web Accessibility Initiative (W3C WAI) has compiled a list of policies by country at http://www.w3.org/WAI/Policy/Overview.html. (This list includes many other references.) Some of the more well-known laws and policies are: Australia: Disability Discrimination Act 1992 and updates (http://www.comlaw.gov.au/Series/C2004A04426/Amendments) Canada: Canadian Human Rights Act (http://www.chrc-ccdp.ca/about/human_rights_act-eng.aspx) United Kingdom: Special Needs and Disability Act 2001 (http://www.legislation.gov.uk/ukpga/2001/10/contents) United States: Section 508 (http://section508.gov/) and Americans with Disabilities Act (http://www.ada.gov/)

http://www.flickr.com/photos/29712230@N08/2861478881/


Don Baird. http://www.flickr.com/photos/old-curmudgeon/2298969471/

Presenter

Presentation Notes

One thing about laws: it is possible to meet the “letter of the law” while not actually improving accessibility. *Photo used with permission.

http://www.flickr.com/photos/old-curmudgeon/2298969471/

Available Solutions

Screen readers Zoom (magnify) Larger fonts Color contrast “Skip” links Speech recognition Heading tags

(sequential)

Hyperlink indicators CART Captions, transcripts,

audio descriptions Plain language Keyboard access Usability testing Browser extensions /

plugins


Presenter

Presentation Notes

Screen readers (such as JAWS, NVDA, and Window Eyes) use the source code of the page, not what can actually be seen. (This is why some fancy sites are still accessible.) Zoom (or other apps) increase the size of images and the font size of the text they are reading. WCAG guidelines state that designs should be resizable to at least 200% without losing clarity or layout. Slightly larger fonts with extra spacing above underlines are easier to read by dyslexics. Good color contrast makes text and images easier to read and comprehend. W3C guidelines suggest a minimum ration of 3:1 for large text, 4.5:1 for other text and images. Add links for “Skip to Main Content” and, if applicable, “Skip to Secondary Navigation”. This makes it easier for people using the keyboard to navigate a website to jump to the areas that they are interested in. Speech recognition applications let people talk to their computers. Smart phones (and just about every Apple device) include many features that improve accessibility, such as Siri. Use headings (and heading tags, not manually formatted text). Screen readers can display a list of headings to make navigation easier. Use sequential headings. Start a page with Heading 1 (or H1). Don’t skip levels because you like the way the other heading looks. Use two indicators for hyperlinks. Typically, we change the color and add an underline or border. Communication Access Realtime Translation (CART) displays a written transcript of what’s being said in a conference, webinar, etc. CART not only helps people who are deaf or hard-of-hearing, it helps those who speak English as a second language or those with cognitive issues. Captions, transcripts, and audio descriptions make video available to people who can’t hear (or who are in a situation where they can’t listen). Use plain language. Use the best words to express yourself, and try to make sure that they can’t be misinterpreted. For example, “Please maintain visual contact with your personal items” instead of “Keep an eye on…”. Keyboard access lets people navigate pages without a mouse or other device. Test with people with disabilities. Browser Extensions and Plugins Fangs (Firefox). View a text representation of a web page, including information about all headings, links, and images. Firebug (Firefox). View the source code and accompanying CSS definition for any element on a page. HTML Validator (Firefox). View any validation errors on a page. WCAG Contract Checker (Firefox). Verify all color contrast ratios on a page. Web Accessibility Toolbar (Internet Explorer, Opera). Web Developer (Firefox). Disable CSS and images, validate HTML and CSS, and more.

Resources

Visit “Bits, Bytes, and Words” at JTF Associates for list of resources from today’s webinar


http://jtfassociates.com/bits-bytes-words/


Upcoming Adobe TechComm Webinars

Char James-Tanny

Part II: Creating an Accessible Layout – Tips to make documents more accessible (structure, colors, fonts, more) (17 July, 10-11 AM PST)

Part III: Developing Accessible Content – Tips on grammar, paragraph, and sentence length, alternate text, and more (31 July, 10-11 AM PST)

Getting Real: Electronic Documents for the Field, 21 June, Joe Golner

Future of TechComm series: Designing technical documentation for tablets 26 June, Ellis Pratt, Cherryleaf

Content Scenarios for Exploring New Information Products, 27 June, Joe Golner

Find Out How to Write XSLT Statements for XML to XML Transformations in a 5-part eSeminars Series, 28 June to 19 July, Tom Aldous

33


Questions and Answers

34


Contact Information

35

Information Char James-Tanny User Assistance Advocate JTF Associates, Inc.

LinkedIn charjtf Email [email protected] Web www.jtfassociates.com Twitter @charjtf / @helpstuff

Maxwell Hoffmann Adobe Systems, Inc. Product Evangelist

Blog blogs.adobe.com/techcomm Blog blogs.adobe.com/mbhoffmann Twitter twitter.com/maxwellhoffmann Twitter twitter.com/AdobeTCS

Email [email protected] Web www.adobe.com LinkedIn www.linkedin.com/in/maxwellhoffmann Facebook As maxwell.hoffmann1 Facebook As Adobe Technical Communication Professionals Group

Previously recorded eSeminars: http://adobe.ly/qo3pzc Calendar of upcoming eSeminars: http://adobe.ly/xdzOYa

http://www.linkedin.com/in/charjtf


http://www.jtfassociates.com/

http://twitter.com/charjtf

http://twitter.com/helpstuff

http://blogs.adobe.com/techcomm

http://blogs.adobe.com/mbhoffmann

http://twitter.com/maxwellhoffmann

http://twitter.com/AdobeTCS

http://[email protected]/



http://www.adobe.com/

http://www.linkedin.com/in/maxwellhoffmann

http://adobe.ly/qo3pzc

http://adobe.ly/xdzOYa

Making Sense of Accessibility

Design

Transcript of Making Sense of Accessibility