Make WordPress Core

Opened 6 years ago

Closed 2 years ago

#41613 closed enhancement (wontfix)

Media Modal: Consider redesigning "Link to" pattern

Reported by: melchoyce's profile melchoyce Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Media Keywords:
Focuses: ui, accessibility Cc:


From both experience and usability testing, it seems that “Link to” as a dropdown in the Media Modal isn’t a great interaction pattern. Could we explore some other options that might be more clear or intuitive?

Attachments (1)

Wireframe.png (111.0 KB) - added by JoshuaWold 6 years ago.
Wireframe showing link to as radio buttons

Download all attachments as: .zip

Change History (12)

#1 @afercia
6 years ago

  • Focuses accessibility added

6 years ago

Wireframe showing link to as radio buttons

#2 @JoshuaWold
6 years ago

What if we we were to change things up and make it a radio button pattern, instead of a dropdown?

#3 @melchoyce
6 years ago

Radio buttons seem like a simple improvement that would improve discoverability 👍

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

6 years ago

#5 @afercia
6 years ago

  • Milestone changed from Awaiting Review to Future Release

Discussed during today's accessibility bug-scrub and we don't have objections to try radio buttons, definitely something worth trying. Moving to future release.

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

6 years ago

#7 @afercia
5 years ago

Note: in the wireframe above, the URL input field misses a visible <label> element.

I'd also like to remark, kindly, that this ticket was created 14 months ago and still there's no feedback from the Media component maintainers.

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

5 years ago

#9 @joedolson
2 years ago

This is a feature that has changed radically between classic editing and the block editor. The entire attachment details section is removed when operating in the block editor, and the method for handling linking is completely different.

Given that, I think that this is probably a wontfix.

This ticket was mentioned in Slack in #core-media by joedolson. View the logs.

2 years ago

#11 @antpb
2 years ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

I agree this is a wontfix due to the nature of the new editor vs. classic. I feel uneasy changing the classic experience at this point now 3 years later especially with less folks ensuring that this doesnt create problems for new and existing content.

Note: See TracTickets for help on using tickets.