Make WordPress Core

Opened 8 years ago

Last modified 4 weeks ago

#32728 assigned defect (bug)

Customizer Menus: Accessibility: reordering menu items should have some indication about the item level

Reported by: designsimply's profile designsimply Owned by:
Milestone: 6.5 Priority: normal
Severity: normal Version: 4.3
Component: Customize Keywords: needs-patch
Focuses: accessibility, javascript Cc:


/hat tip @afercia for the original report at

Splitting this out from the users test post on Make WordPress Accessible:

When reordering menu items, there should be an audible indication of their level.

When reordering menu items, NVDA announces “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 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.

Change History (15)

#1 @afercia
8 years ago

  • Focuses javascript added

In nav-menus.php they have (at least) some text to indicate they're sub-items. This could be further improved adding a depth indicator.

#2 @afercia
8 years ago

  • Type changed from enhancement to defect (bug)

Changing from "enhancement" to "bug" as agreed with @obenland.

#3 follow-up: @celloexpressions
8 years ago

Is the depth useful or would it be better to know what the parent item is? "Sub item under [title]"

#4 in reply to: ↑ 3 @afercia
8 years ago

Replying to celloexpressions:

Is the depth useful or would it be better to know what the parent item is? "Sub item under [title]"

I'd say no parent info but would be useful to know the actual sub items level.

#5 @valendesigns
8 years ago

  • Keywords needs-patch added
  • Milestone changed from Awaiting Review to 4.3
  • Owner set to valendesigns
  • Status changed from new to assigned
  • Version set to trunk

Anymore suggestions/expectations on the output before I get started on a patch?

#6 @afercia
8 years ago

Just discovered something I was not aware of because, well it's pretty undiscoverable :) In the current nav-menus.php screen, menu items have some infos about the menu item level and parent. It's done with JavaScript as hidden text and also title attribute. I'd remove the title attribute and keep just the hidden text but the question here is: would users expect to find the same kind of information in the Menu Customizer too? See screenshot:

#7 @celloexpressions
8 years ago

@afercia could you advise on the ideal wording/information provided and where it should be placed (I'm guessing inside the edit menu item button like on the admin screen?)?

#8 @afercia
8 years ago

@celloexpressions I'd say it should be placed on the focusable elements, i.e. the buttons yeah. Something like what was done in 33151 for the available menu items, hiding redundant text with aria-hidden.
Not sure about the wording. Maybe use the same wording/information used in the admin screen to keep consistency? And then change it in both places if we find something better in future iterations?

#9 @obenland
8 years ago

  • Milestone changed from 4.3 to Future Release
  • Type changed from defect (bug) to enhancement

No patch and we're a ew days away from beta4, let's iterate on this in a future release.

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.

7 years ago

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.

5 years ago

#14 @afercia
5 years ago

  • Milestone set to Future Release

#15 @celloexpressions
3 years ago

  • Owner valendesigns deleted
  • Type changed from enhancement to defect (bug)

There is clear direction above on the preferred text and location from the accessibility team. Re-typing as a bug because the experience is broken for some users and is worse in the customizer than in the equivalent wp-admin screen.

The next step is to create a patch. The patch will likely need to edit the customize menu item control's HTML template in addition to the JS methods that handle reordering and changing depth to keep the text updated when items are moved around.

This ticket was mentioned in Slack in #accessibility by joedolson. View the logs.

4 weeks ago

#17 @joedolson
4 weeks ago

  • Milestone changed from Future Release to 6.5
Note: See TracTickets for help on using tickets.