(In reply to James Teh [:Jamie] from comment #2)
Thanks for the heads up about this. This is definitely relevant for a11y.
The good news is that from my initial testing with the NVDA screen reader on Windows, this works quite nicely as is. Because it uses a menupopup, it behaves like any other Firefox context menu, with which users are already quite familiar. The appearance of the menu is reported just like the appearance of any other context menu. It might be slightly confusing to some beginning screen reader users because context menus don't tell you what's inside them when they appear - you have to move to the first item (e.g. with down arrow) in order to know what's inside them - but that's true for any context menu and is thus a pattern they will have to learn regardless.
Thanks for having tested that and for the context.
Just to clarify, you called this a paste "button"... but from what I can see, it's really a menu item.
Yes, for simplicity I called it a "button", a menupopup with a single menu item is indeed more precise.
Is there/will there be some visual styling that makes it more prominent and/or look more like a button for sighted users?
Currently, that's not intended. FYI, Safari shows such a menu item too under certain circumstances when calling
clipboard.readText(), so that's encouraging in terms of UX and presumably we'll keep it as it is.
That might change the semantics we should be using for a11y.
Thanks for making me aware of this.
Morgan, would you mind taking a look with VoiceOver and/or HCM when you get a chance? I don't anticipate any problems, but best to be sure.