Make WordPress Accessible

Updates from August, 2013 Toggle Comment Threads | Keyboard Shortcuts

  • esmi 9:00 am on August 9, 2013 Permalink
    Tags: , ,   

    Title Attributes Galore 

    The patches for Trac ticket 24766 are slated for addition to WordPress 3.7. This is great news for assistive technology users who have been forced to wade through a sea of unnecessary title attribute verbiage. But we need to ensue that the patches cover all unnecessary title attributes and that those deliberately excluded from the patches do not present any accessibility issues.

    Currently, the excluded methods, functions and scripts are:

    • the_author_posts_link()
    • rss.php
    • wp_fullscreen_html()
    • get_adjacent_post_rel_link()
    • _walk_bookmarks()
    • get_image_tag()
    • the_shortlink()

    (More …)

    • David A. Kennedy 12:02 pm on August 9, 2013 Permalink | Log in to Reply

      I’m wondering if we missed any? I believe some functions, like

      get_the category_list



      have title tags built in as well. I’m not as familiar with core so looking through the diff makes it hard to tell. Commenting here to get opinions and not junk up the ticket.

      • Amy Hendrix (sabreuse) 3:53 pm on August 9, 2013 Permalink | Log in to Reply

        Both of those functions are included in the patch that’s currently on the ticket — you can see the full list at the ticket link.

        The list in this post is just the ones that I left off the patch, either because they’re deprecated functions (which means aren’t actually used in core anywhere, and we normally wouldn’t make any changes to them unless it was for something like security), or because the title attributes are being used for help and not just labels (and in that case, they should get a better solution rather than just being deleted without any kind of fallback).

        It’s definitely not a problem to get this batch in, and still pick up any that were missed in subsequent patches.

        • esmi 4:16 pm on August 9, 2013 Permalink | Log in to Reply

          Understood, But my concern is how to handle wp_fullscreen_html()

          • Amy Hendrix (sabreuse) 5:08 pm on August 9, 2013 Permalink | Log in to Reply

            Yep, got that — I was just trying to answer David’s question about other functions that didn’t appear in this post.

            On with the wp_fullscreen_html() discussion, which is definitely a tougher case than most of these!

    • Joe Dolson 8:58 pm on August 10, 2013 Permalink | Log in to Reply

      I think we need to consider some alternatives for the wp_fullscreen_html labels and interface generally — this is definitely not a simple case of removing the title attributes alone. It should probably be pushed as a separate ticket; it’s related, but it seems sufficiently different that treating it independently is worth while. Thoughts on that?

    • Joe Dolson 5:55 pm on August 21, 2013 Permalink | Log in to Reply

      So, went to work on this to create the ticket, and decided that I first needed to create a ticket on keyboard focus — there are a lot of problems with keyboard focus in the full screen editor, so it’s nearly impossible to use with a keyboard. Ticket 25111.

  • esmi 2:58 pm on August 8, 2013 Permalink
    Tags: , , ,   

    IRC Meeting: August 7, 2013 

    A very busy & productive meeting. We’ve identified two high priority areas that we’d like to focus on in the next couple of months.

    (More …)

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc
Skip to toolbar