Make edit hyperlink dialog in word 2016 navigable by keyboard
In the edit hyperlink dialog in Word 2016, the following undesirable behaviour is observed:
Pressing tab to move between elements, as you move from the "link to: existing file or web page" to the "Text to display" edit box, the OK button loses it's default button status. This means when you press ENTER, you get an error ding and nothing happens. The OK button should remain default button.
As you press tab and move into "current folder tree view" (the list of files) - the first file is automatically selected and thus the URL you had previously used or typed is replaced with the address to the first file in your documents folder. Traditionally when tabbing to a tree view such as this, the list takes focus but the first file does not until you press spacebar or down arrow to the second file.
When you select "Browsed pages", the list of pages displayed is drawn from the history from Internet Explorer. On Windows 10 particularly, many users don't even realise iE still exists. This list should be populated from the history from the users default browser.
Quentin
shared this idea
Thank you for your input. We chatted with the Word Team on these issues:
• Issue 1: Fixed. This enhancement will start rolling out to Office 365 First Release and Office Insider Customers before Fall.
• Issue 2: We are working on a fix for this issue now, thank you for your feedback. Our goal is to fix this issue as part of our commitment to accessibility.
• Issue 3: Unfortunately, we don’t have the ability to fetch the browsing history from most browsers. The team is looking into other potential improvements.
1 comment
-
Thank you for your input. We chatted with the Word Team on these issues:
• Issue 1: Fixed. This enhancement will start rolling out to Office 365 First Release and Office Insider Customers before Fall.
• Issue 2: We are working on a fix for this issue now, thank you for your feedback. Our goal is to fix this issue as part of our commitment to accessibility.
• Issue 3: Unfortunately, we don’t have the ability to fetch the browsing history from most browsers. The team is looking into other potential improvements.