Page MenuHomePhabricator
Create Task
Maniphest T263834

Test new header-first DOM with screenreader users
Closed, ResolvedPublic
Actions

Description

With the new header-first DOM enabled in T261802 and outcome of T240489 we need to collect feedback from users of screenreader software.

  • Does orientation on page meet user expectation?
  • Does users get in timely and usable manner to
    • navigation?
    • content?
    • search?
  • What are your impressions of this order of regions in article compared to this one?

Example article
New DOM structure: https://en.wikipedia.org/w/index.php?title=Helianthus&useskinversion=2
Former DOM structure: https://en.wikipedia.org/w/index.php?title=Helianthus&useskinversion=1

Main page
New DOM structure: https://en.wikipedia.org/w/index.php?useskinversion=2
Former DOM structure: https://en.wikipedia.org/w/index.php?useskinversion=1

Related Objects

Event Timeline

Volker_E created this task.Sep 25 2020, 9:36 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 25 2020, 9:36 AM
ovasileva triaged this task as Medium priority.Sep 25 2020, 9:54 AM
ovasileva added a subtask: T240489: [Epic] Determine the optimum Vector DOM structure for a11y and performance.
Volker_E updated the task description. (Show Details)Sep 25 2020, 10:10 AM
• nray added a comment.Sep 25 2020, 4:24 PM

lgtm, just had one thought below:

How disruptive is the change in contrast to the old DOM order?

Not sure if the question should be asked in that way as it seems a bit of a leading question (assumes that the change might be disruptive). Something like "What are your impressions of the this tab order compared to this tab order" might be less suggestive

ovasileva added a comment.Sep 25 2020, 4:30 PM
In T263834#6494516, @nray wrote:

Not sure if the question should be asked in that way as it seems a bit of a leading question (assumes that the change might be disruptive). Something like "What are your impressions of the this tab order compared to this tab order" might be less suggestive

+1 to this

• nray added a comment.Sep 25 2020, 4:49 PM

Also, I'm not sure what effect this would have on the test, but wanted to note that the implementation of T262872 (currently in ready for dev) might play a role in how users perceive the new DOM order (bringing back the ability to jump from the sidebar button directly into the sidebar)

Volker_E updated the task description. (Show Details)Sep 25 2020, 5:09 PM
Volker_E updated the task description. (Show Details)
Volker_E added a comment.Sep 25 2020, 5:11 PM
In T263834#6494516, @nray wrote:

lgtm, just had one thought below:

How disruptive is the change in contrast to the old DOM order?

Not sure if the question should be asked in that way as it seems a bit of a leading question (assumes that the change might be disruptive). Something like "What are your impressions of the this tab order compared to this tab order" might be less suggestive

Sounds good to me, generalizing, as tab order is not necessarily point for screenreader users, more for keyboard only users.

ovasileva moved this task from Needs Analysis to Upcoming on the Web-Team-Backlog (Kanbanana-FY-2020-21) board.Sep 30 2020, 1:17 PM
Volker_E updated the task description. (Show Details)Oct 8 2020, 8:08 PM
ovasileva moved this task from Upcoming to Doing on the Web-Team-Backlog (Kanbanana-FY-2020-21) board.Oct 13 2020, 11:19 AM
MBinder_WMF moved this task from Doing to Blocked on Others on the Web-Team-Backlog (Kanbanana-FY-2020-21) board.Oct 14 2020, 5:28 PM
Jdrewniak mentioned this in T240489: [Epic] Determine the optimum Vector DOM structure for a11y and performance.Oct 14 2020, 5:28 PM
Volker_E added a comment.Oct 14 2020, 5:30 PM

AFB told that they should be able to get back to us approximately mid-week 11 Oct–17 Oct.

ovasileva moved this task from Blocked on Others to Ready for Signoff on the Web-Team-Backlog (Kanbanana-FY-2020-21) board.Oct 19 2020, 11:45 AM
Volker_E closed this task as Resolved.Oct 20 2020, 10:13 AM
Volker_E claimed this task.

The AFB response on the new DOM is positive!

From a usability perspective, the changes made to the DOM all seem to be improvements to navigation or understandability of the content of the page. There are menus and tools that have been moved that reduce the amount of navigation a keyboard or screen reader user needs to perform, which is always helpful.

From a technical perspective, nothing provided in this feedback appears to be a WCAG violation. All the elements behaved as expected and we didn't see anything that stood out during our time investigating the feedback.

They've shared some minor concerns about heading structure that will be filed as follow-ups.

Another win:

On the old DOM structure the 'Personal Tools', 'Namespaces', and 'Views' Navigation
landmark regions were part of the level 2 'Navigation menu' heading which was further down in
the page. The screen reader user had to navigate deep in the page to get to these options. This
is also true for the search field which was part of the level 3 heading and appeared after the
'Navigation Menu'.
This challenge has been solved in the new DOM structure.

Volker_E mentioned this in T265993: Heading structure & ordering in (new) DOM structure.Oct 20 2020, 11:30 AM
Volker_E removed a subtask: T240489: [Epic] Determine the optimum Vector DOM structure for a11y and performance.Oct 20 2020, 11:33 AM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits