Accessibility of Web links: introduction
  |  |
Print  |
Send  |
Share         |
Warning: The original version of this document is Web Links and Hypertext: an introduction . This French translation was done by Ideose as part of an agreement between WebAIM and Ideose .
Note: See page documents on web accessibility for a list of all translated documents. Other resources on web accessibility are also listed in the portal accessible digital .
Summary
- You are on Page 1: Introduction
- Page 2: Create text links accessible
- Page 3: Creating hyperlinks accessible
Overview
The hyperlink is one of the basic elements of HTML as its name suggests (HTML stands for HyperText Markup Language).
As such, make hyperlinks accessible is one of the most fundamental and most important of web accessibility.
Mostly, this is an easy task.
The hyperlinks will work with any standard technologies and platforms.
Users of all levels can access it directly or through the use of assistive technology.
But as can be expected, the accessibility of hyperlinks is not simply to create a link.
Some types of links are more accessible than others, and some types of links are inaccessible to people with certain disabilities.
Because links are so essential to the operation of web content, the links are inaccessible one of the most serious barriers to the overall accessibility.
Accessibility links the keyboard
Users must be able to browse and select each link using the keyboard alone. permet aux utilisateurs d'activer un lien. In most browsers, the Tab key to move from link to link, and the Enter key allows users to activate a link. If the only way to access a link with a mouse then the link is unusable for people who can not use a mouse. How is it possible to create a link that is inaccessible to the keyboard? The most common method is to use JavaScript event handlers that do not allow keyboard access (read the document on JavaScript event handlers ). In other ways to make the links accessible to users using the keyboard, there is the fact of using non-HTML technologies such as Flash or Java, to create links in an HTML document. Java and Flash can be made accessible, but only if the developer uses them with a concern for accessibility. Overall, the creation of HTML links accessible is easier and simpler than creating links with other available technologies.
One of the biggest barriers is to create links that go nowhere. Developers sometimes use JavaScript to create dynamic menus that take place when the user hovers the mouse with some links. In some cases, the link itself leads nowhere. Its sole purpose is to display the menu links, which have their real destinations. This type of relationship often has a destination sign (#), which means that the link destination is on the same page. Click on this link causes no action. Users and those using the keyboard using the mouse will not get it by clicking this link.
Bad example
The link in this example is not going anywhere. Its sole purpose is to activate a JavaScript function.
Users using the mouse can at least click on the links in the menu, but users using the keyboard can not access the menu.
Therefore, the link is totally useless and all the link destinations of the menu are completely inaccessible.
One solution is to abandon the dropdown menu and to use instead of hyperlinks.
Another solution is to define a real link destination (eg, href="products.htm" ) which would list the same links that are available via the dropdown menu.
For more information, see Example 2 of paragraph " onMouseOver and onMouseOut " in the document on JavaScript event handlers.
Screen readers and links
People who use screen readers to access the Web most often use the keyboard rather than mouse. Thus, keyboard accessibility is an important first step in making available hyperlinks to users of screen readers. Beyond the basic aspects of accessibility to the keyboard, it helps to know how users of screen readers to access the links.
Screen readers inform users that text (or image) is a link
JAWS says "link" before each link. modifie sa voix. For example, a link that says "products" would be read as "link products" by JAWS. IBM Home Page Reader alters his voice. A man's voice reads the text content so that it is a female voice that reads text links.
Result: there is no need to write "link" in the link text.
All users already know that the link is a link.
The question is more for the images used as links.
There is no need to write "link" or "link" in the alt text of an image.
Otherwise, JAWS users will hear "link graphic link to the products," which is redundant.
Users of screen readers often navigate from link to link, skipping the text from the links between
Tabbing from link to link is a way to view Web content, especially if users try to find a particular section of a website.
A consequence: the links should make sense out of context. Phrases such as "click here", "more", "click for details" and so on are almost completely meaningless when read out of context. At the same time, it would be too excessive detail the link in order that its destination is perfectly discernible by listening out of context. Users do not want to hear "Product page on which a list of all our products are presented, including software and training products, with a price list and availability by region (this page uses the same navigation model that page where you are now). " Perhaps a better solution would be simply a link that says "Products".
Result 2: Update the link-specific information at the beginning. Do not put non-specific information at the beginning of the relationship but in the end link. For example, do not write "link that opens in a new window: Products". Instead, write "Products (opens in new window)" or something of that style. This is particularly important in this example, if multiple links from the same Web page open in a new window. With positioning information in the first place instead of specific information, users of screen readers will hear the term "link opens in a new window" many times. They will find it harder to distinguish the different links, or at least they will take them longer.
Users of screen readers sometimes get a list of links sorted alphabetically
Screen readers allow users to post links on a Web page in a list organized alphabetically. They use a keyboard shortcut in their screen reader for that. This is especially helpful if they know the first letter of the link they want.
Therefore: Use as links words and phrases that can be intuitively organized in alphabetical order. For example, the phrase "contact us" appears in a conventional manner on many websites and can be the link sought by users. If the link says "contact us" or "how to contact us" or another phrase, which is less intuitive than the first mentioned (as least used), then users may have more difficulty finding the link.
Read also:
WebAIM Resources
External resources
WebAIM is an initiative of:
Copyright 1999-2009 WebAIM
