Accessibility Usertest Create and edit links inline

In WordPress version 4.5 there will be a new way of adding links in the content: create and edit links inline. The URL input and the search field are now one and the same.
This is similar to what Google Docs does. Search results are shown as an autocomplete dropdown.
Related ticket: #33301.
The test are done from Februari 18 until Februari 24 2016.

Conclusions are at the bottom of this post.

To test this for accessibility we set up a WordPress 4.5-alpha nightly install.
And asked our testers:

  • Can you access the little window with the input field for the link
  • Can you understand how to add a link using this inline window
  • Can you understand how to search for a page using a search word using this inline window
  • Is this usable with your assistive technology?
  • If you use a screen reader: can you hear the search result if you enter a search word instead of an URL
  • Are you missing functionality to make this work for you
  • Which browser and operating system did you use (for example Safari on Mac)
  • Which assistive technology did you use for this test

Testers who joined: Jeff de Wit, Geoff Collis, Tobias Clemens Hacker, Reagan Lynch, Ruth Niesenbaum, Gabriela Nino, Michele DeYoung, Sirisha Gubba, Wim Moons and Marco Zehe.

Test results for keyboard

Wim Moons: Windows7 & FireFox with loupes.
If you type a word, a list appears. If you walk through the list with the arrow keys the text in the search field disappears. I found this confusing.

Geoff Collis: JAWS 14.5 IE 11
A bit confusing at first but I managed to do it. I wasn’t sure what happened, all I heard was “apply” after doing it so moved around and found out I could type the url, needs some work to let me know where I was after the keystroke command.

Of note:, when I first typed in the url and used tab to go to the apply button it didn’t work, took me right out of the edit box, when I came back I was able to get to it by tabbing this time.

Jeff de Wit: In Firefox, with just a keyboard:
You specifically have to tab to the submit button to add the link without issues. If you press Enter on the input field, it will also add a linebreak where the cursor is when you opened the link dialog (in addition to adding the link). Here’s a video of that:

What I’m doing in the video:

  • Select some text
  • Hit Ctrl + K to open the link dialog
  • Type in the URL for Google
  • Press Enter
  • Press Ctrl + Z to “revert” the random line break that appears

Also not super clear how to remove the link this way, since you can’t actually get to the pencil / remove icons. It’s not impossible to remove links though, but not sure how “obvious” it is that you can also remove the URL text and hit apply to remove the link.

Michele DeYoung: Firefox 44.0.2 and Windows 10.
Using the spacebar instead of Enter when creating a link using the keyboard will make it so a line break does not occur after the text link.

Test results for screen reader

Jeff de Wit: In Firefox, with NVDA enabled:
It seems to announce really well. It even makes it clear when you’re moving your cursor to a link. Not sure if it’s a good idea here to also announce what URL it’s linking to (Not what links usually do, and it may add too much noise, but it’s editing content and it may help with spotting broken/mistyped links).

One thing I did notice though, is when I hit the “Advanced” button NVDA only announced “alert” for me. It doesn’t say anything about the text field I have focus on (even though it’s supposed to, and I do see it in the NVDA speech log, so it may be related to my NVDA settings).

Gabriela Nino: Mac + Safari + VoiceOver

  • After using cmd + k to open the window: The window opens but Voice Over does not announce it. So is not clear for a non sighted user what exactly is happening.
    Right after the window is opened, the focus is supposed to be on the URL input text. But this behavior is not consistent, the focus is sometimes on the input text and sometimes not. When is not on the input text, I managed to give it focus using the tab key. But a non sighted user might not be able to figure this out.
  • Voice Over is sometimes announcing the input text placeholder, but mostly of the times it does not.
  • On the advanced window, when searching for existing content, Voice Over does not announce the results found.
  • It was impossible to access to pencil / remove icons, tried using cmd+k but instead of allowing me to access the pencil and remove icons, it opens the little window with the input field for the link. Without mouse or when using Voice Over, I’m not able to select those icons.

Michele DeYoung: Firefox 44.0.2 and Windows 10.

I can understand how to add a link using this inline window, but only if the focus is in the url input field. After adding multiple links, when other text is selected to create a link, the inline window focus was on the last element in the window that was used, for example – the Advanced button. This will be confusing for screen reader users when the window launches and it voices “Advanced” or “Apply.”

Note: When the inline window opens and the last focus was on the Advanced button or Apply button, and Advanced is selected, the pop-up for the Advanced selection will open, however, the keyboard focus remains in the window behind it. Keyboard focus is correctly in the pop-up when the starting focus point in the inline window is in the input field.
The pop-up is not announced as a dialog, and a heading should be announced with it.

Advanced Pop-up: When the search is entered, if I tabbed I would go to the results container, however, NVDA would just voice that number of items in the list. It would be helpful to know that it is the results list. When arrowing through the list each item was voiced.

Another way: when using the down arrow to move from the search entry, I can move into the search results list (still not clear that it is the results list), but when I arrow to each item in the list I just hear the search entry repeated for each one.

Tobias Clemens Hacker: Chrome Vox/ Chrome on Windows 7
The buttons have no distinguished voice output. I don’t know which one is “Apply” and which one is “Advanced”. For some reason the aria-label in the containing div is not being output.
I miss distinguished voice output for the buttons.

Reagan Lynch: Windows 7 running IE 11 with JAWS 17.
If I paste a link into the text field the raw link appears in the text of the post, but the word I highlighted is a link with the link pointing to <a href=”http://example.com”>highlited text</a>
I was unable to insert a link using the new method. I was able to get into the advanced dialog like we currently have, but only after pressing ctrl+k and then arrowing right and exiting forms mode, and then my text highlight was gone.

Sirisha Gubba: IE and FireFox with NVDA

  • I can access the window with keyboard in FF but not in IE. AT with short cut keys provided
  • I can’t understand with NVDA as it announces “Toolbar” and focus is taken to the apply button.
  • I can see the placeholder in FF. With NVDA it is not announcing as soon as the small window gets opened but if user uses back arrow it reads the instruction.

Ruth Niesenbaum: Chrome and NVDA with Windows 10.
It was not clear how to enter data: I started entering a word and it did not tell me that it found options, when I went down to the options it did not read them loud so it does not say the When I press the down arrow and enter the list of urls it says : unknown 2 of 7 and it does not read the name of the post

Conclusions

Some issues are already fixed in the current version, using these test results.

 

The issues that remain are according to @afercia (Andrea Fercia)

Reagan Lynch Using Windows 7 running IE 11 with JAWS 17:

If I paste a link into the text field the raw link appears in the text of the post, but the word I highlighted is a link with the linnk pointing to
highlited text

Andrea: after last changes I’m not even able to insert a link with IE 11

Jeff de Wit:

If you press Enter on the input field, it will also add a linebreak

Andrea: maybe fixed, but I’m pretty sure it still happens when *pasting* a link in the input field and then pressing Enter

Also not super clear how to remove the link

Andrea: totally agree

Michele DeYoung: NVDA Firefox 44.0.2 and Windows 10.

Using the spacebar instead of Enter when creating a link using the keyboard will make it so a line break

Andrea: it’s a legitimate expectation since it’s announced as “Button” it should work also with spacebar

Jeff de Wit: In Firefox, with NVDA enabled:

when I hit the “Advanced” button… (it’s about the Advanced modal dialog)

Andrea: yeah, the link modal dialog still needs some a11y treatment. We should fix that but it’s a bit unrelated

Gabriela Nino: Mac + Safari + VoiceOver

It was impossible to access to pencil / remove icons, tried using cmd+k but instead of allowing me to access the pencil and remove icons, it opens the little window with the input field for the link. Without mouse or when using Voice Over, I’m not able to select those icons.

Andrea: we should make more clear the Alt+F8 shortcut, maybe it’s a bit confusing now

Gabriela Nino: Mac + Safari + VoiceOver

After using cmd + k to open the window: The window opens but Voice Over does not announce it. So is not clear for a non sighted user what exactly is happening.
Right after the window is opened, the focus is supposed to be on the URL input text. But this behavior is not consistent, the focus is sometimes on the input text and sometimes not. When is not on the input text, I managed to give it focus using the tab key. But a non sighted user might not be able to figure this out.
Voice Over is sometimes announcing the input text placeholder, but mostly of the times it does not.

Michele DeYoung: NVDA Firefox 44.0.2 and Windows 10.

I can understand how to add a link using this inline window, but only if the focus is in the url input field. After adding multiple links, when other text is selected to create a link, the inline window focus was on the last element in the window that was used, for example – the Advanced button. This will be confusing for screen reader users when the window launches and it voices “Advanced” or “Apply.”

Andrea: totally agree, already in my list

When using the down arrow to move from the search entry, I can move into the search results list (still not clear that it is the results list), but when I arrow to each item in the list I just hear the search entry repeated for each one.

Andrea: works for me using Firefox + NVDA

Andrea: additionally:

  • after 36703 in IE 11 can’t insert a link
  • we’d recommend to add an audible confirmation message when a link is successfully inserted from the inline toolbar; also, when a link is successfully selected in the advanced modal dialog; of course messages need to be different since in the modal the link is inserted only after users press the “Update” button

And further: For next tests we will ask the test team not to test with ChromeVox anymore. This screen reader is too limited in functionality. And if a tester uses NVDA: the preferred browser to use with this screen reader is FireFox.

Update March 2, 2016: additional tests

Marco Zehe: Safari and Chrome on OS X with VoiceOver. That is, Chrome + VoiceOver, not ChromeVox.

I can confirm the brokenness of the search results when arrowing up and down. I do get the focus into the combobox consistently, though. And here’s the thing: In Chrome, while that has a nasty bug with no text being read out when typing or arrowing, the search result widget works. So whatever is going wrong has something to do specifically with Safari’s interpretation of WAI-ARIA.

A few ideas:

  1. I assume you are using aria-activedescendant when pointing at the various search results when arrowing up and down, right? Are you also adding tabindex=”-1″ to these role “option” items to make them focusable, but not include them in the tab order? If not, add them ad see if that makes a difference.
  2. Are you using aria-owns? If so, that may be interfering somehow, see if you can do without that.
  3. Or are the items spoken via a live region? I do not know the code, so these are just some things that popped into my mind as possible reasons.

#a11y-audit, #accessibility-usertest, #testing

Calling a Meeting for the Documentation Group

The documentation working group will have a one time meeting on February 22nd at 17:30 UTC. We are going to discuss finalizing the structure of the Handbook as well as discuss strategy going forward. If you are interested in getting started with documentation this will be a great time to join in!

#documentation, #documentation-meeting, #meeting

Summary Team Chat for Februari 8, 2016

Core accessibility coding standards

After discussion with @jorbin some last changes where made on the Accessibility Coding Standards. @jorbin will bring it up at the next Core meeting to make sure there are no objections there.

Documentation

@hearvox finished the Quick Start Guide in our Handbook. @rachievee is working to add other pages to expand on topics from the Quick guide that need longer explanations.
@trishasalas organizes a one time meeting on Februari the 22nd 17:30 UTC to discuss finalizing (for now) the structure for the handbook. In the meantime Trisha is going to begin writing the Plugin section of the Handbook.

Accessibility Test Team

Nimbus Hosting is so generous to sponsor the #wpa11y team with a VPS server. Here we can install a production, nightly and trunk version of WordPress and also have SVN and SSH access.
We will set the server up next week, then we’re up and running again and resume sending tests to our team.

Accessibility-ready themes

Joe started to work on a fork of the theme unit test data, focused on accessibility testing – a smaller set of data, eliminating false positives in the data, etc. He will let us know when it’s usable.

The post with the requirements for the accessibility-ready tag has been improved. There is now more information on how to test a theme to help theme authors better.

Tickets

@afercia: Investigation about color contrast continues.

#26601: Inappropriate content in headings on admin screens.
@trishasalas will write an new, refresed patch, keeping the add new link visually on the same place but placing it in the HTML outside the h1 heading

From Februari 16 on we will have an extra meeting to work on tickets. The group has grown so much last year that we need more time to discuss and work on core tickets then we have now in the regular meeting. This ticket meetings will be every Tuesday on 18:30 UTC.

And from everybody in the a11y team:
We wish @accessiblejoe a good and quick recovery!

#accessibility-team-meetup, #weekly-meetings

Accessibility Quick Start Guide in draft: needs vetting

The WordPress Accessibility Handbook now has a draft of a Quick Start Guide. The doc needs edits, comments, and vetting.

We intend this as a resource for developers to quickly grab WordPress-oriented code examples and a11y guidelines. Let’s make sure everything is accurate and clearly explained, and that nothing a11y-critical for WP dev is missing. (This process might also help us identify which topics need further explanations in other Handbook sections.)

Please review the draft and leave your comments on this post.

#documention, #handbook