[wp-hackers] Accessibility of WP back end

[Jennifer Hodgdon]

That is good to know. Jeremy: I have read that some of the dynamic 
update things could be difficult for (blind) screen reader users. How 
does your blind author like the Tags section, when he adds a tag and 
it appears? Can he use the X buttons to delete the tags?

In any case, blindness is not the only issue. From the introduction to 
the WCAG guidelines (http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/):

     * They may not be able to see, hear, move, or may not be able to 
process some types of information easily or at all.
     * They may have difficulty reading or comprehending text.
     * They may not have or be able to use a keyboard or mouse.
     * They may have a text-only screen, a small screen, or a slow 
Internet connection.
     * They may not speak or understand fluently the language in which 
the document is written.
     * They may be in a situation where their eyes, ears, or hands are 
busy or interfered with (e.g., driving to work, working in a loud 
environment, etc.).
     * They may have an early version of a browser, a different 
browser entirely, a voice browser, or a different operating system.

    --Jennifer

ps: I filed a bug on the JS issues.
    http://core.trac.wordpress.org/ticket/9698


Jeremy Clarke wrote:
> FWIW we have a blind author on our site and he does fine with WP and
> his screen reader. I'm sure there are some readers that can't handle
> it as well but his success implies that WP is at least good enough
> that someone can work it out.
> 
> Interesting fact: he *prefers* tinymce. Apparently it's more
> accessible to his screen reader than the code view. (I know a lot of
> people like it these days, but that still seems counter-intuitive to
> me :P )

-- 
Jennifer Hodgdon * Poplar ProductivityWare
www.poplarware.com
Drupal, WordPress, and custom Web programming