Context Navigation

Changes between Version 5 and Version 7 of Ticket #27403

Ticket #27403
- Property Focuses accessibility added
- Property Priority changed from low to normal

-                      v5
+                      v7
 Additionally, there is a fundamental issue with the shift+click feature: it is not mobile friendly since there is no ability to do this on a touch screen. The immediate equivalent feature for mobile I think would be a long press. On mobile, the preview fills the screen so if a widget, nav menu item, or other partial was long-pressed it could then flip over to the controls pane where the relevant control would be focused. The problem with shift-click on desktop is similar to the problem with long-press on mobile: there is no indication which elements can be edited so the user doesn't know where to try.
+And @afercia notes from duplicate ticket #33251:
+> By the way, the point is this feature is really hidden. The only chance users have to be informed about this is when by accident they hover on a widget and notice the title attribute. Not to mention touch devices, as far as I know, won't ever show this. There are no instructions or Help text that mention this, as far as I know.
+>
+> Considering also #24766 I'd recommend to don't rely on title attributes alone to convey such important information. It would be a nice, interesting, challenge trying to find a new design/UI pattern to be used instead of a title attribute. Call for designers :)
+>
+> Also, from an accessibility point of view, this UI control is not focusable and hardly usable for keyboard users and screen reader users.