WordPress.org

Make WordPress Accessible

Updates from July, 2015 Toggle Comment Threads | Keyboard Shortcuts

  • Rian Rietveld 10:25 am on July 28, 2015 Permalink
    Tags:   

    Team chat Summary, July 27, 2015 

    A11y tickets

    #29102: we decided on closing this ticket, autofocus on the search form is not a good idea a11y wise.

    #31363, #23432 and #31386 all address the same issue: when to open links in a new window. After some discussion, also with @ceo, who uses a screen reader, we came up with the following:

    • no links should open in a new window (to be consistent throughout the Admin)
    • already made settings might be lost, so before following a link, the user must be warned like: “there are unsaved changes….”
    • an alternative, but complex solution would be that settings are auto saved before leaving a window
    • we should do a search on all links that open in a new window in the Admin

    We will comment with tickets #31363 and #31386, suggesting to close them. And continue to work on this issue further with ticket #23432.

    #21414: a 3 year old ticket by @azaozz about enabling/disabling the keyboard shortcuts in the user profile settings. For assistive technology it can be useful to disable them. We will comment on the ticket to start the conversation again.

    _s

    @davidakennedy committed a change in the heading structure in _s.
    It should be easier to create accessible-ready themes now with Underscores.

    Testing

    The accessibility testers are trying out if they can download an export file in the Admin/ Tools/Export with all kind of assistive technology, results will be in July 30. First results look promising.

    Spam

    The application form for new a11y testers is temporary offline, because of the huge amount of spam. It’s on Sams to-do list.

    Knowbility OpenAIR project

    @accessibjoe is looking for volunteers to be accessibility mentors for the Knowbility OpenAIR project this year. To get development teams and accessibility mentors together and they help non-profits create websites.

     
  • Joseph Karr O'Connor 8:45 am on July 8, 2015 Permalink
    Tags: , ,   

    H1 in the admin

    For 4.3 there will be an H1 in the admin. #31650: Missing H1 heading in the admin. Assistive technology users look for the H1 for way finding. Though there is the page title, when AT separates out elements such as links, lists, and headings, the info needs to be there too. Two weeks ago we ran this by Mika Epstein @Ipstenu and she helped us understand heading levels and plugins. Mika spot checked some plugins and it showed that they are using H2 and her opinion is that “we can post about that in make/plugins to try and spread the word.” Thanks Mika. More work will be done on the rest of the hierarchy.

    Main Open Tickets

    We also briefly discussed:

    • #31661: Quicktags: Can’t add them using just a keyboard in IE,
    • #26601: Inappropriate content in headings on admin screens,
    • #32152 List table: sortable column headers accessibility,
    • #26601: Inappropriate content in headings on admin screens, and
    • #31336: Customizer: separate navigation from options UI for better UX by removing accordion behavior.
     
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