Appendix B - Examples and Specifications

Introduction

This section of the guidelines contains examples to support various sections in the rest of the guidelines document. This section is intended to provide a more detailed look at the designs outlined in the guidelines and to provide developers and UI designers with a head start on creating guidelines-compliant HTML-based prototypes.

Sample HTML Sections
Component		Section in Guidelines
Add-and-Remove Idiom	Specification \| Example	8.2
Breadcrumb/Parentage Path	Specification \| Example not yet available	6.3
Buttons	Specification \| Example	7.1
Common Tasks Page	Specification \| Example	5.5
Popup Calendar	Specification \| Example	8.4.1
Date/Time Element (Scheduler)	Specification \| Example not yet available	8.4.2
Editable Scrolling List	Specification \| Example	8.1
File/Folder Chooser	Specification \| Example	8.5.2
Form Elements	Specification \| Checkbox/Radio Button Example DropDown and ListBox Example Text Input Example	7.2 & 7.3
Full-Page Alert Messages	Specification \| Example	14.3
Help Window	Specification \| Example not yet available	11.2
HREFS	Specification \| Example	--
Inline Alert Messages	Specification \| Example	14.1
Inline Help	Specification \| Example not yet available	11.1
Label	Specification \| Example	7.3.1 & 14.5
Masthead	Specification \| Example	4
Page Title	Specification \| Example	6.2
Progress Indicators	Specification \| Example	15
Properties Page	Specification \| Example	6
Skip Navigation Links	Specification	--
Spacer	Specification	--
Tables	Specification \| Example	9
Tabs	Specification \| Example not yet available	5.2
Tree	Specification \| Example	5.4
Version Page	Specification \| Example not yet available	18
Wizard	Specification \| Example not yet available	13

Accessibility

The sample HTML also contains hooks and examples for meeting the section 508 accessibility guidelines, which are discussed in Appendix D, Accessibility Requirements of the guidelines. Additions in this version of the sample HTML include examples for skipping repetitive navigation links, associating labels with form elements, properly marking up data tables for accessibility, and use of alt and title attributes to mark up contents for users of assistive technologies.

Section 508 compliance is not guaranteed or complete, however, as there is still some ambiguity surrounding the best way to handle some of the scripting and other aspects of the HTML. This ambiguity is only going to be resolved via testing with assistive technologies.