Top Mistakes in Web Accessibility

48
Top Mistakes in Web Accessibility KRAKÓW, 20.10.2011 FRONT ROW CONFERENCE

description

The presentation given at http://frontrowconf.com/.

Transcript of Top Mistakes in Web Accessibility

Page 1: Top Mistakes in Web Accessibility

Top Mistakesin Web Accessibility

KRAKÓW, 20.10.2011

F R O N T R OW CO N F E R E N C E

Page 2: Top Mistakes in Web Accessibility

TYPES

3

Page 3: Top Mistakes in Web Accessibility

1. Bored manager

his blackberry

“Disabled people are not in my target group”

FAVO R I T E TO O L

T H E Y SAY

Page 4: Top Mistakes in Web Accessibility

FAVO R I T E T E C H N I Q U E

hashbangs

T H E Y SAY

“I’ll AJAX all over your CSS3”

2. A future lover

Page 5: Top Mistakes in Web Accessibility

FAVO R I T E TO O L

JS text resizer

3. Over-exciter

“I created a text-only version of my church’s website”

T H E Y SAY

Page 6: Top Mistakes in Web Accessibility

You’ll need to deal with different types of people.

Let’s getsome facts

straight

Page 7: Top Mistakes in Web Accessibility

✦ About 15% (5 mln) of total population in Poland live with some kind of disability

✦ The average age of web users increases every year

✦ Good for not proficient language users

✦ Meets legal requirements

✦ Everyone benefits! (think slower connections)

Benefits of web accessibility

Page 8: Top Mistakes in Web Accessibility

Benefits of web accessibility

✦ Strong overlap with: mobile webhttp://www.w3.org/TR/mwbp-wcag/

Page 9: Top Mistakes in Web Accessibility

Benefits of web accessibility

✦ Strong overlap with: SEO

Page 10: Top Mistakes in Web Accessibility

Types of disability

Page 11: Top Mistakes in Web Accessibility

Visual Hearing Motor Cognitive

✦ Blind✦ Partial vision loss✦ Color blindness

Page 12: Top Mistakes in Web Accessibility

Visual Hearing Motor Cognitive

Video transcription (closed captioning) benefits not just those with hearing impairments.

✦ Disabling sound✦ Content becomes searchable and quotable

Page 13: Top Mistakes in Web Accessibility

Visual Hearing Motor Cognitive

Motor impaired can find using keyboard or mouse problematic. Alternative inputs can have different range of complexity, most frequent being different types “switches”.

Page 14: Top Mistakes in Web Accessibility

Visual Hearing Motor Cognitive

✦ Increase readability✦ Large headlines✦ Descriptive link text✦ Increased target area of navigation links

Cognitive problems occur to older users and those with worse level of document language.

Page 15: Top Mistakes in Web Accessibility

“For me being online is everything.It’s my hi-fi, my source of income, my supermarket, my telephone.

It’s my way in”TeLynn Holdsworth, screen reader user

http://www.flickr.com/photos/tjc/4084712050/

Page 16: Top Mistakes in Web Accessibility

A brief guideinto frequent problems

Page 17: Top Mistakes in Web Accessibility

Incorrect alternative text

Page 18: Top Mistakes in Web Accessibility

Text provided as

the text alternative must present

the content and function.

Page 19: Top Mistakes in Web Accessibility

fig. Image based navigationwith no alt text

Page 21: Top Mistakes in Web Accessibility

✦ Context is important✦ Short is better than long✦ Avoid redundancy

Some rules to remember…

✦ Skip “image of…” or “graphic of…”✦ Describe function✦ alt= "" for decorative images

Page 22: Top Mistakes in Web Accessibility

Following the visual appearance

Page 23: Top Mistakes in Web Accessibility
Page 24: Top Mistakes in Web Accessibility

<h3> <ul>

Semantics is the king

Page 25: Top Mistakes in Web Accessibility

Not changing defaults

Page 26: Top Mistakes in Web Accessibility
Page 27: Top Mistakes in Web Accessibility

2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)

Don’t doOUTLINE: 0;

(or at least provide with alternatives)

Page 28: Top Mistakes in Web Accessibility

Disabling mobile zoom

Page 29: Top Mistakes in Web Accessibility

<meta name="viewport"content="width=device-width; initial-scale=1.0; maximum-scale=1.0; user-scalable=0;" />

Don’t copy & paste

without testing

Page 30: Top Mistakes in Web Accessibility

Failing in navigation

Page 32: Top Mistakes in Web Accessibility

Keep the proper structure

of document headings.

Page 33: Top Mistakes in Web Accessibility

Keep the proper structure

of document headings.

Page 34: Top Mistakes in Web Accessibility

.hide { display: none; visibility: hidden;}

.hidden { position: absolute; left: -10000px; top: auto; width: 1px; height: 1px; overflow: hidden;}

Hiding content

.hidden:focus { position: static; width: auto; height: auto; }

F R O M S C R E E N

F R O M S C R E E N R E A D E R S

D I S P L AY O N F O C U S

Page 35: Top Mistakes in Web Accessibility

QUIC

K FIX

Page 36: Top Mistakes in Web Accessibility

Landmark HTML 5 elementrole=”application” none

role=”banner” none

role=”complementary” <aside>

role=”contentinfo” <footer>

role=”main” none

role=”navigation” <nav>

role=”search” none

~ The Paciello Group

WAI-ARIA Landmark Roles

Page 37: Top Mistakes in Web Accessibility

Inaccessible forms

Page 38: Top Mistakes in Web Accessibility

Name: [radio button] Mr. [radio button] Mrs. [text input] [text input] [text input] eMail Address Retype eMail

W R O N G :

✦ Label your inputs✦ Group form elements

✦ Check the tab order✦ Make sure it’s JS independent

Page 40: Top Mistakes in Web Accessibility

Ambiguous links

Page 41: Top Mistakes in Web Accessibility

Read more Click here

Success Criterion 2.4.4 - Link Purpose (In Context)Failure 63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link

Success Criterion 2.4.9 - Link Purpose (Link Only)Failure 84: Failure of Success Criterion 2.4.9 due to using a non-specific link such as "click here" or "more" without a mechanism to change the link text to specific text.

Page 42: Top Mistakes in Web Accessibility
Page 43: Top Mistakes in Web Accessibility

Adding interaction

Page 44: Top Mistakes in Web Accessibility

Manage focus order!

Page 45: Top Mistakes in Web Accessibility

Use ARIA roles to add meaning

to your components and

provide with readable data.

aria-live="off"

aria-live="polite"

aria-live="assertive"

aria-live="rude"

L I V E R E G I O N S fo r A JAX

<li role="menuitemcheckbox" aria-checked="true"> Sort by Last Modified</li>

Page 46: Top Mistakes in Web Accessibility

NVDAChromeVoxFireVoxVoiceOver

Browser extensionsFangsWeb Developer ToolbarAccessibility Evaluation Toolbar

Free screen readers

Page 47: Top Mistakes in Web Accessibility

No headingsNo anchor text

No alt text

Submit not beingread out

Fangs

Page 48: Top Mistakes in Web Accessibility

Q & A

Wojtek Zając (@theanxy)http://www.slideshare.net/wojciechzajac This work is licensed

under a Creative Commons Attribution 3.0 Unported License

Thanks!