Techniques for Web Content Accessibility Guidelines 1.0
`
`Techniques for Web Content Accessibility
`Guidelines 1.0
`
`W3C Note 6 November 2000
`
`This version:
`http://www.w3.org/TR/2000/NOTE-WCAG10-TECHS-20001106/
`(plain text, PostScript, PDF, gzip tar file of HTML, zip archive of HTML)
`Latest version:
`http://www.w3.org/TR/WCAG10-TECHS/
`Previous version:
`http://www.w3.org/TR/2000/NOTE-WCAG10-TECHS-20000920/
`Editors:
`Wendy Chisholm, W3C;
`Gregg Vanderheiden, Trace R & D Center, University of Wisconsin -- Madison;
`Ian Jacobs, W3C
`
`Copyright ©1999 - 2000 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C
`liability, trademark, document use and software licensing rules apply.
`
`Abstract
`This document is the gateway to a series of related documents that provide
`techniques for satisfying the requirements defined in "Web Content Accessibility
`Guidelines 1.0" [WCAG10] [p. 22] . This series includes:
`
`1. "Techniques for Web Content Accessibility Guidelines 1.0", the current
`document, which is the gateway to the other documents.
`2. "Core Techniques for Web Content Accessibility Guidelines 1.0"
`([WCAG10-CORE-TECHNIQUES] [p. 22] ), which discusses the accessibility
`themes and general techniques that apply across technologies (e.g., validation,
`testing, etc.).
`3. "HTML Techniques for Web Content Accessibility Guidelines 1.0"
`([WCAG10-HTML-TECHNIQUES] [p. 22] ), which provides examples and
`strategies for authoring accessible Hypertext Markup Language (HTML)
`content.
`4. "CSS Techniques for Web Content Accessibility Guidelines 1.0"
`([WCAG10-CSS-TECHNIQUES] [p. 22] ), which provides examples and
`strategies to help authors write Cascading Style Sheets (CSS) as part of
`accessible content design.
`
`1
`
`
`
` 6 Nov 2000 12:33
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 1 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`Status of this document
`This version has been published to correct some broken links in the previous
`version.
`The 6 November 2000 version of this document is a Note in a series of Notes
`produced and endorsed by the Web Content Accessibility Guidelines Working
`Group. This Note has not been reviewed or endorsed by W3C Members. The series
`of documents supersedes the 5 May 1999 W3C Note "Techniques for Web Content
`Accessibility Guidelines 1.0". That single document has been divided into
`technology-specific documents that may evolve independently. Smaller
`technology-specific documents also allow authors to focus on a particular
`technology.
`While the "Web Content Accessibility Guidelines 1.0" Recommendation
`[WCAG10] [p. 22] is a stable document, this series of companion documents is
`expected to evolve as technologies change and content developers discover more
`effective techniques for designing accessible Web sites and pages. In the near
`future, the Working Group intends to incorporate techniques for the Synchronized
`Multimedia Integration Language (SMIL) [SMIL] [p. 21] described in "Accessibility
`Features of SMIL" ([SMIL-ACCESS] [p. 21] ) and techniques for Scalable Vector
`Graphics (SVG) [SVG] [p. 21] described in "Accessibility Features of SVG"
`([SVG-ACCESS] [p. 21] ). The Working Group also intends to incorporate techniques
`for non-W3C technologies such as ECMAScript, PDF and Flash.
`The history of changes to the series of documents as well as the list of open and
`closed issues are available. Readers are encouraged to comment on the document
`and propose resolutions to current issues. Please send detailed comments on this
`document to the Working Group at w3c-wai-gl@w3.org; public archives are
`available.
`The English version of this document is the only normative version. However, for
`translations in other languages see
`"http://www.w3.org/WAI/GL/WAI-WEBCONTENT-TRANSLATIONS".
`The list of known errors in this document is available at "Errata in Web Content
`Accessibility Guidelines." Please report errors in this document to
`wai-wcag-editor@w3.org.
`The Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C)
`makes available a variety of resources on Web accessibility. WAI Accessibility
`Guidelines are produced as part of the WAI Technical Activity. The goals of the
`WCAG WG are described in the charter.
`A list of current W3C Recommendations and other technical documents is
`available.
`
` 6 Nov 2000 12:33
`
`
`
`2
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 2 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`Table of Contents
`
`Abstract
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`Status of this document
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`1 How this Document is Organized
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`1.1 Priorities
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`2 Techniques for Web Content Accessibility Guidelines
`.
`.
`.
`.
`.
`1. Provide equivalent alternatives to auditory and visual content.
`.
`.
`2. Don’t rely on color alone.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`3. Use markup and style sheets and do so properly.
`.
`.
`.
`.
`.
`4. Clarify natural language usage
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`5. Create tables that transform gracefully.
`.
`.
`6. Ensure that pages featuring new technologies transform gracefully.
`7. Ensure user control of time-sensitive content changes.
`.
`.
`.
`.
`.
`.
`8. Ensure direct accessibility of embedded user interfaces.
`.
`.
`.
`9. Design for device-independence.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`10. Use interim solutions.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`11. Use W3C technologies and guidelines.
`.
`.
`.
`.
`.
`.
`12. Provide context and orientation information.
`.
`.
`.
`.
`.
`.
`13. Provide clear navigation mechanisms.
`.
`.
`.
`.
`.
`.
`.
`14. Ensure that documents are clear and simple.
`.
`.
`.
`.
`.
`.
`3 Glossary
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`4 References
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`5 Resources
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`5.1 Other Guidelines
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`5.2 User agents and other tools
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`6 Acknowledgments
`.
`.
`.
`.
`
`.1
`
`
`.2
`
`.4
`
`.4
`
`.6
`
`.6
`
`.7
`
`.7
`
`.8
`
`.8
`.9
`
`.10
`
`.11
`
`.11
`
`.12
`
`.12
`
`.13
`
`.13
`
`.14
`
`.15
`
`.21
`
`.22
`
`.22
`
`.22
`
`.23
`
`3
`
`
`
` 6 Nov 2000 12:33
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 3 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`1 How this Document is Organized
`Section 2 of this document reproduces the guidelines and checkpoints of the "Web
`Content Accessibility Guidelines 1.0" [WCAG10] [p. 22] . Each guideline includes:
`
`The guideline number.
`The statement of the guideline.
`A list of checkpoint definitions. Checkpoints are ordered according to their
`priority [p. 4] , e.g., Priority 1 before Priority 2.
`
`Each checkpoint definition includes:
`
`The checkpoint number.
`The statement of the checkpoint.
`The priority of the checkpoint.
`A link back to the definition of the checkpoint in "Web Content Accessibility
`Guidelines 1.0" [WCAG10] [p. 22] . Definitions may also include informative
`notes, examples, cross references, and commentary to help readers understand
`the scope of the checkpoint.
`
`Each checkpoint is followed by one or more links to techniques in the following
`documents:
`
`"Core Techniques for Web Content Accessibility Guidelines 1.0"
`([WCAG10-CORE-TECHNIQUES] [p. 22] ), which discusses the accessibility
`themes and general techniques that apply across technologies.
`"HTML Techniques for Web Content Accessibility Guidelines 1.0"
`([WCAG10-HTML-TECHNIQUES] [p. 22] ), which provides examples and
`strategies for authoring accessible Hypertext Markup Language (HTML)
`content.
`"CSS Techniques for Web Content Accessibility Guidelines 1.0"
`([WCAG10-CSS-TECHNIQUES] [p. 22] ), which provides examples and
`strategies to help authors write Cascading Style Sheets (CSS) as part of
`accessible content design.
`
`1.1 Priorities
`Each checkpoint has a priority level assigned by the Working Group based on the
`checkpoint’s impact on accessibility.
`
`[Priority 1]
`A Web content developer must satisfy this checkpoint. Otherwise, one or more
`groups will find it impossible to access information in the document. Satisfying
`this checkpoint is a basic requirement for some groups to be able to use Web
`documents.
`
` 6 Nov 2000 12:33
`
`
`
`4
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 4 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`[Priority 2]
`A Web content developer should satisfy this checkpoint. Otherwise, one or
`more groups will find it difficult to access information in the document. Satisfying
`this checkpoint will remove significant barriers to accessing Web documents.
`[Priority 3]
`A Web content developer may address this checkpoint. Otherwise, one or more
`groups will find it somewhat difficult to access information in the document.
`Satisfying this checkpoint will improve access to Web documents.
`
`Some checkpoints specify a priority level that may change under certain
`(indicated) conditions.
`
`5
`
`
`
` 6 Nov 2000 12:33
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 5 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`2 Techniques for Web Content Accessibility Guidelines
`
`Guideline 1. Provide equivalent alternatives to auditory and
`visual content.
`Checkpoints:
`
`1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or
`in element content). This includes: images, graphical representations of text
`(including symbols), image map regions, animations (e.g., animated GIFs), applets
`and programmatic objects, ASCII art, frames, scripts, images used as list bullets,
`spacers, graphical buttons, sounds (played with or without user interaction),
`stand-alone audio files, audio tracks of video, and video. [Priority 1] (Checkpoint 1.1)
`Core Techniques: Text equivalents
`HTML Techniques: Images used as bullets
`HTML Techniques: Text for images used as links
`HTML Techniques: Short text equivalents for images ("alt-text")
`HTML Techniques: Long descriptions of images
`HTML Techniques: Text equivalents for client-side image maps
`HTML Techniques: Text and non-text equivalents for applets and
`programmatic objects
`HTML Techniques: Text equivalents for multimedia
`HTML Techniques: Describing frame relationships
`HTML Techniques: Writing for browsers that do not support FRAME
`HTML Techniques: Graphical buttons
`HTML Techniques: Alternative presentation of scripts
`1.2 Provide redundant text links for each active region of a server-side image map.
`[Priority 1] (Checkpoint 1.2)
`Refer also to checkpoint 1.5 and checkpoint 9.1.
`Core Techniques: Text equivalents
`HTML Techniques: Server-side image maps
`1.3 Until user agents [p. 20] can automatically read aloud the text equivalent of a
`visual track, provide an auditory description of the important information of the visual
`track of a multimedia presentation. [Priority 1] (Checkpoint 1.3)
`Core Techniques: Visual information and motion
`1.4 For any time-based multimedia presentation (e.g., a movie or animation),
`synchronize equivalent alternatives (e.g., captions or auditory descriptions of the
`visual track) with the presentation. [Priority 1] (Checkpoint 1.4)
`Core Techniques: Audio information
`HTML Techniques: Directly accessible applets
`1.5 Until user agents [p. 20] render text equivalents for client-side image map links,
`provide redundant text links for each active region of a client-side image map.
`[Priority 3] (Checkpoint 1.5)
`Refer also to checkpoint 1.2 and checkpoint 9.1.
`Core Techniques: Text equivalents
`
` 6 Nov 2000 12:33
`
`
`
`6
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 6 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`HTML Techniques: Redundant text links for client-side image maps
`
`Guideline 2. Don’t rely on color alone.
`Checkpoints:
`
`2.1 Ensure that all information conveyed with color is also available without color, for
`example from context or markup. [Priority 1] (Checkpoint 2.1)
`Core Techniques: Structure vs. Presentation
`CSS Techniques: Ensuring information is not in color alone
`2.2 Ensure that foreground and background color combinations provide sufficient
`contrast when viewed by someone having color deficits or when viewed on a black
`and white screen. [Priority 2 for images, Priority 3 for text]. (Checkpoint 2.2)
`HTML Techniques: Color in images
`CSS Techniques: Color Contrast
`
`Guideline 3. Use markup and style sheets and do so properly.
`Checkpoints:
`
`3.1 When an appropriate markup language exists, use markup rather than images to
`convey information. [Priority 2] (Checkpoint 3.1)
`Core Techniques: Structure vs. Presentation
`HTML Techniques: Markup and style sheets rather than images: The
`example of math
`CSS Techniques: Generated content
`3.2 Create documents that validate to published formal grammars. [Priority 2]
`(Checkpoint 3.2)
`HTML Techniques: The !DOCTYPE statement
`3.3 Use style sheets to control layout and presentation. [Priority 2] (Checkpoint 3.3)
`Core Techniques: Structure vs. Presentation
`HTML Techniques: Emphasis
`CSS Techniques: Text instead of images
`CSS Techniques: Text formatting and position
`CSS Techniques: Layout, positioning, layering, and alignment
`3.4 Use relative rather than absolute units in markup language attribute values and
`style sheet property values. [Priority 2] (Checkpoint 3.4)
`HTML Techniques: Directly accessible applets
`HTML Techniques: Sizing frames with relative units
`CSS Techniques: Units of measure
`3.5 Use header elements to convey document structure and use them according to
`specification. [Priority 2] (Checkpoint 3.5)
`Core Techniques: Structure vs. Presentation
`HTML Techniques: Section headings
`
`7
`
`
`
` 6 Nov 2000 12:33
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 7 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`3.6 Mark up lists and list items properly. [Priority 2] (Checkpoint 3.6)
`Core Techniques: Structure vs. Presentation
`HTML Techniques: Lists
`CSS Techniques: Providing contextual clues in HTML lists
`3.7 Mark up quotations. Do not use quotation markup for formatting effects such as
`indentation. [Priority 2] (Checkpoint 3.7)
`HTML Techniques: Quotations
`
`Guideline 4. Clarify natural language usage
`Checkpoints:
`
`4.1 Clearly identify changes in the natural language of a document’s text and any
`text equivalents [p. 17] (e.g., captions). [Priority 1] (Checkpoint 4.1)
`HTML Techniques: Identifying changes in language
`4.2 Specify the expansion of each abbreviation or acronym in a document where it
`first occurs. [Priority 3] (Checkpoint 4.2)
`HTML Techniques: Acronyms and abbreviations
`4.3 Identify the primary natural language of a document. [Priority 3] (Checkpoint 4.3)
`HTML Techniques: Identifying the primary language
`
`Guideline 5. Create tables that transform gracefully.
`Checkpoints:
`
`5.1 For data tables, identify row and column headers. [Priority 1] (Checkpoint 5.1)
`HTML Techniques: Identifying rows and column information
`5.2 For data tables that have two or more logical levels of row or column headers,
`use markup to associate data cells and header cells. [Priority 1] (Checkpoint 5.2)
`HTML Techniques: Identifying rows and column information
`5.3 Do not use tables for layout unless the table makes sense when linearized.
`Otherwise, if the table does not make sense, provide an alternative equivalent
`(which may be a linearized version [p. 18] ). [Priority 2] (Checkpoint 5.3)
`Core Techniques: Structure vs. Presentation
`HTML Techniques: Tables for layout
`CSS Techniques: Layout, positioning, layering, and alignment
`5.4 If a table is used for layout, do not use any structural markup for the purpose of
`visual formatting. [Priority 2] (Checkpoint 5.4)
`Core Techniques: Structure vs. Presentation
`HTML Techniques: Tables for layout
`5.5 Provide summaries for tables. [Priority 3] (Checkpoint 5.5)
`HTML Techniques: Providing summary information
`5.6 Provide abbreviations for header labels. [Priority 3] (Checkpoint 5.6)
`HTML Techniques: Providing summary information
`
` 6 Nov 2000 12:33
`
`
`
`8
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 8 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`Refer also to checkpoint 10.3.
`
`Guideline 6. Ensure that pages featuring new technologies
`transform gracefully.
`Checkpoints:
`
`6.1 Organize documents so they may be read without style sheets. For example,
`when an HTML document is rendered without associated style sheets, it must still be
`possible to read the document. [Priority 1] (Checkpoint 6.1)
`CSS Techniques: Generated content
`CSS Techniques: Rules and borders
`CSS Techniques: Using style sheet positioning and markup to transform
`gracefully
`6.2 Ensure that equivalents for dynamic content are updated when the dynamic
`content changes. [Priority 1] (Checkpoint 6.2)
`HTML Techniques: Text and non-text equivalents for applets and
`programmatic objects
`HTML Techniques: Frame sources
`HTML Techniques: Alternative presentation of scripts
`6.3 Ensure that pages are usable when scripts, applets, or other programmatic
`objects are turned off or not supported. If this is not possible, provide equivalent
`information on an alternative accessible page. [Priority 1] (Checkpoint 6.3)
`HTML Techniques: Text and non-text equivalents for applets and
`programmatic objects
`HTML Techniques: Directly accessible scripts
`6.4 For scripts and applets, ensure that event handlers are input
`device-independent. [Priority 2] (Checkpoint 6.4)
`Core Techniques: Structure vs. Presentation
`HTML Techniques: Directly accessible applets
`HTML Techniques: Directly accessible scripts
`6.5 Ensure that dynamic content is accessible or provide an alternative presentation
`or page. [Priority 2] (Checkpoint 6.5)
`Core Techniques: Alternative pages
`Core Techniques: Audio information
`HTML Techniques: The LINK element and alternative documents
`HTML Techniques: Directly accessible applets
`HTML Techniques: Writing for browsers that do not support FRAME
`HTML Techniques: Graceful transformation of scripts
`
`Refer also to checkpoint 11.4.
`
`9
`
`
`
` 6 Nov 2000 12:33
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 9 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`Guideline 7. Ensure user control of time-sensitive content
`changes.
`Checkpoints:
`
`7.1 Until user agents [p. 20] allow users to control flickering, avoid causing the
`screen to flicker. [Priority 1] (Checkpoint 7.1)
`Core Techniques: Screen flicker
`Core Techniques: Visual information and motion
`HTML Techniques: Directly accessible applets
`HTML Techniques: Scripts that cause flickering
`7.2 Until user agents [p. 20] allow users to control blinking, avoid causing content to
`blink (i.e., change presentation at a regular rate, such as turning on and off).
`[Priority 2] (Checkpoint 7.2)
`HTML Techniques: Directly accessible applets
`HTML Techniques: Scripts that cause movement and blinking
`CSS Techniques: Text style effects
`7.3 Until user agents [p. 20] allow users to freeze moving content, avoid movement
`in pages. [Priority 2] (Checkpoint 7.3)
`Core Techniques: Visual information and motion
`HTML Techniques: Animated images
`HTML Techniques: Directly accessible applets
`HTML Techniques: Scripts that cause movement and blinking
`CSS Techniques: Creating movement with style sheets and scripts
`7.4 Until user agents [p. 20] provide the ability to stop the refresh, do not create
`periodically auto-refreshing pages. [Priority 2] (Checkpoint 7.4)
`Core Techniques: Automatic page refresh
`HTML Techniques: The META element
`HTML Techniques: Directly accessible applets
`HTML Techniques: Page updates and new windows
`7.5 Until user agents [p. 20] provide the ability to stop auto-redirect, do not use
`markup to redirect pages automatically. Instead, configure the server to perform
`redirects. [Priority 2] (Checkpoint 7.5)
`Core Techniques: Automatic page refresh
`HTML Techniques: The META element
`HTML Techniques: Page updates and new windows
`
`Note. The BLINK and MARQUEE elements are not defined in any W3C HTML
`specification and should not be used. Refer also to guideline 11.
`
` 6 Nov 2000 12:33
`
`
`
`10
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 10 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`Guideline 8. Ensure direct accessibility of embedded user
`interfaces.
`Checkpoint:
`
`8.1 Make programmatic elements such as scripts and applets directly accessible or
`compatible with assistive technologies [Priority 1 if functionality is important [p. 18]
`and not presented elsewhere, otherwise Priority 2.] (Checkpoint 8.1)
`Refer also to guideline 6.
`HTML Techniques: Directly accessible applets
`HTML Techniques: Directly accessible scripts
`
`Guideline 9. Design for device-independence.
`Checkpoints:
`
`9.1 Provide client-side image maps instead of server-side image maps except where
`the regions cannot be defined with an available geometric shape. [Priority 1]
`(Checkpoint 9.1)
`Refer also to checkpoint 1.1, checkpoint 1.2, and checkpoint 1.5.
`HTML Techniques: Client-side versus server-side image maps
`9.2 Ensure that any element that has its own interface can be operated in a
`device-independent manner. [Priority 2] (Checkpoint 9.2)
`Refer to the definition of device independence [p. 16] .
`Refer also to guideline 8.
`Core Techniques: Alternative pages
`HTML Techniques: Directly accessible applets
`9.3 For scripts, specify logical event handlers rather than device-dependent event
`handlers. [Priority 2] (Checkpoint 9.3)
`Core Techniques: Alternative pages
`HTML Techniques: Directly accessible scripts
`9.4 Create a logical tab order through links, form controls, and objects. [Priority 3]
`(Checkpoint 9.4)
`Core Techniques: Alternative pages
`HTML Techniques: Keyboard access
`HTML Techniques: Keyboard access to forms
`9.5 Provide keyboard shortcuts to important links (including those in client-side
`image maps [p. 18] ), form controls, and groups of form controls. [Priority 3]
`(Checkpoint 9.5)
`Core Techniques: Alternative pages
`HTML Techniques: Keyboard access
`HTML Techniques: Keyboard access to forms
`
`11
`
`
`
` 6 Nov 2000 12:33
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 11 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`Guideline 10. Use interim solutions.
`Checkpoints:
`
`10.1 Until user agents [p. 20] allow users to turn off spawned windows, do not cause
`pop-ups or other windows to appear and do not change the current window without
`informing the user. [Priority 2] (Checkpoint 10.1)
`HTML Techniques: Anchors and targets
`HTML Techniques: Directly accessible applets
`HTML Techniques: Using FRAME targets
`HTML Techniques: Page updates and new windows
`10.2 Until user agents [p. 20] support explicit associations between labels and form
`controls, for all form controls with implicitly associated labels, ensure that the label is
`properly positioned. [Priority 2] (Checkpoint 10.2)
`HTML Techniques: Labeling form controls
`10.3 Until user agents [p. 20] (including assistive technologies) render side-by-side
`text correctly, provide a linear text alternative (on the current page or some other) for
`all tables that lay out text in parallel, word-wrapped columns. [Priority 3] (Checkpoint
`10.3)
`
`HTML Techniques: Linearizing tables
`10.4 Until user agents [p. 20] handle empty controls correctly, include default,
`place-holding characters in edit boxes and text areas. [Priority 3] (Checkpoint 10.4)
`HTML Techniques: Techniques for specific controls
`10.5 Until user agents [p. 20] (including assistive technologies) render adjacent links
`distinctly, include non-link, printable characters (surrounded by spaces) between
`adjacent links. [Priority 3] (Checkpoint 10.5)
`HTML Techniques: Grouping and bypassing links
`
`Guideline 11. Use W3C technologies and guidelines.
`Checkpoints:
`
`11.1 Use W3C technologies when they are available and appropriate for a task and
`use the latest versions when supported. [Priority 2] (Checkpoint 11.1)
`Core Techniques: Technologies Reviewed for Accessibility
`11.2 Avoid deprecated features of W3C technologies. [Priority 2] (Checkpoint 11.2)
`HTML Techniques: Index of HTML elements and attributes
`CSS Techniques: User override of styles
`CSS Techniques: Fonts
`11.3 Provide information so that users may receive documents according to their
`preferences (e.g., language, content type, etc.) [Priority 3] (Checkpoint 11.3)
`Note. Use content negotiation where possible.
`Core Techniques: Content negotiation
`CSS Techniques: Aural Cascading Style Sheets
`CSS Techniques: Access to alternative representations of content
`CSS Techniques: Media types
`
` 6 Nov 2000 12:33
`
`
`
`12
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 12 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`11.4 If, after best efforts [p. 13] , you cannot create an accessible [p. 15] page,
`provide a link to an alternative page that uses W3C technologies, is accessible, has
`equivalent [p. 17] information (or functionality), and is updated as often as the
`inaccessible (original) page. [Priority 1] (Checkpoint 11.4)
`Core Techniques: Alternative pages
`
`Note. Content developers should only resort to alternative pages when other
`solutions fail because alternative pages are generally updated less often than
`"primary" pages. An out-of-date page may be as frustrating as one that is
`inaccessible since, in both cases, the information presented on the original page is
`unavailable. Automatically generating alternative pages may lead to more frequent
`updates, but content developers must still be careful to ensure that generated pages
`always make sense, and that users are able to navigate a site by following links on
`primary pages, alternative pages, or both. Before resorting to an alternative page,
`reconsider the design of the original page; making it accessible is likely to improve it
`for all users.
`
`Guideline 12. Provide context and orientation information.
`Checkpoints:
`
`12.1 Title each frame to facilitate frame identification and navigation. [Priority 1]
`(Checkpoint 12.1)
`HTML Techniques: Providing a frame title
`12.2 Describe the purpose of frames and how frames relate to each other if it is not
`obvious by frame titles alone. [Priority 2] (Checkpoint 12.2)
`Core Techniques: Text equivalents
`HTML Techniques: Describing frame relationships
`12.3 Divide large blocks of information into more manageable groups where natural
`and appropriate. [Priority 2] (Checkpoint 12.3)
`HTML Techniques: Structural grouping
`HTML Techniques: Grouping form controls
`12.4 Associate labels explicitly with their controls. [Priority 2] (Checkpoint 12.4)
`HTML Techniques: Labeling form controls
`
`Guideline 13. Provide clear navigation mechanisms.
`Checkpoints:
`
`13.1 Clearly identify the target of each link. [Priority 2] (Checkpoint 13.1)
`HTML Techniques: Link text
`13.2 Provide metadata to add semantic information to pages and sites. [Priority 2]
`(Checkpoint 13.2)
`Core Techniques: Navigation
`HTML Techniques: Metadata
`CSS Techniques: Providing contextual clues in HTML lists
`
`13
`
`
`
` 6 Nov 2000 12:33
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 13 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`13.3 Provide information about the general layout of a site (e.g., a site map or table
`of contents). [Priority 2] (Checkpoint 13.3)
`Core Techniques: Navigation
`13.4 Use navigation mechanisms in a consistent manner. [Priority 2] (Checkpoint
`13.4)
`
`Core Techniques: Navigation
`13.5 Provide navigation bars to highlight and give access to the navigation
`mechanism. [Priority 3] (Checkpoint 13.5)
`Core Techniques: Navigation
`13.6 Group related links, identify the group (for user agents), and, until user agents
`[p. 20] do so, provide a way to bypass the group. [Priority 3] (Checkpoint 13.6)
`HTML Techniques: Grouping and bypassing links
`13.7 If search functions are provided, enable different types of searches for different
`skill levels and preferences. [Priority 3] (Checkpoint 13.7)
`Core Techniques: Navigation
`13.8 Place distinguishing information at the beginning of headings, paragraphs, lists,
`etc. [Priority 3] (Checkpoint 13.8)
`Core Techniques: Comprehension
`13.9 Provide information about document collections (i.e., documents comprising
`multiple pages.). [Priority 3] (Checkpoint 13.9)
`For example, in HTML specify document collections with the LINK element and
`the "rel" and "rev" attributes. Another way to create a collection is by building an
`archive (e.g., with zip, tar and gzip, stuffit, etc.) of the multiple pages.
`Core Techniques: Bundled documents
`HTML Techniques: The LINK element and navigation tools
`13.10 Provide a means to skip over multi-line ASCII art. [Priority 3] (Checkpoint
`13.10)
`
`HTML Techniques: Ascii art
`
`Guideline 14. Ensure that documents are clear and simple.
`Checkpoints:
`
`14.1 Use the clearest and simplest language appropriate for a site’s content.
`[Priority 1] (Checkpoint 14.1)
`Core Techniques: Comprehension
`14.2 Supplement text with graphic or auditory presentations where they will facilitate
`comprehension of the page. [Priority 3] (Checkpoint 14.2)
`Core Techniques: Comprehension
`14.3 Create a style of presentation that is consistent across pages. [Priority 3]
`(Checkpoint 14.3)
`Core Techniques: Navigation
`CSS Techniques: Decrease maintenance and increase consistency
`
` 6 Nov 2000 12:33
`
`
`
`14
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 14 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`3 Glossary
`
`Accessible
`Content is accessible when it may be used by someone with a disability.
`Applet
`A program inserted into a Web page.
`Assistive technology
`Software or hardware that has been specifically designed to assist people with
`disabilities in carrying out daily activities. Assistive technology includes
`wheelchairs, reading machines, devices for grasping, etc. In the area of Web
`Accessibility, common software-based assistive technologies include screen
`readers, screen magnifiers, speech synthesizers, and voice input software that
`operate in conjunction with graphical desktop browsers (among other user
`agents [p. 20] ). Hardware assistive technologies include alternative keyboards
`and pointing devices.
`ASCII art
`ASCII art refers to text characters and symbols that are combined to create an
`image. For example ";-)" is the smiley emoticon. The following is an ASCII figure
`showing the relationship between flash frequency and photoconvulsive
`response in patients with eyes open and closed [skip over ASCII figure [p. 15] or
`consult a description of chart]:
`
`
` % __ __ __ __ __ __ __ __ __ __ __ __ __ __
`100 | * |
` 90 | * * |
` 80 | * * |
` 70 | @ * |
` 60 | @ * |
` 50 | * @ * |
` 40 | @ * |
` 30 | * @ @ @ * |
` 20 | |
` 10 | @ @ @ @ @ |
` 0 5 10 15 20 25 30 35 40 45 50 55 60 65 70
` Flash frequency (Hertz)
`
`Authoring tool
`HTML editors, document conversion tools, tools that generate Web content from
`databases are all authoring tools. Refer to the "Authoring Tool Accessibility
`Guidelines 1.0" ([ATAG10] [p. 21] ) for information about developing accessible
`tools.
`Backward compatible
`Design that continues to work with earlier versions of a language, program, etc.
`Braille
`Braille uses six raised dots in different patterns to represent letters and numbers
`to be read by people who are blind with their fingertips. The word "Accessible" in
`braille follows:
`
`15
`
`
`
` 6 Nov 2000 12:33
`
`ACCESSIBE LTD EXHIBIT 1012
`Page 15 of 23
`
`

`

`Techniques for Web Content Accessibility Guidelines 1.0
`
`A braille display, commonly referred to as a "dynamic braille display," raises or
`lowers dot patterns on command from an electronic device, usually a computer.
`The result is a line of braille that can change from moment to moment. Current
`dynamic braille displays range in size from one cell (six or eight dots) to an
`eighty-cell line, most having between twelve and twenty cells per line.
`Content developer
`Someone who authors Web pages or designs Web sites.
`Deprecated
`A deprecated element or attribute is one that has been outdated by newer
`constructs. Deprecated elements may become obsolete in future versions of
`HTML. The index of HTML elements and attributes in the Techniques Document
`indicates which elements and attributes are deprecated in HTML 4.01.
`Authors should avoid using deprecated elements and attributes. User agents
`should continue to support them for reasons of backward compatibility.
`Device independent
`Users must be able to interact with a user agent (and the document it renders)
`using the supported input and output devices of their choice and according to
`their needs. Input devices may include pointing devices, keyboards, braille
`devices, head wands, microphones, and others. Output devices may include
`monitors, speech synthesizers, and braille devices.
`Please note that "device-independent support" does not mean that user agents
`must support every input or output device. User agents should offer redundant
`input