-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review updates made to link example page #228
Comments
Made the following updates for issue #228: * updated link examples to use new example template * fixed bug in CSS * updated description * Editorial revisions to link example page.
The pattern says that shift+f10 opens the link context menu. Our examples do not have a context menu to open the link in a new tab, etc. Should we include this feature? |
Might be worth it to at least implement a keyboard shortcut for “open in new window”. On macOS this would be cmd+enter. Regardless of whether we implement the context menu. |
Made the following changes Per discussion of issue #228 in Feb 6 authoring practices meeting. modified aria-practices.html: In the link pattern section, keyboard subsection, marked the context menu key (shift+f10) as optional. modified examples/link/link.html: In the example introduction, added the following sentence to the note encouraging authors to use native HTML links: "Browsers provide valuable functionality for native HTML links, e.g., open the target in a new window and copy the target URL to the system clipboard."
Question: does link number 4 disappear in high contrast mode? |
For the context menu to open link in a new window or new tab. Is there any other markup that needs to be added to the link like: aria-haspopup, aria-expanded and/or aria-controls. I am assuming the context menu follows the ARIA menu pattern. Jon |
Example#3 doesn't have focus. Thanks, |
If a link takes to another webpage(outside the current website) , should they be informed through the screen reader text. Thanks |
@jongund wrote:
No. As with menubutton, aria-controls and aria-expanded are not necessary. While it would not be incorrect to add aria-haspopup, all links already have context menus so there is no value in doing so.
Yes. |
@jongund wrote:
OK, that's what I thought. I wonder if we should flag that example as not recommended and put a note for the reason? Thoughts? |
@shirsha wrote:
You mean, the focus ring disappears when link 3 gets focus? What browser? Others seeing this? |
@shirsha wrote:
Some sites have such a policy, but that is not needed for accessibility. Some sites use an icon to indicate that, and if they do, they should make sure that icon is accessible. One thing I did at IBM was to make it more screen reader friendly by having the accessible text that represented that icon appended to the end of the link text even though the icon preceeded the link. But, again, that is not core to this pattern. Now, you might be thinking of a WCAG technique that suggests that links should indicate whether they open a new window. While that is not an essential aspect of this pattern, we could have a note that references it from the design pattern. We reference WCAG in a few other places. |
Per issue #228, make changes to examples/link/link.html: 1. Remove link 4, which used a background image that disappears in Windows high contrast mode. 2. Edit introduction, states and properties table, and source code section to reflect removal of link 4. 3. Change CSS to fix disappearance of custom focus ring on link 3. 4. Change CSS to make the custom focus ring more visually distinct.
@annabbott I’ll fix that a bit later today. Update: Fixed! |
Confirmed fixed |
The review process is now complete for this example page. modified examples/link/link.html: Removed paragraph with link to issue #228, which was the review issue for this example.
All reviewer feedback has been addressed. Closing to complete the review process. |
The Link Examples page
needs the following updates.
Requested Reviews
The text was updated successfully, but these errors were encountered: