wordpress accessibility - wordcamp buffalo 2016

82
WordPress Accessibility Presented by Adrian Roselli for WordCamp Buffalo 2016 #WCBuf Slides from this talk will be available at rosel.li/ WCBuf

Upload: adrian-roselli

Post on 15-Apr-2017

435 views

Category:

Internet


3 download

TRANSCRIPT

Page 1: WordPress Accessibility - WordCamp Buffalo 2016

WordPress AccessibilityPresented by Adrian Roselli for WordCamp Buffalo 2016

#WCBuf

Slides from this talk will be available at rosel.li/WCBuf

Page 2: WordPress Accessibility - WordCamp Buffalo 2016

What We’ll Cover

• Intro• WordPress Goes WCAG• Techniques• Key Takeaways

Work with me, people.

Page 3: WordPress Accessibility - WordCamp Buffalo 2016

Intro

1 of 4 sections.

Page 4: WordPress Accessibility - WordCamp Buffalo 2016

About Adrian Roselli

• Co-written four books.• Technical editor

for two books.• Written over fifty

articles, most recentlyfor .net Magazine andWeb Standards Sherpa.

Great bedtime reading!

Page 5: WordPress Accessibility - WordCamp Buffalo 2016

About Adrian Roselli

• Member of W3C HTML Working Group*, W3C Accessibility Task Force, five W3C Community Groups.

• Building for the web since 1994.• Business owner / founder, ~20 years.• Now independent / unemployed.• Learn more at AdrianRoselli.com.• Avoid on Twitter @aardrian.

I warned you.

Page 6: WordPress Accessibility - WordCamp Buffalo 2016

What is a11y?

• A numeronym for “accessibility”:• The first and last letter,• The number of characters omitted.

• Prominent on Twitter (character restrictions):• #a11y

• Examples:• l10n → localization• i18n → internationalization

Ain’t language funsies?

Page 7: WordPress Accessibility - WordCamp Buffalo 2016

Accessibility Gets No Respect

In fairness, Sherwin Williams needs to come up with a lot of color names...

“Cyberspace” (gray)

“Online” (blue)

“Lime Rickey” (green)

Page 8: WordPress Accessibility - WordCamp Buffalo 2016

Accessibility Gets No Respect

…however I think the team could have done better than this.

Page 9: WordPress Accessibility - WordCamp Buffalo 2016

WordPress Goes WCAG

2 of 4 sections

Page 10: WordPress Accessibility - WordCamp Buffalo 2016

<irony>No transcripts nor captions, but go here and search (ctrl + F) for “It's Martin.” to jump to the point in the in-progress slightly inaccurate transcript.</irony>

Page 11: WordPress Accessibility - WordCamp Buffalo 2016

“All new or updated code released into WordPress core and bundled themes must conform with the WCAG 2.0 guidelines at level AA.”

— Rian RietveldMarch 21, 2016

Page 12: WordPress Accessibility - WordCamp Buffalo 2016

Notes

• Leans on WP Core Accessibility Coding Standards• https://make.wordpress.org/core/handbook/best-pr

actices/coding-standards/accessibility-coding-standards/

• Itself informed by WCAG (Web Content Accessibility Guidelines) 2.0 (a W3C recommendation)• https://www.w3.org/WAI/intro/wcag

• Get involved• https://make.wordpress.org/accessibility/get-involve

d/

Page 13: WordPress Accessibility - WordCamp Buffalo 2016

More Notes

• To get accessibility-ready tag for your theme, must follow specific guidelines• https://make.wordpress.org/themes/handbook/re

view/accessibility/required/• “The accessibility of plugins is the

responsibility of each plugin author.”

Page 14: WordPress Accessibility - WordCamp Buffalo 2016

Yet More Notes

• Accessibility wish list for 4.6+, posted April 27• https://make.wordpress.org/core/2016/04/27/acc

essibility-wish-list-for-4-6-and-beyond/• Rian Rietveld won Heroes of Accessibility

Award, Individual Achievement category• http://wptavern.com/wordpress-contributor-rian-

rietveld-wins-heroes-of-accessibility-award

Page 15: WordPress Accessibility - WordCamp Buffalo 2016

Accessibility Ready Themes

https://wordpress.org/themes/tags/accessibility-ready/

Page 16: WordPress Accessibility - WordCamp Buffalo 2016

Techniques

3 of 4 sections.

Page 17: WordPress Accessibility - WordCamp Buffalo 2016

Use @alt Text on Images

Page 18: WordPress Accessibility - WordCamp Buffalo 2016

Use @alt Text on Images

Page 19: WordPress Accessibility - WordCamp Buffalo 2016

Use @alt Text on Images

• Can you still make sense of the page?• Is content missing?• Can you still use the site?• Is your alt text useful?

http://www.karlgroves.com/2013/09/05/the-6-simplest-web-accessibility-tests-anyone-can-do/

Page 20: WordPress Accessibility - WordCamp Buffalo 2016

Use @alt Text on Images

http://www.4syllables.com.au/2010/12/text-alternatives-decision-tree/http://dev.w3.org/html5/alt-techniques/#tree

1. What role does image

play?

2. Does it present new

info?

3. What type of info?

Informative Yes

alt=""or

<a href="foo"><img alt="">Link</a>alt=""or

Use CSS

alt="descriptive identification"or

alt="short label" + caption

Pure

ly D

ecor

ative Se

nsor

y

No alt="label for link"

alt=“short alternative"or

alt="short label" + caption

alt="short label + location of long alternative"or

long text alternative on same or linked page

Long

/ Co

mpl

ex

Shor

t / S

impl

eLink

Page 21: WordPress Accessibility - WordCamp Buffalo 2016

Use On-Page Descriptions

http://adrianroselli.com/2014/04/we-need-to-raise-stink-about-net.html

Page 22: WordPress Accessibility - WordCamp Buffalo 2016

Use On-Page Descriptions

• Not just for longdesc or aria-describedat, but any long description technique,

• Use an in-page anchor,• Don’t link to another page without reason:• Consider burden of loading a new page,• Consider burden of re-loading original page.

• Based on results of latest WebAIM screen reader survey results.

http://adrianroselli.com/2015/09/use-on-page-image-descriptions.html

Page 23: WordPress Accessibility - WordCamp Buffalo 2016

Hyperlinks!

http://www.sitepoint.com/15-rules-making-accessible-links/

Page 24: WordPress Accessibility - WordCamp Buffalo 2016

Hyperlinks!

• Is there any “click here,” “more,” “link to…”?

http://www.sitepoint.com/15-rules-making-accessible-links/

Page 25: WordPress Accessibility - WordCamp Buffalo 2016

Hyperlinks!

• Is there any “click here,” “more,” “link to…”?• Are you using all-caps, URLs, emoticons?

http://www.sitepoint.com/15-rules-making-accessible-links/

Page 26: WordPress Accessibility - WordCamp Buffalo 2016

Hyperlinks!

• Is there any “click here,” “more,” “link to…”?• Are you using all-caps, URLs, emoticons?• Do you warn before opening new windows?

http://www.sitepoint.com/15-rules-making-accessible-links/

Page 27: WordPress Accessibility - WordCamp Buffalo 2016

Hyperlinks!

• Is there any “click here,” “more,” “link to…”?• Are you using all-caps, URLs, emoticons?• Do you warn before opening new windows?• Do links to downloads provide helpful info?

http://www.sitepoint.com/15-rules-making-accessible-links/

Page 28: WordPress Accessibility - WordCamp Buffalo 2016

Hyperlinks!

• Is there any “click here,” “more,” “link to…”?• Are you using all-caps, URLs, emoticons?• Do you warn before opening new windows?• Do links to downloads provide helpful info?• Are you using pagination links?

http://www.sitepoint.com/15-rules-making-accessible-links/

Page 29: WordPress Accessibility - WordCamp Buffalo 2016

Hyperlinks!

• Is there any “click here,” “more,” “link to…”?• Are you using all-caps, URLs, emoticons?• Do you warn before opening new windows?• Do links to downloads provide helpful info?• Are you using pagination links?• Are your links underlined (or otherwise obvious)?

http://www.sitepoint.com/15-rules-making-accessible-links/

Page 30: WordPress Accessibility - WordCamp Buffalo 2016

Hyperlinks!

• Is there any “click here,” “more,” “link to…”?• Are you using all-caps, URLs, emoticons?• Do you warn before opening new windows?• Do links to downloads provide helpful info?• Are you using pagination links?• Are your links underlined (or otherwise obvious)?• Is there alt text for image links?

http://www.sitepoint.com/15-rules-making-accessible-links/

Page 31: WordPress Accessibility - WordCamp Buffalo 2016

Hyperlinks!

• Is there any “click here,” “more,” “link to…”?• Are you using all-caps, URLs, emoticons?• Do you warn before opening new windows?• Do links to downloads provide helpful info?• Are you using pagination links?• Are your links underlined (or otherwise obvious)?• Is there alt text for image links?• Is the link text consistent?

http://www.sitepoint.com/15-rules-making-accessible-links/

Page 32: WordPress Accessibility - WordCamp Buffalo 2016

Use Link Underlines

http://www.theverge.com/2014/3/13/5503894/google-removes-underlined-links-site-redesign

Page 33: WordPress Accessibility - WordCamp Buffalo 2016

Use Link Underlines

• You are not Google:• Users know Google’s layout,• Users probably don’t visit your site daily.

• Relying on color alone will not suffice (WCAG 1.4.1 [A], 1.4.3 [AA]),

• Necessary contrast values:• 4.5:1 between text and its background for copy,• 3:1 between text and its background for larger text,• 3:1 between surrounding text and a hyperlink, plus an

additional visual cue (G183).http://adrianroselli.com/2014/03/i-dont-care-what-google-did-just-keep.html

Page 34: WordPress Accessibility - WordCamp Buffalo 2016

Use :focus Styles

https://www.virginamerica.com/

Page 35: WordPress Accessibility - WordCamp Buffalo 2016

Use :focus Styles

• Particularly if you removed link underlines,• Everywhere you have :hover, add :focus,• Look for :focus{outline:none;} in libraries:• If you find it, remove it.

• Easy to test with the tab key.

http://adrianroselli.com/2014/06/keep-focus-outline.html

Page 36: WordPress Accessibility - WordCamp Buffalo 2016

Tritanopia

Color Contrast

Page 37: WordPress Accessibility - WordCamp Buffalo 2016

Protanopia

Color Contrast

Page 38: WordPress Accessibility - WordCamp Buffalo 2016

Deuteranopia

Color Contrast

Page 39: WordPress Accessibility - WordCamp Buffalo 2016

Color Contrast

• Is there enough contrast?• Are hyperlinks, menus, etc. still visible?• WCAG 2.0:• 4.5:1 for normal text• 3:1 for large text (14+pt & bold, or 18+pt)

• Tools:• Chrome Color Contrast Analyzer• Lea Verou’s Contrast Ratio• WebAIM Color Contrast Checker• CheckMyColours.com

http://www.inpixelitrust.fr/blog/en/tips-create-accessible-color-palette/http://alistapart.com/blog/post/easy-color-contrast-testing

Page 40: WordPress Accessibility - WordCamp Buffalo 2016

Use <label> (properly)

Page 41: WordPress Accessibility - WordCamp Buffalo 2016

Use <label> (properly)

• Match the for attribute to the field’s id attribute.

• When you click label text next to a text box, does the cursor appear in the field?

• When you click label text next to a radio / checkbox, does it get toggled?

• When you click label text next to a select menu, does it get focus?

http://www.karlgroves.com/2013/09/05/the-6-simplest-web-accessibility-tests-anyone-can-do/

Page 42: WordPress Accessibility - WordCamp Buffalo 2016

Use HTML5

Page 43: WordPress Accessibility - WordCamp Buffalo 2016

Use HTML5

<header role="banner">

<nav role="navigation">

<aside role="complementary">

<form role="search">

<footer role="contentinfo">

<main role="main">

Page 44: WordPress Accessibility - WordCamp Buffalo 2016

Use HTML5

“Mobile” often means narrow screen in RWD, as well as this context.

Page 45: WordPress Accessibility - WordCamp Buffalo 2016

Use HTML5

<header role="banner">

<nav role="navigation">

<aside role="complementary">

<form role="search">

<footer role="contentinfo">

<main role="main">

“Mobile” often means narrow screen in RWD, as well as this context.

Page 46: WordPress Accessibility - WordCamp Buffalo 2016

Use HTML5

• Sectioning elements already have accessibility built in. Use them.• <header>• <nav>• <main> (one per page)• <aside>• <footer>• <form> (a search form)

This stuff is baked in!

Page 47: WordPress Accessibility - WordCamp Buffalo 2016

Use Only One <main> per Page

Modified version of Hixie’s image at https://github.com/whatwg/html/issues/100#issuecomment-138620240

Page 48: WordPress Accessibility - WordCamp Buffalo 2016

Use Only One <main> per Page

• <main> maps directly to role="main",• AT users expect one main content block, may

miss subsequent <main>s,• AT doesn’t expose that there are multiples,• Can erode trust in landmark navigation.

http://adrianroselli.com/2015/09/use-only-one-main-on-a-page.html

Page 49: WordPress Accessibility - WordCamp Buffalo 2016

Use <h#> Wisely

Page 50: WordPress Accessibility - WordCamp Buffalo 2016

Use <h#> Wisely

• Use only one <h1> per page,• Don’t skip heading levels,• Use appropriate nesting,• There is no Document Outline Algorithm:• Don’t use <h1> within every new <section> nor <article>,

• This will not affect your SEO.

http://adrianroselli.com/2013/12/the-truth-about-truth-about-multiple-h1.html

Page 51: WordPress Accessibility - WordCamp Buffalo 2016

<button>, <input>, or <a>

http://adrianroselli.com/2016/01/links-buttons-submits-and-divs-oh-hell.html

Page 52: WordPress Accessibility - WordCamp Buffalo 2016

<button>, <input>, or <a>

http://adrianroselli.com/2016/01/links-buttons-submits-and-divs-oh-hell.html

Page 53: WordPress Accessibility - WordCamp Buffalo 2016

<button>, <input>, or <a>

• Don’t use a <div> nor <span>.• Does the control take me to another URL?• Use an <a href> .• Note: does not fire on space-bar.

• Does the control change something on the current page?• Use a <button>.

• Does the control submit form fields?• Use a <input type="submit"> or <button type="submit">.

http://adrianroselli.com/2016/01/links-buttons-submits-and-divs-oh-hell.html

Page 54: WordPress Accessibility - WordCamp Buffalo 2016

Don’t Use tabindex > 0

https://www.digitalgov.gov/2014/11/17/user-experience-impossible-the-line-between-accessibility-and-usability/

Page 55: WordPress Accessibility - WordCamp Buffalo 2016

Don’t Use tabindex > 0• tabindex="-1"• Use to set focus with script,• Does not put it in tab order of page.

• tabindex="0"• Allows user to set focus (eg: via keyboard),• Puts in tab order of page (based on DOM).

• tabindex="1" (or greater)• Do not do this,• Messes with natural tab order.

http://adrianroselli.com/2014/11/dont-use-tabindex-greater-than-0.html

Page 56: WordPress Accessibility - WordCamp Buffalo 2016

Maybe Use tabindex = 0

http://adrianroselli.com/2016/02/keyboard-and-overflow.html

Page 57: WordPress Accessibility - WordCamp Buffalo 2016

Maybe Use tabindex = 0

• Do you have scrolling content boxes?• Keyboard users cannot access it.

• Do you have content that displays on hover?• Keyboard users probably cannot access it.

• A technique:• <div role="region" aria-label="[if appropriate]" tabindex="0">

http://adrianroselli.com/2016/02/keyboard-and-overflow.html

Page 58: WordPress Accessibility - WordCamp Buffalo 2016

Set lang attribute on <html>

http://codepen.io/aardrian/pen/rOGYNL

Page 59: WordPress Accessibility - WordCamp Buffalo 2016

Set lang attribute on <html>

http://codepen.io/aardrian/pen/rOGYNL

Page 60: WordPress Accessibility - WordCamp Buffalo 2016

Set lang attribute on <html>

• VoiceOver uses to auto-switch voices,• VoiceOver uses appropriate accenting,• JAWS loads correct phonetic engine /

phonologic dictionary,• NVDA matches VoiceOver and JAWS,• Use the correct lang value:• Sub-tags are ok,• Avoid private-use: en-GB-x-hixie

http://adrianroselli.com/2015/01/on-use-of-lang-attribute.html

Page 61: WordPress Accessibility - WordCamp Buffalo 2016

Source Order Matters

http://codepen.io/aardrian/full/MavVeb/

Firefox

Chrome

Page 62: WordPress Accessibility - WordCamp Buffalo 2016

Source Order Matters

• CSS techniques allow visual order to break from DOM order:• Floats,• Absolute positioning,• Flexbox (see 5.4.1 of ED for a11y note),• Grid (read Rachel Andrew on subgrid).

• WCAG 1.3.2 and 2.4.3 describe meaningful sequence and tab order matching visual flow,

• Different behavior among different browsers.http://adrianroselli.com/2015/09/source-order-matters.html http://200ok.nl/a11y-flexbox/

Page 63: WordPress Accessibility - WordCamp Buffalo 2016

Don’t Disable Zoom

http://codepen.io/aardrian/full/dYNJOVhttp://codepen.io/aardrian/full/ojBpjw

Page 64: WordPress Accessibility - WordCamp Buffalo 2016

Don’t Disable Zoom

• Allow users on mobile to zoom in,• Look in <meta name="viewport"> for this:

• minimum-scale=1.0• maximum-scale=1.0• user-scalable=no

• Look in @-ms-viewport {} for this:• zoom:1.0

• Enhance!• (Google AMP HTML is getting fixed)

http://adrianroselli.com/2015/10/dont-disable-zoom.html

Page 65: WordPress Accessibility - WordCamp Buffalo 2016

Avoid Infinite Scroll

http://www.pewresearch.org/category/publications/

Page 66: WordPress Accessibility - WordCamp Buffalo 2016

Avoid Infinite Scroll

• Makes it impossible to access some content:• Footer,• Sidebar links.

• Destroys the back button,• Makes it impossible to share a URL to specific

“page” of results,• Makes it impossible to jump ahead several “pages”

of results,• Can overwhelm AT users, less powerful devices.

http://adrianroselli.com/2014/05/so-you-think-you-built-good-infinite.htmlhttp://adrianroselli.com/2015/05/for-infinite-scroll-bounce-rate-is.html

Page 67: WordPress Accessibility - WordCamp Buffalo 2016

Reconsider Typefaces for Dyslexia

http://opendyslexic.org/try-it/

Page 68: WordPress Accessibility - WordCamp Buffalo 2016

Reconsider Typefaces for Dyslexia

• Use good typography rules:• Avoid justified text,• Use generous line spacing / leading,• Use generous letter spacing,• Avoid italics,• Generally use sans serif faces,• Use larger text,• Use good contrast,• Use clear, concise writing.

http://adrianroselli.com/2015/03/typefaces-for-dyslexia.html

Page 69: WordPress Accessibility - WordCamp Buffalo 2016

Test in Windows High Contrast Mode

Page 70: WordPress Accessibility - WordCamp Buffalo 2016

Test in Windows High Contrast Mode

• It removes CSS background images,• This is changing in a coming Edge release.

• Colors defined in your CSS are overridden,• To activate:• Left ALT + left SHIFT + PRINT SCREEN

• Media queries:• -ms-high-contrast: active• -ms-high-contrast: black-on-white• -ms-high-contrast: white-on-black

http://adrianroselli.com/2012/08/css-background-images-high-contrast-mode.html

Page 71: WordPress Accessibility - WordCamp Buffalo 2016

Use Captions/Subtitles

https://www.youtube.com/watch?v=V592VMJeXc8

Page 72: WordPress Accessibility - WordCamp Buffalo 2016

https://www.youtube.com/watch?v=zCqN_cCLnnk

Use Captions/Subtitles

Page 73: WordPress Accessibility - WordCamp Buffalo 2016

Use Captions/Subtitles

• Everybody uses them:• Working in public, in bed, at home,• Surfing in public, in bed, at work.

• Should include audio descriptions,• Should include speaker identification,• Review auto-captions (“craptions”):• NoMoreCraptions.com

http://adrianroselli.com/2013/11/captions-in-everyday-use.html

Page 74: WordPress Accessibility - WordCamp Buffalo 2016

Use Captions/Subtitles

• Do video/audio clips have text alternatives?• Are links to closed-captions or transcripts built into

the player or separate text links?• Is there an audio description available?• Tools:• Media Access Australia YouTube captioning tutorial,

Vimeo captioning tutorial,• Tiffany Brown’s WebVTT tutorial,• DIY Resources for Closed Captioning and Transcription

from 3 Play Media.http://webaim.org/techniques/captions/

Page 75: WordPress Accessibility - WordCamp Buffalo 2016

Share a11y Experiences

http://blog.podio.com/2015/07/08/hard-truths-helped-us-start-improving-podio-experience-visually-impaired/https://medium.com/medium-eng/five-goofy-things-medium-did-that-break-accessibility-3bc804ae818d

Page 76: WordPress Accessibility - WordCamp Buffalo 2016

Share a11y Experiences

• We’re all trying to do what we can,• Don’t attack someone who doesn’t know what

they don’t know,• Someone may find something you never

considered,• You may get feedback on something you never

considered,• a11ywins.tumblr.com FTW:• Thanks to Marcy Sutton.

http://adrianroselli.com/2015/07/lets-share-more-accessibility-experiences.html

Page 77: WordPress Accessibility - WordCamp Buffalo 2016

Key Takeaways

4 of 4 sections.

Page 79: WordPress Accessibility - WordCamp Buffalo 2016

≠ Checklist

• Accessibility is not a checklist.

No matter how pretty that checklist looks nor how many items you get to check.

Page 80: WordPress Accessibility - WordCamp Buffalo 2016

Snowtreeramp

“Wheelchair ramp at pharmacy not only hasn’t been cleared of snow but has 2 potted trees to ensure nobody can pass.”

Nicolas Steenhouthttps://twitter.com/vavroom/status/571092086365261824

Page 81: WordPress Accessibility - WordCamp Buffalo 2016

= Process

• Accessibility is not a checklist.• Accessibility is an ongoing process.

You know, kinda like all software.

Page 82: WordPress Accessibility - WordCamp Buffalo 2016

WordPress AccessibilityPresented by Adrian Roselli for WordCamp Buffalo 2016

My thanks and apologies.

Slides from this talk will be available at rosel.li/WCBuf