WordPress.org

Make WordPress Core

Opened 22 months ago

Last modified 15 months ago

#43305 assigned feature request

Accessibility Issue in Arranging the Menu Items: I need a combobox for selecting the parent item and a combobox for selecting the item position

Reported by: javad2000 Owned by: audrasjb
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: Menus Keywords:
Focuses: accessibility Cc:
PR Number:

Description

Hello
I shall firstly thank WordPress team for their utmost attention to accessibility standards, which makes WordPress unique among all CMSs. All WordPress
core features are fairly Accessible for me as a blind person who uses screen reader (JAWS), but I always have problems with rearranging the menu items.
Although the menu-items are also very accessible for a blind person and I can re-arrange them very well, this process is very time consuming for me, because;
for example, if I want to send a menu-item from position 16 to position 11, I have to press “Move Up” 5 times. The problem is:
I don’t have any combobox that assigns the mother-item and the item-position. Therefore, I have to adjust the positions by moving each item one by one,
level by level.

Suppose I have a menu with lots of sub-menus and sub-items. Now, I want to add 6 new sub-items to the different menus. Of course, when I add them to the
menu, they are at the end of menu. If I want to bring each item to a certain position near the center of menu, I have to click “Move up” and “Move down”
one by one for many many times over and over. It takes me about 2 hours to rearrange those menu items. I hope I could explain clearly.

Solution:
Beside each menu item, there is a link called “Edit Menu Item”. When I click on the link, a set of options open up: move up, move down, name, etc. I would
like to have two other options as well: mother-item, and position. For example, I adjust the mother-item of “Audio Translation” as “Translation”, and I
adjust its position to “2”, which means subitem number 2 under “Translation”. I hope I could explain clearly what I mean. If I can adjust the menu positions
with comboboxes, I will not have to click “move up” and “move down” many many times.

Attachments (1)

be278c6a27d93abb7dceeeaeb7b15aa0.gif (478.0 KB) - added by audrasjb 22 months ago.
Workaround

Download all attachments as: .zip

Change History (8)

#1 @audrasjb
22 months ago

Hi @javad2000 and many thanks for this ticket,

We are still working on a similar ticket: #40678 - Editing menus in WP admin for blind people. Of course, feel free to comment this other one as well.
I think we can keep both tickets for now because what you offer brings additional elements to the other ticket.

I will work to integrate your solutions on my work on the other ticket.

Cheers,
Jb

Related: #40678

Last edited 22 months ago by audrasjb (previous) (diff)

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


22 months ago

#3 @juliemoynat
22 months ago

Hi,

I think that's a good idea!

@audrasjb, I'm not sure that @javad2000 can see your animated image. :)

In your example, you add a "Move to position:" field with "1", "2", "3", "4" options.
Can we add the total number of items to help a little bit more?

"Move to position:"

  • 1 of 8
  • 2 of 8
  • 3 of 8
  • etc.

@javad2000 also needs another field to define an item as a child. Can we do as we have it for "Pages"?

"Parent:"

  • (no parent)
  • Blog page
  • Sample page
  • W.org
  • Google
  • etc.
Last edited 22 months ago by juliemoynat (previous) (diff)

#4 @afercia
22 months ago

  • Component changed from General to Menus
  • Focuses accessibility added
  • Version 4.9.2 deleted

I will work to integrate your solutions on my work on the other ticket.

I'd recommend to keep things separated :) It's far better to have smaller patches, focused on a single issue, rather than big ones that are difficult to review, test, and they often go stale pretty soon.

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


22 months ago

#6 @afercia
22 months ago

  • Milestone changed from Awaiting Review to Future Release
  • Owner set to audrasjb
  • Status changed from new to assigned

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


15 months ago

Note: See TracTickets for help on using tickets.