[WG: Accessibility] Creation of Verbose CK Editor Accessible Content Creation Guidelines

[Humbert, Joseph A]

Hi AWG,

Over the past few AWG teleconferences the group has been fleshing out a skeletal set of accessibility guidelines for content created using Sakai's rich text editor CK Editor.  Due to many factors, I would like to move this topic to the list to solicit feedback and contributions from people on this list who may not attend the teleconference calls. Below is our current progress:

CK Editor Accessibility Guideline Categories (CK Editor v3.6)
Alternative text descriptions for Images

*         alt (heuristics TBD), if complex add a paragraph, if paragraph is a problem then longdesc

Requiring of alternative text for image links

*         needs a alt if image is anchor for a link

Heading structure

*         start with an h4, can use h5, h6

*         except HTML Resource, all headings are allowable

*         what can be a heading candidate (short, title-like)

*         separate structure from visual styling (h6 with font size of 22)

Semantically coded lists
Proper list nesting

*         when not to use a  list (one item)

Use of only color to convey information. For example, "click the blue button on the left."
Color Contrast

*         example?

*         link to checker

*         link to color picker tool

Inclusion of Skip navigation links

*         heuristic? when to do this?

*         not possible? target blank - bring up with community see KNL-1001

o   https://jira.sakaiproject.org/browse/KNL-1001

*         would describe as Table of Contents

Unique and Descriptive link text

*         make descriptive sense, identify uniquely

Identifying downloadable files

*         example: report (pdf)

*         identify file type in link text

Unique and Descriptive page titles (This may only be needed for external tools and Web pages).

*         only in HTML attachments

We need create verbose descriptions, add details and create examples, etc. for each of these guidelines. I am including a draft of the first guideline that can be used as a model:

Alternative text descriptions for Images
For every image embedded into the rich text editor, concise and descriptive alternative text should be provided. However, if the image is complex, an equally verbose description (paragraph) should be provided in the surrounding content. Finally, if the longer alternative text is not feasible, create a link to an external Web page that contains an appropriate description.
Heuristics

*         If the image is pure decorative or used for visual formatting, the alterative text description should be left blank to hide it from users of assistive technology

*         The alternative text should be no longer than 10 words or 160 characters.

o    If the image cannot be conveyed with this limitation, provide a longer description.

*         The image description should be contained in the surrounding content no further than 2 sentences before or after the image.

o     Where possible, use identifying descriptors to inform users of the description (e.g., Image caption, in the image on the left, etc.)

o    If the image description needs to occur farther away, link the description to the image (e.g. image Figure 1.3....In Figure 1.3 in section ****)

*         If an external link to the description is needed, make the purpose of the link clear in the link text (e.g., description of "Fresco Clean" image)

Steps to add alternative text

*         Activate the "image" button on the toolbar.

*         Locate the "Alternative Text" input form control in the dialog that is loaded after you activate the button.

*         Place the appropriate alternative text in the form control following the guidelines in the heuristics section.

Examples

*         Alt Text: "Scientist in a lab filling a vile with fluid"

*         Description: "A female forensic scientist is filling a vile containing a small about of blood with fluid to denature the sample as part of the process of the PCR analysis method of DNA profiling. In the background is a centrifuge which will aid in the process of extracting the DNA from the sample of blood."



If people would like to volunteer to create the first draft for each guideline, we can then discuss the draft on list or hold a special (off-week) teleconference.

I would like to set a goal of June 1 for the first draft of guidelines being sent to the list and an end date of June 31 for the completed guidelines.

Comments? Questions?

Joe Humbert, Accessibility Specialist
UITS Adaptive Technology and Accessibility Centers
Indiana University, Indianapolis and Bloomington
535 W Michigan St. IT214 E
Indianapolis, IN 46202
Office Phone: (317) 274-4378
Cell Phone: (317) 644-6824
johumber at iupui.edu<mailto:johumber at iupui.edu>
http://iuadapts.Indiana.edu/<http://iuadapts.indiana.edu/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130506/96f98ef4/attachment-0001.html