WordPress.org

Ready to get started?Download WordPress

Make WordPress Accessible

Updates from November, 2012 Toggle Comment Threads | Keyboard Shortcuts

  • esmi 3:54 pm on November 26, 2012 Permalink  

    Core Accessibility Updates 

    With WordPress 3.5 due out in the next few weeks, has there been any work done to increase core accessibility?

    The answer is an overwhelming “Yes!”

    Since WordPress 3.4, 35 separate accessibility Trac tickets have been raised — many since July 2012 — and more than half have already been resolved in WordPress 3.5. The breakdown is as follows:

    • 18 tickets already resolved and implemented in WordPress 3.5.
    • 1 ticket being worked on for WordPress 3.5
    • 7 tickets awaiting review
    • 9 tickets slated for a future version of WordPress

    Much of this flurry of activity followed Graham Armfield’s WordPress and Web Accessibility presentation at WordCamp UK earlier this year. And Graham has published an overview of the accessibility changes since then.

    However, as Graham points out, we still need people to report issues as, and when, they find them if we want this level of activity to be maintained. You can, of course, raise your own Trac tickets but if that is too difficult (or just too plain intimidating) for you, you can raise issues here for discussion and we will raise a ticket if necessary.

    Testers are, also, always needed to ensure that submitted patches do actually fix a problem and do so without raising another barrier elsewhere. The larger the testing pool – both in terms of users and the assistive technology used — the better. So if you do use any assistive technology and would like to help, please let us know.

     
    • Cyndy Otty 4:11 pm on November 26, 2012 Permalink | Log in to Reply

      This is very good and encouraging news. :-)

    • Graham Armfield 5:26 pm on November 26, 2012 Permalink | Log in to Reply

      Just to echo Esmi’s comments, I’ve started to do some testing with Dragon Naturally Speaking – speech recognition software used by some with motor impairments. I’m still new to it and finding my way around so don’t know all the necessary techniques.

      So we could really do with some people who are familiar with using Dragon to do some testing. I’m aware of issues still within Theme Customizer and Dragon. Where we (collectively) do find issues it would also be useful to think if there are any other websites where comparable functionality is working OK with AT. That way the developers can perhaps get some clues as to what’s happening – or not happening.

    • esmi 5:47 pm on November 26, 2012 Permalink | Log in to Reply

      I’ve used Dragon (for real for about 6 months – coding with it is… interesting), so I could look at dusting my copy off, if that helps. That said, the Dragon developers really only support IE, so the rest of us have to use a fairly basis sub-set of commands that replicate keyboard navigation using the TAB key for the most part.

    • Sveta 3:11 am on November 30, 2012 Permalink | Log in to Reply

      It would also be great if all online WP videos (like on WordPress.tv) had quality captions. I’m one of hundreds millions of deaf and hard of hearing people who cannot access aural information unless audio transcription is provided. I also presented at a WP meetup in NYC earlier this fall to discuss the web accessibility issues: http://www.youtube.com/watch?feature=player_embedded&v=6sTYOTB8hC8#!

    • xaoc 11:09 am on December 2, 2012 Permalink | Log in to Reply

      Hi. Why don`t you make wordpress with control panel features so it won`t depend on the cpanel or plesk or other paid control panel… :D

      • Ipstenu (Mika Epstein) 4:39 pm on December 2, 2012 Permalink | Log in to Reply

        Because WordPress is a web application, not a server one :) cPanel and Plesk are for controlling your server and server instance. It’s the difference between your Control Panel and MS Word.

  • esmi 3:49 pm on November 12, 2012 Permalink  

    We’ve now completed the draft Theme Accessibility Audit Criteria and have settled on a proposed new theme tag: accessibility-ready. We’re now discussing how the new Accessibility Audit can be added to the workflow of the Theme Review Team. As this is going to involve some programmatic changes to the current theme submission system, this might take some time to iron out but I’ll try to keep everyone updated with the progress.

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel