Make WordPress Accessible

Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts

  • Rian Rietveld 12:51 pm on June 16, 2015 Permalink

    Team chat Summary, June 15, 2015 


    • #31650 Missing H1 heading in the admin: Has a working patch: @obenland will review if it can be committed. If this ticket is committed we can continue with the other heading related tickets.
    • #26601: Inappropriate content in headings on admin screens: Has a working patch, we discussed the option of adding a <header> or a <div class=“header”>. @trishasalas will comment on that ticket further.
    • List table tickets: in the last days some major changes to the List Tables were committed and some of them need a refresh. @aferica divided work: #32253 (pagination links) @rianrietveld#32254 (thumbnail link) @rianrietveld#32147 (headings) @joedolson; #32152(comments bubble) @joedolson; #32170(sortable columns) @afercia; #31654 (select all) @afercia.
    • #27705: Keyboard navigation should be constrained to the theme installer overlay. We discussed if this ticket could be closed and decided it was still relevant. @joedolson will comment to this ticket to explain why.
    • #29897:  Some focus styles are broken: This ticket was split in separate tickets that all have been fixed, so this ticket can be closed.
    • #30333: Media filtering behavior should be the same in list and grid mode displays. This solution was reverted back, to not using the auto submit, ticket will be set to closed/wontfix.
    • #30368: Issue with category selection using VoiceOver. @rianrietveld will let the test team look at this, if they can’t reproduce this, the ticket will be closed.
    •  #32600 wp.a11y.speak improvement: @afrecia wrote a patch so testing and feedback is more than welcome.

    Documentation and training

    New work

    • Better Password: @markjaquith created a patch (#32589) for a new password changing UI. We will have to do an a11y review on that.
    • Menu Customizer: the test team reviewed the menu customizer and the issues where reported to the dev team.



  • Rian Rietveld 2:10 pm on June 12, 2015 Permalink
    Tags: ,   

    Accessibility Usertest: Menu Customizer 

    • Tests done in June 4-9, 2015
    • Update June 14, results from Michelle DeYoung
    • Update June 18, results from Kim van Iersel
    • Update June 20, results from Michelle DeYoung (NVDA/ChromeVox, after integration into core)
    • Update June 23, results form Tobias Clemens Häcker (ChromVov, after integration into core)

    Questions for the test team

    Can you:

    • can you add a menu
    • can you fill it with menu items
    • can you remove a menu item
    • can you reorder a menu item
    • can you access the menu options
    • can you access the menu help

    Test results

    Shaun Everiss

    Testing using NVDA latest version, Firefox and Internet Explorer latest builds and windows 7

    Just did some tests on the menus.
    And I found them hard to navigate stuff all over the place.
    I think I reordered a menu successfully but no feadback.
    I can edit various items but I couldn’t find where to add one.
    I was able to find a menu button at the bottem of the page to add but didn’t manage to edit and add it.
    The structure was quite confusing.

    Reagan Lynch

    Testing using Windows 8.1, IE 11, and JAWS 16.

    First, to actually get into editing the menu is a lot of clicks and
    reading buttons that need to be expanded. by the time I was able to
    locate where to edit the actual menu in terms of the menu items
    themselves I felt kind of lost.

    The text on the button reads Add Links. It might be better to read
    something like Add Menue Item/Links or Add menu Item.

    I was able to add a menu and add links. However, I was *not* able to
    move any of the menu items. The move options are not clickable by
    screen  readers.

    From a usability/accessibility standpoint the menu customizer is slow
    and cluncky to use. It took me a good 15 minutes to add a menu which
    using the current menu tool would have taken me about 2 minutes.
    Granted I had to figure my way around the UI, so there’s that.

    I know the current proposal is to remove this feature from the menu in
    4.3 and place the menu creation function inside the customizer. I
    think I like the concept, but think we should punt it to 4.5 to ensure
    accessibility of the feature is strong. I think other parts of the
    customizer need a lot of accessibility work as well.

    Geof Collis

    Testing using JAWS 14.5 IE 11

    When I click on a sub heading I’m not sure where I am, took me a bit to realize so I would like the focus to be on the heading I clicked on and not the back button after the heading.

    Focus works well when I edit a menu item but I get dead air when I arrow through edit boxes , navigation and title attribute for example

    There are way too many sections here, I would like to see it set up the way the other menu section:
    1 area for all options
    list pages, categories etc without having to click on a heading.
    be able to change all attributes of a menu item in the same place, with this setup I have to go to another section to reorder, this is just to time consuming and annoying way they have it.
    Conclusion: If they are going to do away with the Menus section then just move it to the Customize section just the way it is.

    John Sexton

    On the whole I was able to do basic tasks, like select which menu is active for which location, add/remove links, reorder links and add new menus. It took a little while to figure out how it all worked but once I understood this, was able to use it. The issues are listed below, some are down to limitations of ARIA support in Supernova.

    Testing with Supernova V14 on Win7 64bit & IE11

    When using the reorder feature, there is no screen reader feedback to indicate the menus level, perhaps a level indicator can be added after the page title that says something like “top”, “level 1”, “level 2”, etc to show how far down the tree each menu item is. As this is only really to benefit screen reader users, it could be visually hidden using the CSS clip method.

    When adding new menu items, the overlay appears at the end of the page, which is not imediately obvious, perhaps moving focus to the top of this overlay on the click event of the add links button will help alternatively insert the overlay in the dom tree at the point where the add links button was clicked or where the link will be inserted.

    The level 4 headings in the add new menu items overlay are not declared as links, so is not obvious that they need to be clicked to show/hide content. Either use regular html anchors or add ARIA attributes to indicate these headings have a click action.

    Testing with NVDA V2015.1 on Win7 64bit & IE11

    The click events to select the menus tab or any section/menu within the tab, with NVDA you need to press enter twice, the first press appears to put NVDA into a form edit mode and the second press makes the selection and exits the form edit mode. Not sure why this is.

    When reordering menu items, NVDA anounces “menu is now a submenu item” or “menu item moved out of submenu”, which is useful, However, when reviewing the list while reordering, there is no indication at what level any given menu item is currently set to.

    When adding new menu items, the overlay is placed at the end of the dom tree, it will be better if placed either after the add links button or at the point where the links are inserted.

    The level 4 headings in NVDA also anounce “toggle”, to indicate the click action is required to show/hide options. This probably don’t work in Supernova V14, due to very limited ARIA support.

    Also the toggle state for collapse/expand menus in the preview panel, work in NVDA, were as Supernova doesn’t work so well, giving the same output for both states.

    Gabriela Nino de Rivera Torres

    VoiceOver and Safari.

    Adding a new menu

    Add a menu button: when the user select the button she hears “add a menu button press return or enter to open”. When clicking on on the button, a new menu name field and button appears, but the user is not aware of it.

    When the user clicks on “Create menu” the user hears that the menu was created. The new menu has a blue color that differentiates it of the rest, but when I try moving to another element in the page it gets berserk.

    I not sure if this weird behavior is due to using Safari, but when the interface gets crazy it is very difficult to find the way back to anything. At some point, a lot of elements that are hidden gets focus and it is very confusing to know were I am. After it gets berserk I need to refresh the page and start anew.

    It was difficult too to add an item to the menu. There is a lot happening on the screen that is not necessary told to the user.

    I will agree with previous comments, adding menus or items requires a lot of clicking and the way that page elements are organized makes very hard to understand the elements order with the screen reader.

    I prepared a video to show the strange behavior after clicking on the “Create menu” button.

    Michelle deYoung (June 14)

    Creating Menus, Keyboard only testing

    Tested in Windows 8.1 using FireFox, Chrome and Internet Explorer 9 with Keyboard only.

    Issue: Once a new menu is created, the keyboard focus is moved to the content area.
    Suggested: Keyboard focus should remain in the left sidebar menu section so the user can add items, reorder, delete menu, etc.

    Issue: The Reorder link receives focus, but does not reorder menu items when selected. The “Add Links” button might be more understandable if it is renamed.
    Suggested: Rename “Add Links” button to “Add Menu Item”.
    Add Links button

    Issue: When adding a Menu item, the item is added twice to the Menu sidebar.
    Menu item is added twice to the Menu sidebar.

    Issue: When tabbing from the ‘X’ to the “Add Links” button, there are 12 to 14 tabs that have no visible focus indicators. The number of tabs vary. I assume this is from hidden items that it is hitting.
    If ‘Enter is selected, it unfolds a blank area above the Customizing > Menus item.
    ‘X’ and “Save and Publish” only appear to get focus when the user tabs in reverse tab order.
    Suggested: Remove extraneous tabbing to reach focusable elements on the screen, so user can easily identify where they are at on the screen.
    Navigation from the ‘X’ to the “Add Links” button

    Issue: No visible focus indicator for the help icon.
    Suggested: Make it gray like the Properties (gear) icon, then blue when it receives focus. Or add a border around it when it receives focus.

    No visual focus

    Firefox: No visible focus indicator for the help icon.

    IE: visual focus

    This is how it looks in IE: Visual focus on the help button

    Issue: Access to menu item – reverse tab order: Once user has added a menu item, if they choose to navigate/move backwards in the tab order to customize the added item, the items in to expandable. The user has to navigate back to top of the browser and start from there.
    Access to menu item – reverse tab order

    Issue: In Internet Explorer 9. When the “Add Links” button is selected and the right side section is expanded, the user focus is dropped into the Search field which is fine, however, the user is not able to see the placeholder text unless they don’t enter a search criteria and tab out of the field.
    Suggested: Allow the placeholder text to be visible when the field receives focus.
    Place tab on the expanding section, and allow the user to tab into the Search field.
    Placeholder gone

    Kim van Iersel (June 18)

    On Jaws 16 Pro.

    I did all the tests and could answer everything with: Yes I could do that (add a menu. fill it with menu items, remove a menu, reorder a menu, access menu options, access menu help).

    Michelle deYoung (June 20, after integration into core)

    Tested in Windows 8.1 using Chrome + ChromeVox and FireFox + NVDA
    • can you add a menu (YES)
    • can you fill it with menu items (Yes – as far as functionally with the screen reader and keyboard. No – The extraneous text voice by ChromeVox and NVDA will be confusing to user and could very well impact their ability to accomplish their task.)
    • can you remove a menu item (YES)
    • can you reorder a menu item items (Yes – as far as functionally with the screen reader and keyboard. No – it is not very understandable for a non-sighted user to hear “Reorder” and “Done” without knowing they have to navigate back to the menu itself, and without instruction of what and how to reorder. Once back in the menu the reorder buttons are nicely done and announced clearly as to what the action is.
    • can you access the menu options (YES)
    • can you access the menu help (YES)

    Issue: Add Menu button:
    Once the user has selected ‘Add a Menu’ the focus stays on that item.
    Before selecting ‘Enter’ or ‘Return’:
    ChromeVox and NVDA:“Add a menu press return or enter to open.

    add menu before
    After selecting ‘Enter’ or ‘Return’:
    ChromeVox:“Add a menu press return or enter to open”.
    NVDA: only announced after user as moved away from the button and then back to it:“Add a menu press return or enter to open.”>
    add menu after

    Remediation suggested: Once the user has selected ‘Add a Menu’ it might make it easier to have the cursor focus dropped into the ‘New menu name’ field.
    When the button changes to the ‘X Add a Menu’ it should say something like
    “Add a menu press return or enter to collapse or close.”

    <button class="button-secondary add-new-menu-item add-menu-toggle" type="button">
    Add a Menu
    <span class="screen-reader-text">Press return or enter to collapse or close </span>

    Issue ChromeVox: >Add Menu button
    Once the menu name is added and the ‘Create Menu’ button is selected,

    Screen reader voices:

    • “Menu create”
    • “Status create menu button”
    • “List items widgets press return or enter to open this panel heading 3”
    • “List item static front page press return or enter to open heading 3”
    • “Collapse internal link”
    • “Search widget within search widgets edit test search entry”
    • “Archives heading 4”
    • “A monthly archive of your sites posts”
    • “Calendar heading 4”
    • … (and so on)

    after creating menu


    after-creating-menu code
    Issue NVDA: Add Menu Field

    Form field is voiced as “List with two items edit has auto complete”
    The input element needs a label relationship defined.
    No label no-label

    Placeholder is only read with NVDA if user accesses the field via forms mode. If the user is arrowing to the item in virtual mode no label will be announced.

    <label><input class="menu-name-field" type="text" data-customize-setting-link="new_menu_name" value="" placeholder="New menu name"></label>

    Remediation suggested: 
    Place holders should not be used for labeling.  Use explicit or implicit labeling. When using implicit labeling ensure that the for and id attributes are used to create a data relationship between the label and form field since some AT’s don’t support implicit labeling well.
    If you do not want the label to show hide it from view using css, but allow AT’s to still access the label name.
    Note: If aria-label is used on the input for a label, it will only be read by screen readers when tabbed to.

    <label for="menuname">
    <span class="hidefromview>Enter new menu name</span> (hide label text from view with css, but allow it to be read by screen readers.)
    <input id="menuname" class="menu-name-field" type="text" data-customize-setting-link="new_menu_name" value="" placeholder="New menu name">

    Issue: Adding a Menu Item
    Add button is just announced as “Add”.  The item name is read prior to the button, but it might be more understandable for it to be voiced with the item name.

    add items buttons<
    Remediation suggested:
    Ex: “Add a Gallery Page menu item”

    Issue: When user selects ‘Enter’ to add a menu item it is duplicated in the left panel.
    Menu item is added twice to the Menu sidebar.

    Issue NVDA/FireFox: Reorder/Done button
    Once the user as selected “Reorder” the focus remains on the button that then has changed to “Done”.
    Note: “Done” is only announced is the user navigates away from the element and then back to it.
    done button
    Remediation suggested:
    Reorder should have some more information associated with it for non-visual users. Perhaps taking user focus to the top of the list of menu items along with additional instruction on what to do now the reorder button has been selected would be beneficial and more understandable

    Issue NVDA:  Removing Menu Items

    When the add menu item window pane is open, the “X” for removing the item is available, but once the user closes the pane and moves to the window pane where they can edit the menu item, the remove “X” is moved down toward the bottom of the expanding collapsing accordion items for editing.
    pane open remove item

    pane closed remove item

    pane closed edit accordian

    Tobias Clemens Häcker (June 23, after integration into core)

    Windows 7, Chrome, ChromeVox
    Except for menu items being added twice everything works well. Was surprised how easy it was to use.

    Video (might need some minutes to render)

  • Rian Rietveld 7:50 pm on May 27, 2015 Permalink

    Team chat Summary, May 25, 2015 

    Main focus of the chat: The List Table tickets

    Tickets that need work

    • #32253: List table: posts navigation links pointing to same page
      And related #32028: List table pagination: text improvements for screen readers
      32028 has a working and tested patch and needs to be committed to continue the work on 32253
    • #32255: List Table: media wp-list-table lacks table header content for column-icon and related. Action: @joedolson will think of a proper heading (<th> text) for the thumbnails
    • #32509: List table: media thumbnail and title links improvements
      We stick to the current patch of #32255 and don’t add the aria-hidden + tabindex=-1> How to deal with the link in the image will be solved in#32509

    Ticket that needs dev feedback

    #32170: List table: sortable column headers accessibility
    Summary for devs and committers:

    • we need to give feedback about the current tables ‘order by’ and ‘asc/desc order’, also in the initial view
    • we also need to make clear which columns are sortable and what will happen when users click on the table header links
    • hence, we need to get additional information about the sortable columns extending what is set in get_sortable_columns()
    • a new method print_table_description() prints a hidden table description, referenced as target for the table aria-describedby attribute

    Of course we’re totally open to discuss a different implementation and better practices, any thoughts more than welcome.

    Ticket that needs translation feedback

    #32399List table: Lists of items should inform users about the “current view” being displayed
    Needs translation feedback, how to properly translate custom post types in this case

    Ticket that needs UI feedback

    #32152: List table: Comments column accessibility improvements

    Tickets to be closed

    • #31965: Add screen-reader-text to list “filter” links
    • #31966: Add screen-reader-text to list “filter” links: Posts and Pages

    We decided on close and won’t fix because these issues will be solved when a relevant heading will be added, see ticket #32399

    Tickets ready for commit

    • #32150: List table: better indication for “no taxonomy”
    • #32254: List Table: avoid adjacent links pointing to the same resource
    • #32147: List table: headings for pagination and views links
    • High priority: #32028 List table pagination: text improvements for screen readers
    • #32509: List table: media thumbnail and title links improvements

    Other work:

    • High priority: #32495 WP Admin bar multi-level menu accessibility
      This has a working patch, ready to commit.
    • #31650: Missing H1 heading in the admin: @joedolson will work on this
    • #32494: Semantic elements for non-link links: Help and Screen Options

    New work:

    Customizer accessibility audit

    Related tickets are:

    • #32493: Customizer accessibility audit (tracking ticket)
    • #31336: Customizer: separate navigation from options UI for better UX by removing accordion behavior


    Related ticket:
    #31696Better select, multi-select, and autocomplete/suggestion inputs in the admin.
    At the moment the a11y team has no capacity to work on an a11y audit of the Select2 library.
    Drupal has done some work on this already: https://www.drupal.org/node/2346973

  • Rian Rietveld 7:05 am on May 5, 2015 Permalink

    Team chat Summary, May 4, 2015 


    We use the Accessibility Priorities for 4.3 as guideline on what to work on.

    List table issues:

    @afercia wrote extra tickets to complete the list of issues for the list table.

    • #32150 List table: better indication for “no taxonomy”
    • #32189 List table: make the sorting indicator arrow visible on focus (new)
    • #32187 List table: Pages displayed in “Excerpt View”
    • #32170 List table: sortable column headers accessibility
    • #32015 List table views: missing current class for “All” when logged in as Author

    Patches we come up with will be given to the wpa11y test team for review with assistive technology. Test result will be added as a reply with the ticket.

    We discussed how to address the “too many links” and “too much noise” issues in the list table.
    In the tables on edit.php and upload.php there are more than one link to edit:

    1. the post title
    2. “Edit” in the row-actions
    3. in upload.php also the attachment is a link to edit

    Our proposal:

    • remove the link “Edit” in the row-actions
    • test if the link on the attachment in upload.php can be hidden for screen readers by aria-hidden

    Heading structure Admin

    This is a complex problem, two tickets are addressing this:

    • #31650: Missing H1 headings in admin
    • #26601: Inappropriate content in headings on admin screens.

    @trishasalas will investigate how best to address this problem and add that to the according tickets, we all will join in the discussion if needed.




  • Joseph Karr O'Connor 2:38 am on May 2, 2015 Permalink
    Tags: , ,   

    Weekly Meeting Change

    This week during the Wednesday meeting we decided that the Monday testing meeting is now where the action is so we decided to stop having the Wednesday meeting. On Monday, May 4, we will all meet in the #accessibility channel in Slack at 18:00 UTC. We are also using Slack throughout the week to work on tickets and patches, ask questions, and discuss anything that comes up. First register for the WordPress forums and then follow the steps on the WordPress chat instruction page to get set up. Then find your way to #accessibility. See you there!

  • Joe Dolson 7:46 pm on April 27, 2015 Permalink
    Tags: 4.3-early, , priorities   

    Accessibility Priorities for 4.3 

    For the development of WordPress 4.3, we’ve got a handful of major issues we want to work on to create a smoother and more predictable experience for users with disabilities.

    Reconcile Heading hierarchy throughout admin & clean-up heading contents

    #31650: Missing H1 headings in admin (fixed)
    #26601: Inappropriate content in headings on admin screens.

    Use Semantic elements for non-link links

    Tracking ticket: #26504
    Individual tickets (so far): #31487, #31476
    Related: #26550

    Reconcile search methods

    WordPress incorporates 5 different search interactions in the admin. For usability, accessibility, and maintenance reasons, this should be made more uniform. We’d like to see this reduced to two basic interactions.

    #31818 Uniform Search Form Display/Experience

    List table issues

    We gathered a ton of data on the List table navigation experience during 4.2, and those are being turned into tickets.

    #32028 List table pagination: text improvements for screen readers (fixed)
    #32150 List table: better indication for “no taxonomy” (fixed)
    #32152 List table: Comments column accessibility improvements (fixed)
    #32147 List table: headings for pagination and views links
    #31654 List tables: Select All shouldn’t be a column header (fixed)

    Color contrast issues in admin:

    #31548, #31713, #28599

    Improve editor experience:

    The editor is the single most frequently used part of most WordPress installations – and the experience with this interface should be more consistent.

    #29838: Editor focus order issues.

    Throughout the cycle, we’ll also be picking away at the dozens of other smaller tickets we want to fix, but these are large issues that will have a deep impact on WordPress, and will require a community effort to make progress.

  • Joe Dolson 6:09 pm on April 15, 2015 Permalink
    Tags: ajax, ARIA, javascript   

    Let WordPress Speak: New in WordPress 4.2 

    Written by Andrea Fercia & Joe Dolson

    WordPress 4.2 is shipping with a useful new JavaScript method: wp.a11y.speak(). This is a utility to make it easy for WordPress core to create consistent methods for providing live updates for JavaScript events to users of screen readers – with the side benefit that developers of plug-ins and themes can also make use of it either on the front or back end.


    In modern web development, updating discrete regions of a screen with JavaScript is common. The use of AJAX responses in modern JavaScript-based User Interfaces allows web developers to create beautiful interfaces similar to Desktop applications that don’t require pages to reload or refresh.

    JavaScript can create great usability improvements for most users – but when content is updated dynamically, it has the potential to introduce accessibility issues. This is one of the steps you can take to handle that problem.


    When a portion of a page is updated with JavaScript, the update is usually highlighted with animation and bright colors, and is easy to see. But if you don’t have the ability to see the screen, you don’t know this has happened, unless the updated region is marked as an ARIA-live region.

    If this isn’t marked, there’s no notification for screen readers. But it’s also possible that all the region content will be announced after an update, if the ARIA live region is too large. You want to provide users with just a simple, concise message.


    That’s what wp.a11y.speak() is meant for. It’s a simple tool that creates and appends an ARIA live notifications area to the <body> element where developers can dispatch text messages. Assistive technologies will automatically announce any text change in this area. This ARIA live region has an ARIA role of “status” so it has an implicit aria-live value of polite and an implicit aria-atomic value of true.

    This means assistive technologies will notify users of updates but generally do not interrupt the current task, and updates take low priority. If you’re creating an application with higher priority updates (such as a notification that their current session is about to expire, for example), then you’ll want to create your own method with an aria-live value of assertive.

    How do I use this?

    • enqueue ‘wp-a11y’ from your plugin or theme or set it as a dependency of the script that generates updates
    • on DOM ready, pass a translatable string to wp.a11y.speak(): wp.a11y.speak( mystring );
    add_action( 'wp_enqueue_scripts', 'yourprefix_a11y' );
    function yourprefix_a11y() {
    	wp_enqueue_script( 'wp-a11y' );


    add_action( 'wp_enqueue_scripts', 'yourprefix_ajax' );
    function yourprefix_ajax() {
    	wp_enqueue_script( 'yourprefix.ajax', get_template_directory_uri() . '/js/ajax.js', array( 'wp-a11y' ) );

    For an implementation example, take a look at wp-admin/js/updates.js. An important note: wp.a11y.speak() is only available after DOM ready, so be sure not to call it earlier!

    If you’re intending to use this in your theme, you should take note that your theme should also support the core class .screen-reader-text, which is used in the inserted content. Read more about screen reader text.

    References and further reading

  • Rian Rietveld 6:48 pm on April 14, 2015 Permalink

    Usertest: Link texts in the page with all posts (edit.php) 

    Question for the test team

    We would like you to investigate the links and link texts on wp-admin/edit.php page and suggest better solutions for the link texts, how to make them understandable and unique, without overloading a screen reader user with a huge amount of extra text. Hidden text suggestions (screen reader only) are welcome and also visual text suggestions.
    We hope to make this list of posts (and pages) understandable for everyone.

    Test results

    Geof Collis

    Sort of like they’ve done in the media section I’d like to be able to select the posts/pages in a list with just a link and checkbox for bulk edit an nothing else.
    I’d also like a heading at the beginning.

    Tobias Clemens Häcker

    Tested with: Windows7, Chrome Browser, ChromeVox


    The link texts for the link itself the control box and the sublinks (edit, quickedit, trash and view) are well-done. The voice output is clear. However author, category and comments are only announced as link.


    Links to author, categories and comments should add the type. Announcing “author mwa”, “category uncategorized” and “zero comments” instead of just “mwa”, “uncategorized” and “zero”.

    YouTube demo

    Jeffrey de Wit

    NVDA (default settings, so includes reading out title) goes entirely nuts on this stuff. I’ll see if I can get a recording of it. Something that may be useful to change are the All/Published/Drafts/Trash links. These could probably use some screen reader text.

    Something like this (Maybe use List instead of Display? Not sure):

    [Display] All (13) [posts] / [Display only] Published (10) [posts] / [Display only post] Drafts (3) / [Display posts in] Trash (1)

    Right now it gets read out by NVDA as:
    “All 13 link”, “Published 10 link”, “Drafts 3 link”, “Trash 1 link”.

    On a similar note, the column headers for sorting could probably use the same treatment. It just announces the link (“Title link”, “Comments link”, “Date link”).

    Should probably be something like:

    “[Sort ascending/descending by] Title link”
    “[Sort ascending/descending by pending] Comments link”
    “[Sort ascending/descending by] Date link”

    Ascending is the “default” link for title and comments, that is, when you get on the page and you trigger one of these sort links the order will be ascending (A->Z, or 0->x).

    For Date the default is descending, which means the newest comment will appear on top.

    Neither the current sort order (if any), nor what the sort order will be when the link is used is conveyed by the screen reader. The suggested text in the list above would take care of what the link will do, but not what sort order is currently active.

    I’m worried that adding additional text for what sort order is active may be too much, nor do I know of an elegant way to word what the current sort order is. Or even where the most appropriate place to put it is.

    NB. NVDA + Chrome doesn’t announce the Comments header at all. Could possibly be because the screen reader text span is wrapped in two other spans.
    Seems the craziness only happens with Chrome and NVDA. Firefox is a bit more sane.

    Demo in Firefox + NVDA:

    Demo in Chrome + NVDA:

    John Sexton

    I’ve done a quick check with Supernova V14 on a Win7 PC with IE11 and have the following comments:

    When tabbing through links with supernova on all posts (starting from the h2) you get:

    “Add New”, “All 13”, “Published 10”, “Drafts 3”, “Trash 1”, “Forms mode Search Posts blankline edit”, “Search Posts button”,

    “Forms mode select bulk action Bulk Actions pull down list box”, “Apply button”, “Forms mode Filter by date All dates pull down list box”, “Forms mode Filter by category All categories pull down list box”, “Filter button”,

    “visited link”, “link”, “Forms mode select page 1 edit”, “link”, “link”, “List View link”, “Excerpt View link”,

    “table 14 rows by 7 columns selectall unchecked checkbox”, “title link”, “comments link”, “date link”,

    “select no title unchecked checkbox”, “no title link”, “mwa link”, “uncategorized link”, “0 link”

    Note: as the above is just using the tab navigation it skips over the empty tags and date columns. However, if using the Supernova table navigation controls the empty tags cell is just read out as “column 5 row 2”. This is because by default Supernova doesn’t read all punctuation.

    Pagination links:

    the symbols are not often read out by default and their purpose may not be immediately obvious.

    add ” First”, ” Back”, ” Next” & ” Last” as screen reader text inside the link text.

    alternatively add ” First Page”, ” Previous Page”, ” Next Page” & ” Last Page” as screen reader text inside the link text.

    or ” Page 1″, ” Page n”, ” Page n” & Page n” where “n” is the page number that the link will go to.

    Personally I prefer the first option as is short and to the point.

    Data links in table:

    It may be an idea to add ” tag” & “0 pending of 1 comments” (where 0 are the number of pending comments and 1 is the total comments), as screen reader text inside the link text after the displayed value.

    It would also make it more usable if the pending & comments are shown as 0/1 or 0of1 or just add another column for pending just before the comments column. This way both values are visible without the need for title attributes.

    For when there are no tags, adding ” no tags” as screen reader text inside the link after the – symbol may help for cases when the – is not read out by default.

    You could add “author ” as screen reader text inside the link text before the authors name.

    It may be an idea to add “Edit ” to the link text as screen reader text before the title link text.

    The “Edit | Quick Edit | Trash | View” menu is not accessible without a mouse in list view. However, in excerpt view, the following works from a keyboard.

    The “Edit | Quick Edit | Trash | View” links are not immediately obvious, to gain access with Supernova, first you have to switch to excerpt view then you have to use cursor navigation to find the  post excerpt text and press space while over this text.

    Options could be to add a show/hide link for these four links this can have the same action of as you show one it hides previously shown menus. This way there’s only one “Edit | Quick Edit | Trash | View” menu visible at any one time.

    When these links are visible you can tab through them. It may be an idea to add the post title as screen reader text to the end of each of the four menu links, so it reads “Edit post title | Quick Edit post title | Trash post title | view post title” (where post title is the name of the post that is being acted upon.

    It is probably worth considering removing either the “Edit |” link or the title edit link. As these are duplicated links one following the other. Perhaps while in excerpt view, the title link could be used to show/hide the menu links instead of performing the Edit link.

    Another interesting thing I noticed is when using Supernova’s list links function while in excerpt view with one “Edit | Quick Edit | Trash | View” menu visible you get:

    • The pagination links are shown with the title text “Go to the first page «”, “Go to the previous page ‹”, “Go to the next page ›”, “Go to the last page »”.
    • The comments link has “c o m m e n t s”, would be better as “Comments”
    • The post titles have “Edit ” preceding the title text.
    • The post comment fields have “0 pending 1” (where 0 are the number of pending comments and 1 are the total comments).
    • The menu “Edit | Quick Edit | Trash | View” is only listed once for the currently visible menu and the links are listed as:
    • Edit this item “Edit” (where “Edit” is the actual link text and the first part is the title text).
    • Edit this item inline “Quick Edit” (where “Quick Edit” is the actual link text and the first part is the title text).
    • Move this item to the trash “Trash”, (where “Trash” is the actual link text and the first part is the title text).
    • View [post title] (where [post title] is the post title to view.



    I used VoiceOver and Safari.


    All/Published/Draft/Trash links

    I agreed with Jeffrey’s idea of adding a “post” word to links to provide a better context to the user. In my opinion, the context for this group of links for a sighted user is more than clear, so maybe only adding this information for the screen reader should be better.

    Column headers for sorting

    I agreed with Jeffrey’s suggestion to add extra info to let the user know the sort ascending/descending order. To tell you the truth, if Jeffrey did not mentioned that those links are to change the sorting order, they had gone unnoticed for me. I suggest to show by default the black triangle instead of only making it visible when the user does a mouse over or a click on the object.

    First, previous, next, last page links

    The title for these links already contain the information describing the action of each one of the links, is a shame that that browsers don’t announce it.
    So to make them accessible, I see two options:

    1. Add the information in a span same technique than the one used for list view and excerpt view;
    2. Converting the symbols and background color to images and adding the information with the ALT attribute.
    Edit | Quick Edit | Trash | View links

    In my case, it was not difficult to access these links only using the TAB key. I tried on list view and excerpt view.

    Since edit/quick/trash/view are all in the same cell as the title of the post I think the user gets a good idea that those actions apply to the current post.

    My only concern with these links is that they appear only when the post title gets the focus. VoiceOver and NDVA let the user to open a window dialog containing a list with all links available on the page. But these links won’t appear on the list because the title post don’t have the focus on. So the user won’t be able to use these links from the link list window.

    Tags information

    I would suggest to add a text for the screen reader so instead of listening to a “end dash” the user will hear something like “not tags for this post”.

    Data table

    The table used for the posts is a data table type. But not all the data cells are associated with their corresponding head (th) cells. This could create confusion for the screen readers and affect the way the cells are read to the user.

    Shaun Everiss,

    NVDA latest version, firefox and internet explorer latest builds and windows7.

    I have looked at the links having the title of the posts and the date on when it was posted works for me thats how it has been in 4.1 what is the issue of keeping it that way.

    Reagan Lynch

    Test Environment: Windows 7 64 bit, Internet Explorer 11, JAWS 16

    I did this test on just the main listing you first go to when you click on All Posts. This focus is on links and what feedback you get with a screen reader.

    After the bulk action combo box you get the unlabled links.

    The first is links that I think are for navigating back and forward among the posts. In JAWS 16 these are not labled. I know that one is two left double angle brackets, but that is because I did a jaws command (insert+up arrow twice quickly) The next thing I see as I arrow down is a unlabled link that I cannot even determine because nothing is labled and JAWS cannot read the character that is there.

    These links are repeated in opposite after the edit field to select the page. For these unlabled links it would be nice to here prev and next for the links that move you page to page, and maybe first page and last page for the links that go to the first and last page. Just labeling these page nav links would make the all posts/pages pages more usable with a screen reder.

    In the table of posts I don’t really know what you can do to make the links that are numbers that take you to comments more accessible. Since we now have the wp speak function how hard would it be to use that function to tell a screen reader when it sees that link to report 1 comments or 0 comments. I know if you use I think a title attribute you can read that with a say line command twice quickly, but screen reader users are not really going to take the extra time to issue that command. Using WP speak or something else might be the best solution especially if you don’t want to impact the sighted experience.

    Sebastien Massy

    Use of title attribute

    Not all browser/screen-reader combinations will convey the title attribute to the user. For instance, Firefox/Orca/Linux conveys the
    title attribute, but Chrome/ChromeVox/Linux does not. What this means is that the user might wind up having or not having the information
    depending on his A-T choice. (Example, if there are comments pending moderation for a post, Firefox/Orca might say “7 pending” while Chrome/ChromeVox would just say

    The screen-reader-text class

    In Firefox/Orca/Linux all text belonging to this class winds up being stretched out to one letter per line of the virtual buffer, presumably
    in an attempt to represent the text as it would appear if formatted according to the class. The end result is that using down or up arrow to
    scroll rapidly through a list of posts (or any other list employing this class) is at best tedious and at worst impossible. Chrome/ChromeVox,
    which tends to promote structural navigation over layout reproduction does not exhibit this problem. I would be curious to hear whether other
    firefox users on other platforms are experiencing this issue.

    Not all information is displayed

    Using either browsers, I ran into the simple fact that not all information would be spoken reliably. In particular, such things as
    publication dates and attached taxonomies were not always spoken. For example, in Chrome/ChromeVox, I found that navigating forward would
    speak the quick action links but omit the information mentioned, whilst navigating backwards would speak the whole information but the action
    links were not there. I am wondering whether this has to do with the fact that the action links appear on hover, i.e when focused (for us):
    could it be that they mask some information when they appear?

    All in all, I found that neither browser/A-T combination provided a good experience when attempting to scroll rapidly through a list of posts.

    Tina Tedesco

    Jaws 15
    After arrowing down past the #13 it said “link left double bracket.” It did not indicate the type of link. Arrowed down again and it just said “link” no type of link or no dataspoken. Arrowed after #2 after select page and there is a blank link; arrowed down again and another blank link.
    Some sort of data link or labeled tags need to be added.

    The table was very confusing for someone using a screen reader. To much text is being spoken in each column.
    As a user of a screen reader, I was able to go into table navigation mode which enabled me to navigate through the table. However, even using that, it was confusing.

    Amy Li

    I have some suggestions and they may not related to Accessibility but usuability issues. Hope it helps. Please see below:

    Too much links and caused confusion
    Remove non-important information on default, remove “Author”, “Categories”, “Tag” and “Date” since those items are in Filter list.
    Add icon-style for Tagging, add alt-text for tagging and other icons
    Links button need be less, combining View with Edit. Quick Edit should be default, adding “More” to extend functions like “Edit”
    “Trash” is better to be selectable in the front so that admin can bulk-select and delete together, instead of one by one clicking.

    Mocked screenshot in default page with removed extra links:Mocked screenshot in default page with removed extra links

    Issues and actions:

    Overall impression

    • For screen reader users this page is overwhelmed with links and hard to get an overview of.
    • There is a need for a quick overview with links to all posts (or pages).
    • A lot more screen reader text should be added to explain what the links are about.

    Page navigation

    Page navigation

    • The page navigation should have a heading to make clear what it is about: ticket @afercia
    • The page navigation is missing decent screen reader labeling: ticket @afercia
    • The previous links are still links on the first page , and the next links on the last page. They should not be links. Also the colour contrast of the >> and > is to low for these “inactive” links.  Ticket @rianrietveld

    Post filter

    post filter

    The links like Published, Sticky etc. are missing decent screen reader labeling: ticket @Cheffheid #31965 and #31966



    The amount of pending comments are included in the title attribute of the comments link and only visible on hovering, this is not clear for screen reader users but also not clear for sighted users. Ticket @rianrietveld



    A “—” ( “end dash”) for no tags needs screen reader labeling or a better explanation.  Ticket @rianrietveld

    Post link and row-actions

    Below the link for the post title there are action like: Edit, Quick Edit, Trash and View.

    • The link to the post title and the Edit link are double.
    • Some screen reader have difficulties entering the row-actions, we should review the way this is done now.
    • The | seperator could be included into the css or made invisible for screen readers by ARIA
    • Remove the explaining text out of the title attribute and add screen reader text
    • The quick edit link should be a button is now href=”#”

    Screen reader text needs to reset word-wrap

    In Firefox/Orca/Linux all text belonging to this class winds up being stretched out to one letter per line of the virtual buffer. This is due to the word-wrap: break-word; applied on an element Ticket @afrecia

    No feedback on sort order of a column

    • The way a column is sorted should be added for screen readers
    • The only way you can see if a column is sortable is by the colour of the table header text and by hovering over the link

    To consider

    How to decrease the number of links and make a post quicker selectable for a screen reader user

    One more thing to consider

    Edit by Andrea. We missed the format links: when a post has a specific format set, a small icon is prepended to the post title, see screenshot:
    video post format
    the image is linked to a screen with all the post belonging to that post format. Read out by screen readers as: “video link video”.

  • Rian Rietveld 7:59 pm on March 30, 2015 Permalink

    Usertest: The search functions in the Admin 

    Question for the test team

    We like you to test the search function options in the WordPress Admin.
    We know there are accessibility issues here, we would like your expert opinion about this.

    Test on WordPress 4.2-alpha

    • Try the search function in:
    • Posts > All posts
    • Posts > Categories
    • Posts > Tags
    • Media
    • Pages > All pages
    • Comments
    • Appearance > Themes
    • Plugins > Installed Plugins
    • Plugins > Add New (try different options, like featured, favorites, etc.)
    • Users > All users
    • And if you still have time: Pages > Add new > Add Media > search an image or file in the Media Library, try different options, like kind of media item and date


    • Try with search words you know give results
    • Try an empty search
    • Try with nonsence words

    Can you tell us if:

    • it’s easy to do a search or do you get stuck
    • you get what you expected
    • you can read the results well
    • you get good feedback when there are no results
    • you miss something to make it work for you
    • you have suggestions for improvement (keep it short please)

    Shaun Everiss

    I just did the test with NVDA, search worked as expected. I didn’t see any issues.


    Tools: Safari + VoiceOver

    • Posts > All posts: The function worked perfectly, however I think that the missing part is telling the user how many results he obtained with his search. Also if is possible, make the focus stays on the main content after the page is refreshed would be nice.
    • Posts > Categories: Same comment than Post > All posts.
    • Posts > Tags: Same comment than Post > All posts.
    • Pages > All pages: Same comment than Post > All posts.
    • Comments: Same comment than Post > All posts.
    • Appearance > Themes: See missing search button comment.
    • Plugins > Installed Plugins: Same comment than Post > All posts
    • Plugins > Add New: Same comment than Post > All posts.
    • Users > All users: Same comment than Post > All posts.


    Media: The function worked perfectly.
    Missing search button: I noticed that in this page, the search function is a little bit different than search functions in the other pages. In the media page the button “search for XX” at the right side of the search input text is missing. Since in most of the pages we found a label + input text + button search, the user is used to this pattern. I propose to modify the search function to be consistent with the rest of the functions.
    Media: Select class=”attachment-filters” missing label
    The select option for type of media (images, audio, etc) does not have a label so the select context is not clear since the user only listen to “All (4)”.

    Pages > Add new > Add Media: Here we have a similar case to the search function on Themes page. This is an interactive search. The problem here is that there is nothing that tells the screen readers what is happening while the user is performing the search.


    Search Placeholder in Themes: The themes search function is the only one where the input text has a placeholder. Listening to it is a little confusing because the same word is repeated two or tree times:
    “Search installed themes, clickable, Search installed themes, Search installed themes search text field”.
    Since this function is the only with a placeholder, what do you think about removing the placeholder from the code to keep consistency with the other search functions?

    Search function inside the H2: The search function for the themes page is grouped inside the H2. With VoiceOver, the user won’t be able to write in the input text unless she goes inside (control+option+shift+down arrow) the group to interact with it.

    Blocked search input text; There is a bug when writing some text in the input text and clicking enter to execute the search. The focus is blocked and the text can not be erased. One solution is to move to another element on the page and come back to the input text to regain the functionality. The search function in Themes is different because is an interactive search, the user write something and at the same time results appears. The problem here is that there is nothing that tells the screen readers what is happening while the user is performing the search. Clicking on enter to execute a search is a normal behaviour because all the other pages offer the same pattern. I think if the user get trapped in this bug won’t be able to find a way out.

    Missing search button: In this page, the button “search for XX” at the right side of the search input text is missing. Since in most of the pages we found a label + input text + button search, the user is used to this pattern. I propose to modify the search function to be consistent with the rest of the functions.

    Also missing in this page is the text “Search results for “XX”” that appears inside the H2. Most of the pages added it when the page is refreshed after doing a search.

    Amy Li

    Posts > All posts

    • Focus should set to search input box when first enter all posts page
    • Screen reader read “Search Posts” button as “Disabled”
    • Search Posts color contrast radio is not higher than 4.5:1


    • Focus should set to search input box when first enter
    • When Enter space into Name input it should read out warning in Screen Reader
    • After input empty into Name, nothing shows and focus is gone and removed


    • After enter input text it should read results when there’s results found
    • Focus should set to first search result after click Enter into search box

    Plugins > Installed Plugins

    Focus should set to first search result after click Enter into search box or set back to search input box

    Plugins > Add New

    When enter “Jet” text which there’s search result, the the typeselector select field has no text/label

    <select name="type" id="typeselector">
     <option value="term" selected="selected">Keyword</option>
     <option value="author">Author</option>
     <option value="tag">Tag</option>

    Users > All users

    • Focus should set to search input box when first enter all posts page
    • Focus should set to first search result after click Enter into search box

    Resize window:

    Search box should be on top when screen size is smaller than <320 like mobile version.

    Tina Tedesco

    I use JAWS 15.

    When I search for something, and whether it found it or not, my results did not appear until the end. I had to use the arrow key to go down to see where the actual results were.

    It did say out loud searching but did not bring me right to the search results. Can you put in something where the screen reader will read out how many results after searching?

    Besides that I thought the search worked well. Definitely doable with a screen reader.

    John Sexton

    Test on Win7 64bit, IE11 & Supernova14

    Search in categories:

    Focus is placed in the new category name field on page load

    Search in tags:

    Focus is placed in the new tag name field on page load

    Search in media library

    While in grid view, this search works differently it appears to filter items as you type but from a screen reader point of view clicking the search button gives no feedback that any search has been performed. Perhaps on pressing the search button focus can be moved to the first search result or if a total of items found message is added, like in posts, categories and tags focus can be moved to that.
    While in list view, it works more like the posts, categories and tags search.

    Search on all pages

    Search on “(no title)” and “mwa” both return no items
    It doesn’t seem possible to search for all pages with no titles

    Search on themes

    Empty search returns all six themes
    Search on “four” returns two items: twenty fourteen and twenty ten
    Search on “ten” returns four items: twenty fifteen, twenty eleven, twenty fourteen and twenty ten
    There is no search button and pressing enter in the search field gives no indication to the screen reader of any changes and the search results are a little odd.

    On the whole quite reasonable. However, themes gave the most odd results. Not having any screen reader friendly feedback a search has been done is a little off putting as is placing the focus on a form field on page load.
    The searches appear to be limited to the first column of the results table and it may be nice to be able to search or filter on file type in the media library. IE jpeg, png, gif, mp3, mp4, doc, docx, pdf etc.
    Another nice to have may being able to search or filter by user who created/uploaded the item.

    Geof Collis,

    Tools: IE 11, JAWS 14.5

    search post, pages, comments, plugins and media/library

    no problem with search function initially but I dont like trying to find the results, there needs to be a heading for the results, as it is right now I’ve got to tab through all of the regular stuff before I find a table with results if any, very annoying and time consuming, also, I’d like the focus to be taken to the results after a search if possible

    On another note a heading before all posts, pages, categories etc would be nice.

    I noticed that when I do a second search that the previous text is still in the edit box, this should be removed after the initial search.

    Tags and categories

    This is better, they have a heading and the search term used but the focus gets taken past the heading, I have to move backwards, this might be more of a problem for a keyboard user.

    Still the issue of previous search term in edit box.


    Something wrong with the edit box, as I start typing it is reading off the url and search term and when I hit enter it doesn’t go out of forms mode, I have to do it manually and again a heading with the results would be better than tabbing through the regular stuff.

    Plugins add new, all criteria

    This worked great, a heading for each plugin made it easier to sift through them but still the issue of text in edit box after search.

    Add new

    Posts and pages work fine as long as the disable the visual editor checkbox is selected in Profile.

    Add media

    Uploading from my computer has become a whole lot better but do have issues with adding alt text etc, trying to add one from the media library is non existent, perhaps a test for another day.


    • Give screen reader feedback for search results and what’s happening with the interactive search in themes.php and upload.php
    • Give better screen reader feed back about the amount of search results
    • Set the focus on search the results after search submit (and not for example at New category)
    • Add a (hidden) submit button  and remove the placeholder for search in upload.php (at least for list mode),  plugin-install.php and themes.php (see ticket #26600)
    • In themes the search input text gets blocked after clicking enter to execute the search.
    • Bug: Plugins > Add New: typeselector select field has no text/label (see ticket #26601 )
    • It is not possible to search for posts/pages with no title
    • Search installed themes gives to much results?
    • Remove search function for the themes.php outside the H2 (see ticket #26601 )
    • Move the search field on top in small windows

    Discussions in Slack about the results:

    Slack log

    Now there are 5 different ways for a search:

    1. Search input no submit button, no live search (need to press Enter) in Media Library list mode
    2. Search input no submit button, live search fires “as you type” in Media Library grid mode, Themes (add new, wp.org API), Network Themes (add new, wp.org API)
    3. Search input no submit button, live search fires “as you type” (more a “filter current collection” than a search), Themes (installed themes), Customizer add widget, Plugins (installed plugins)
    4. Search input with hidden submit button, press Enter or tab and submit the hidden button (after the search, the “typeselector” select appears) in , Plugins (add new), Network Plugins (add new)
    5. “Classic” search: search input with submit button, press Enter or submit button, in Posts, Categories, Tags, Pages, Comments, Users, Network index: search users, Network index: search sites, Network Sites, Network Users, Network Themes (installed), Network Plugins (installed)

    We recommend only 2 forms of search:

    • the classic one, the same for every search, with visible submit button
    • the dynamic one:  adding wp.a11y.speak to show the results count, and making sure focus doesn’t change dynamically


    • Open ticket for the missing label for the  typeselector select field – @rianrietveld
    • Open ticket on a unified search form display: 2 types – @cheffheid
    • Rian Rietveld 6:39 am on March 31, 2015 Permalink | Log in to Reply

      Some extra remarks:
      It seemed there already was a ticket for the missing label for the typeselector select field : #31795
      Searching for posts with no title is possible if you ‘enter no title and not ‘(no title)’ in the search field

    • Jeff de Wit 2:56 pm on March 31, 2015 Permalink | Log in to Reply

      Here’s the ticket proposing the unified search form display changes: #31818 – open to thoughts from all.

  • Rian Rietveld 4:18 pm on March 26, 2015 Permalink

    Usertest: Extra small test about role=application in Press This 

    Send to the test team March 26, 2015
    For WordPress 4.2-beta2


    We would like you to test the “Press This” categories selection in
    You can access Press This directly in WordPress, at: /wp-admin/press-this.php

    After the editor, you will find a “Post Options” area where you can set the Post format, Categories and Tags.
    About Categories, it’s made with a list of DIV elements with role=checkbox, for several reasons developers choose to implement them this way so switching back to native checkboxes is not an option :)

    You should be able to check them as you usually do with native checkboxes, by the way screen readers won’t automatically switch to “forms mode”.
    To force the switch we added role=application to the list container.
    This has pros and cons and, generally, it’s recommended to use role=application sparingly and wisely.
    See for example this post by Mr. Zehe:

    Since any recommendation and best practice should be always tested in a real world experience, we would like you to test what’s best for you.

    • with no role=application, users will have to manually switch to “forms mode”
    • with role=application, the switch should automatically happen but you will lose the native behaviour and other things like the number of items in the list being automatically announced, not mentioning arrowing won’t work.

    Results so far:

    Bram Duvigneau

    After a quick look, I come to the following conclusions:

    • NVDA shows an application region and you need to press space bar/enter to interact with it. Please note this is not necessary if the user just navigates by pressing tab
    • The application region contains just a bunch of elements that behave like checkboxes

    Given the fact that this is not a real application, but just a list of checkboxes, I recommend against using role=”application” here.
    By putting the checkboxes in an <ul> or an element that has the corresponding aria role (list from the top of my head), you wil just make it clear that these checkboxes belong together. As a bonus I would suggest using the new wp.a11y.speak to announce the number of results when a user types in the search field, e.g.: “4 categories displayed” or similar.

    Susan R Grossman

    On JAWS

    This doesn’t work for me even when using tab/shift/tab.

    It skips some of the choices when trying to tab/arrow/space/navigate in any method through them.  Does every other “radio button”.

    Geof Collis

    On JAWS 14.5 IE11

    I dont like it one bit and it should not be implemented, it goes against everything I know about radio buttons and checkboxes.

    Not sure if this is relevant but when ever I see a form I go through the whole form without going into forms mode to give my self an idea what it looks like, then I will fill in the first edit box/ button etc, go out of forms mode go to the next field fill it in then go out of forms mode again, I do this for all forms because I dont trust them to cycle properly.

    Michelle DeYoung

    FF/NVDA/Win7: Once the screen readers announces “application” and throws me into forms mode, the next tab takes me back to the Category tab and “Back to Post Options Button” is voiced. Then I have to tab through the other items in the tab order to access the categories I would like to check/not check.
    Each category item name is voiced with checkbox not checked.

    IE/JAWS/Win7: Once the screen readers announces “application” and throws me into forms mode, the next tab takes me back to the Category tab and “Back to Post Options Button” is voiced. Then I have to tab through the other items in the tab order to access the categories I would like to check/not check.
    Each category item name is voiced with checkbox not checked, to check press spacebar.

    Chrome/ChromeVox/Win7: Once the screen readers announces “application” and throws me into forms mode, the next tab takes me back to the Category tab and “Back to Post Options Button” is voiced. Then I have to tab through the other items in the tab order to access the categories I would like to check/not check.
    Each category item name is voiced with checkbox not checked item.

    Keyboard only: Another accessibility impact would be for keyboard users. Tabbing to the category item highlights it but they have no idea that the item is selected and operational via a checkbox. If you do not want the checkbox displayed then add some verbiage to let visual keyboard users know how and what they are supposed to do so they don’t have to guess that if they use a spacebar that it will check the category item.

    I would recommend not using the role=”application” in this case, and focus on getting this to work for screen reader users and keyboard only users. Perhaps a tab/accordian widget. Here is a link to an example, but it also is using role=”application” which impacts access via different screen readers, so in this example I would remove it as well, but it still shows a different widget option.
    Example 37 – Tab Panel: Accordian using ARIA CSS selectors

    I think the role=”application” will only frustrate users more and impact how they access those content items.

    Anna Natorilla,

    Trunk: This custom checkbox implementation allows the user to activate the checkbox with spacebar key only. The user has no problem checking the custom checkboxes. If the user reads the checkbox via virtual cursor mode and they press the enter key to select a checkbox, the screen reader will tell the users to press the spacebar key to check or uncheck a checkbox. Once the users check or uncheck a checkbox with the spacebar key, the user was switched to forms mode.

    It is a fact that switching to forms mode on the checkboxes will cause the screen reader to not announce the number of items in the list. The user has to use virtual cursor mode to hear the list items numbering and levels.

    Nightly: This native checkbox implementation allows the users to activates the checkbox with both the spacebar and enter key on via virtual cursor or forms mode. The users have no problem checking the forms control whether they are in forms mode or virtual cursor mode.

    Gabriela Nino de Rivera Torres

    Tools: Safari 8.0.4 + VoiceOver

    I found very easy moving between the categories list. It’s a great improvement compared with the old situation. In the old version, first I need to go inside the group to interact with the items inside. When moving from one category to the next VoiceOver was speaking twice each item, one for the button ratio and the second for the text inside the button ratio, which was very annoying.

    In the new version I don’t need to go inside the group to interact with its items. Selecting the ratio buttons it is also very easy to do.

    Points not so good:

    I noticed that when adding a new category, the user is not notified of the action. There is not a message confirmation to tell the user if the category was successfully created.

    Also, when adding a new category, the category is selected by default (the ratio button is selected). The user won’t not know until she moves from one category to the next.

    The categories are added at the beginning of the list under their parent category. It is funny, I was expecting to be added at the end instead. This has nothing to do with accessibility issues. 😀

    When moving in the list of categories, there is nothing that announce the user if a category is a parent or a children. This information is being transmitted only visually.

    For some reason all the sub-categories inside the testing category are announced by VoiceOver like “list of X items”. I added categories in other parent categories, but this behaviour only happened with the testing parent category. I looked in the code, I could not find any differences between the parent categories. So, I’m very puzzled about this.

    Tina Tedesco

    Using JAWS 15

    Not sure I did this correctly but I concentrated on the list starting whith the checkboxes. I was able to check and uncheck with any problems.

    When arrowing down it said, “Entering Categories Application.” Then arrowed down and came to accessibility, it indicated “list of 6 items.” When I arrowed passed accessibility it indicated “list of 4 items nesting level 1.” When I got to the end of that list it indicated “list end nesting level 1.)

    I heard no more beginning or ending of levels until I arrowed passed JDFh checkbox. it indicated “list of 2 items nesting level 1.” When I got to the end of the list it said “end of list nesting level 1.”

    I arrowed to Testing (did not mention a new listing) and when I arrowed again it said “list of 5 items nesting level 1 as well as end of list nesting level1. ”

    Came to Uncategorized (nothing to indicate any listing before the word) arrowed down once indicating “list of 2 items nesting level 1.” Once I arrowed past the 2 items it said “list end nesting level 1.”

    At the end of this list it said “Categories applications end.”

    Should there have been some sort of message for all listings?

    Hope this is not too confusing.

    Malgorzata Mlynarczyk

    Tested with NVDA in Firefox

    As I’ve said before I’m not a native screen reader user, so I’m probably not the best person to test it (it would be better to test it with actual screen reader users). However, I personally prefer the solution with role=”application”. First of all, screen readers are expected to switch to application mode when in the form, so this is an expected behaviour. Once in the form, the users are used to navigate using Tab key, rather than by moving the virtual cursor using the arrow keys, so I don’t think this is a problem. The fake checkboxes work well – the change in state (checked / unchecked) and the ‘checkbox’ label are announced to the user. And although the screen reader doesn’t inform the user how many items the list contains, I don’t think this is particularly important here, and sighted users don’t know it either (unless they decide to manually count them…).

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