Beruflich Dokumente
Kultur Dokumente
Version 3.0
Table of Contents
CHANGE HISTORY...........................................................................................................................................4 INTRODUCTION................................................................................................................................................4 PURPOSE.............................................................................................................................................................4 REFERENCES.....................................................................................................................................................4 1. NAVIGATION AND DESIGN .......................................................................................................................5 1.1 COMPREHENSIVE CONTENT DESCRIPTIONS.................................................................................5 1.2 COLOR...........................................................................................................................................................5 Color Challenges ...................................................................................................................................5 1.2.3 Photo-Sensitivity IssuesT ..............................................................................................................9 1.3 NAVIGATION, STRUCTURE AND LAYOUT........................................................................................9 1.3.1 Opening New Windows..................................................................................................................9 1.3.2 Structural Elements and Order......................................................................................................9 1.3.2.1 Header Markup .......................................................................................................................10 1.3.2.2 Structural Markup ...................................................................................................................11 1.3.3 Keyboard Access .........................................................................................................................13 1.3.3.1 Keyboard Focus on Active Elements.........................................................................................13 1.3.3.2 Logical Tab Order....................................................................................................................13 1.3.4 Clear Link Text............................................................................................................................15 1.3.4.1 Navigable Links .......................................................................................................................16 1.3.4.2 Appropriate Link Text...............................................................................................................17 1.3.5 Repetitive Links...........................................................................................................................18 1.3.6 Proper Table Design....................................................................................................................21 1.3.6.1 Data Table Specifications ........................................................................................................21 1.3.6.2 Layout Table Requirements ....................................................................................................23 1.4 ACCESSIBLE ELECTRONIC FORMS..................................................................................................24 T1.4.1 TForm Usability .....................................................................................................................24 1.4.1.1 Form field Labeling and Positioning........................................................................................25 1.4.1.2 Grouping complex forms..........................................................................................................26 1.4.1.2-a Error and Success Indicators ...............................................................................................27 1.4.1.2-b Time-Based Response Considerations...................................................................................27 1.4.1.2-c Session Time-Outs.................................................................................................................27 2. DEVELOPMENT...........................................................................................................................................28 2.1 ALT AND TITLE ATTRIBUTES ...........................................................................................................28 2.1.1 Alt Attributes................................................................................................................................28 2.1.2 Title Attributes.............................................................................................................................30 2.1.3 Attribute Labels...........................................................................................................................31 2.2 BROWSER SUPPORT...............................................................................................................................31 2.3 WEB PAGE CONTENT USING JAVASCRIPT, AJAX, AND/OR CSS.............................................31 2.3.1 JavaScript Policy.........................................................................................................................32 2.3.2 AJAX ...........................................................................................................................................32 2.3.3 Cascading Style Sheets ...............................................................................................................32 2.4 STANDARD REDIRECTION FUNCTIONS ........................................................................................32
2.5 FRAMESETS...............................................................................................................................................33 2.5.1 Frame Titles................................................................................................................................33 GLOSSARY........................................................................................................................................................34 APPENDIX I: TARGET ONLINE ASSISTIVE TECHNOLOGY GUIDELINES (TOATG) EXEMPTION POLICY.....................................................................................................................................37 EXEMPTION FORM........................................................................................................................................38
Change History
This document is located in: http://sharepoint.target.com/sites/im/teamsites/creative/TOATG%20Wiki/Home.aspx
TU
UTT
This document was created based on the Target Online Assistive Technology Guidelines (TOATG) - Short Form.
Introduction
Target is dedicated to providing the best experience for all Target.com guests, including those who use assistive technologies. Target Team Members and agency partners are expected to follow the Target Online Assistive Technology Guidelines (TOATG) when either developing new creative for Target.com or improving existing creative.
Purpose
To provide a scope of technology recommendations, including the logical and physical components of an application, in sufficient detail, to effectively and appropriately build a Target site experience.
References
Title
Target Online Assistive Technology Guidelines
Author
Target.com Guest Experience, Interactive Marketing Creative, TTS
TU
Location
http://sharepoint.target.com/sites/im/t eamsites/creative/TOATG %20Wiki/Home.aspx
UT
1.2 Color
The use of color can impact the compatibility of the site with assistive technologies. Guidelines : 1. Do not use color alone to convey information. 2. Do use color to reinforce information presented in text, images or icons. 3. Provide sufficient contrast between text and background. 4. Avoid images that flash more than 4 times per second.
U U
Best Practice : Use a variety of indicators such as color, text layout, shape/texture, and audio to improve the user experience for all guests.
U U
Color Challenges
Information presented in color should also be evident without color. Use effective markup or context solutions on Target site pages to accomplish this objective.
U
To match the error message at the top of the form, three asterisks before and after the error message in the form field conveys the necessary information with or without the use of color.
Example: Use a colored an icon to reinforce information In order to indicate an important feature of the site, the shopping cart is accentuated with the color red.
Example: Use multiple indicators to convey and reinforce information The Target site uses a red button labeled Go with the alt attribute Search Submit to initiate a search (see section 2.1 Alt and Title Attributes ). Note: Even though the same image is used for different tasks on the site, the alt tag adequately describes the buttons action.
T T
In addition to text and images, appropriately utilize markup language. a. CSS Markup Cascading Style Sheets (CSS) should be used to define system colors and fonts. Use of CSS improves accessibility by separating presentation from content. Avoid placing formatting attributes in HTML tags (i.e. background, color, text size, etc.) where they could be better served through the use of Cascading Style Sheets. b. Color Markup Use hexadecimal colors values (for 'color', 'background-color', 'border-color', and 'outline-color') and system fonts (for 'font-family').
Non-preferred
Color: red
Preferred
Color: #CC0000
Use icons to provide contextual clues and easy recognition. Example: Use an icon to reinforce color The color red reinforces the asterisk symbol indicating a required form field.
Ensure there is sufficient contrast between text and background colors. If an image contains text, use either light text on a dark background or dark text on a light background to provide adequate contrast. Avoid placing text over strongly patterned backgrounds. Optimal Color Combinations:
black on white dark gray on white white on black red on white white on red
gray on gray blue on black purple on black light on light white on yellow yellow on white vibrating colors red on red
Avoid high contrast flickering or the intense blinking of colors as some guests may have sensitivity to such effects, potentially resulting in severe physical reactions. Guidelines: 1. Avoid strobe-like effects that combine rapid flashing (more than 4 flashes per second) with high contrast. 2. If flickering, flashing, or blinking content is used, provide a mechanism to stop the blinking, such as a Stop Animation button.
< a href = "www.target.com" title = "Link will open new window" >Sign up here</ a >
T TT T T TT T T T T T
Example: Consistent use of an icon that indicates a new page. If using an icon to show a link opening in a new window, please ensure that the icon is included in the anchor.
Guidelines: 1. Follow rules and conventions specified in the current Target Production and Front End Web Development Guidelines. 2. Separate content markup from presentational markup: a. Content Markup is the text, images and other informational elements of the document. b. Presentation Markup is how the content is displayed. 3. Use style sheets to control the layout and presentation of a page. 4. Create pages that are readable with style sheets turned off.
<h1>Reviewing & Changing My Orders</h1> <h2>Your Recent Orders</h2> <p>Click "My Account" in the top right corner of any page and you'll find an Instant Order Update.</p> <h3>Reviewing and Changing Your Orders</h3> <p>You can review the status of any order you've placed by clicking "My Account" in the top right corner of any page.</p> <p>You can confirm the date and method of shipment, an estimated date of arrival and a tracking number, if available.</p>
Example: A Spanish phrase within an English document could be coded as <span lang="es"> Toca El Tambor </span>.
c. When the bulk of the content on a page is in a language other than English,
specify the language code in the HTML tag to declare the primary natural language of the document. This will enable screen readers to serve the correct text-processing language to the guest. This should also be used in conjunction with http-equiv and content attributes on the meta tag to specify the language of the targeted audience.
<html lang="en"> <head> <meta http-equiv="Content-language" content="en"> <title>Childrens Toys</title> </head> <body> Find more information on <span lang="es">Toca El Tambor</span>. </body> </html>
<label for="fullname">Name<span class="required">*</span></label> <input type="text" name="fullname" id="fullname" tabindex="1"><br> <label for="address1">Address 1<span class="required">*</span></label> <input type="text" name="address1" id="address1" tabindex="2"> <label for="address2">Address 2</label> <input type="text" name="address2" id="address2" tabindex="3"><br> <strong>How many students, staff and volunteers will be participating?</strong> <br>
<label for="staff">Staff<span class="required">*</span></label> <input type="text" name="staff" id="staff" tabindex="4"><br> <label for="students">Students<span class="required">*</span></label> <input type="text" name="students" id="students" tabindex="5"> <select name="grade" id="grade" title="Please select your student's grade." tabindex="6"> <option VALUE="" selected>Select Level</option>
<option VALUE="K">K</option> <option VALUE="1">1</option> <option VALUE="2">2</option> <option VALUE="3">3</option> </select><br> <label for="volunteers">Volunteers<span class="required">*</span></label> <input type="text" name="volunteers" id="volunteers" tabindex="7"> See section 1.3.5 Repetitive Links for a discussion of ways to skip over sections of repetitive links.
T T
3. If it is necessary to use the same link text to point to different link targets, use title
attributes to distinguish between them (see section 2.1.2 Title Attributes ).
T T
4. Links should not be a single word or letter. Links presented as buttons or icons
should be large enough to easily navigate.
Non-preferred
Click here to view this weeks specials.
Preferred
Current Target.com Specials
Example: Inappropriate Link text Avoid sets of links that are single letters or numerals presented in a horizontal row separated only by a space. Some screen readers might interpret the entire series as a single link. The small size could be difficult to navigate. Example: Link text
Non-preferred
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Next >>
T T
Preferred
What 1-Day and 2-Day Shipping Mean Changing Your Shipping Address
T T
In general, screen readers read each link in the navigation bar of each page prior to reading page content. Avoid this by providing guests with a means to bypass repetitive links as a group. The skip navigation link consists of two elements: 1. A named anchor link at the initiation of the main content area of the page 2. A link that points to the named anchor The code below is a model for the named anchor, which goes directly before the HTML code that contains the main content of the page. The name attribute of the HTML tag sets the anchor. Names should be all lower case, without spaces. Example: Named anchor link.
<span style=postion:absolute;><a name=skiptocontent> </a></span>
The skip navigation link is near the top of the page; this is often the first item on the web page. Connect to the named anchor using a link similar to the one below.
<a href=#skiptocontent>Skip Page Navigation</a>
The skip navigation link can be presented in a number of ways: Example: On Focus Skip Link By making the skip link visible with keyboard focus, mouse users will not see the link; however, if the link is positioned appropriately it will be the first thing a screen reader or keyboard user encounters on the page. Without keyboard focus, the skip link is not visible:
Example: Transparent Skip Link A skip link can be made invisible to sighted guests if it is coded as a 1 pixel transparent image.
Layout Table
Data Table
Guidelines: 1. Identify data cells with TD (tabular data) and headers with TH (table headers). 2. Use scope=row for each row header and scope=col for each column header 3. Identify structural groups of rows by using THEAD for repeated table headers, TFOOT for repeated table footers, and TBODY for other groups of rows. Use COLGROUP and COL for groups of columns. a. For data tables which have two or more levels of row or column headers add an id attribute to each header cell and provide a header attribute for each data cell that lists all header cells for that data cell. (Example: [like headers=id1 id2 id3] if those were the ids of the headers of that data cell.) (Note: Screen readers may not render tables with more than two logical levels of row and/or column headers correctly, even when they are properly marked.) 4. Use the TABLE element, rather than PRE, to create a tabular layout of text, enabling many assistive technologies to recognize a table.
<table width="450" border="0" cellpadding="3" cellspacing="1" > <caption>SHIPPING INFORMATION</caption> <tr> <th id="price" colspan="3">Pricing</th> </tr> <tr> <th id="cat" scope="col">CATEGORY</th> <th id="ship" scope="col">PER SHIPMENT</th> <th id="pounds" scope="col">+ PER POUND</th> </tr> <tr> <td headers="price cat" scope="row">Baby</td> <td headers="price ship">$4.50</td> <td headers="price pounds">$0.40 per lb</td>
</tr> <tr>
</tr> <tr>
<td headers="price cat" scope="row">Bath & Bedding</td> <td headers="price ship">$2.99</td> <td headers="price pounds">$0.59 per lb</td>
<td headers="price cat" scope="row">Books & VHS Videos</td> <td headers="price ship">$3.00</td> <td headers="price pounds">$0.99 per lb</td> </tr> </table>
The linear order of this table is: 1. Page Header 2. Link 3. Link 4. Link 5. Link 6. Link 7. Link 8. Link 9. Main Content 10. Page Footer
Logically order form elements so guests are able to navigate through forms using only the keyboard. Guidelines: 1. Use form labels properly and/or keep descriptive text next to the form field. Techniques for doing this include wrapping each form label with a label tag and associating it to its respective form field using the ID attribute. Group related form fields by using the fieldset element (see section 1.4.1.2 Grouping Complex Forms ).
T T TTT
Example:
<label for="firstname">First Name</label> <input type="text" name="firstname" id="firstname" tabindex="1">
2. Follow guidelines in section 1.3.2 Keyboard Access to assure that guests can tab to
T T
appropriate fields and navigate using arrow keys. 3. Mouseover text should not be used to provide instructions in the form unless there is a keyboard-accessible equivalent. 4. If only one option is displayed when using radio buttons, the available radio button should be selected by default.
5. Provide a non-Flash equivalent for all Flash forms. 6. Where CAPTCHA (Completely Automated Public Turing Test to Tell Computers
and Humans Apart) is used to validate form entries, provide a non-graphic equivalent, such as an audio alternative. Example:
Example: One field per label This label provides accurate information to all users
<fieldset> <legend>Contact Information</legend> <label for="firstName">First Name:</label> <input size="30" maxlength="100" value="" id="firstName" name="firstName"> </fieldset> <fieldset> <legend>Order Information</legend> <label for="subject"><b class="small">Subject:</b></label> <select id="subject" name="subject"> <option value="Please Select">Please Select</option>... </fieldset>
2. Development
Target is committed to the development of web page content that can be fully experienced by all guests. The following technical guidelines should be applied in the development of Target web pages.
Example: Alt attributes to convey information The bulls eye logo on the home page is described as Target, not picture of bulls eye.
Example: Alt attributes to convey information The search button is labeled Search Submit, not red rectangle with the word Go in it.
Areas of an image map Each area of an image map should have its own alt attribute, in addition to the alt attribute for the image map as a whole. Example: Alt attributes for areas of an image map
Structural and decorative images The alt attribute for structural and decorative images should be blank (null); preventing assistive technologies from reading the file name or other irrelevant information. A blank or null alt attribute is coded as alt= (two quotation marks with no text and no spaces in between.) Example: Null alt attributes for decorative images
<img src=images/pumpkin.gif width=139 height=110 alt=> Example: Null alt attributes for spacer images Use the null alt attribute for structural, transparent, or spacer images. These will not be visible on the screen and will be ignored by most assistive technologies.
Example: Null alt attribute for redundant images Use the null alt attribute rather than repeating the same alt attribute for multiple images in the same area to prevent repeating redundant alt text.
<img src=images/redcard_header.gif width=146 height=35 alt=The REDcards><br><img src=images/redcards.gif width=146 height=44 alt=><br><a href=http://target.com/redcards>Apply for a card</a>
Background images Background images should not contain text or other information, as assistive technologies would likely not render these images (see section 1.3.1 Structural Elements and Order ).
T T
Title attributes can be added to images and form input fields as well as text links. Example: Coded title attributes
<a href="http://target.com/targethouse" title="Learn more about Target House">Target House</a>
2.3.2 AJAX
When using AJAX techniques, strive to create a consistent screen reader experience by avoiding situations where content is overwritten or refreshed without first alerting the guest. Guidelines: 1. Never rewrite content in a region of a page that has already loaded, without alerting the guest that such an event has occurred, and providing a clear means for the guest to retrieve that content. 2. When using a JSON or XML data source to populate a page, be sure to populate the content during the load time of the page. Never repopulate a portion of the page with new content without an alert (see above). 3. If an AJAX-powered experience must rely upon portions of the page being repopulated without a page reload, provide an alternate means to guests to retrieve the same content without AJAX.
2.5 Framesets
Use appropriate frame titles when implementing framesets. Most screen readers identify frames by speaking the name and/or page title of each frame. To navigate through the site, users require an understandable name for each frame indicating the frames function.
2. HTML Frame Title Attribute The <frame> tag includes a title attribute, and it should be a one-word descriptor.
<frame src="frame_nav.htm" name="navigation" scrolling="auto" noresize title="navigation">
3. Web Page Title Tag All HTML files carry a <title> tag as part of page identification. Properly identify all web pages using the <title> tag.
<title>Site Navigation</title>
Glossary
Assistive Technology (AT)
Technology which allows persons with disabilities to perform web functions with little to no difficulty. Examples of assistive technology related to computers and IT include keyboards with large keys for persons with mobility impairments and software that reads aloud text on a document or website for persons with vision impairments.
Accessible Design
To intentionally create products - including websites - for use by people with a wide range of capabilities, either through direct access or with assistive technology. Accessible design is required for Assistive Technology to work.
Accessibility
The process in which a website is made usable by people with a wide range of physical, visual, and cognitive abilities.
Alt Attribute
Language added to images, image map areas, and graphics within the HTML code that communicates the same information as the images. (Alt Attributes are sometimes incorrectly referred to as Alt Tags and/or Alt Text.)
Alt Tag
HTML code that contains the alt attribute (see Alt Attribute).
Alt Text
The descriptive language that is served by the alt tag (see Alt Tag).
Braille Devices
Assistive Technology that renders website text as raised dots that can be read by visually impaired guests.
Cognitive Impairment
A problem with the ability to think about, concentrate on, or remember information or ideas.
Data table
A matrix used for displaying tabular or numeric content (see Layout Table).
Device Dependent
An experience that can only be accessed by means of a particular device, such as a mouse or keyboard. These experiences are not accessible to assistive technologies that do not use those devices (e.g. mousedependent experiences cannot be accessed with the keyboard).
Device Independent
An experience can be accessed by more than one device (e.g. both mouse and keyboard).
Flash
Technology used to add interaction or animation to a web site.
Focus
An interaction whereby an image, form field, button or otherwise selectable object within a web page is selected by the guest. A JavaScript routine can be executed from a Focus event by using the onFocus event handler within certain HTML tags.
Form
A document containing blank fields; the guest can fill the field with data as appropriate.
Form Field
Blank area within a form; the guest can fill the form with data as appropriate.
Frame
A segment of a browser window which can be scrolled independently of other segments.
Frameset
The element that specifies the layout of the main user window within which independent segments (Frames) reside.
Header Markup
Used to define a pages organizational structure (i.e. <H1>, <H2>, <H3>, etc.). Header markup provides a navigational aid to help guests using assistive technology quickly scan the content of a page.
Hover State
The active highlighted state of an element when the cursor is positioned over it.
JavaScript
A scripting language that can interact with HTML code to create dynamic content.
Layout Table
Use of a hierarchical matrix to create a desired visual display or effect (see Data Table).
Linear Order
Elements of a web page arranged from top to bottom and left to right. Accessible web pages are laid out in linear order (see Screen Reader Order).
Markup Language
A combination of text intermingled with information about the texts structure or presentation. HTML and XML are examples of markup languages.
Noframes
An element in a frameset that provides alternate content for guests who do not use frames.
Null Value
An alt attribute that is coded to remain blank and is used for images which are ornamental or decorative. A screen reader will skip over a null value; the blank value that is placed inside an alt attribute.
Photo-Sensitivity
A condition in which flashing or flickering lights can cause adverse physical reactions.
Presentational Markup
HTML or other markup language used to control the appearance of a page (see Structural Markup).
Screen Readers
Assistive technologies that reproduce text displayed on a computer screen as a synthesized voice or Braille; used by persons who have vision impairments.
Structural Markup
HTML or other Markup Language used to define the logical structure of the page (see Presentational Markup).
Time-Based Response
Interactions must be completed within a set time (e.g. forms or applications that are set to time out in a certain period of time.
Title Attribute
Language added to tags within the HTML code that communicates the same information as the tagged content.
Title Tag
The element that defines the title of a web page document.
Exemption Form
PROJECT INFORMATION Date: Project Name: Project Manager: Business Owner: Project Launch Date: Description: Guideline Exemption Information Request Date: Impacted Area of the site: (Select all that apply) Home Page and Global Navigation Search Checkout Forms My Accounts & Pages Using/Storing/Displaying Personal Information (not including Checkout) Online Return Center Registries Store Locator Weekly Ad Shopping Pages Corporate Information Site SuperTarget Target Commercial Interiors Other (specify)
Approval Information
Date Received: Date Reviewed: Questions/Clarification Needed: Dated returned for questions: Date all information received: