Presented at 11:45am in Meadowbrook I on Friday, November 18, 2016.#4944
- Joe Dolson, Cheese
- Length of Session: 1-hr
- Expertise Level: Expert
- Type of session: General Conference
WordPress has made great progress in recent years towards an accessible back-end, and has improved its capabilities for creating accessible web sites. The Authoring Tool Accessibility Guidelines throw in additional questions to address. Does WordPress encourage creating an accessible web site? How easy it this? Where does WordPress fall short?
While the recent progress in WordPress has made it easier to create an accessible web site, there are still gaps when it comes to meeting the expectations of a fully ATAG-compliant authoring tool. WordPress fails at making it easy to add certain types of alternative content, creating richly semantic content, and doesn't contain many tools for checking or enforcing accessible content. I'll discuss some of the ways that you can make WordPress better at this, so that your WordPress set up can better encourage great accessibility from the beginning.
- What ATAG requires that's unique from WCAG
- Where does WordPress fail to encourage creating accessible content.
- How can you use plug-ins and themes to encourage and enforce accessible content.
Cognitive/Learning, Deaf/Hard of Hearing, Mobility, Vision
Check "quotes" and apostrophe's. Check saving in admin profile editor.