[#SAK-11783] Accessibility: Multiple accessibility problems with FCK editor

Sakai

Accessibility: Multiple accessibility problems with FCK editor

Created: 02-Oct-2007 12:59 Updated: 23-Oct-2008 06:30

Component/s:

WYSIWYG Widget (FCK Editor), Accessibility

Affects Version/s:

2.5.0, 2.5.2, 2.5.3

Fix Version/s:

None

Time Tracking:

Issue & Sub-Tasks

Issue Only

Not Specified

Environment:

Various

2.4.x Status:	None
2.5.x Status:	None
2.6.x Status:	None

Sub-Tasks:

All

Open

1.	Accessibility--FCK editor inaccessible	Open	Unassigned
2.	Accessibility--WYSIWYG Editor Focus	Open	Unassigned
3.	Accessibility--Problems using FCKEditor with a screen reader	Open	Unassigned
4.	Accessibility: Cannot style text in FCK Editor when using screen reader	Open	Unassigned
5.	Accessibility: Edit field is unlabeled for FCK editor (Messages)	Open	Unassigned
6.	Accessibility: Text edit box has no label in FCK editor (Syllabus)	Open	Unassigned

Description

« Hide

The FCK Editor has numerous accessibility issues and crosses multiple tools. I have attached the following problems as subissues: Text box for input is unlabeled; exiting from text box is difficult; formatting options for text are unlabeled; formatting options cannot be accessed from the text box when using a screen reader.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Peter A. Knoop - 12-Oct-2007 12:31

I'm sure Joshua will weigh-in here too, but most of these problems are probably dependent on the third-party FCKeditor fixing these things. I'm not sure there is much we can do in Sakai about this.

[ Permlink | « Hide ]

Joshua Ryan - 13-Nov-2007 17:19 - edited

Peter nailed it, this is a shortcoming of the editor currently that they are supposedly working on.

[ Permlink | « Hide ]

Megan May - 27-Nov-2007 19:04

Peter, how do we typically handle issues reported against 3rd party code in Sakai's JIRA?

[ Permlink | « Hide ]

Peter A. Knoop - 27-Nov-2007 21:32

We generally handle them on a case-by-case basis. In this particular case its probably best to leave this issue (and its subtasks) open so they are flagged as "known issues" with Sakai for folks interested in accessbility. The accessibility review can re-test them when Sakai upgrades to a newer version of FCK or replaces it with a different WYSIWYG editor.

[ Permlink | « Hide ]

Peter A. Knoop - 27-Nov-2007 21:34

Megan, I've also downgraded the priority to the default of Major, since its really out of our hands here, and to get it off of your list of Critical issues that folks in the community are able to work on.

[ Permlink | « Hide ]

Peter A. Knoop - 27-Nov-2007 21:42

I've also unassigned these issues until we have a way forward to fix them. I've seen some discussion on sakai-dev of other WYSIWYG editors being looked at. Maybe one of those will attract sufficient interest and resources to make it into 2.6 or a future release.

[ Permlink | « Hide ]

Michael Elledge - 05-Feb-2008 10:11

This is a critical issue for resolution. Our WYSIWYG editor puts us at a major disadvantage vs. other CMS and is also a problem for screen reader users.

[ Permlink | « Hide ]

Peter A. Knoop - 07-Feb-2008 08:36

The list of sub-tasks here provides a good set of things to test and evaluate in any alternative WYSIWYG editors that we want to consider.