Problem/Motivation

If you narrow down the browser to a mobile viewport so the navigation sidebar is collapsed and you then activate a screenreader (voiceover in my example) you will notice that buttons and form controls contain elements that are only available in the expanded navigation sidebar. Illustrated in menu_items.mp4

`discussed and raised with @mgifford and @drupa11y

the appearance page in mobile viewport with voiceover active showing the buttons section in the rotor

Steps to reproduce

  • narrow down the browser to a mobile viewport so the navigation sidebar is collapsed
  • active your screenreader

Proposed resolution

remove all the navigation module related buttons from the aural interface except the "expand sidebar collapsed" button

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

CommentFileSizeAuthor
#3 collapsed.jpg260.34 KBrkoller
#2 menu_items.mp41.81 MBrkoller

Comments

rkoller created an issue. See original summary.

rkoller’s picture

StatusFileSize
new1.81 MB

forgot to add the mp4

rkoller’s picture

Issue summary: View changes
StatusFileSize
new260.34 KB
mgifford’s picture

I can see how this would cause confusion for sure. Thanks @rkoller

https://webaim.org/blog/hiding-content-for-screen-readers/

kentr’s picture

I think the the proposed fix for #3541910: Elements in closed sidebar are focusable will also fix this.

I didn't point this issue out explicitly, but experimenting with visibility: hidden did remove the items from the VoiceOver rotor.

catch’s picture

Title: on the mobile viewport with the navigation sidebar collapsed the menu items are still available in the aural interface » [PP-1] on the mobile viewport with the navigation sidebar collapsed the menu items are still available in the aural interface
Status: Active » Postponed
rkoller’s picture

Status: Postponed » Closed (duplicate)

I've tested the proposed solution in MR14200 on #3541910: Elements in closed sidebar are focusable and the MR is fixing the linked issue as well as this issue. closing this one as duplicate (this issue deals with with one aspect of the other issue).

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.