Accessible Text Editor Options – Accessibility First

Date: April 14, 2016

Location: University Library, Room 323C

Attendees:
Ku, JaEun, Gunderson, Jon R, Weathers, William Fletcher, Lane, Lori, Hoyt, M Nicholas

Investigate text editor menu structure and its custom configuration to ensure a11y when the users author the contents (ie, heading structure menu should be more visible than styling menus such as bold or italic styling)
Adding images and video to contents – “add media” UI in wordPress – how and in which way (tooltips, instruction underneath the alt text form field?) we can optimize UI for adding images (considering SEO, best image tagging practices and more) – ICEBOX

WYSIWYG editor in OneNet: Jon Gunderson and Mike Scott – Texteditor from OneNet is built from scratch — back when we built it, Mike had trouble getting any of the existing editors (or the contentEditable implementation in browsers besides IE) to produce HTML that he could work with. He would be interested in working on updating and/or porting it over to TinyMCE if that’s something Library IT might be working on
WordPress CKeditor
CK editor 4 documentation: Nick Hoyt – CKEditor’s WCAG Checkpoints page, they are claiming that list markup and use of headings are not applicable. On top of that, the compliance page is based on WCAG 1.0. (WCAG 2.0 became a standard in December 2008)
TinyMCE: WordPress default editor
TinyMCE + Quail library in WordPress, which is also used at CKEditor accessibility checker: Jon Gunderson – the author will not be able to fix (or even understand) and the messaging from Quailjs.js rules will most likely not help the author to know how to fix the problem using TinyMCE or other WYSIWYG editors

Configuration of editor to support custom feature
APIs to support update editing controls based on context (e.g. heading level)
APIs to inspect content before insertion (e.g. IMG ALT Text, Headers for Tables)
APIs to support continuous accessibility feedback