[WG: Accessibility] [Management] 2.7.0: FckEditor upgrade to CK3.0.1

[Ken Petri]

Hi Eli,

I think Hadi is the best one to address this. He is screen reader reliant. I
just use them for testing.

However, in my experience you gain two things from a
markdown/textile/wikitext form of input: 1) Since you are working with just
text, there are no UI complications for either screen reader or
keyboard-only users, and 2) End users are much more conscious of what they
are doing in terms of the semantics of a page and, if your parser is good,
you can guarantee perfect HTML output (outside of HTML intentionally
included by end users).

Hadi has worked closely with systems that take wikitext/textile input for
HTML rendering. He is also a very experienced developer.

Best,
ken


On Tue, Nov 3, 2009 at 3:05 PM, Eli Cochran <eli at media.berkeley.edu> wrote:

> Ken,
> I'm curious about your recommendation. Is your experience that the overhead
> and complexity of navigating rich text controls with the keyboard makes it
> more appealing to screen reader users or keyboard users to use a wiki-style
> markup language instead? It actually makes a lot of sense to me, but I'd
> never really thought about it, nor have I heard this before.
>
> Thanks,
> Eli
>
> On Nov 3, 2009, at 10:31 AM, Ken Petri wrote:
>
> Though I'm not involved in the Sakai Access WG except as a lurker (and now
> a poster, I guess), my ultimate recommendation would be to offer an option
> to use Textile or WikiText or Markdown or some similar text
> based/interpreted for content editors.
>
>
>  . . . . . . . . . . .  .  .   .    .      .         .              .
>                 .
>
> Eli Cochran
> user interaction developer
> ETS, UC Berkeley
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20091104/c910a93a/attachment.html