WordPress.org

Make WordPress Core

Opened 4 years ago

Last modified 25 hours ago

#23328 assigned enhancement

While editing widgets in accessibility mode the position can be indicated by widget titles instead of numbers

Reported by: mark-k Owned by: afercia
Milestone: 4.7 Priority: normal
Severity: normal Version:
Component: Widgets Keywords: has-patch has-screenshots dev-feedback needs-refresh
Focuses: ui, accessibility, administration Cc:

Description

Guess it title says it all. Right now you need to figure out the position you want the widget to be at and try remember it while editing the widget.

I suggest to change the text text of the position column header from "position" to "position after" and use labels in the drop down

1 => "top"

2 => top widget title

3 => second widget title

etc

Attachments (3)

23328.patch (3.5 KB) - added by afercia 11 months ago.
23328.2.patch (3.6 KB) - added by afercia 5 months ago.
23328.3.patch (5.7 KB) - added by Mte90 5 months ago.
fix also #36772

Download all attachments as: .zip

Change History (17)

#1 @_Redd
4 years ago

Hi mark-k, you may be interested in a related development here:

http://core.trac.wordpress.org/ticket/14045

Version 0, edited 4 years ago by _Redd (next)

#2 @chriscct7
17 months ago

  • Focuses accessibility administration added
  • Keywords needs-patch added

#3 @afercia
11 months ago

  • Focuses ui added

Not all users know this alternate mode so basically we're speaking about this, see in the screenshot below:

https://cldup.com/CRzCpWdnb2.png

This alternate screen can be enabled toggling the link "Enable/Disable accessibility mode" in the Screen Options. When reordering the widget position the select shows just numbers. It's difficult to remember the actual widgets position in each sidebar.

By the way, not all widgets have "titles" to show, several instances of the same widgets can be used on the sidebars, etc. Widgets do always have a widget type "name" though and we could at least add the widget type name. Additionally, the selects the edited widget is not assigned to, should have an empty, available, select option with some proper text, e.g. "Available position".

This screen could receive some UI tweaking too, for example I don't see any reason why the content should be centered, unless I'm missing something.

@afercia
11 months ago

#4 @afercia
11 months ago

  • Keywords has-patch has-screenshots added; needs-patch removed

A very fist pass, to get something like in the screenshot below. Any improvements and patches welcome :)

Couple of notes:

  • the option text should be shorter
  • noticed there's no "Cancel" button to cancel editing and go back to the Widgets screen

https://cldup.com/dj-OjRvZnS.png

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


6 months ago

#6 @afercia
6 months ago

  • Milestone changed from Awaiting Review to 4.6
  • Owner set to afercia
  • Status changed from new to assigned

@afercia
5 months ago

#7 @afercia
5 months ago

Refreshed patch, coding standards, better variable names. Would appreciate a review.

#8 @afercia
5 months ago

Related: #36772. Needs to take care of the case of a widget from a disabled plugin that still has its "position" in the sidebar.

https://cldup.com/yIb2Qyfkud.png

@Mte90
5 months ago

fix also #36772

#9 @Mte90
5 months ago

  • Keywords dev-feedback added

Respect to the patch of @afercia contain:

  • In the select of the widget for the area if the widget not exist anymore (because remove like a plugin), that position is removed from the ui (added a new loop to add an empty option field)
  • On the save of the widgets of that sidebar now there is a check to detect if that widget is registered, in case it is removed from the db so in the next editing of that sidebar this problem don't happen again (like for the classic editing with drag & drop)

With this implementation fix also the #36772.

This ticket was mentioned in Slack in #core by chriscct7. View the logs.


4 months ago

#11 @chriscct7
4 months ago

  • Milestone changed from 4.6 to Future Release

Punting per discussion

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


11 days ago

#13 @rianrietveld
11 days ago

  • Milestone changed from Future Release to 4.7

#14 @jorbin
25 hours ago

  • Keywords needs-refresh added

The patch needs to be refreshed to follow the coding standards and also needs some additional testing with various AT.

Note: See TracTickets for help on using tickets.