Transcript
Page 1: WordPress and ATAG Compliance

WordPress and ATAG

Compliance is a work in progress

Page 2: WordPress and ATAG Compliance

What does ATAG require?- An accessible user interface- The ability to create accessible

content- Promotion and integration of

accessible content creation

Page 3: WordPress and ATAG Compliance

An Accessible User Interface- Constantly improving- Committed to meeting WCAG 2.0

requirements- But it's a long way to go...

Page 4: WordPress and ATAG Compliance

Excluding WCAG 2.0, where does WordPress stand with ATAG?

Page 5: WordPress and ATAG Compliance

A.2 Editing Views Are Perceivable

Page 6: WordPress and ATAG Compliance

A.2.1 Make alternative content available to authors ✅ Image alternative text✓ Video captions: very difficult to manage

⛔ No support for audio description ⛔ No support for programmatically

associated transcripts of audio/video

Page 7: WordPress and ATAG Compliance

A.2.2 Editing view presentation can be programmatically determined ✅ Well, we think so...

⛔ ...but without any systematic testing.

Page 8: WordPress and ATAG Compliance

A.3 Editing Views Are Operable

Page 9: WordPress and ATAG Compliance

A.3.1 Provide keyboard access to authoring features

✅ All aspects of the admin are accessible via the keyboard.✓ Well, almost all.

⛔ But some require keyboard shortcuts that may be hard to discover.

Page 10: WordPress and ATAG Compliance

A.3.2 Provide authors with enough time

✅ WordPress has no time limitations.

Page 11: WordPress and ATAG Compliance

A.3.3 Help authors avoid flashing that could cause seizures ✅ Videos loaded in the editor do not play automatically.

⛔ Animated GIF images do play.

Page 12: WordPress and ATAG Compliance

A.3.4 Enhance navigation and editing via content structure

✅ Possible to discover the content structure for context

⛔ No ability to navigate via the content structure in the editor.

Page 13: WordPress and ATAG Compliance

A.3.5 Provide text search of the content

⛔ No method to search content within the visual editor

✅ All page content searchable within text editor using the browser's search feature

Page 14: WordPress and ATAG Compliance

A.3.6 Manage preference settings

✅ Preferences to change look & options in admin

⛔ No ability to modify the look and feel of the editor beyond text/visual

Page 15: WordPress and ATAG Compliance

A.3.7 Ensure previews are at least as accessible as in-market user agents ✅ Web-based previews in the browser.

Page 16: WordPress and ATAG Compliance

A.4 Editing Views Are Understandable

Page 17: WordPress and ATAG Compliance

A.4.1 Help authors avoid and correct mistakes

✅ WordPress revisions help restore main content;

⛔ Content outside the editor not always stored.

⛔ Settings are not reversible

Page 18: WordPress and ATAG Compliance

A.4.2 Document the user interface, including all accessibility features ✅ WordPress has extensive in-page documentation.

⛔ Do you know where it is? ⛔ Some complex features have minimal

documentation.

Page 19: WordPress and ATAG Compliance

B.1 Fully automatic processes create

accessible content

Page 20: WordPress and ATAG Compliance

B.1.2 Ensure that accessibility information is preserved

⛔ Editor strips some HTML and attributes, including ARIA attributes.

Page 21: WordPress and ATAG Compliance

B.2 Authors are supported in creating accessible content

Page 22: WordPress and ATAG Compliance

B.2.1 Ensure that accessible content production is possible ✅ It is.

⛔ No tools to assist with tabular data ⛔ No tools to assist with forms

Page 23: WordPress and ATAG Compliance

B.2.2 Guide authors to create accessible content

⛔ Alt attributes underexplained, underemphasized, frequently invalid

⛔ Media captions difficult to use ⛔ Hands-off approach to complex data

Page 24: WordPress and ATAG Compliance

B.2.3 Assist authors with managing alternative content for non-text content ✅ Alt attributes are editable, both in library and independently in editor.

⛔ Captions not editable

Page 25: WordPress and ATAG Compliance

B.2.4 Assist authors with accessible templates

✅ "accessible" themes are available ⛔ What constitutes an accessible theme

is...complicated

Page 26: WordPress and ATAG Compliance

B.2.5 Assist authors with accessible pre-authored content ✅ WordPress does not provide any pre-authored content.

Page 27: WordPress and ATAG Compliance

B.3 Authors are supported in improving the accessibility of

existing content

Page 28: WordPress and ATAG Compliance

B.3.1 Assist authors in checking for accessibility problems

⛔ Nope. Nothing.

Page 29: WordPress and ATAG Compliance

B.3.2 Assist authors in repairing accessibility problems

⛔ Nope. Nothing.

Page 30: WordPress and ATAG Compliance

B.4 Authoring tools promote and integrate their accessibility

features

Page 31: WordPress and ATAG Compliance

B.4.1 Ensure the availability of features that support the production of accessible content

✅ Accessibility features are enabled by default, and there is no option to disable them.

⛔ There aren't a lot of accessibility features...

Page 32: WordPress and ATAG Compliance

B.4.2 Ensure that documentation promotes the production of accessible content

⛔ It doesn't, for the most part, mention accessibility at all.

Page 33: WordPress and ATAG Compliance

Overall?

16⛔

24

Page 34: WordPress and ATAG Compliance

Some plugins that can help:WP Accessibility https://wordpress.org/plugins/wp-accessibility/Access Monitor https://wordpress.org/plugins/access-monitor/Accessible Video Libraryhttps://wordpress.org/plugins/accessible-video-library/

Page 35: WordPress and ATAG Compliance

Questions?Joe Dolson // [email protected] // https://www.joedolson.com


Recommended