WordPress.org

Make WordPress Accessible

Updates from June, 2013 Toggle Comment Threads | Keyboard Shortcuts

  • Joe Dolson 4:54 am on June 29, 2013 Permalink
    Tags: , , , media,   

    Potentially useful accessibility plug-in I learned about today at WordCamp Chicago: https://wordpress.org/plugins/media-ally/

     
  • esmi 8:01 pm on June 25, 2013 Permalink
    Tags: , ,   

    Next IRC Meetup 

    Just a quick reminder that the next IRC meetup will be on Wednesday, 26 June at 19:00 UTC in #wordpress-iu.

    Everyone welcome!

    If you have never attended an WordPress IRC meetup before, you can find all of the details you will need to join in the Codex’s IRC page.

    One topic for discussion is likely to be the development of a proposed accessibility statement for WordPress. To whet your appetite and give you an idea of what we could aim for longer term, have a look at Drupal’s accessibility statement.

     
  • esmi 12:49 pm on June 25, 2013 Permalink
    Tags: , html5,   

    Should We Be Dropping the Role Attribute in Twenty Thirteen Yet? 

    Your feedback is requested on Trac Ticket 24629.

    Cited example: Should the Twenty Thirteen drop the use of the role attribute on the HTML5 nav element on the grounds that the element, by definition, has the role of navigation? Or should role="navigation" be retained in order to support technologies that are not yet HTML5 aware?

    My own opinion that the role attribute should be retained for the time being in order to support the widest range of technologies. Dropping it would offer only a marginal benefit in reducing page bloat. Please do weigh in with your opinions on the ticket.

     
    • tady 12:59 pm on June 25, 2013 Permalink | Log in to Reply

      Deffo not. The role attribute is still as important now as it was pre-HTML5. A cited counter example: The main element (<main>) has only just been introduced to the HTML5 spec and is recommended it take the format:

      <main role=”main”>

      Personally feel that it doesn’t make any more or less work to include it. I wouldn’t be in such a rush to remove attributes such as this any time soon. The spec has a long way to go and will change again before it is fully RC, so I reckon removing helpful attributes like roles have the possibility of shooting us in the foot at some point in the future.

    • _Redd 1:17 pm on June 25, 2013 Permalink | Log in to Reply

      Don’t drop it. We’re finding that HTML5 attributes are starting to gain support, and we’re including it in our sites.

    • ceo 2:54 pm on June 25, 2013 Permalink | Log in to Reply

      While I don’t think we should be bound to supporting users with outdated software, which isn’t to say state-of-the-art is fully supporting HTML5 anyway, I think the pros of keeping it far outweigh the cons of not.

    • gogreener 1:40 am on June 26, 2013 Permalink | Log in to Reply

      Agreed. Is it possible to set a reminder to review it again at a later date?

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
Skip to toolbar