[wp-trac] [WordPress Trac] #33301: Create and edit links inline

Thu Apr 28 11:46:00 UTC 2016

#33301: Create and edit links inline
-------------------------+-------------------------------------------------
 Reporter:  iseulde      |       Owner:  azaozz
     Type:  task         |      Status:  closed
  (blessed)              |   Milestone:  4.5
 Priority:  normal       |     Version:
Component:  Editor       |  Resolution:  fixed
 Severity:  normal       |     Focuses:  ui, accessibility, javascript,
 Keywords:  dev-         |  administration
  feedback has-patch     |
-------------------------+-------------------------------------------------

Comment (by rianrietveld):

 Test results form the accessibility test team on Wp 4.5 plus patch
 33301.voiceover.diff

 Same questions where asked as in the first test
 https://make.wordpress.org/accessibility/2016/02/25/accessibility-
 usertest-create-and-edit-links-inline/. Conclusion is at the bottom, only
 Gabriela tested with VoceOver.

 Results:

 '''Reagan Lynch (screen reader user & developer)'''
 This works great. I understand the instructions, I can edit the link,
 insert the link, and also look for a page or post to link to.
 When I type a word into the search field JAWS correctly reports that
 there are results and I can arrow through the results using the up and
 down arrows. Very nicely done.
 AT used: Windows 7 and JAWS 17

 '''Shaun Everiss  (screen reader user)'''
 Ok works. I didn't find any issues, access, incerting, searching for
 things to insert it works.
 AT used: NVDA, Windows 7, Firefox 45

 '''Tobias Clemens Häcker (screen reader user & developer)'''

 Q: Can you understand how to add a link using this inline window
 A: Yes and no. After pressing Ctrl + K I can start typing the URL or a
 search term and get voice notifications of the amount of results. However
 when using the up/down arrows to select the a single result only their
 number (6 of 20 for example) is spoken by NVDA, not the title. I can
 activate apply once it’s selected by hitting Tab to access the “Apply”
 button and then Enter to activate it.

 Q: Is this usable with your assistive technology?
 A: Yes and no, I don’t know which post is selected but typing in a URL
 works fine.

 Q: Can you hear the search result if you enter a search word instead of an
 URL
 A: No, only the number of results or the number of a specific result is
 spoken.

 Q: Are you missing functionality to make this work for you
 A: I miss voice output of search results.

 AT used: NVDA, Windows 7, Chrome browser

 '''Michelle DeYoung  (developer)'''

 Results Windows10/Chrome/NVDA:
 Can you understand how to search for a page using a search word using this
 inline window - Partially.
 Is this usable with your assistive technology? - Not the Search feature.
 If you use a screen reader: can you hear the search result if you enter a
 search word instead of an URL - No.
 The Search result list items are announced as "unknown", so user will not
 know what to select.

 Results Win10/FF/NVDA
 The pop-up is announced as "Alert". The heading is not voiced by the
 screen readers. The heading should be announced as "Insert/Edit Link". The
 keyboard focus is dropped in the URL text field, so when the user tabs the
 first item they hear announced after 'Alert" is "Link text". If the user
 happened to arrow as their first movement in the popup, they are thrown
 down to the section list of content items. Each content item is not
 voiced, but their URL is - and the cursor focus remains in the URL field.
 The URL field is dynamically updated with the url of the items they are
 arrowing through in the list. The user will not know that the URL is being
 updated dynamically. I suggest it gets updated only when a selection is
 made. If the URL field was initially populated with a user URL,  that URL
 should remain until they have decided to make another selection. The
 section list of content is announced as "Section".  I think it needs to be
 clearer about what the section contains.  When the user tabs to the
 Section list of content, they can arrow to the items, but none of them are
 announced.

 '''Geof Collis (screen reader user & developer)'''
 I'm not sure how the wheel part works but I had no problems inserting a
 link or finding a page on the site.
 AT used: Windows 7, JAWS 14.5, IE 11.0.96

 '''Sirisha Gubba (developer)'''
 Q: Can you understand how to add a link using this inline window?
 A: Instructions are given through place holder and as user starts typing
 in they are gone.
 AT user does not understand the if the search result is a page or the
 modified date  next to it etc.
 Wheel should have more description then just "Link Option" button.
 Unable to close the "type/search URL" small window with "ESC" key

 Q: Can you understand how to search for a page using a search word using
 this inline window?
 A: AT and Keyboard: Able to search it but unable to close the
 "Edit/delete" small window  with ESC key and also user is unable to access
 the "EDIT" and Delete" button

 AT used: NVDA, with FF on Windows7

 '''Gabriela Nino de Rivera Torres (developer)'''
 Keyboard only test: Everything worked great. The only issue that I found
 is that the Esc key won't close the small window.

 Safari/VoiceOver test:
 Can you access the little window with the input field for the link? - yes
 Can you understand how to add a link using this inline window? – yes
 Can you understand how to search for a page using a search word using this
 inline window?
 cmd +K opens the small window, VoiceOver announce it as a combo box and
 instructs me to type text to display a list of choices.
 Is this usable with your assistive technology? I will say yes, but some
 details need attention:

 1) When opening the small window with cmd + K, the focus will jump very
 fast two or three times before settling down on the input field. I hear
 VoiceOver announcing: “li, li, links selected”. This problem won’t prevent
 the user to use the functionality because once the focus is on the input
 field it will stay there.

 2) When searching on the input field, I see the number of results found on
 the VoiceOver text console, but there is not enough time to announce them
 before VoiceOver announce me the word that I typed on the input field. I
 tried lowering VoiceOver speech rate and pitch, also I changed the
 verbosity from high to medium. It did a little difference, but in most of
 the cases the results are not announced.

 3) I’m not sure if the extra options window is part of the test, but when
 searching, VoiceOver does not announce the total of results found. If I
 move to the list of the results, VoiceOver won’t announce the result when
 it receives focus. Although, it does announce them in the small window
 (like Twitter does ;-)).

 If you use a screen reader: can you hear the search result if you enter a
 search word instead of an URL? See comment number 2 below.
 Are you missing functionality to make this work for you? I won’t say
 missing a functionality since only small details need to be corrected to
 make it work with the assistive technology.

 '''Conclusions'''
 Common remark: the window doesn't close on Esc.
 The functionality works understandable in IE/JAWS, FF/NVDA
 Chrome/NVDA has isses: it misses voice output of search results.
 For Safari/Voiceover: see remarks 1,2 and 3 from Gabriela.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/33301#comment:94>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform