**Suggested WSB Web Site Best Practices**

Web Solutions Branch

CAO Advanced Business Application Solutions

House Information Resources

Chief Administrative Officer

U.S. House of Representatives

December 1, 2008

+-----------------------------------------------------------------------+
| The current version of this document is available at                  |
| <http://cao.house.gov/web-standards/best-practices.pdf> (in PDF) and  |
| at <http://cao.house.gov/web-standards/best-practices.doc> (in Word   |
| format).                                                              |
|                                                                       |
| If you would like to receive a monthly notice of updates to this      |
| document, please send a request to                                    |
| [[webassista                                                          |
| nce@mail.house.gov]{.underline}](mailto:webassistance@mail.house.gov) |
| to be added to the distribution list.                                 |
+-----------------------------------------------------------------------+

**S****uggested WSB Web Site Best Practices**

(Each of these suggestions was originally raised at a CAO-Web Solutions
Branch (WSB) Peer Review, WSB Skills Seminar, or another WSB-wide forum;
and appeared to represent a consensus of those in attendance. Material
in footnotes may not have been raised at those forums.)[^1]

+-----------------------------------------------------------------------+
| **** indicates sections that primarily deal with text content.       |
|                                                                       |
|  indicates sections that primarily give warnings about text.         |
+-----------------------------------------------------------------------+

[Abbreviations and Acronyms 9](#__RefHeading___Toc216009896)

[ "About" page (or section) 9](#__RefHeading___Toc216009897)

[Academy Nominations 10](#__RefHeading___Toc216009898)

[ Accessibility Policy 11](#__RefHeading___Toc216009899)

[Accesskey attribute 11](#__RefHeading___Toc216009900)

[ Accomplishments 12](#__RefHeading___Toc216009901)

[ActiveX controls 12](#__RefHeading___Toc216009902)

[Acronyms 12](#__RefHeading___Toc216009903)

[\<address\> tags 12](#__RefHeading___Toc216009904)

[Addresses (Postal) 13](#__RefHeading___Toc216009905)

[Alignment 13](#__RefHeading___Toc216009906)

[Ampersands 14](#__RefHeading___Toc216009907)

[\<applet\> tags 14](#__RefHeading___Toc216009908)

["Approved by" Icons 14](#__RefHeading___Toc216009909)

[Apostrophes and Quotation Marks 14](#__RefHeading___Toc216009910)

[Arabic language material 15](#__RefHeading___Toc216009911)

[Archived House Websites 15](#__RefHeading___Toc216009912)

[\<area\> tags 15](#__RefHeading___Toc216009913)

[Armed Forces 15](#__RefHeading___Toc216009914)

[Armenian language material 15](#__RefHeading___Toc216009915)

[ Articles and Op-Eds 15](#__RefHeading___Toc216009916)

[ Artistic Discovery Contest 16](#__RefHeading___Toc216009917)

[Attributes 16](#__RefHeading___Toc216009918)

[Audio files 17](#__RefHeading___Toc216009919)

[Aural Style Sheets 17](#__RefHeading___Toc216009920)

[Babel Fish 17](#__RefHeading___Toc216009921)

[Backgrounds 18](#__RefHeading___Toc216009922)

[Banners 20](#__RefHeading___Toc216009923)

[\<base\> tags 22](#__RefHeading___Toc216009924)

[\<basefont\> tags 22](#__RefHeading___Toc216009925)

[ Biographies 22](#__RefHeading___Toc216009926)

[\<blockquote\> tags 24](#__RefHeading___Toc216009927)

[Blogs 24](#__RefHeading___Toc216009928)

[\<body\> tags 25](#__RefHeading___Toc216009929)

[Bolding 25](#__RefHeading___Toc216009930)

[\<br\> tags 26](#__RefHeading___Toc216009931)

[ Browsealoud 26](#__RefHeading___Toc216009932)

[Browser compatibility 27](#__RefHeading___Toc216009933)

[ Business Assistance 29](#__RefHeading___Toc216009934)

[Cambodian language material 30](#__RefHeading___Toc216009935)

[Campaign material 30](#__RefHeading___Toc216009936)

[Capital letters 30](#__RefHeading___Toc216009937)

[Capitol tours 30](#__RefHeading___Toc216009938)

[CAPTCHA 30](#__RefHeading___Toc216009939)

[\<caption\> tags 31](#__RefHeading___Toc216009940)

[Casework 31](#__RefHeading___Toc216009941)

[Caucuses 31](#__RefHeading___Toc216009942)

[Census data 31](#__RefHeading___Toc216009943)

[Centering 31](#__RefHeading___Toc216009944)

[Certification Icons 32](#__RefHeading___Toc216009945)

[Character Entities 32](#__RefHeading___Toc216009946)

[Charts and Graphs 32](#__RefHeading___Toc216009947)

[Children 32](#__RefHeading___Toc216009948)

[Chinese language material 32](#__RefHeading___Toc216009949)

[Classes 32](#__RefHeading___Toc216009950)

[\<col\> tags 33](#__RefHeading___Toc216009951)

[Colors 33](#__RefHeading___Toc216009952)

[Comments 33](#__RefHeading___Toc216009953)

[**** Commercial references 34](#__RefHeading___Toc216009954)

[ Committee assignments and Caucus memberships
34](#__RefHeading___Toc216009955)

[ Committee Websites 35](#__RefHeading___Toc216009956)

[Communication 36](#__RefHeading___Toc216009957)

[ Compliance Icons 36](#__RefHeading___Toc216009958)

[Conformance Icons 36](#__RefHeading___Toc216009959)

[Congressional Art Competition 36](#__RefHeading___Toc216009960)

[Congressional Page Program 36](#__RefHeading___Toc216009961)

[Congressional Record 36](#__RefHeading___Toc216009962)

[Congressional Research Service products
36](#__RefHeading___Toc216009963)

[ Constituent Recognitions 36](#__RefHeading___Toc216009964)

[ Constituent Services 37](#__RefHeading___Toc216009965)

[ Consumer Protection Information 39](#__RefHeading___Toc216009966)

[ Contact Information and Techniques 39](#__RefHeading___Toc216009967)

[Contrast 45](#__RefHeading___Toc216009968)

[Cookies 45](#__RefHeading___Toc216009969)

[COPPA 45](#__RefHeading___Toc216009970)

[**** Copyrighted material 45](#copyrighted-material)

[Corners 46](#__RefHeading___Toc216009972)

[Courts 46](#__RefHeading___Toc216009973)

[**** Dates, Time, and Timeliness 46](#__RefHeading___Toc216009974)

[Demographics 47](#__RefHeading___Toc216009975)

[ Digital Television Information 47](#__RefHeading___Toc216009976)

[\<dir\> tags 47](#__RefHeading___Toc216009977)

[ Disaster Preparation Information 47](#__RefHeading___Toc216009978)

[ District Information 48](#__RefHeading___Toc216009979)

[\<!DOCTYPE\> declarations 50](#__RefHeading___Toc216009980)

[Download time 51](#__RefHeading___Toc216009981)

[Dutch (Flemish) language material 51](#__RefHeading___Toc216009982)

[ Earmarks 51](#__RefHeading___Toc216009983)

[Earthquake Preparation Information 51](#__RefHeading___Toc216009984)

[Election Campaign material 52](#__RefHeading___Toc216009985)

[Elements 52](#__RefHeading___Toc216009986)

[Ellipsis 52](#__RefHeading___Toc216009987)

[E-mail addresses 52](#__RefHeading___Toc216009988)

[E-mail a friend 52](#__RefHeading___Toc216009989)

[\<embed\> tags 52](#__RefHeading___Toc216009990)

[Employment Opportunities 53](#__RefHeading___Toc216009991)

[E-Newsletters 53](#__RefHeading___Toc216009992)

[Event Handlers 53](#__RefHeading___Toc216009993)

[Events Schedule 55](#__RefHeading___Toc216009994)

[Farsi language material 55](#__RefHeading___Toc216009995)

[Favicons 55](#__RefHeading___Toc216009996)

[Fax Numbers 55](#__RefHeading___Toc216009997)

[**** Federal Bureau of Investigation tours
55](#__RefHeading___Toc216009998)

[Federal Government 55](#__RefHeading___Toc216009999)

[File Names and Extensions 55](#__RefHeading___Toc216010000)

[ FirstGov 56](#__RefHeading___Toc216010001)

[ Flags 56](#__RefHeading___Toc216010002)

[ Floor Statements 57](#__RefHeading___Toc216010003)

[Fonts 57](#__RefHeading___Toc216010004)

[Foreign Languages 58](#__RefHeading___Toc216010005)

[Forms 58](#__RefHeading___Toc216010006)

[Frames and Iframes 65](#__RefHeading___Toc216010007)

[French language material 66](#__RefHeading___Toc216010008)

[ Frequently Asked Questions 66](#__RefHeading___Toc216010009)

[German language material 67](#__RefHeading___Toc216010010)

[ Government Resources 67](#__RefHeading___Toc216010011)

[Grammar 67](#__RefHeading___Toc216010012)

[ Grants and Federal Domestic Assistance
67](#__RefHeading___Toc216010013)

[Graphics 68](#__RefHeading___Toc216010014)

[Graphs 72](#__RefHeading___Toc216010015)

[Greek language material 72](#__RefHeading___Toc216010016)

[ Greetings 72](#__RefHeading___Toc216010017)

[Haitian-Creole language material 74](#__RefHeading___Toc216010018)

[Hawaiian language material 74](#__RefHeading___Toc216010019)

[hCard 74](#__RefHeading___Toc216010020)

[Headings 74](#__RefHeading___Toc216010021)

[Hebrew language material 75](#__RefHeading___Toc216010022)

[Hindi language material 75](#__RefHeading___Toc216010023)

[Hmong language material 75](#__RefHeading___Toc216010024)

[Homeland Security threat index 75](#__RefHeading___Toc216010025)

[ Homepage 75](#__RefHeading___Toc216010026)

[Honorifics 76](#__RefHeading___Toc216010027)

[HOUSE.GOV Domain 76](#__RefHeading___Toc216010028)

[\<hr\> tags 76](#__RefHeading___Toc216010029)

[HTML 77](#__RefHeading___Toc216010030)

[Hurricane Preparation Information 78](#__RefHeading___Toc216010031)

[Hyphenation 78](#__RefHeading___Toc216010032)

[Ice Storm Preparation Information 78](#__RefHeading___Toc216010033)

[Icons 78](#__RefHeading___Toc216010034)

[Id attribute 78](#__RefHeading___Toc216010035)

[ Identity Theft Information 78](#__RefHeading___Toc216010036)

[Iframes 79](#__RefHeading___Toc216010037)

[Image Maps 79](#__RefHeading___Toc216010038)

[Images 80](#__RefHeading___Toc216010039)

[**** Immigration 80](#immigration)

[\<input\> tags 81](#OLE_LINK4)

[ Internships 81](#__RefHeading___Toc216010042)

[ Issues and Voting Information 81](#__RefHeading___Toc216010043)

[Italian language material 85](#__RefHeading___Toc216010044)

[Italics 85](#__RefHeading___Toc216010045)

[Japanese language material 85](#__RefHeading___Toc216010046)

[**** Jargon 85](#__RefHeading___Toc216010047)

[JavaScript 85](#__RefHeading___Toc216010048)

[ Job Opportunities 85](#__RefHeading___Toc216010049)

[Judicial Branch 86](#__RefHeading___Toc216010050)

[ Kids' pages 86](#__RefHeading___Toc216010051)

[Korean language material 88](#__RefHeading___Toc216010052)

[\<label\> tags 88](#__RefHeading___Toc216010053)

[Language of Text 88](#__RefHeading___Toc216010054)

[Lao language material 89](#__RefHeading___Toc216010055)

[Law references 89](#__RefHeading___Toc216010056)

[Layout 89](#__RefHeading___Toc216010057)

[Legal citations 91](#__RefHeading___Toc216010058)

[\<legend\> tags 91](#__RefHeading___Toc216010059)

[ Legislative Material 91](#__RefHeading___Toc216010060)

[Library of Congress products 95](#__RefHeading___Toc216010061)

[Linking 95](#__RefHeading___Toc216010062)

[\<listing\> tags 101](#__RefHeading___Toc216010063)

[Lists 101](#__RefHeading___Toc216010064)

[ Listserv and E-Newsletters 102](#__RefHeading___Toc216010065)

[Load time 103](#__RefHeading___Toc216010066)

[Lorem Ipsum 103](#__RefHeading___Toc216010067)

[\<map\> tags 103](#__RefHeading___Toc216010068)

[ Maps and Directions 103](#__RefHeading___Toc216010069)

[Margins and Padding 104](#__RefHeading___Toc216010070)

[Mastheads 105](#__RefHeading___Toc216010071)

[Meeting with Member 105](#__RefHeading___Toc216010072)

[\<menu\> tags 105](#__RefHeading___Toc216010073)

[\<meta\> tags and \<link\> tags 105](#__RefHeading___Toc216010074)

[ Military (Active Duty, Reserves, and National Guard)
105](#__RefHeading___Toc216010075)

[ Missing and Exploited Children 106](#__RefHeading___Toc216010076)

[MP3 files 106](#__RefHeading___Toc216010077)

[ Multimedia files and Audio files 106](#__RefHeading___Toc216010078)

[Name attribute 108](#__RefHeading___Toc216010079)

[National Guard 108](#__RefHeading___Toc216010080)

[ Navigation 108](#__RefHeading___Toc216010081)

[Newsletters 112](#__RefHeading___Toc216010082)

[Numbers 112](#__RefHeading___Toc216010083)

[\<object\> tag 112](#__RefHeading___Toc216010084)

[Office Hours 113](#__RefHeading___Toc216010085)

[onBlur 113](#__RefHeading___Toc216010086)

[onClick 113](#__RefHeading___Toc216010087)

[onFocus 113](#__RefHeading___Toc216010088)

[onKeyPress 113](#__RefHeading___Toc216010089)

[onMouseOut 113](#__RefHeading___Toc216010090)

[onMouseOver 113](#__RefHeading___Toc216010091)

[Op-eds 113](#__RefHeading___Toc216010092)

[\<optgroup\> tags 113](#__RefHeading___Toc216010093)

[Padding 113](#__RefHeading___Toc216010094)

[ Page Program 113](#__RefHeading___Toc216010095)

[\<param\> tags 114](#__RefHeading___Toc216010096)

[ Parents 114](#__RefHeading___Toc216010097)

[PDF Files 114](#__RefHeading___Toc216010098)

[Phone Numbers 115](#__RefHeading___Toc216010099)

[ Photo Album 115](#__RefHeading___Toc216010100)

[Picas 116](#__RefHeading___Toc216010101)

[PICS (Platform for Internet Content Selection)
116](#__RefHeading___Toc216010102)

[Pixels 116](#__RefHeading___Toc216010103)

[\<plaintext\> tags 116](#__RefHeading___Toc216010104)

[Points 116](#__RefHeading___Toc216010105)

[Polish language material 116](#__RefHeading___Toc216010106)

[Political Language 116](#__RefHeading___Toc216010107)

[ Polls and Surveys 116](#__RefHeading___Toc216010108)

[Pop-up Windows 117](#__RefHeading___Toc216010109)

[Portuguese language material 117](#__RefHeading___Toc216010110)

[Postal Abbreviations 117](#__RefHeading___Toc216010111)

[Postal Addresses 117](#__RefHeading___Toc216010112)

[\<pre\> tags 117](#__RefHeading___Toc216010113)

[Presidential Greetings 118](#__RefHeading___Toc216010114)

[Press Releases 118](#__RefHeading___Toc216010115)

[Printing 118](#__RefHeading___Toc216010116)

[Privacy Act Release Form 119](#__RefHeading___Toc216010117)

[ Privacy Policy and Cookies 119](#__RefHeading___Toc216010118)

[Pseudo-classes 120](#__RefHeading___Toc216010119)

[Punctuation 120](#__RefHeading___Toc216010120)

[Punjabi language material 120](#__RefHeading___Toc216010121)

[Quotations 120](#__RefHeading___Toc216010122)

[Reserves (Military) 121](#__RefHeading___Toc216010123)

[Reuse of Content 121](#__RefHeading___Toc216010124)

[Roman Numerals 121](#__RefHeading___Toc216010125)

[RSS 122](#__RefHeading___Toc216010126)

[Russian language material 124](#__RefHeading___Toc216010127)

[Samoan language material 124](#__RefHeading___Toc216010128)

[Schedule meeting with Member 124](#__RefHeading___Toc216010129)

[ Schedule of Member 124](#__RefHeading___Toc216010130)

[Scholarships 124](#__RefHeading___Toc216010131)

[Screen resolution 124](#__RefHeading___Toc216010132)

[Scripts 124](#__RefHeading___Toc216010133)

[Searching 126](#__RefHeading___Toc216010134)

[\<select\> tags 127](#__RefHeading___Toc216010135)

[Server-side Includes 127](#__RefHeading___Toc216010136)

[ Service Academy Nominations 127](#__RefHeading___Toc216010137)

[Site maps 127](#__RefHeading___Toc216010138)

[Skip-navigation links 127](#__RefHeading___Toc216010139)

[Small Businesses 127](#__RefHeading___Toc216010140)

[Social Bookmarking 128](#__RefHeading___Toc216010141)

[Social Security numbers 128](#__RefHeading___Toc216010142)

[Spanish language material 128](#__RefHeading___Toc216010143)

[Special Characters 128](#__RefHeading___Toc216010144)

[Strike-through text 128](#__RefHeading___Toc216010145)

[ Student Financial Aid 128](#__RefHeading___Toc216010146)

[Style Sheets 129](#__RefHeading___Toc216010147)

[Subcommittees 130](#__RefHeading___Toc216010148)

[Support Office Websites 131](#__RefHeading___Toc216010149)

[Tables 131](#__RefHeading___Toc216010150)

[Tagalog language material 132](#__RefHeading___Toc216010151)

[Tags (general rules) 132](#__RefHeading___Toc216010152)

[Telephone Numbers 133](#__RefHeading___Toc216010153)

[\<textarea\> tags 133](#__RefHeading___Toc216010154)

[Text-only pages and sites 133](#__RefHeading___Toc216010155)

[Thai language material 133](#__RefHeading___Toc216010156)

[Titles 133](#__RefHeading___Toc216010157)

[Tools for Validating Web Sites 134](#__RefHeading___Toc216010158)

[Tours 135](#__RefHeading___Toc216010159)

[Typeface 135](#__RefHeading___Toc216010160)

[Ukrainian language material 135](#__RefHeading___Toc216010161)

[ Unclaimed Property 135](#__RefHeading___Toc216010162)

[Under Construction 135](#__RefHeading___Toc216010163)

[Underlining 136](#__RefHeading___Toc216010164)

[U.S. Code 136](#__RefHeading___Toc216010165)

[Upper case letters 137](#__RefHeading___Toc216010166)

[Urchin 137](#__RefHeading___Toc216010167)

[URLs 137](#__RefHeading___Toc216010168)

[Usage Statistics 137](#__RefHeading___Toc216010169)

[USA.gov 138](#__RefHeading___Toc216010170)

[Validation Tools 138](#__RefHeading___Toc216010171)

[VBScript 138](#__RefHeading___Toc216010172)

[vCard 138](#__RefHeading___Toc216010173)

[ Veterans 138](#__RefHeading___Toc216010174)

[Vietnamese language material 140](#__RefHeading___Toc216010175)

[ Visiting Washington 140](#__RefHeading___Toc216010176)

[Voice 141](#__RefHeading___Toc216010177)

[Voting Information 141](#__RefHeading___Toc216010178)

[ Waste 141](#__RefHeading___Toc216010179)

[Web Designer 142](#__RefHeading___Toc216010180)

[Welcome Messages 142](#__RefHeading___Toc216010181)

[White House tours 142](#__RefHeading___Toc216010182)

[WIDA 142](#__RefHeading___Toc216010183)

[Word Choice 143](#__RefHeading___Toc216010184)

[Write Your Representative 145](#__RefHeading___Toc216010185)

[\<xmp\> tags 145](#__RefHeading___Toc216010186)

[Appendix 1: Social Bookmarking 146](#appendix-1-social-bookmarking)

[Appendix 2: Federal Judicial Branch
153](#appendix-2-federal-judicial-branch)

[Appendix 3: Caucus Web Sites 156](#appendix-3-caucus-web-sites)

[Appendix 4: \<meta\> and Related Tags
160](#appendix-4-meta-and-related-tags)

[Appendix 5: Language Identification Codes
168](#appendix-5-language-identification-codes)

[Appendix 6: Model Privacy Policy 173](#appendix-6-model-privacy-policy)

[1. English Language Version 173](#english-language-version)

[2. P3P Reference File 176](#p3p-reference-file)

[3. P3P Policy File 176](#p3p-policy-file)

[4. P3P \<link\> 181](#p3p-link)

[5. P3P compact policy 181](#p3p-compact-policy)

[]{#__RefHeading___Toc216009896 .anchor}**Abbreviations and Acronyms**
*see also Forms #(12); and Roman Numerals*

(1) Abbreviations should be coded with \<abbr\> tags (each having a
    "title" attribute identifying what the abbreviation means).[^2]

(2) Acronyms[^3] should be coded with \<acronym\> tags (with "title"
    attributes).[^4]

[]{#__RefHeading___Toc216009897 .anchor}** "About" page (or section)**
*see also Biographies #(3)*

Each committee, leadership, caucus, or support office website should
have an "about" page[^5] that describes the purpose and function of the
office[^6] (and perhaps the philosophy of the office), the history of
the office, and who is in charge of the office. The "about" page should
also provide information on how to contact the office.[^7]

[]{#__RefHeading___Toc216009898 .anchor}**Academy Nominations** *see
Service Academy Nominations*

[]{#__RefHeading___Toc216009899 .anchor}** Accessibility Policy**

Each website should include a page indicating what accessibility
standard(s) the site attempts to comply with and a way that persons with
disabilities can contact the office if they have problems accessing the
site.[^8]

[]{#__RefHeading___Toc216009900 .anchor}**Accesskey attribute**

(1) Use caution when assigning values to the "accesskey" attribute.
    (Some House websites use the accesskey=\"x\" attribute in the \<a
    href\> skip-navigation tag; and the accesskey=\"h\" attribute in the
    \<a href\> tag for the "home" navigation button). The "accesskey"
    attribute allows the user to activate a command by pressing the ALT
    key with another key; for instance, if the \<a href\> tag in the
    "home" navigation button has an accesskey=\"h\" attribute, then when
    a user presses the ALT key and the "H" key, the browser will go to
    the site's homepage. **Note**, however, that there is substantial
    disagreement among accessibility standards experts over whether the
    use of "accesskey" attributes is a good practice or a bad practice
    because of conflicts with ALT key combinations defined by Web
    browsers and screen readers.[^9]

(2) The name for the "accesskey" attribute must be in lower case
    ("\<accesskey\>" not "\<acccessKey\>" or "\<accesskey\>").[^10]

[]{#__RefHeading___Toc216009901 .anchor}** Accomplishments**

Highlight the office's accomplishments -- particularly recent
accomplishments.[^11] Consider having a page of the website devoted to
accomplishments[^12] and perhaps even making "accomplishments" a major
navigation button (e.g., "My Priorities/07 Recap" on [Rep. Jeff
Fortenberry's](http://fortenberry.house.gov/) website).[^13]

[]{#__RefHeading___Toc216009902 .anchor}**ActiveX controls** *see
\<object\> tags*

[]{#__RefHeading___Toc216009903 .anchor}**Acronyms** *see Abbreviations
and Acronyms*

[]{#__RefHeading___Toc216009904 .anchor}**\<address\> tags** *see
Contact Information and Techniques #(o)*

[]{#__RefHeading___Toc216009905 .anchor}**Addresses (Postal)** *see
Contact Information and Techniques #(6) and #(12)*

[]{#__RefHeading___Toc216009906 .anchor}**Alignment** *see also
Centering*

Style sheets, not the "align" attribute, should be used to set
alignments.[^14] Which style sheet property is appropriate to use for
alignment depends on what is being aligned:

-   Alignment of text should be done with the style sheets "text-align"
    property.

-   Alignment of \<hr\>, \<iframe\>, \<img\>, \<input\>, \<object\> and
    similar tags should be done with the style sheets "margin"
    property.[^15]

-   Alignment of table captions (i.e., the \<caption\> tag) should
    ideally be done with the style sheets "caption-side" property.
    Internet Explorer 6, however, does not support the "caption-side"
    property.[^16] It is, nonetheless, recommended that the
    "caption-side" style sheets property be used (instead of the "align"
    attribute of the \<caption\> tag), with the understanding that the
    feature will not work until browsers become more standards
    compliant.

-   Alignment of \<legend\> content with respect to the \<fieldset\> tag
    does not appear to be supported by style sheets. Until the
    \<legend\> tag will accept style sheet "align" properties, it is
    reasonable to continue using the "align" attribute (note, however,
    that the only valid values for the "align" attribute of the
    \<legend\> tag are "left", "right", "top", and "bottom" -- "center"
    is not a valid value for the "align" attribute of the \<legend\>
    tag).[^17]

[]{#__RefHeading___Toc216009907 .anchor}**Ampersands**

Ampersands (&) should only be used as part of character entities (e.g.,
&quot; or &#160;).[^18] To represent an ampersand in text (or as part of
a URL), use:

&amp;

[]{#__RefHeading___Toc216009908 .anchor}**\<applet\> tags**

The \<object\> tag, not the \<applet\> tag, should be used to insert
programs into HTML pages. The \<applet\> tag should not be used for any
purpose.[^19]

[]{#__RefHeading___Toc216009909 .anchor}**"Approved by" Icons** *see
Compliance Icons*

[]{#__RefHeading___Toc216009910 .anchor}**Apostrophes and Quotation
Marks** *see also Quotations*

Open and close, single and double quotation marks (and apostrophes)
generated by Microsoft products, often generate proprietary coding that
is not compliant with the Unicode standard.

(1) When it is desired -- in the content of a website -- to use the
    curved open and close single and double quotation marks (or a curved
    apostrophe), use the decimal representations:[^20]

> ' open single quote &#8216;
>
> ' close single quote (or apostrophe) &#8217;
>
> " open double quote &#8220;
>
> " close double quote &#8221;

(2) When using a single or double quotation mark in the coding of a
    website (e.g., in \<a href=\"index.shtml\"\>), use neutral (i.e.,
    uncurved) single or double quotation marks:

> \' single quote
>
> \" double quote

[]{#__RefHeading___Toc216009911 .anchor}**Arabic language material**
*see Government Resources #(2); Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216009912 .anchor}**Archived House Websites**

The National Archives and Records Administration's official copy of the
House and Senate websites of the 109^th^ Congress is available at
<http://webharvest.gov/collections/>. Additional copies of former House
office Web pages are available (going back to 1996) through the Internet
Archive at <http://www.archive.org/index.php>. Copies of websites of
former Members of the House that were recognized by the Congressional
Management Foundation with their 2006 Gold, Silver or Bronze Mouse
Awards, are available at <http://www.connectingtocongress.org/>.

[]{#__RefHeading___Toc216009913 .anchor}**\<area\> tags** *see Image
Maps #(3)*

[]{#__RefHeading___Toc216009914 .anchor}**Armed Forces** *see District
Information #(5); Military (Active Duty, reserves, and National Guard);
Service Academy Nominations; and Veterans*

[]{#__RefHeading___Toc216009915 .anchor}**Armenian language material**
*see Government Resources #(2); Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216009916 .anchor}** Articles and Op-Eds**

(1) Offices should be encouraged to have available on their website the
    articles, op-eds, and similar material issued by the Member[^21] and
    to make them available in chronological order and in subject
    order.[^22]

(2) Offices should be encouraged to use
    [WIDA](http://housenet.house.gov/keywords/wida) for putting
    articles, op-eds, and similar material on their site.

[]{#__RefHeading___Toc216009917 .anchor}** Artistic Discovery Contest**

(1) Member offices should be encouraged to provide information about how
    to apply to compete in their competition in the Artistic Discover
    Contest. Offices may also want to include information about previous
    winners of the contest from their district.[^23]

(2) The Artistic Discovery page should be linked to from both the
    Constituent Services page and from the Kid's page.

[]{#__RefHeading___Toc216009918 .anchor}**Attributes** *see also
Accesskey attribute; Apostrophes and Quotation Marks #(2); Centering;
Contact Information and Techniques #(12); Event Handlers #(1); Favicons
#(1); Forms; HTML #(3); Image Maps #(2); Language of Text; Margins and
Padding #(2); \<object\> tags #(3); Privacy Policy and Cookies #(4);
Roman Numerals #(1); RSS #(4); Scripts #(2); Tables; and WIDA #(4)*

(1) The value of each attribute should be in quotation marks or
    apostrophes (e.g., use colspan=\"2\" or colspan=\'2\', not
    colspan=2).[^24]

(2) The name of each attribute should be in lower case (e.g., use
    "href", not "HREF").[^25]

(3) Every attribute must have a value (e.g., use checked=\"checked\",
    not just: checked).[^26]

(4) Line breaks[^27] and multiple blanks should not be used in the value
    of an attribute.[^28]

(5) Attribute values are case-sensitive and should normally be in lower
    case.[^29]

[]{#__RefHeading___Toc216009919 .anchor}**Audio files** *see Multimedia
files and Audio files*

[]{#__RefHeading___Toc216009920 .anchor}**Aural Style Sheets**

If using aural style sheets,[^30] keep in mind that Jaws (starting with
version 8) uses screen style sheets -- not aural style sheets -- to
determine the text to be presented.

[]{#__RefHeading___Toc216009921 .anchor}**Babel Fish** *see also
Language of Text; Linking #(14); and Privacy Policy and Cookies*

Offices desiring to include the Alta Vista's free [Babel
Fish](http://babelfish.altavista.com/) language translation function on
the office's website should be cautioned that:

-   Babel Fish generates third party cookies on the PCs of people who
    use their service. Use of cookies on Congressional websites has
    generated bad publicity in the past.[^31] If an office does decide
    to use Babel Fish, the office should be strongly encouraged to (a)
    provide notice on their Privacy Policy page that use of this feature
    may generate third-party cookies on their PC; and (b) include (in
    the office's Privacy Policy) a link to [Alta Vista's Privacy
    Policy](http://www.altavista.com/about/privacy) (with an appropriate
    exit message)[^32].

-   The [Babel Fish
    software](http://www.altavista.com/help/free/free_searchbox_transl)
    imports a JavaScript on the office's website and jumps the user to a
    non-House of Representatives website
    (http://babelfish.altavista.com/) without informing the user that
    they are leaving the House website and that neither the office nor
    the House is responsible for the content of that site. This would
    appear to violate the provision in the [*Members' Congressional
    Handbook*](http://cha.house.gov/official_and_representational_expenses_continued.aspx#WebSites)
    (Web Sites, § 5) that states that "HIR will display an exit notice
    stating that users are leaving the House of Representatives prior to
    linking to a non-House of Representatives website. The exit notice
    will include a disclaimer that neither Members nor the House are
    responsible for the content of linked sites. Member offices
    maintaining their sites on the Public web server are required to
    incorporate the exit notice into their external links." (Similar
    language is contained in the *Committees' Congressional
    Handbook*.)[^33]

-   Babel Fish may not accurately translate some of the nuances of a
    website's text. As the sponsor's of Babel Fish point out, "Expect
    Babel Fish to allow you to grasp the general intent of the original,
    not to produce a polished translation."[^34]

[]{#__RefHeading___Toc216009922 .anchor}**Backgrounds** *see also
Centering; and Navigation #(1)*

(1) Background colors should be designated with style sheets (using the
    "background" property).[^35] The "bgcolor" attribute should not be
    used for this purpose.[^36]

(2) Background images should be designated with style sheets,[^37] not
    with the "background" attribute.[^38]

(3) Different browsers have different default background colors.
    Background colors, therefore, should be specified by style sheet,
    rather than relying on browser defaults.

(4) The contrast between any text and its background should at least
    meet the minimum level set out in a respected accessibility
    standard,[^39] e.g., [Guideline
    1.4.6](http://www.w3.org/TR/WCAG20/#visual-audio-contrast7) of the
    World Wide Web Consortium's Web Content Accessibility Guidelines 2.0
    (November 3, 2008, proposed recommendation).[^40] Text and
    background contrast should be tested using a tool such as Colour
    Contrast Analyser,[^41] which is able to test the luminosity
    contrast ratio (the standard contained in the W3C WCAG 2.0 May 17,
    2007 working draft) and the color difference and brightness (the
    standard contained in the
    [W3C](http://www.w3.org/TR/AERT#color-contrast) *Techniques for
    Accessibility Evaluation and Repair Tools* (April 26, 2000 working
    draft). To maximize accessibility, the contrast between any text and
    its background should have a luminosity ratio of at least 7:1 (with
    and without allowing for colorblindness); have a color brightness
    level greater than 125; and have a color difference greater than
    500.

(5) Rather than using the "background-color", "background-image",
    "background-repeat", "background-attachment", or
    "background-position" style sheet properties, use the "background"
    property -- and specify those elements in that order (i.e., color,
    image, repeat, attachment, and then position).

(6) Every background graphic that is not purely decorative needs to
    include a "title" attribute (or its equivalent)[^42] in the HTML tag
    that invoked the graphic. The "title" attribute (or its equivalent)
    should convey the information that the graphic provides.

    a.  If the graphic includes text, the "title" attribute (or its
        equivalent) should include that text.

    b.  Phrases such as "photo of" or "link to" should not be used as
        part of a "title" attribute (or its equivalent).[^43]

    c.  Abbreviations should not be used in a "title" attribute.

    d.  File names should not be used as the value of an "title"
        attribute.[^44]

[]{#__RefHeading___Toc216009923 .anchor}**Banners** *see also Committee
Websites #(2); Navigation #(2); Printing; and Searching*

(1) Avoid unnecessary blank space under the banner.

(2) Each page should have a banner with the name of the office.[^45] The
    banner of a Member's website should also include the Member's state
    and district.

(3) On Member websites, having multiple pictures of different aspects of
    the district in the banner helps convey the diversity of the
    district and shows that the Member takes pride in all of it. To
    expand the ability to cover a wide number of images, consider having
    a slide show[^46] in the banner (see e.g., [Rep. Dan Lungren's
    website](http://www.house.gov/lungren/)).[^47] **Note:** When a
    script, applet, object, or similar technique is used to generate
    such a slide show, the coding needs to be done in such a way that
    browsers that do not support the technique (or have been set by the
    user not to support the technique) will display either (a) links to
    the images from the slide show, or (b) a composite of the images
    from the slide show, or (c) one image from the slide show.[^48]

(4) When a Member website's banner includes scenes or symbols related to
    the Member's district and/or state, as well as scenes or symbols
    related to Congress or the Federal Government, consider placing the
    district/state material closer to the Member's picture than the
    Federal material. See, e.g., the banner on [Rep. Abercrombie's
    site](http://www.house.gov/abercrombie/).[^49] Additionally
    (particularly when the banner graphics are coded as a background
    image), consider putting the symbols relating to Congress or the
    Federal Government on the right side so that on small resolution
    displays they will be eliminated rather than the symbols relating to
    the Member's district.

(5) The height of the banner should be as small as possible, while still
    conveying the information desired by the office.[^50]

(6) When practical, graphics used in the banner should be implemented as
    background images. Deployment of images as background images (rather
    than using \<img\> tags) promotes scalability of web pages.[^51]

-   **Note**, however, that many browsers have the default set to not
    display backgrounds in printing. To make sure that a banner will
    display when the page is printed, consider the following technique:

    a.  Have separate style sheets for screen display and printing.

    b.  In the HTML coding, in addition to providing a banner as a
        background image, also have a banner called by an \<img\> tag
        with a unique "id" attribute.

    c.  In the screen display style sheet, assign that \<img\> tag's
        "id" attribute value a property of "display:none;".

    d.  In the print style sheet, assign that \<img\> tag's "id"
        attribute value a property of "display:block;" (or
        "display:inline;").[^52]

-   **Additionally,** see the section, above, on **Backgrounds**.

(7) On Member websites, consider including a map of the Member's state
    with the location of the Member's congressional district
    highlighted.

(8) Do not use "banner" as the name of a directory, as some
    anti-intrusion software (e.g., Symantec's Norton Internet Security)
    may interpret this as the content of a banner advertisement and
    block it.[^53]

[]{#__RefHeading___Toc216009924 .anchor}**\<base\> tags**

(1) Each file should contain no more than one \<base\> tag. The \<base\>
    tag should be between the \<head\> tag and the \</head\> tag. A
    \<base\> tag should not be used between the \<body\> and \</body\>
    tags.[^54]

(2) Each \<base\> tag should end with "/\>".[^55]

[]{#__RefHeading___Toc216009925 .anchor}**\<basefont\> tags** *see Fonts
#(3)*

[]{#__RefHeading___Toc216009926 .anchor}** Biographies** *see also
Committee Assignments and Caucus memberships; Legislative Material;
Navigation #(5); and Word Choice*

(1) Each Member website should have a biography of the Member.[^56]

(2) When a Member's biography mentions an issue (or an accomplishment of
    the Member), it is recommended that the mention be hypertext linked
    to the place in the website that sets out the Member's position or
    accomplishments on the issue.[^57] Likewise, if the Member's
    biography mentions a committee, caucus, or other organization that
    the Member has an affiliation with, it is suggested that the mention
    be hypertext linked to that organization's website; and if the
    biography mentions an event (e.g., receipt of an award) where there
    is a relevant press release on the Member's website, it is suggested
    that the mention be hypertext linked to the press release.[^58]

(3) Rather than having "Biography" (or "My Background") as a major
    navigation heading, consider making the Member's biography part of a
    section titled "About \[Member's name\]".[^59] This facilitates
    including additional material about the Member, e.g.,

-   the Member's committee assignments and caucus memberships,

-   a description of a typical day (or week) of the Member[^60], and

-   the Member's upcoming schedule.[^61]^,^ [^62] (Consider laying this
    information out calendar-style -- see, e.g., the calendar of the
    [Committee on Natural Resources (Republican
    Office)](http://republicans.resourcescommittee.house.gov/).)

-   the Member's official photo.

-   having an expanded version of the biography as well as the
    "standard" version (see, e.g., [Rep. Trent Franks'
    website](http://www.house.gov/franks/bio.shtml)).

(4) Offices should be encouraged to write their Member's Web biography
    so that:

-   It is clearly up-to-date (e.g., it includes information from the
    current year)[^63]

-   It tells what the Member is doing now

-   It tells the Member's priorities and interests

-   It tells the Member's accomplishments

-   It tells about the Member's expertise and experience.[^64]

> (See, e.g., the Rep. Frank Pallone's "[About
> Me](http://www.house.gov/pallone/biography.shtml)" page.)

[]{#__RefHeading___Toc216009927 .anchor}**\<blockquote\> tags** *see
Quotations*

[]{#__RefHeading___Toc216009928 .anchor}**Blogs**

(1) Offices interested in having blogs on their website[^65] should be
    encouraged to use the House Web Log Utility.[^66] Offices using the
    House Web Log Utility include [Rep. Dan
    Burton](http://www.house.gov/apps/blog/in05_burton/index.shtml),
    [Rep. Tom Feeney](http://www.house.gov/feeney/wwwblog/index.shtml),
    [Rep. Tom
    Tancredo](http://tancredo.house.gov/press/press_blog.shtml), the
    [Republican Policy Committee](http://policy.house.gov/), and the
    [Republican Study Committee](http://www.house.gov/hensarling/rsc/).

(2) When using the House Web Log Utility, set the "Data Server" value to
    "www.house.gov", not just to "www".

[]{#__RefHeading___Toc216009929 .anchor}**\<body\> tags** *see Margins
and Padding #(2)*

[]{#__RefHeading___Toc216009930 .anchor}**Bolding**

(1) Where bolding would be appropriate on a visual display, use
    \<strong\> tags, not \<b\> tags.[^67]

(2) Other than in headings, bolding should normally be limited to a few
    words -- entire sentences or paragraphs should normally not be
    bolded.[^68] Bolding a few words per paragraph is a useful technique
    to give the reader a feel for the contents, particularly in
    documents with substantial amounts of text and few headings[^69]
    (though use of properly coded headings is preferred).[^70]

[]{#__RefHeading___Toc216009931 .anchor}**\<br\> tags**

(1) The "clear" property in style sheets should be used instead of the
    "clear" attribute of the \<br\> tag.[^71]

(2) Each \<br\> tag should end with "/\>".[^72]

[]{#__RefHeading___Toc216009932 .anchor}** Browsealoud**

Offices should consider including a Browsealoud link on each page.
Browsealoud is a screen reader designed particularly for people with
English literacy problems and/or learning disabilities such as dyslexia.
The Browsealoud link should point to a page on the office's website that
has the content of the House "About The Browsealoud Plug-In" page
(<http://www.house.gov/house/browsealoud.shtml>).[^73]

Possible graphic links to Browsealoud include:

(1) ![](media/image2.png){width="0.15555555555555556in"
    height="0.1673611111111111in"} [^74]

(2) ![](media/image3.png){width="0.3659722222222222in"
    height="0.2604166666666667in"} [^75]

(3) ![](media/image4.png){width="0.96875in"
    height="0.3236111111111111in"} [^76]

(4) ![](media/image5.png){width="1.3527777777777779in"
    height="0.3659722222222222in"} [^77]

(5) ![](media/image6.png){width="1.34375in"
    height="0.4166666666666667in"} [^78]

[]{#__RefHeading___Toc216009933 .anchor}**Browser compatibility**

(1) Designing websites to only run well in one type of browser is
    contrary to industry best practices and will generally produce
    websites that are not accessible to people with disabilities.[^79]
    Sites should be checked[^80] against a range of browsers and
    versions of browsers. To help identify which browsers should be
    tested against House websites, CAO-WSB conducted an analysis of
    www.house.gov usage for July 9 to 15, 2008, and found that the
    following browsers each accounted for at least 0.1% of the
    identifiable, non-robot access to the site:[^81]

```{=html}
<!-- -->
```
10. Internet Explorer 7.x 46.32%

11. Internet Explorer 6.x 30.30%

12. Firefox 2.x 13.15%

13. Firefox 3.x 5.01%

14. Internet Explorer 5.x 1.39%[^82]

15. Firefox 1.x 0.45%

16. Safari 0.35%

17. Opera 0.21%

> 9\. Netscape 7.x 0.11%

(2) Browser compatibility does not require that a website look
    absolutely identical from one browser to another. Instead, it
    expects merely that a site will be at least presentable (and have at
    least equivalent functionality) from one browser to the next.

[]{#__RefHeading___Toc216009934 .anchor}** Business Assistance**

Member offices (and other House offices that deal regularly with people
seeking business opportunities with the Federal government)[^83] should
be encouraged to include in their website:

(1) The CRS-maintained "Business Opportunities with the Federal
    Government" material.[^84]^,^[^85]

(2) Information for small businesses (see, e.g., [Rep. Trent Franks'
    "Small Business Assistance"
    page](http://www.house.gov/franks/small_business.shtml)).[^86]

(3) Information on programs that are specific to the Member's state or
    district, e.g., material available through:

    a.  [Small Business
        Administration](http://www.business.gov/states/);

    b.  [Internal Revenue
        Service](http://www.irs.gov/businesses/small/article/0,,id=99021,00.html);
        and

    c.  [ABC's of Small
        Business](http://www.abcsmallbiz.com/bizbasics/gettingstarted/state_resource_too.html)
        (because this site has not been updated recently, it is
        recommended that rather than linking a House site to their
        state's portion of the ABC's site, use the ABC's site to find
        up-to-date URLs on state-related small business sites and put
        those links directly on to the House site).

[]{#__RefHeading___Toc216009935 .anchor}**Cambodian language material**
*see Government Resources #(2); Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216009936 .anchor}**Campaign material** *see
Election Campaign Material*

[]{#__RefHeading___Toc216009937 .anchor}**Capital letters**

Use of all capital letters in text or in a heading is the equivalent of
shouting and should generally be avoided.[^87]

[]{#__RefHeading___Toc216009938 .anchor}**Capitol tours** *see Visiting
Washington*

[]{#__RefHeading___Toc216009939 .anchor}**CAPTCHA**[^88]

When trying to prevent software from spamming forms, do not rely solely
on displaying an image with distorted text and then asking the user to
rekey the text. Such an approach is inaccessible by many persons with
vision disabilities.[^89] One alternative to CAPTCHA is to use a logic
test where the user is asked a simple mathematical (or other
question).[^90] So as to not make a form inaccessible to persons with
cognitive disabilities, try to keep logic puzzle questions to a second
or third grade level.

[]{#__RefHeading___Toc216009940 .anchor}**\<caption\> tags** *see
Alignment*

[]{#__RefHeading___Toc216009941 .anchor}**Casework** *see also Contact
Information and Techniques #(13); Constituent Services; and Forms #(1)*

Avoid using the term "casework" -- it is jargon and may confuse or
alienate constituents. Consider, instead using something along the lines
of "How I Can Help You with Government Agencies".[^91]

[]{#__RefHeading___Toc216009942 .anchor}**Caucuses** *see "About" page;
Committee Assignments and Caucus memberships; and Contact Information
and Techniques #(12)*

[]{#__RefHeading___Toc216009943 .anchor}**Census data** *see District
Information #(4)*

[]{#__RefHeading___Toc216009944 .anchor}**Centering**

Style sheets, not \<center\> tags (or align=\"center\" attributes),
should be used to achieve centering.[^92] Which style sheet property is
appropriate to use for centering depends on what is being centered,

-   centered text should use the style sheets property
    "text-align:center"

-   background images being centered should use the style sheets
    property "background"[^93]

-   all other items being centered (e.g., the \<hr\>, \<iframe\>,
    \<img\>, \<input\>, and \<object\> tags) should use "margin: 0
    auto;"[^94]

[]{#__RefHeading___Toc216009945 .anchor}**Certification Icons** *see
Compliance Icons*

[]{#__RefHeading___Toc216009946 .anchor}**Character Entities** *see also
Ampersands; Navigation #(6); Quotations #(1); Roman Numerals #(3); U.S.
Code #(3)*

When referencing a character entity by its hexadecimal value, the
letters should be lower case. E.g., to represent  using its hex value,
use "&#x260e;", not "&#X260E;".

[]{#__RefHeading___Toc216009947 .anchor}**Charts and Graphs**

All charts and graphs should have a link to a table that contains the
same data as the chart or graph.[^95] Such tables should conform to the
standards for accessible tables.

[]{#__RefHeading___Toc216009948 .anchor}**Children** *see Missing and
Exploited Children*

[]{#__RefHeading___Toc216009949 .anchor}**Chinese language material**
*see Babel Fish; Government Resources #(2); Language of Text: and
Linking #(14)*

[]{#__RefHeading___Toc216009950 .anchor}**Classes** *see Style Sheets
#(5)*

[]{#__RefHeading___Toc216009951 .anchor}**\<col\> tags** *see Tables*

[]{#__RefHeading___Toc216009952 .anchor}**Colors** *see also
Backgrounds; and Tools for Validating Web Sites #(4)*

(1) When color is used to supply information (e.g., listing in red the
    school districts where most of the enrolled students receive
    subsidized meals), the information also needs to be made available
    to people who are color blind and to people who are using monochrome
    monitors -- in order to comply with § 508 of the Rehabilitation
    Act.[^96]

(2) It is not necessary to just use "browser safe" colors.[^97]

(3) Text colors should be designated with style sheets (using the
    "color" property). The "text" attribute should not be used for this
    purpose.[^98]

(4) When specifying the hexadecimal value of a color that can be
    represented as either a three-digit representation or a six-digit
    representation, use the three-digit representation (e.g., instead of
    "#336699", use "#369").

[]{#__RefHeading___Toc216009953 .anchor}**Comments** *see also Style
Sheets #(7)*

Comments should be preceded with a less-than-sign, an exclamation mark,
two dashes, and a space (\<!\-- ). At the end of each comment should be
a space, two dashes and a greater-than-sign ( \--\>). In between those
two delimiters, do not use two or more consecutive dashes. Some browsers
have problems with comments that do not conform to this standard, e.g.,
Firefox will display improperly coded comments as if they were intended
to be page text.[^99]

[]{#__RefHeading___Toc216009954 .anchor} **Commercial references** *see
also District Information #(2)*

Other than possibly in comments in the source code, House websites
should not contain any reference to the commercial firm or developer who
designed, coded, or maintains the website.[^100]

The suggested format for placing the information in comments is:

> \<!\-- Web designer: ***Jane Smith*** (***House Information
> Resources***); site published: ***February 30, 2008*** \--\>

where ***Jane Smith*** should be replaced with the name of the
designer(s) of the website; ***House Information Resources*** should be
replaced with the name designer's company; and ***February 30, 2008***
with the date that the website (rather than the individual page) was
published.

[]{#__RefHeading___Toc216009955 .anchor}** Committee assignments and
Caucus memberships**

Member offices should be encouraged to

-   list the committees, subcommittees, and caucuses[^101] that the
    Member serves on;

-   provide links to those committees, subcommittees[^102] and caucuses;
    [^103] and

-   explain the purpose of each committee, subcommittee, and
    caucus.[^104]

[]{#__RefHeading___Toc216009956 .anchor}** Committee Websites** *see
also "About" page; Contact Information and Techniques #(12); and
Legislative Material #(1)*

(1) Committee websites should include:

-   transcripts of hearings held by the committee[^105]

-   full text of reports issued by the committee[^106]

-   full text of the committee's rules[^107]

(2) On pages devoted to individual subcommittees, consider using a
    banner that is similar to the full committee's banner but uses
    graphics that relate to the subcommittee's mission.[^108]

(3) The website for a minority office of a committee should indicate the
    distinctive philosophy and/or message of the office (rather than of
    the full committee).[^109]

[]{#__RefHeading___Toc216009957 .anchor}**Communication** *see Contact
Information and Techniques*

[]{#__RefHeading___Toc216009958 .anchor}** Compliance Icons**

Sites that comply with the World Wide Web Consortium's *Web Content
Accessibility Guidelines* should consider displaying an appropriate icon
from <http://www.w3.org/WAI/WCAG1-Conformance.html>.[^110] For instance:

![](media/image7.png){width="0.9166666666666666in"
height="0.3229166666666667in"}

[]{#__RefHeading___Toc216009959 .anchor}**Conformance Icons** *see
Compliance Icons*

[]{#__RefHeading___Toc216009960 .anchor}**Congressional Art
Competition** *see Artistic Discovery Competition*

[]{#__RefHeading___Toc216009961 .anchor}**Congressional Page Program**
*see Page Program*

[]{#__RefHeading___Toc216009962 .anchor}**Congressional Record** *see
Floor Statements*

[]{#__RefHeading___Toc216009963 .anchor}**Congressional Research Service
products** *see Business Assistance; Grants and Federal Domestic
Assistance; Issues and Voting Information #(3); Legislative Material
#(1); and Student Financial Aid*

[]{#__RefHeading___Toc216009964 .anchor}** Constituent Recognitions**

Consider having a page devoted to recognizing constituents (as part of
the site's photo album and as a link from the site's congressional
district section).[^111]

[]{#__RefHeading___Toc216009965 .anchor}** Constituent Services** *see
Artistic Discovery Contest; Business Assistance; Consumer Protection
Information; Disaster Preparedness Information; District Information
#(3); Flags; FirstGov; Government Resources; Grants and Federal Domestic
Assistance; Graphics #(15); Greetings; Identity Theft Information;
Internships; Missing and Exploited Children; Navigation #(5); Page
Program; Service Academy Nominations; Student Financial Aid; Unclaimed
Property; Veterans; and Visiting Washington*

(1) Where possible, include step-by-step instructions for what a
    constituent needs to do (and provide) to get assistance.[^112]

(2) Avoid using the term "constituent services" -- it is jargon and may
    confuse or alienate constituents. Consider, instead using something
    along the lines of "How Can I Help You".[^113]

(3) Consider including a form[^114] to allow constituents to request
    assistance.[^115]

(4) Consider including a Privacy Act release form.[^116] Because the
    requests sensitive personal information (e.g., Social Security
    numbers), it should either be a secure form[^117] or a form along
    the lines of [Rep. Neil Abercrombie's Constituent Consent and
    Information Form](http://www.house.gov/abercrombie/casework.shtml),
    which uses an HTML form to capture the information and then
    generates a filled out form to be signed and mailed to the office.

(5) Consider including information about services regardless of whether
    they are provided by Federal, state, or local agencies.[^118]
    Constituents often do not care which layer of government fixes their
    problem, as long as the problem gets fixed. Where a service is
    completely outside the ability (or jurisdiction) of the office,
    indicate that and -- if at all possible -- offer to help the
    constituent get in touch with the right office (for an example of
    this approach, see the "[Local
    Help](http://www.house.gov/wu/services.shtml#local)" section of Rep.
    Congressman David Wu's "Constituent Services" page).

(6) Consider organizing the Constituent Services portion of the website
    by function, rather than by agency name.[^119] Constituents may not
    know the function of an individual government agency or may be
    confused as to which government agency is the one that can sole
    their problem.

(7) Where the website deals with both services and issues that are
    related to each other (e.g., a page on veterans' benefits and a page
    on legislation dealing with veterans), make sure each one has a link
    to the other.[^120]

[]{#__RefHeading___Toc216009966 .anchor}** Consumer Protection
Information** *see also Identity Theft Information*

(1) Member offices (and offices that have consumers as a constituency)
    should consider including consumer protection information on their
    website. The Federal Trade Commission's September 2007 *For the
    Consumer: Congressional Outreach Projects Using FTC Resources*,
    sites as examples the consumer protection pages of the following
    Congressional offices: [Rep. Neil
    Abercrombie](http://www.house.gov/abercrombie/consumers.shtml),
    [Rep. Judy
    Biggert](http://biggert.house.gov/ConstituentServices.aspx?section=121),
    [Rep. William Lacy Clay](http://lacyclay.house.gov/con_pro.htm),
    [Rep. John
    Dingell](http://www.house.gov/dingell/consumer_issues.htm), [Sen.
    Byron Dorgan](http://dorgan.senate.gov/services/consumer/), [Rep.
    Phil
    English](http://www.house.gov/english/consumerassistance.shtml),
    [Rep. J. Randy
    Forbes](http://forbes.house.gov/ConstituentServices/consumerresources.htm),
    [Rep. Gene
    Green](http://www.house.gov/green/issues/consumer_protection.shtml),
    [Rep. Mary
    Bono](http://bono.house.gov/ConstituentServices/Consumer_Protection.htm)
    Mack, [Rep. Henry
    Waxman](http://www.henrywaxman.house.gov/services_consumer.htm),
    [Sen. Barbara Boxer](http://boxer.senate.gov/services/consumer/),
    [Sen. Jon Kyl](http://kyl.senate.gov/constit_center/consumer.cfm),
    [Sen. James
    Inhofe](http://inhofe.senate.gov/public/index.cfm?FuseAction=ConstituentServices.ConstituentResources),
    and [Sen. Blanche
    Lincoln](http://lincoln.senate.gov/info_links.htm).[^121]

(2) When linking to consumer protection Web pages from the Federal Trade
    Commission, consider using the icons available at
    <http://www.ftc.gov/ftc/consumer/partners_buttons.shtm>.

[]{#__RefHeading___Toc216009967 .anchor}** Contact Information and
Techniques** *see also Blogs; Listserv; Maps and Directions #(1);
Navigation #(5); and Privacy Policy #(1)*

(1) Consider including, in the "Contact Me" page, a method to allow
    constituents to communicate electronically with the office[^122]
    (preferably through a form[^123] on the "Contact Me" page)[^124].
    When using a form -- and not a public e-mail address -- consider
    including an explanation as to why a public e-mail address is not
    being provided.[^125]

(2) Consider including, in the "Contact Me" page, an electronic
    newsletter[^126] subscription sign-up opportunity (via
    [Listserv](http://housenet.house.gov/portal/server.pt?open=512&objID=296&&PageID=25805&mode=2&in_hi_userid=2&cached=true)).

(3) Consider including a staff directory.[^127]

(4) Consider including a form to allow constituents to schedule a
    meeting with the Member (see e.g., [Rep. Jesse Jackson Jr.'s
    "Contact Me to Schedule an Appointment"
    page](http://www.house.gov/jackson/ContactReAppt2.shtml) and [Rep.
    Trent Franks' "Appointment Scheduling Request"
    page](http://www.house.gov/franks/appointment.shtml)).[^128]

(5) Consider including a form to allow constituents to invite the Member
    to attend an event.[^129]

(6) Consider including the regular office hours along with the addresses
    (and phone numbers) of Washington and district offices.[^130] Also,
    when providing this information on the Washington and district
    offices, indicate special services that each office offers so that a
    constituent will know which office to contact (e.g., if one of the
    district offices is particularly equipped to provide services to
    speakers of a particular foreign language or if the Washington
    office normally takes care of veterans' benefits problems, indicate
    that).[^131]

(7) Offices are urged to include a fax number on their website.[^132]

(8) Consider including information as to how soon a constituent can
    expect to get a response and how they will be contacted.[^133]

(9) Offices should be encouraged **not** to include an "e-mail this page
    to a friend" capability on their website because of the security
    problems that such a feature may create.[^134]

(10) Some Member websites us a two-step contact form that has the user
     submit address information that the system uses to determine that
     the user lives in the Member's district before providing the user
     with the opportunity to submit a message to the Member.[^135]
     Offices using this approach should be encouraged to indicate why
     the address information is being requested.

(11) Where the primary contact page includes various methods of
     contacting the office, and the electronic form is just linked to
     the page, put that link at the top of the page.[^136]

(12) Contact information from an office should be coded in conformance
     with the hCard Microformat Standard,[^137] specifically:

     a.  **street numbers** and **street names** should be enclosed by a
         tag with a class=\"street-address\" attribute, e.g.,

> \<span class=\"street-address\"\>101 First Street\</span\>

b.  **post office box numbers, room numbers, suite numbers, building
    names,** etc., should be enclosed by a tag with a
    class=\"extended-address\" attribute, e.g.,

> \<span class=\"extended-address\"\>2401 Rayburn House Office
> Building\</span\>

c.  the names of **cities, towns,** etc. should be enclosed by a tag
    with a class=\"locality\" attribute, e.g.,

> \<span class=\"locality\"\>Springfield\</span\>

d.  the names of **states** should be enclosed by a tag with a
    class=\"region\" attribute, e.g.,

> \<abbr class=\"region\" title=\"Maryland\"\>MD\</abbr\>
>
> or
>
> \<span class=\"region\"\>Virginia\</span\>

e.  **zip codes** should be enclosed by a tag with a
    class=\"postal-code\" attribute, e.g.,

> \<span class=\"postal-code\"\>20515\</span\>
>
> or
>
> \<span class=\"postal-code\"\>20515-6165\</span\>

f.  the **street-address, extended-address, locality, region, and
    postal-code** **classes** should all be within a wrapper with a
    class=\"adr\" attribute, e.g.,

> \<span class=\"adr\"\>
>
> \<span class=\"street-address\"\>101 First Street\</span\>
>
> \<span class=\"locality\"\>Springfield\</span\>,
>
> \<abbr class=\"region\" title=\"Maryland\"\>MD\</abbr\>
>
> \<span class=\"postal-code\"\>20515-6165\</span\>
>
> \</span\>

g.  **telephone numbers** should be enclosed by a tag with a
    class=\"tel\" attribute, e.g.,

> \<span class=\"tel\"\>(202) 226-2140\</span\>

h.  **fax numbers** should be coded with class=\"tel\", class=\"type\",
    and class=\"value\" as follows:

> \<span class=\"tel\"\>\<span class=\"type\"\>Fax\</span\>: \<span
> class=\"value\"\>(202) 226-1872\</span\>\</span\>

i.  **e-mail addresses** (including links to e-mail addresses) should be
    enclosed by a tag with a class=\"email\" attribute, e.g.,

> \<a href=\"mailto:WebAssistance@mail.house.gov\"
> class=\"email\"\>WebAssistance@mail.house.gov\</a\>

j.  **URLs** (including links to URLs) should be enclosed by a tag with
    a class=\"url\" attribute, e.g.,

> \<a href=\"http://www.house.gov\" class=\"url\"\>House of
> Representatives\</a\>

k.  with **Member offices**,

    i.  the **title** of the Member (i.e., Representative, Congressman,
        Congresswoman, Delegate, or Resident Commissioner) should be
        enclosed by a tag with a class=\"honorific-prefix\" attribute;

    ii. the **first name** of the Member should be enclosed by a tag
        with a class=\"given-name\" attribute;

    iii. the **middle name** (or middle initial) -- if any -- of the
         Member should be enclosed by a tag with a
         class=\"additional-name\" attribute;

    iv. the **last name** of the Member should be enclosed by a tag with
        a class=\"family-name\" attribute;

    v.  any **attribute that normally follows a Member's last name**
        (e.g., "Jr." or "III") should be enclosed by a tag with a
        class=\"honorific-suffix\" attribute;

    vi. **all of the elements relating to a Member's name** should all
        be within a wrapper with a class=\"fn\" attribute, e.g.,

> \<span class=\"fn\"\>
>
> \<span class=\"honorific-prefix\"\>Representative\</span\>
>
> \<span class=\"given-name\"\>John\</span\>
>
> \<span class=\"additional-name\"\>J.\</span\>
>
> \<span class=\"family-name\"\>Jones\</span\>,
>
> \<abbr class=\"honorific-suffix\" title=\"Junior\"\>Jr.\</abbr\>
>
> \</span\>

l.  with **Committee, Caucus, Leadership, Officer, and support office**
    websites, the name of the office should be enclosed by a tag with a
    class=\"fn org\" attribute, e.g.,

> \<span class=\"fn org\"\>Committee on House Administration\</span\>

m.  where the contact information does not have the specific name of the
    office, add that information (with, as appropriate, either
    class=\"fn\" or class=\"fn org\") and use the style sheet
    "display:none; visibility:hidden;" property[^138] so that it will
    not display on the Web page, but will be picked up by applications
    making use of hCard data.

n.  all of the contact information (full name, address, phone numbers,
    URL, and e-mail address) should be within a wrapper with a
    class=\"vcard\" attribute, e.g.,

> \<span class=\"vcard\"\>
>
> \<span class=\"fn org\"\>Committee on Rules\</span\>
>
> \<span class=\"adr\"\>
>
> \<span class=\"extended-address\"\>H-312 The Capitol\</span\>
>
> \<span class=\"locality\"\>Washington\</span\>,
>
> \<abbr class=\"region\" title=\"District of Columbia\"\>DC\</abbr\>
>
> \<span class=\"postal-code\"\>20515\</span\>
>
> \</span\>
>
> \</span\>

o.  Where the contact information is the contact information for most of
    the material on the current page, use the \<address\> tag[^139] as
    the tag to carry the class=\"vcard\" attribute, e.g.,

> \<address class=\"vcard\"\>
>
> \<span class=\"fn org\"\>Committee on Rules\</span\>
>
> \<span class=\"adr\"\>
>
> \<span class=\"extended-address\"\>H-312 The Capitol\</span\>
>
> \<span class=\"locality\"\>Washington\</span\>,
>
> \<abbr class=\"region\" title=\"District of Columbia\"\>DC\</abbr\>
>
> \<span class=\"postal-code\"\>20515\</span\>
>
> \</span\>
>
> \</address\>

(13) When practical, the office's phone number and address on each
     page.[^140]

(14) The main content of the contact page should have a link to the
     site's constituent services and/or casework pages.[^141]

(15) Consider providing tips on how to communicate effectively with the
     office.[^142]

[]{#__RefHeading___Toc216009968 .anchor}**Contrast** *see Backgrounds
#(4); and Tools for Validating Web Sites #(5)*

[]{#__RefHeading___Toc216009969 .anchor}**Cookies** *see Privacy Policy
and Cookies*

[]{#__RefHeading___Toc216009970 .anchor}**COPPA** *see Kids' pages; and
Privacy Policy and Cookies*

#  Copyrighted material 

(1) Copyrighted material[^143] should be used only with the written
    permission of the copyright owner.

(2) When using copyrighted material on a Web page that is also using
    Dublin Core meta tags, the "content" attribute of the \<meta
    name=\"DC.rights\" /\> tag should indicate the name of the copyright
    owner and what part of the page is copyrighted material.

(3) Copyrighted material should not be photo-edited (or otherwise
    altered) unless the copyright owner has given written permission for
    the alteration (permission to use copyrighted material does not
    imply permission to alter the material).

(4) Where material used on a website contains a copyright notice (e.g.,
    "©," "copyright," or "copr.;" with the name of the copyright owner
    and the year of original publication), the copyright notice should
    not be removed from copyrighted material without specific written
    permission of the copyright owner.

(5) Material prepared by (or for) a House office is not copyrightable
    and should not have a copyright notice.[^144]

(6) Material copied from any website -- other than a Federal government
    website -- should be presumed to be copyrighted. Material from state
    and local government websites; commercial websites; newspaper,
    television, or radio websites; educational websites; and non-profit
    websites should all be presumed to be copyrighted.

[]{#__RefHeading___Toc216009972 .anchor}**Corners** *see Layout #(5)*

[]{#__RefHeading___Toc216009973 .anchor}**Courts** *see Government
Resources #(1)*

[]{#__RefHeading___Toc216009974 .anchor} **Dates, Time, and
Timeliness**

(1) If you dynamically generate the current date or time, use a
    server-side include, rather than grabbing the information from the
    user's PC.[^145]

(2) When referring to congresses (e.g., the 109^th^ Congress), also
    provide the years. Do not assume that people off of Capitol Hill
    know what a particular congress is.[^146]

(3) Information on the website should be kept up to date.[^147] The
    information should also convey the idea that it is current (see,
    e.g., Rep. Frank Palone's "[About
    Me](http://www.house.gov/pallone/biography.shtml)" page, that starts
    off with "On January 4, Frank Pallone, Jr. was officially sworn in
    for his tenth full term").

(4) When possible, avoid using numeric notation for dates (e.g.,
    5/10/07), especially where the potential audience includes an
    appreciable number of people who use a language other than American
    English as their primary language. The United States, Canada, and a
    few former U.S. territories appear to be the only countries using
    month-day-year, as opposed to day-month-year or
    year-month-day.[^148]

[]{#__RefHeading___Toc216009975 .anchor}**Demographics** *see District
Information #(4)*

[]{#__RefHeading___Toc216009976 .anchor}** Digital Television
Information**

Member offices should consider including information on their websites
concerning the upcoming conversion to digital television.[^149]
Information on the transition is available at
<https://www.dtv2009.gov/>, however offices should be encouraged to
provide some information on their own website information on the
transition before linking the user to the dtv2009 website.[^150]

[]{#__RefHeading___Toc216009977 .anchor}**\<dir\> tags** *see Lists
#(5)*

[]{#__RefHeading___Toc216009978 .anchor}** Disaster Preparation
Information**

Member offices should consider including information on their websites
concerning disaster preparation information. Rep. Mary Bono's website,
for instance, provides [earthquake preparation
information](http://bono.house.gov/HomePage/earthquake.htm).[^151]

[]{#__RefHeading___Toc216009979 .anchor}** District Information** *see
also Banner #(7); Constituent Recognitions; Maps and Directions;
Navigation #(5); and Government Resources #(1)*

(1) Member offices should be urged to include on their website material
    on the history of their congressional district. See, e.g., [Rep.
    Diana DeGette's district history
    page](http://www.house.gov/degette/history.shtml), which lists all
    of the Members of the House who have represented the district since
    1861, when Colorado became a territory; [Rep. Ray LaHood's "Abraham
    Lincoln's Legacy" page](http://www.house.gov/lahood/legacy.shtml)
    that links the current 18^th^ District of Illinois with the district
    represented by Abraham Lincoln when he was a member of the House of
    Representatives (1847-1849); and Rep. Jeff Fortenberry's
    "[Interesting First District
    Facts](http://fortenberry.house.gov/ne01facts.shtml)" page which
    provides information on noteworthy events from the 1800s to the
    present that occurred in what is now the 1^st^ District.[^152]

(2) Many Members of Congress view it as one of their responsibilities to
    serve as the goodwill ambassador for their district. As such, they
    may want to feature (and link to) attractions and industries in
    their district. The *[Members' Congressional Handbook (Web Sites,
    Content §
    5)](http://cha.house.gov/official_and_representational_expenses_continued.aspx#Content)*
    and the [*Committees' Congressional Handbook (Web Site Regulations,
    Content §
    e)*](http://cha.house.gov/committee_handbook.aspx#Content)**,**
    however, prohibit House Member and House committee websites from
    including "any advertisement for any private individual, firm, or
    corporation, or imply in any manner that the government endorses or
    favors any specific commercial product, commodity, or service." Two
    practices have been developed by House offices that wish to provide
    links to external Web pages that provide information on attractions
    and industries in their district, while staying within the House
    rules:

    a.  Listing **all** of the companies in a Member\'s district that
        are within a specific segment of the economy (e.g., all
        professional sports teams in the district, or all the wine
        vineyards in a district) and linking to informational pages --
        not pages primarily containing solicitations for money,
        volunteerism, or other things of value[^153]; [^154] and

    b.  Including a statement on the Web page with the links, that these
        links are not intended to be an endorsement.[^155]

(3) Where there are offices of Federal agencies in (or near the
    district), Member offices should be encouraged to include
    information about the offices (or at least links to their
    websites).[^156] Consider placing these references in the District
    Information section of the website and in the Constituent Services
    section of the website and in the Federal Government section of the
    website.[^157]^,^ [^158]

(4) Member offices should be encouraged to include Census Bureau data
    about their district.[^159]

(5) On Member websites, consider providing links to the websites of
    military units stationed in (or near) the district; and military
    units associated with the district. See, e.g., Rep. Rush Holt's
    "[Guard and Reserves](http://holt.house.gov/NationalGuard.shtml)"
    page.

(6) Member offices should consider providing information about the
    counties, towns, and other localities within their district. Rather
    than just linking to the websites of a county, town, or other
    locality within a district, it is preferable to link to pages on the
    Member's website that provide information about the locality and
    include on that page a link to the locality's website.[^160]

(7) Member offices should consider including information for people who
    are moving (or contemplating moving) to the Member's district. Such
    information would include topics such as how to register cars (and
    other vehicles), how to get utilities activated, and how to register
    children for school.[^161]

[]{#__RefHeading___Toc216009980 .anchor}**\<!DOCTYPE\> declarations**

(1) Each file should have a \<!DOCTYPE\> declaration. Unless there is an
    important reason to do otherwise, the \<!DOCTYPE\> declaration on
    each file should be[^162]:

> \<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"
> \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\"\>
>
> If that \<!DOCTYPE\> is not used, then it is recommended that a
> \<!DOCTYPE\> from the W3C *[Recommended List of
> DTDs](http://www.w3.org/QA/2002/04/valid-dtd-list.html)* be used.
> (Note that the \<!DOCTYPE\> declaration **is** case sensitive.)

(2) There should only be one \<!DOCTYPE\> declaration in a file and it
    should precede everything in the file.[^163]

[]{#__RefHeading___Toc216009981 .anchor}**Download time** *see also
Graphics #(1) and (5)*

Offices should be encouraged to have each Web page take no more than 15
seconds to download on a 56.6kb connection.[^164]

[]{#__RefHeading___Toc216009982 .anchor}**Dutch (Flemish) language
material** *see Babel Fish; Government Resources #(2); Language of Text:
and Linking #(14)*

[]{#__RefHeading___Toc216009983 .anchor}** Earmarks**

Member offices should consider including on their websites information
about their earmarks. Rep. Jeff Fortenberry's "[First District
Earmarks](http://fortenberry.house.gov/earmarks1.shtml)" page, for
instance, starts with an explanation of what earmarks are and the
criteria he uses before seeking an earmark; and then lists the earmarks
that he has succeeded in getting and provides a description of
each.[^165]

[]{#__RefHeading___Toc216009984 .anchor}**Earthquake Preparation
Information** *see Disaster Preparation Information*

[]{#__RefHeading___Toc216009985 .anchor}**Election Campaign material**
*see also Political Language*

(1) Material originally developed for (or originally paid for by) an
    election campaign should not be used on House websites.[^166]

(2) House websites should not contain election campaign information or
    links to election campaign sites.[^167]

[]{#__RefHeading___Toc216009986 .anchor}**Elements** *see Tags (general
rules)*

[]{#__RefHeading___Toc216009987 .anchor}**Ellipsis** *see Quotations*

[]{#__RefHeading___Toc216009988 .anchor}**E-mail addresses** *see
Contact Information and Techniques #(12)*

[]{#__RefHeading___Toc216009989 .anchor}**E-mail a friend**

Offices should avoid having "e-mail this page to a friend" features on
their websites, because of their potential for creating security
vulnerabilities.[^168]

[]{#__RefHeading___Toc216009990 .anchor}**\<embed\> tags**

When possible,[^169] the \<object\> tag, not the \<embed\> tag, should
be used to insert programs into HTML pages. The \<embed\> tag is not
compliant with the W3C XHTML 1.0 (2^nd^ edition) standard.[^170]

[]{#__RefHeading___Toc216009991 .anchor}**Employment Opportunities**
*see Job Opportunities*

[]{#__RefHeading___Toc216009992 .anchor}**E-Newsletters** *see Listserv
and E-Newsletters*

[]{#__RefHeading___Toc216009993 .anchor}**Event Handlers**

(1) When used within an HTML tag, event handlers are syntactically
    equivalent to attributes. Event handler names should therefore be in
    all lower case when used inside a tag (though the value of the event
    handler may include any character).[^171] For instance, use

> \<img on**k**ey**p**ress=\"nextPage();\" /\>
>
> but not
>
> \<img on**K**ey**P**ress=\"nextPage();\" /\>

(2) An "onclick" event handler does not need to have a redundant
    "onkeypress" event handler.[^172]

(3) Rather than using the "onmouseout" event handler to convey
    information (or to provide functionality),[^173] either:

    a.  include an "onblur" event handler with the same value as the
        "onmouseout" event handler;

    b.  replace the "onmouseout" event handler with an "onblur" event
        handler with the same value;[^174] or

    c.  replace the "onmouseout" event handler with a different
        technique that provides the same functionality.[^175]

(4) Rather than using the "onmouseover" event handler to convey
    information (or to provide functionality) replace the onmouseover
    with the a:hover property of style sheets,[^176] if possible. If it
    is not possible to replace onmouseover with a:hover then,[^177]
    either:

    a.  include an "onfocus" event handler with the same value as the
        "onmouseover" event handler;

    b.  replace the "onmouseover" event handler with an "onfocus" event
        handler with the same value;[^178] or

    c.  replace the "onmouseover" event handler with a different
        technique that provides the same functionality.[^179]

[]{#__RefHeading___Toc216009994 .anchor}**Events Schedule** *see
Schedule of Member*

[]{#__RefHeading___Toc216009995 .anchor}**Farsi language material** *see
Government Resources #(2); Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216009996 .anchor}**Favicons**

(1) Each Web page should specify its favicon[^180] with a \<link
    rel=\"SHORTCUT ICON\" /\> tag, where the "href" attribute specifies
    the URL of the image to be used as the favicon,[^181] e.g.:

\<link rel=\"SHORTCUT ICON\"
href=\"http://altmire.house.gov/favicon.ico\" /\>

(2) Favicon file names must end with a .ico extension.[^182]

(3) The "Favicon from Pics" tool at
    <http://www.chami.com/html-kit/services/favicon/> can convert gif,
    jpg, png, and bmp files into ico format. Adobe GoLive, Adobe
    Illustrator, and CorelDraw also are able to generate ico files.

[]{#__RefHeading___Toc216009997 .anchor}**Fax Numbers** *see Contact
Information and Techniques #(7) and #(12)*

[]{#__RefHeading___Toc216009998 .anchor} **Federal Bureau of
Investigation tours**

The FBI's ["FBI Tours" web
page](http://www.fbi.gov/aboutus/tour/tour.htm) indicates that "The FBI
Tour is presently closed. No date has been set for its reopening."

[]{#__RefHeading___Toc216009999 .anchor}**Federal Government** *see
Government Resources*

[]{#__RefHeading___Toc216010000 .anchor}**File Names and Extensions**
*see also Banners #(8); and Favicons #(2)*

(1) When redesigning a website, whenever possible reuse the file names
    of the old site in the new site, so that pre-existing bookmarks and
    links from other sites will continue to work. If it is not possible
    to reuse the previous file names, then use redirects to take users
    who attempt to access the old pages and move them to the
    corresponding new page (not just to your new homepage).[^183]

(2) Whenever possible, ".shtml" (rather than ".htm" or ".html") should
    be used as the extension for HTML pages. (Use of the ".shtml"
    extension facilitates the use of server-side includes.)

(3) When creating a new file (or subdirectory), choose a meaningful name
    for the file (or subdirectory).

(4) If a name consists of several words, separate each one by a dash,
    e.g., **use** "best-practices", **not** "bestPractices" or
    "best_practices" or "best practices".[^184]

(5) Avoid starting a file name with the third level domain name of the
    site (e.g., "jones" in "jones.house.gov"). Using the domain name as
    the beginning of a file name may result in being redirected to the
    homepage of that Member, e.g., http://jones.house.gov/jones.css may
    resolve as http://jones.house.gov/.

[]{#__RefHeading___Toc216010001 .anchor}** FirstGov**

FirstGov.gov (the U.S. Government information portal maintained by the
U.S. General Services Administration) was renamed USA.gov, effective
January 18, 2007. House websites should, therefore, not contain
references to FirstGov.gov, except in a historical context.
Additionally, House offices should link[^185] to pages on
[www.USA.gov](http://www.USA.gov/), rather than to www.FirstGov.gov.

[]{#__RefHeading___Toc216010002 .anchor}** Flags** *see also Forms*

(1) Member offices should be encouraged to include information on how to
    order U.S. flags flown over the Capitol Building.[^186]

(2) Member offices should be encouraged to use the [E-Flag
    Calculator](http://housenet.house.gov/portal/server.pt?open=18&objID=614&parentname=CommunityPage&parentid=20&mode=2&in_hi_userid=2&cached=true)
    as part of their Web pages for ordering U.S. flags flown over the
    Capitol building. The E-Flag Calculator will calculate the cost of a
    flag request (including postage) and produce an invoice that the
    constituent can mail to your office with their check. Additionally,
    the cost of the flags are automatically updated by the House Office
    Supply Service and postage rates are automatically updated by the
    U.S. Postal Service.

(3) Consider including a link (from the flag order page) to a page with
    instructions for the proper care of a flag. See, e.g., Rep. Steven
    LaTourette's "[Care and Presentation of the
    Flag](http://web.archive.org/web/20070807115042/http:/www.house.gov/latourette/flag_care.htm)"
    page.

(4) For links to the flag page (and for the heading of the flag page),
    rather than using a variation on "Order a Flag", consider using
    something along the lines of "Fly a Flag over the Capitol
    Building"[^187] or "Have a Flag flown over the Capitol".

[]{#__RefHeading___Toc216010003 .anchor}** Floor Statements** *see also
WIDA*

Member offices should be encouraged to include Floor statements made by
the Member.[^188] The official text of all House Floor statements is
available in the Congressional Record -- which is available on the
Internet (through Thomas).[^189] Alternatively, offices may provide its
own transcripts (see, e.g., [Rep. Jason Altmire's
website](http://www.altmire.house.gov/index.php?option=com_content&task=blogcategory&id=22&Itemid=49),
which uses WIDA and presents the material in chronological order and in
subject order).[^190]

[]{#__RefHeading___Toc216010004 .anchor}**Fonts** *see also Bolding;
Italics; and Roman Numerals #(2)*

(1) Style sheets, not \<font\> tags, should be used to set font colors,
    type faces, and type size.[^191]

(2) Font sizes (for material that will be displayed on a screen)[^192]
    should be specified in ems or percentages, not in points, picas,
    centimeters, inches, or pixels.[^193]

(3) Style sheets associated with the \<body\> tag should be used to set
    the document-wide default values for text size, color, and
    typeface.[^194] The \<basefont\> tag should not be used for this or
    any other purpose.[^195]

(4) When specifying a serif font for screen display, consider specifying
    Georgia, rather than Times New Roman. When specifying a sans-serif
    font for screen display, consider specifying Verdana, rather than
    Arial. Georgia and Verdana were designed for screen display, whereas
    Times New Roman and Arial were designed for printing.[^196]

(5) When specifying a font family, use a series of fonts[^197] with a
    generic font as the last in the series.[^198]

(6) Consider adding an on-page feature to allow font size to be
    increased, e.g., the
    ![](media/image8.png){width="0.2708333333333333in" height="0.125in"}
    feature on the house.gov homepage.[^199]

[]{#__RefHeading___Toc216010005 .anchor}**Foreign Languages** *see Babel
Fish; and Language of Text*

[]{#__RefHeading___Toc216010006 .anchor}**Forms** *see also Alignment;
CAPTCHA; Centering; Contact Information and Techniques #(1); Flags #(2);
Graphics #(3); Social Security numbers; and Visiting Washington #(1)*

(1) All forms (other than those that appear on every -- or nearly every
    -- page of a website) should be coded as secure forms.[^200] Secure
    forms should particularly be used for casework forms, tour request
    forms, and general purpose contact forms.

(2) When designing a form, assume that most of the instructions will
    neither be read nor remembered. Ideally, forms should be so
    self-explanatory that instructions are not needed.[^201]

(3) When most of the fields in a form are **not** required fields, then
    the fields that are required should indicate that they are
    required.[^202] Where most (or all) of the fields in a form are
    required, do not mark each field as required.[^203]

(4) When marking fields as being required, consider the following
    techniques:

    a.  Use an asterisk to identify required fields. When using this
        technique, include a title=\"required field\" attribute in a tag
        pair surrounding the asterisk (e.g., \<span title=\"required
        field\"\>\*\</span\>).[^204]

    b.  Highlight in yellow[^205] those cells that correspond to
        required fields.[^206] Highlighting those cells, however, should
        not be the only method used to indicate that the field is a
        required field.[^207]

    c.  Underlining should not be used to indicate that a field is a
        required field.[^208]

    d.  Any instructions indicating how to identify required fields
        should precede the form.[^209]

(5) When asking for data that is familiar to the person filling out the
    form (e.g., name and address information), put the label above the
    input box.[^210]

(6) Every form should either have a "submit" button (or its equivalent)
    or clear instructions as to how to activate the form.[^211]

(7) When deciding on the text of a form button, use the fewest words
    necessary to convey your meaning.

(8) Forms should not ask for more information than the office
    needs.[^212]^,^ [^213]

(9) If submitting a form generates a follow-up page that requires the
    person who filled out the form to confirm the information before the
    content of the form is actually transmitted to the office, the
    confirmation button should be prominent and "above the fold" (i.e.,
    it should be on the portion of the screen that a user sees without
    having to use a scroll bar). **Do not assume** that the user will
    have read either the instructions on the original form or
    instructions on the confirmation page.[^214]

(10) Normally, each input field (whether created by an \<input\>,
     \<select\>, or \<textarea\> tag) has text associated with it that
     explains what information should be put into the field (e.g.,
     "First Name", "Street Address", or "City").

     a.  If that explanatory text is present, it should be preceded by a
         \<label\> tag and followed by a \</label\> tag. The \<label\>
         tag should have a "for" attribute with a value equal to the
         value of the "id" attribute of the \<input\>, \<select\>, or
         \<textarea\> tag.[^215] For example:

> \<label for=\"querytext\"\>Search for:&nbsp;\</label\>
>
> \<input type=\"text\" name=\"QueryText\" name=\"querytext\"
> id=\"querytext\" size=\"10\" value=\"\" /\>
>
> If the explanatory text surrounds the \<input\>, \<select\>, or
> \<textarea\> tags, e.g.
>
> User name: ┌────────────────┐(E-mail address:
>
> └────────────────┘ xxx@xxx.xxx)
>
> surround the entire string in the \<label\> tags. For instance,[^216]
>
> \<label for=\"user2\"\>User name:\
> \<input type=\"text\" name=\"user2\" id=\"user2\" /\>\
> (E-mail address: xxx@xxx.xxx)\</label\>

b.  If there is no explanatory text that can be associated with an
    \<input\>, \<select\>, or \<textarea\> element (e.g., were the label
    asks for a telephone number, but there are three \<input\> tags, one
    for the area code, one for the telephone exchange, and one for the
    remaining four digits), then either:

```{=html}
<!-- -->
```
1.  use a "title" attribute in the tag to indicate what information is
    to go into the field; or

2.  add the information and put it between a \<label\> tag (with an
    appropriate "for" attribute) and a \</label\> tag; and give the
    \<label\> tag a class (e.g. class=\"hidden\"), where the class
    places the text off screen and minimizes the size (e.g.,
    position:absolute;left:-999em; font-size:1%);[^217] or

3.  add the information and put it between a \<label\> tag (with an
    appropriate "for" attribute) and a \</label\> tag; and use the
    technique suggested in "[Labels.js: A Re-introduction to
    DHTML](http://web.archive.org/web/20050427185218/http:/webapp.youngpup.net/?request=/articles/labels.xml)"
    (December 23, 2001).

```{=html}
<!-- -->
```
(11) If a \<select\> tag has a substantial number of \<option\> tags
     associated with it, the \<option\> tags should be grouped together
     with \<optgroup\> tags. See, for example, the "What is the general
     topic of your message?" pull-down on [Rep. Dan Boren's "Contact Dan
     Online Form"](http://boren.house.gov/emailsignup.shtml) page.[^218]

(12) Where a form has a pull-down menu of postal abbreviations, each
     \<option\> tag should have a "title" attribute that specifies the
     name of the state. See, e.g., the "[Contact Me About Constitutional
     Amendments](http://www.house.gov/jackson/ContactReAmends.shtml)"
     page on Rep. Jesse Jackson, Jr.'s website.[^219] Note, however,
     that from a usability and accessibility point of view, it is
     preferable to provide an \<input type=\"text\"\> field where the
     visitor can type in the 2-character postal abbreviation, rather
     than puling the information from a \<select\>/\<option\>
     pull-down.[^220] If the form is only meant to be filled out be
     visitors from the Member's state, it is preferable to hard-code the
     state value and use an \<input type=\"hidden\"\> tag to pass the
     postal abbreviation to the appropriate software.

(13) JavaScripts, VBScripts, and other scripts should not be used as the
     exclusive way to submit forms.[^221]

(14) Rather than using JavaScript or VBScript to determine whether
     required fields are present in a form (or to verify that e-mail
     addresses are in the correct format), websites hosted on the HIR
     Web servers should use the "required-\[field\]", "valid-email", or
     "required-valid-email" options in form_proc.[^222]^,^ [^223]

(15) Any \<input\> tag with a type=\"text\" attribute should not have a
     "value" attribute.[^224]

(16) If a \<form\> tag has a "name" attribute, it should also have an
     "id" attribute with the same value [^225] When assigning the value
     of an "id" (or "name") attribute use the purpose of the data that
     the attribute's tag relates to, not how the data is to be portrayed
     -- the "name" value should indicate function, not form. (For
     instance, "hotTopics" would be an appropriate value for an "id" or
     "name" attribute, but "whiteOnRed" would not be an appropriate
     value.)[^226]

(17) Within every group of radio buttons, the \<input\> tag for one of
     the buttons should have a checked=\"checked\" attribute.[^227]

(18) Within every \<select\> tag, one of the \<option\> tags should have
     a selected=\"selected\" attribute.[^228]

(19) Each \<input\> and \<option\> tag should end with "/\>".[^229]

(20) Consider including a forms library (see, e.g., the websites of
     [Rep. Trent Frank](http://www.house.gov/franks/) and [Rep. Jeff
     Fortenberry](http://fortenberry.house.gov/)).[^230]

(21) On each page that consists primarily of a form, the \<meta
     name=\"DC.type\"\> tag should have a "content" attribute with the
     value "InteractiveResource", and the \<meta name=\"robots\"\> tag
     should have a "content" attribute with a value of "INDEX,NOFOLLOW".
     For example:

> \<meta name=\"DC.type\" scheme=\"DCTERMS.DCMIType\"
> content=\"***InteractiveResource***\" /\>
>
> \<meta name=\"robots\" content=\"***INDEX,NOFOLLOW***\" /\>
>
> The \<meta\> tags should be within \<head\> and \</head\> tags.

[]{#__RefHeading___Toc216010007 .anchor}**Frames and Iframes**[^231]
*see also Alignment; Browsealoud; Banners #(3); Centering; House
Operating Status; Kids Pages #(2); Legislative Material #(1) and (2);
RSS(2); Veterans #(1); and Visiting Washington #(2)*

(1) When a frame (or iframe) calls in a page from outside the HOUSE.GOV
    domain, there needs to be a prominent message indicating that the
    material is not from the House of Representatives and that neither
    the office nor the House are responsible for the content.[^232]

(2) If a \<frame\> tag or a \<iframe\> tag has a "name" attribute, it
    should also have an "id" attribute with the same value [^233] When
    assigning the value of an "id" (or "name") attribute use the purpose
    of the data that the attribute's tag relates to, not how the data is
    to be portrayed -- the "name" value should indicate function, not
    form. (For instance, "hotTopics" would be an appropriate value for
    an "id" or "name" attribute, but "whiteOnRed" would not be an
    appropriate value.)[^234]

(3) Frames may be used, as long as the \<frame\> or \<iframe\> tag has a
    "title" attribute that describes the specific function of that
    frame.[^235] Where the \<frame\> or \<iframe\> is used to call up an
    image that is not able to have an "alt" attribute (or its
    equivalent), then use the "title" attribute of the \<frame\> (or
    \<iframe\>) tag to describe the image, the same way that the "alt"
    attribute would normally be used to describe an image.[^236]

(4) Each \<frame\> tag should end with "/\>"[^237]

[]{#__RefHeading___Toc216010008 .anchor}**French language material**
*see Babel Fish; Government Resources #(2); Language of Text: and
Linking #(14)*

[]{#__RefHeading___Toc216010009 .anchor}** Frequently Asked Questions**

Offices should be encouraged to have FAQs in their website.[^238] The
website of the late [Rep. Juanita
Millender-McDonald](http://web.archive.org/web/20060211090329/www.house.gov/millender-mcdonald/bio.htm),
for instance, had FAQs as a primary navigation item.[^239] See also,
[Rep. Trent Frank's "Frequently Asked Questions -- FAQ's"
page](http://www.house.gov/franks/faqs.shtml) and [Rep. Jeff
Fortenberry's constituent services
FAQ](http://fortenberry.house.gov/faqs.shtml).[^240]

[]{#__RefHeading___Toc216010010 .anchor}**German language material**
*see Babel Fish; Government Resources #(2); Language of Text: and
Linking #(14)*

[]{#__RefHeading___Toc216010011 .anchor}** Government Resources** *see
also Constituent Services; District Information #(3); FirstGov; and
Linking #(4)*

(1) Member offices should be encouraged to include material about (or at
    least links to) the Federal courts that have jurisdiction within the
    Member's congressional district.[^241] See Appendix 2: *Federal
    Judicial Branch* of this document for information on Federal
    Judicial websites.

(2) On websites that have non-English pages, consider also providing
    links to government information pages that are linked from the
    Federal Citizen Information Center's Multilanguage Gateway.[^242]
    Those websites with Spanish pages should be encouraged to include
    the Spanish version of the [CRS-maintained "Grants and Federal
    Domestic Assistance"
    page](http://onlinecao.house.gov/webassistance/html/ht_crs_grants.htm)
    on their website.[^243]

(3) Consider including a link to USA.gov (formerly FirstGov).[^244] See,
    e.g., Rep. David Wu's "[Constituent
    Services](http://www.house.gov/wu/services.shtml)" page.

[]{#__RefHeading___Toc216010012 .anchor}**Grammar** *see Word Choice*

[]{#__RefHeading___Toc216010013 .anchor}** Grants and Federal Domestic
Assistance**

Member offices (and other House offices that deal regularly with grant
applicants)[^245], that are hosted on an HIR Web server should be
encouraged to include the [CRS-maintained "Grants and Federal Domestic
Assistance"
page](http://housenet.house.gov/portal/server.pt?open=18&objID=600&parentname=CommunityPage&parentid=20&mode=2&in_hi_userid=2&cached=true)
in their website. Offices not hosted on an HIR Web server should be
encouraged to iframe the page.[^246] A Spanish-language version of the
["Grants and Federal Domestic Assistance"
page](http://housenet.house.gov/portal/server.pt?open=18&objID=600&parentname=CommunityPage&parentid=20&mode=2&in_hi_userid=2&cached=true)
is also available.

[]{#__RefHeading___Toc216010014 .anchor}**Graphics** *see also
Alignment; Backgrounds; Banners; Centering; Colors; Favicons; Layout
#(5); Lists #(1); Multimedia files and Audio files; Navigation #(6);
Photo Albums; and Tools for Validating Web Sites #(4)*

(1) Optimize graphics to cut download time.
    [GIFBot](http://www.netmechanic.com/GIFBot/optimize-graphic.htm) is
    an easy to use graphics optimizer from NetMechanic that works with
    JPGs as well as GIFs.

(2) Where a small graphic will communicate as well as a large graphic,
    use the smaller graphic. Also consider using thumbnails that link
    large versions of the image.

(3) Every graphic needs to include an "alt" attribute (or its
    equivalent).[^247] The "alt" attribute (or its equivalent) should
    convey the information that the graphic provides.

    a.  If the graphic includes text, the "alt" attribute (or its
        equivalent) should include that text (though, any abbreviations
        should be spelled out).

    b.  If the graphic conveys no information (e.g., it is purely
        decorative), then set the value of the "alt" attribute either to
        null (\"\") or to a single blank (\" \").

    c.  When using an "alt" attribute with a value that exceeds 100 to
        125 characters, also use a "longdesc" attribute.[^248]

    d.  Phrases such as "photo of" or "link to" should not be used as
        part of an "alt" attribute (or its equivalent).[^249] Likewise,
        the "alt" attribute (or its equivalent) should normally not
        state that it is being displayed because scripting, style
        sheets, or similar technologies are not being used.

    e.  Abbreviations should not be used in an "alt" attribute.

    f.  File names should not be used as the value of an "alt"
        attribute.[^250]

(4) Where a graphic consists principally of text, use actual text rather
    than an \<img\> graphic. Use style sheets to control size, color,
    background, positioning, etc. This approach maximizes accessibility,
    scalability, and download speed.[^251]

(5) It is recommended that headings (particularly on text-heavy pages
    that deal with multiple topics) be supplemented with relevant
    icons.[^252]

(6) Every \<img\> tag should either have a "width" attribute and a
    "height" attribute[^253] or should have the height and width set
    through style sheets.

(7) The width of borders around graphics should be set by style
    sheets,[^254] not by the "border" attribute of the \<img\>
    tag.[^255]

(8) When setting a buffer between a graphic and surrounding text, do not
    use the hspace or vspace attributes of the \<img\> tag -- instead
    use style-sheets.[^256]

(9) If an \<img\> tag has a "name" attribute, it should also have an
    "id" attribute with the same value.[^257] When assigning the value
    of an "id" (or "name") attribute use the purpose of the data that
    the attribute's tag relates to, not how the data is to be portrayed
    -- the "name" value should indicate function, not form. (For
    instance, "hotTopics" would be an appropriate value for an "id" or
    "name" attribute, but "whiteOnRed" would not be an appropriate
    value.)[^258]

(10) Graphics originally developed for (or originally paid for by) an
     election campaign should not be used on House websites.[^259]

(11) When modifying a graphic, it is normally best to conduct
     modifications in the following order:

     a.  red-eye correcting

     b.  blemishes and dark or shiny spots

     c.  color levels

     d.  color balance

     e.  brightness and contrast

     f.  shadows and highlighting

     g.  resizing

     h.  cropping

     i.  sharpening

     j.  saving

(12) When using Photoshop:

     -   **Red Eye:** avoid using the Red Eye tool (Shift-J) because it
         tends to be too extreme (turning dark gray whenever it finds
         any red). Instead, zoom in (Control-+) on the problem area. Use
         the Marquee select (Shift-M) or the Lasso select (Shift-L) to
         capture each eye (Shift-mousedrag to add to a selection,
         Alt-mousedrag to subtract from a selection). Use Hue/Saturation
         (Control-U) and attenuate the middle Saturation slider. Try
         darkening a little so you do not end up with gray eyes. Zoom to
         100% (double click the zoom tool) to see what it looks like
         within the entire image.

     -   **Blemishes, Dark Spots, and Shiny Spots:** use the spot
         healing brush (Shift-J). This works best on blemishes that are
         surrounded by the correct tonal value. Make your brush width 1½
         to 2 times the width of the blemish and click once over the
         blemish (the blemish should disappear). For areas with the
         correct tonal value only on one side of the blemish, use the
         healing brush. Alt-Select an area of the image that has the
         tonal value you want and then drag your mouse on the blemish.
         If the result is too harsh, then Edit-Fade immediately after to
         attenuate the effect. Alternatively, step backward and choose a
         different Mode, e.g., Screen, Lighten, or Darken. Another
         approach is to try Smear (Shift-R) to smooth out the result.

     -   **Levels:** use the Control-L function. The ideal curve for
         levels is a double bell curve tailing off at the edges of the
         window with the left tail at black; the right tail at white;
         and the center at gray. If there are peaks at the edges, there
         is too much contrast. If the curve does not reach the edges,
         then the contrast is too low.

     -   **Color Balance:** use Control-B. This is especially useful if
         the image is scanned or the flash was incorrectly set. Color
         balance is usually used to reduce the red in the midtones or
         highlights of an image or, conversely, to correct for overly
         sallow skin tone.

     -   **Brightness and Contrast:** use Image: Adjustments:
         Brightness/ Contrast. Avoid setting the brightness and contrast
         control above 20 or below -20.

     -   **Shadows and Highlights:** use Image: Adjustments: Shadow/
         Highlight. Once adjusting the shadows or highlights, it is
         usually necessary to readjust the color balance and or the
         brightness and contrast.

     -   **Resizing:** use "Bicubic" as the "Resample Image" value.

     -   **Text:** make sure that "Anti-Alias" is not set to
         "None".[^260]

(13) Except when absolutely necessary, spacer images should not be used
     for layout. Style sheets should be used to control layout.[^261]

(14) Each \<img\> tag should end with "/\>".[^262]

(15) When choosing graphics, make sure the image is appropriate for the
     text it is being associated with. For instance, on a page devoted
     to providing assistance to constituents, avoid using stern pictures
     of the Member.

[]{#__RefHeading___Toc216010015 .anchor}**Graphs** *see Charts and
Graphs*

[]{#__RefHeading___Toc216010016 .anchor}**Greek language material** *see
Babel Fish; Government Resources #(2); Language of Text: and Linking
#(14)*

[]{#__RefHeading___Toc216010017 .anchor}** Greetings**

(1) Member offices should consider having information on their website
    as to how a constituent can receive greetings from the Member to
    commemorate events of "public distinction" (e.g., graduation form
    high school or college; becoming an Eagle Scout; receiving U.S.
    citizenship; or election or appointment to public office).[^263]

(2) Member offices should consider having information on their website
    as to how a constituent can receive greetings from the President for
    important birthdays, anniversaries, and similar occasions.[^264]

[]{#__RefHeading___Toc216010018 .anchor}**Haitian-Creole language
material** [^265] *see Government Resources #(2); Language of Text: and
Linking #(14)*

[]{#__RefHeading___Toc216010019 .anchor}**Hawaiian language material**
[^266] *see Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216010020 .anchor}**hCard** *see Contact
Information and Techniques #(12)*

[]{#__RefHeading___Toc216010021 .anchor}**Headings** *see also
Alignment; Capital letters; Graphics #(5); Tables #(1); and Titles*

(1) Headings within a page should be coded with h tags (highest level
    being \<h1\>, second highest level \<h2\>, etc.). Use style sheets
    to set the typeface, bolding, font-size, alignment, etc. so that the
    result is both esthetically pleasing and consistent throughout the
    site.[^267]

(2) The words that convey the most information should be at the
    beginning of each heading -- preferably in the first two
    words.[^268]

(3) Headings should generally not exceed 60 characters.[^269]

(4) An "id" attribute should be associated with each heading so that
    links can go directly to that spot.

[]{#__RefHeading___Toc216010022 .anchor}**Hebrew language material**
*see Government Resources #(2); Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216010023 .anchor}**Hindi language material** *see
Government Resources #(2); Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216010024 .anchor}**Hmong language material** *see
Government Resources #(2); Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216010025 .anchor}**Homeland Security threat
index** *see also House Operating Status*

Offices with websites that display the Department of Homeland Security's
threat advisory icon should be encouraged to make use of the icon that
the automatically changes as the Department's threat index changes.
Instructions for using the icon on a website can be found at:

<http://listserv.gsa.gov/cgi-bin/wa.exe?A2=ind0303&L=EXPRESS-L&P=R2602&I=-3>
.

[]{#__RefHeading___Toc216010026 .anchor}** Homepage** *see also
Navigation #(1) and (9); and Privacy Policy #(2)*

(1) One of the primary goals of a Congressional website is to get
    constituents to return in the future. The first thing that most
    constituents will see, when they go to the office's site is the part
    of the homepage that will fit in a screen without scrolling
    down.[^270] It is strongly recommended that as much of that the
    initial screen be composed of fresh, frequently updated information
    as possible.[^271]

(2) Offices should be encouraged to either **(A)** not place the text of
    a welcome message on the homepage or **(B)** make the welcome
    message on the homepage very short (perhaps one or two sentences,
    with a link to a longer welcome message).[^272]

(3) Try to keep the homepage short.[^273]

[]{#__RefHeading___Toc216010027 .anchor}**Honorifics** *see Contact
Information and Techniques #(12)*

[]{#__RefHeading___Toc216010028 .anchor}**HOUSE.GOV Domain** *see also
Linking #(1)*

Every Web page that is part of a Member's website or a committee's
website must be in the HOUSE.GOV domain.[^274]

[]{#__RefHeading___Toc216010029 .anchor}**\<hr\> tags** *see also
Alignment; and Centering*

(1) Instead of using the "noshade" attribute or the "size" attribute in
    \<hr\> tags, use style sheets.[^275]

(2) Instead of using the "size" attribute in \<hr\> tags, use the
    "height" property in style sheets.[^276]

(3) Each \<hr\> tag should end with "/\>".[^277]

[]{#__RefHeading___Toc216010030 .anchor}**HTML** *see also Attributes;
and \<!DOCTYPE\> declarations*

(1) Use either the \<code\> tag[^278] or the \<pre\> tag to display HTML
    code on a Web page. The \<listing\>, \<plaintext\>, and \<xpm\> tags
    should not be used for this or any other purpose.[^279]

(2) Rather than using the "version" attribute of the \<html\> tag, place
    a \<!DOCTYPE\> declaration at the beginning of each page.[^280]

(3) There should be an \<html\> tag between the \<!DOCTYPE\> declaration
    and the \<head\> tag on each Web page. The \<html\> tag should
    include an xmlns=\"http://www.w3.org/1999/xhtml\" attribute, a
    "lang" attribute (indicating the primary language used on the Web
    page), and an "xml:lang" attribute (also indicating the primary
    language used on the Web page).[^281] For example, a Web page that
    is written primarily in American English should use: \<html
    xmlns=\"http://www.w3.org/1999/xhtml\" lang=\"en-US\"
    xml:lang=\"en-US\"\>

(4) Before publishing a new or revised website, at least some pages on
    the site should be validated through the W3C Markup Validation
    Service (<http://validator.w3.org/>).[^282] The service is free and
    will verify that all of the HTML coding is grammatically correct.

[]{#__RefHeading___Toc216010031 .anchor}**Hurricane Preparation
Information** *see Disaster Preparation Information*

[]{#__RefHeading___Toc216010032 .anchor}**Hyphenation** *see Word
Choice*

[]{#__RefHeading___Toc216010033 .anchor}**Ice Storm Preparation
Information** *see Disaster Preparation Information*

[]{#__RefHeading___Toc216010034 .anchor}**Icons** *see Favicons; and
Graphics*

[]{#__RefHeading___Toc216010035 .anchor}**Id attribute** *see also Forms
#(7) and (16); Frames and Iframes #(2); Graphics #(9); Headings #(4);
Image Maps #(1); Linking #(12); Name attribute; and Tables #(2)*

(1) When assigning a value of an "id" attribute, use the purpose of the
    data that the attribute's tag relates to, not how the data is to be
    portrayed -- the "id" value should indicate function, not form. For
    instance, "hotTopics" would be an appropriate value for an "id"
    attribute, but "whiteOnRed" would not be an appropriate value.[^283]

(2) No two tags on the same page may have the same "id" attribute.[^284]

[]{#__RefHeading___Toc216010036 .anchor}** Identity Theft Information**
*see also Consumer Protection Information*

(1) Member offices (and offices that deal with identity theft issues)
    should consider including identity information on their website. The
    Federal Trade Commission's September 2007 *For the Consumer:
    Congressional Outreach Projects Using FTC Resources*, sites as
    examples the identity theft pages of the following Congressional
    offices: [Rep. Neil
    Abercrombie](http://www.house.gov/abercrombie/consumers.shtml),
    [Rep. Melissa
    Bean](http://www.house.gov/bean/en.us.identitytheft.shtml), [Rep.
    Mike Honda](http://honda.house.gov/faq_cs-identitytheft.shtml),
    [Rep. Darlene
    Hooley](http://hooley.house.gov/index.asp?Type=B_BASIC&SEC={5490FE28-836C-4BBE-965A-FF9AB19F8089}),
    [Rep. Todd
    Platts](http://www.house.gov/platts/services/online.shtml), [Sen.
    Herb Kohl](http://kohl.senate.gov/pri_cons_id.html), and [Sen. Joe
    Lieberman](http://lieberman.senate.gov/services/center/indentitytheft.cfm).

(2) When linking to identity theft Web pages from the Federal Trade
    Commission, consider using one of the icons available at
    <http://www.ftc.gov/ftc/consumer/partners_buttons.shtm>.

[]{#__RefHeading___Toc216010037 .anchor}**Iframes** *see Frames and
Iframes*

[]{#__RefHeading___Toc216010038 .anchor}**Image Maps** *see also Maps
and Directions #(2)*

(1) If a \<map\> tag has a "name" attribute, it should also have an "id"
    attribute with the same value [^285] When assigning the value of an
    "id" (or "name") attribute use the purpose of the data that the
    attribute's tag relates to, not how the data is to be portrayed --
    the "name" value should indicate function, not form. (For instance,
    "hotTopics" would be an appropriate value for an "id" or "name"
    attribute, but "whiteOnRed" would not be an appropriate
    value.)[^286]

(2) Do not use server-side image maps if the same functionality can be
    provided using client-side image maps.[^287] (Client-side image maps
    have a "usemap" attribute in the \<img\> tag. Server-side image maps
    have an ismap=\"ismap\" attribute[^288] in the \<img\> tag.) If the
    same functionality cannot be provided using client-side image maps,
    provide an equivalent text link for each active region in the
    server-side image map.[^289]

(3) Every \<area\> tag should have an "alt" attribute.[^290]

(4) Each \<area\> tag should end with "/\>".[^291]

[]{#__RefHeading___Toc216010039 .anchor}**Images** *see Favicons;
Graphics; and Photo Albums*

#  Immigration 

(1) []{#OLE_LINK4 .anchor}The Immigration and Naturalization Service was
    abolished March 2003 and its service and benefits functions were
    transferred to the newly created [U.S. Citizenship and Immigration
    Services](http://www.uscis.gov/). The law enforcement functions on
    the INS were moved to the newly created [U.S. Immigration and
    Customs Enforcement](http://www.ice.gov/). Both USCIS and ICE are
    agencies within the Department of Homeland Security.[^292] House
    websites should, therefore, not contain references to INS, except in
    a historical context.[^293]

(2) U.S. Citizenship and Immigration Services reorganized its website on
    November 1, 2006. USCIS non-homepage links added to House websites
    before November 1, 2006, should be checked to make sure they are
    still valid links. A list of frequently accessed pages is available
    at:

> <http://www.uscis.gov/files/pressrelease/WebFactSheet_110106.pdf>

**\<input\> tags** *see Forms*

[]{#__RefHeading___Toc216010042 .anchor}** Internships**

(1) Each office that sponsors internships should be encouraged to
    include information (on their website) as to how to apply, as well
    as a description of the duties and responsibilities (see, e.g., the
    website of the late [Rep. Juanita
    Millender-McDonald](http://web.archive.org/web/20060303181054/www.house.gov/millender-mcdonald/internships.htm)).[^294]

(2) The Internships page should be linked to from both the Constituent
    Services page and from the Kid's page.

[]{#__RefHeading___Toc216010043 .anchor}** Issues and Voting
Information** *see also Dates, Time, and Timeliness #(2); Legislative
Material; Navigation #(5); and WIDA #(3)*

(1) Offices should be encouraged to have a section of their website
    devoted to the Member's stands on issues.[^295]^,^ [^296]

(2) Member offices are encouraged to have a portion of their website
    devoted to the Member's voting record.[^297]

> To implement this recommendation, Member offices are urged **not** to
> simply link to the "Legislation & Votes" page[^298] on the website of
> the Clerk of the House. The Clerk's Legislation & Votes page includes
> much more information than just roll call votes and does not include
> an explanation of how to understand the roll call vote information.
>
> As an alternative to simply linking to the Clerk's "Legislation &
> Votes" page, it is recommended that Member office websites have a page
> (or at least part of a page) devoted to roll call votes and that that
> page include at a minimum links that go directly to the roll call vote
> information of each of the sessions of the current Congress and
> Session[^299], as well as a link to the roll call vote information for
> any relevant previous Congresses and Sessions. For example,

-   roll call votes of the 110^th^ Congress, 1^st^ session -
    <http://clerk.house.gov/evs/2007/index.asp>

```{=html}
<!-- -->
```
-   roll call votes of the 109^th^ Congress, 2^nd^ session -
    <http://clerk.house.gov/evs/2006/index.asp>

> Beyond these links, consider also[^300] providing an explanation of
> how to read the roll call vote information.[^301] [Rep. Steve Israel's
> web
> site[^302]](http://israel.house.gov/?sectionid=53&sectiontree=4,53)
> contains an explanation of the Clerk's layout that other offices may
> want to adopt (a similar explanation is also available on the Library
> of Congress' [Thomas web
> site](http://thomas.loc.gov/home/votes/votehelp.html)).
>
> [Rep. Maurice Hinchey](http://www.house.gov/hinchey/issues/vote.shtml)
> includes links to the appropriate pages of the Clerk's and Library of
> Congress' web sites, but also uses WIDAinc to provide material on roll
> call votes of particular interest.[^303] If setting out information on
> roll call votes of particular interest, consider organizing them in
> issue order, rather than just in bill number order.[^304]

(3) Where there are issues (or legislation) that the Member is
    particularly invested in, the office should be urged to make part of
    the website into a substantial source of information on the issues
    (or legislation).[^305]

(4) Where the Member has made floor statements (or issued press
    releases) on an issue that is included in the issues section of
    their website, include a link to the text of each relevant statement
    (and press release).[^306]

(5) Where the website deals with both issues and services that are
    related to each other (e.g., a page on legislation dealing with
    veterans and a page on veterans' benefits), make sure each one has a
    link to the other.[^307]

[]{#__RefHeading___Toc216010044 .anchor}**Italian language material**
*see Babel Fish; Government Resources #(2); Language of Text: and
Linking #(14)*

[]{#__RefHeading___Toc216010045 .anchor}**Italics**

(1) Where italics would be appropriate on a visual display, use \<em\>
    tags, not \<i\> tags. [^308]

(2) When using the name of a publication that would normally be
    italicized, consider using \<cite\> tags.

[]{#__RefHeading___Toc216010046 .anchor}**Japanese language material**
*see Babel Fish; Government Resources #(2); Language of Text: and
Linking #(14)*

[]{#__RefHeading___Toc216010047 .anchor} **Jargon**

Avoid using jargon, as it may confuse or alienate constituents.[^309]

[]{#__RefHeading___Toc216010048 .anchor}**JavaScript** *see Forms #(13)
and (14); Navigation #(12); and Scripts*

[]{#__RefHeading___Toc216010049 .anchor}** Job Opportunities**

Consider providing information on job opportunities (see, e.g., Rep.
Doolittle's "[Federal Job
Postings](http://doolittle.house.gov/ConstituentServices/jobpostings.htm)"
page).[^310] Possible information sources include:

(1) [USAjobs](http://www.usajobs.opm.gov/) -- the official site for
    posting Federal Executive Branch job announcements. (In particular,
    consider linking to a URL within USAjobs that brings up the
    announcements for Federal jobs within the Member's state.)[^311]

(2) [U.S. House of Representatives' employment opportunities
    page](http://www.house.gov/cao-hr/).

[]{#__RefHeading___Toc216010050 .anchor}**Judicial Branch** *see
Government Resources #(1)*

[]{#__RefHeading___Toc216010051 .anchor}** Kids' pages**

(1) COPPA (the Children's Online Privacy Protection Act of 1998)[^312]
    provides extensive requirements for websites (or Web pages) aimed at
    pre-teenage children that request personal information[^313]. The
    requirements include getting parental consent before collecting,
    using, or disclosing personal information from children.[^314] The
    easiest way to comply with the Act is to not ask for personal
    information (including first or last names, postal addresses, e-mail
    addresses, or telephone numbers) on Web pages aimed at
    children.[^315]

(2) The primary audience of a kids' page is different than the primary
    audience of most other pages on a House website. Kids pages should
    be kid friendly (see, e.g., [Rep. Henry Hyde's kid's
    zone[^316]](http://web.archive.org/web/20060207113128/www.house.gov/hyde/KidsZone.htm)
    -- the basic content for this page is now available as a server-side
    include on the HIR Unix Web server that the CAO-Web Solutions Branch
    is now maintaining[^317]).[^318]

(3) When practical, organize kid resources by grade level. See, e.g.,
    the "[Kids](http://www.house.gov/mike-rogers/kids.shtml)" page of
    Rep. Mike Rogers of Alabama.[^319]

[]{#__RefHeading___Toc216010052 .anchor}**Korean language material**
*see Babel Fish; Government Resources #(2); Language of Text: and
Linking #(14)*

[]{#__RefHeading___Toc216010053 .anchor}**\<label\> tags** *see Forms*

[]{#__RefHeading___Toc216010054 .anchor}**Language of Text** *see also
Babel Fish; Government Resources #(2); Linking #(14); and Word Choice*

(1) The language codes used in HTML tags should conform to the [RFC
    4646](http://www.rfc-editor.org/rfc/rfc4646.txt) standard.
    Instructions for using the standard are set out in Appendix 5:
    *Language Identification Codes* of this document.

(2) The primary language of each page should be identified[^320] with
    the appropriate attributes of the \<html\>, \<meta
    name=\"DC.language\"\>, **and** \<meta
    http-equiv=\"Content-Language\"\> tags:

    a.  In the \<html\> tag, use the "lang" attribute and the "xml:lang"
        attribute to identify the primary language of the page. For
        instance, on a page where English (as used in the United States)
        is the primary language, the \<html\> tag should be:

> \<html xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en-US\"
> lang=\"en-US\"\>

b.  In both the \<meta name=\"DC.language\"\> tag and the \<meta
    http-equiv=\"Content-Language\"\> tag, use the "content" attribute
    to identify the primary language of the page. For instance, on a
    page where English (as used in the United States) is the primary
    language, the tags should be:

> \<meta name=\"DC.language\" scheme=\"DCTERMS.RFC4646\"
> content=\"en-US\" /\>
>
> \<meta http-equiv=\"Content-Language\" content=\"en-US\" /\>

(3) When the language on a page changes, the change should be
    identified[^321] by using the "lang" attribute and "xml:lang"
    attribute[^322] in the HTML tags surrounding the text. For instance,
    on a page that is primarily in English, but includes in Spanish (as
    used in Puerto Rico) the phrase

> Subcomité Congresional Aprueba Proyecto de Ley de Fortuño
>
> the phrase could be coded as
>
> \<span **lang**=\"es-PR\" **xml:lang**=\"es-PR\"\>Subcomit&#233;
> Congresional Aprueba Proyecto de Ley de Fortu&#241;o\</span\>

[]{#__RefHeading___Toc216010055 .anchor}**Lao language material** *see
Government Resources #(2); Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216010056 .anchor}**Law references** *see U.S.
Code*

[]{#__RefHeading___Toc216010057 .anchor}**Layout** *see also Margins and
Padding; Style Sheets; and Tables #(3)*

> **(1)** Where practical, font sizes, margins, widths, heights, and
> other similar measure values (for material that will be displayed on a
> screen)[^323] should be specified in ems or percentages, not in
> points, picas, centimeters, inches, or pixels.[^324]

(2) Web pages should be sufficiently scalable that a horizontal scroll
    bar should not be necessary at 800 x 600 screen resolution.[^325]
    Completely liquid layout that is scalable to all screen resolutions
    is highly desirable.

(3) Offices should be encouraged to fill at least two-thirds of each Web
    page with substantive material.[^326]

(4) When developing a website (or page) where final content is not yet
    available, it is sometimes useful to use dummy content to be able to
    make an informed judgment as to how the site will look.[^327] When
    using dummy text during development, however, it is important to
    make sure that it is all removed before the site is published.
    Failure to remove dummy text may result in the office being
    embarrassed if the press is the first to discover the error.[^328]
    Before publishing a website, it is good practice to search the text
    of the site for such words as "dummy", "test", and "ipsum".[^329]

(5) Rather than using 90° angles exclusively, consider also using
    rounded corners. Sample coding for this, using style sheets, is set
    out in Trenton Moss's "[CSS and Round Corners: Build Boxes with
    Curves](http://www.sitepoint.com/article/css-round-corners-boxes-curves)"
    Sitepoint, March 18, 2005.

(6) Material that is particularly time-sensitive should be "above the
    fold" (i.e., it should be on the portion of the screen that a user
    sees without having to use a scroll bar).

(7) To maximize flexibility, it is recommended that the main content on
    each Web page should be preceded by "\<!\--\~!CMB\--\>" and the end
    of the main content on each page should be followed with
    "\<!\--\~!CME\--\>".[^330] The \<!\--\~!CMB\--\> and
    \<!\--\~!CME\--\> tags should **not** be part of server-side
    includes (or their equivalents).

[]{#__RefHeading___Toc216010058 .anchor}**Legal citations** *see U.S.
Code*

[]{#__RefHeading___Toc216010059 .anchor}**\<legend\> tags** *see
Alignment*

[]{#__RefHeading___Toc216010060 .anchor}** Legislative Material** *see
also Committee assignments and Caucus memberships; Dates, Time, and
Timeliness #(2); Issues and Voting Information; Jargon; and U.S. Code*

(1) Offices should be encouraged to include links to:

-   Legislation sponsored (or co-sponsored) by the Member[^331]^,^
    [^332] (in the case of committee websites, link to legislation
    referred to the committee)[^333]

-   Current House Floor Proceedings[^334]^,^ [^335]

-   Weekly House Program[^336]^,^ [^337]

-   Annual House calendar (available as a server-side include or as an
    iframe)[^338]

-   Majority and/or Minority Whip materials: [^339]

    -   Majority Leader's Daily Leader report[^340]

    -   Majority Leader's Weekly Leader report [^341]

    -   Majority Whip's daily WhipLine[^342]

    -   Majority Whip's House calendar[^343]

    -   Republican Whip's daily Whipping Post[^344]

    -   Republican Whip's weekly Whip Notice[^345]

    -   Republican Whip's calendar[^346]

-   Legislation: bills and resolutions[^347]^,^ [^348]

-   Congressional Record[^349]^,^ [^350]

    -   About the Congressional Record[^351] (prepared by the Library of
        Congress)[^352]

-   Committee reports[^353]

-   Committee hearings[^354]^,^ [^355]

-   *How Our Laws Are Made*[^356]^,^ [^357]^,^ [^358]

-   House Rules and Precedents[^359]^,^ [^360]

(2) Offices should be encouraged to have a description of how
    legislation becomes law.[^361] If the office does not have its own
    text for this, they should be encouraged to use the text from the
    [House's "Legislative Process"
    page](http://www.house.gov/house/Tying_it_all.shtml).[^362]

(3) Links to legislation, legislation sponsored by the Member, the
    Congressional Record, committee reports, and the [annual House
    schedule](http://www.house.gov/house/House_Calendar.shtml), should
    include links from the current year.[^363]

(4) References to specific bills (either by name or by number) should be
    linked either to information on the website explaining the bill or
    to the appropriate page in the Library of Congress Thomas
    System.[^364]^,^ [^365] Links **should not** be to Web pages in the
    Library of Congress' Legislative Information System (LIS)[^366]
    because it is only accessible to congressional offices.

[]{#__RefHeading___Toc216010061 .anchor}**Library of Congress products**
*see Congressional Research Service products; Legislative material #(4);
and Veterans #(2)*

[]{#__RefHeading___Toc216010062 .anchor}**Linking** *see also
Biographies #(1); Business Assistance; Committee Assignments and Caucus
memberships; Contact Information and Techniques #(12); District
Information #(2); Forms #(c); Grants and Federal Domestic Assistance;
Graphics #(2); Issues and Voting Information #; Legislative Material;
Lists #(3); Maps and Directions #(2); \<meta\> tags and \<link\> tags;
Multimedia files and Audio files; Navigation; PDF files; Privacy Policy;
Student Financial Aid; Underlining #(2); U.S. Code; Visiting Washington;
and WIDA*

(1) Any hypertext link to a Web page that is not part of either
    HOUSE.GOV or LOC.GOV needs to have an exit message indicating that
    you are leaving the House of Representatives and that neither the
    office nor the House is responsible for the content of the site
    being linked to.[^367] Instructions for adding such a message are
    available at HouseNet → Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance/) → HTML
    Scripts & Products → Exit Message to External Web Sites. Offices
    using the HIR-supplied exit should be encouraged to establish an
    \@leave_site file to retain their site's look and feel when
    generating the exit message.[^368]

(2) Rather than linking to other sites, offices should be encouraged to
    provide material within their own website.[^369]

(3) Except where they point to an \<iframe\>, "target" attributes should
    not be used in \<a\> tags unless there is a substantial reason to
    have them.[^370]^,^ [^371] (One of the relatively rare instances
    when there is a substantial reason to use a "target" attribute is
    the link to an outside page that provides information that will be
    used to fill out a form -- for example, a link to the U.S. Postal
    Service's [Zip Code Lookup
    page](http://zip4.usps.com/zip4/welcome.jsp) when it is used to find
    a nine-digit zip code for a form that needs zip+4.)

(4) Avoid having pages that are primarily just lists of links. Also,
    avoid making pages that have "links" as part of the name of the
    page. Rather than "links", make the emphasis "information" or
    "resources" or a similar description. Where possible, include a
    sentence or short paragraph explaining each link (or each group of
    links).[^372]

(5) Do not use "link to," "click here," or similar phrases in the text
    of links.[^373]

(6) The text of each link should provide enough information that a
    person who has only the text of the link can have a good idea what
    information the link will link to. If it is not practical to provide
    that information in the link, then the information should be
    contained in a "title" attribute of the link's \<a href\> tag.[^374]

(7) When linking to the next file in a series of files designed to be
    viewed in a particular order (e.g., in a photo gallery slide show),
    use "rel" and "rev" attributes in the \<a href\> tag.[^375] The
    "rel" attribute specifies the relationship between the current page
    and the page (or internal anchor) being linked to. The values most
    frequently used[^376] with the \<a href\> tag, are "next" and "prev"
    -- next is used with a link to the next document in the series, and
    "prev" is used to link to the previous document in the series.[^377]
    A special case is the first document in a series: this gets the
    value "start".[^378]^,^ [^379] The "rev" attribute functions the
    same way as the "rel" attribute, except it specifies the
    relationship from the file being linked to the file being linked
    from (rather than the other way around).[^380]

(8) The color of links should be set by style sheets[^381] and not by
    the "alink," "link," or "vlink" attributes of the \<body\>
    tag.[^382]

(9) The colors used for hypertext links should be consistent throughout
    the site.[^383]

(10) The color of each link should make it clear as to whether the
     visitor has visited the link yet or not -- therefore visited links
     should be a different color that links that have not yet been
     visited, and the colors should be sufficiently different that they
     can be easily told from one another.[^384]

(11) Links should look like links.[^385] Where text is used as a link,
     it should be underscored -- whether the link has been visited or
     not (it is not necessary to keep the underscore on a link that is
     currently being hovered over).

(12) The larger the link area, the easier it is to use.[^386]

(13) If an \<a\> tag has a "name" attribute, it should also have an "id"
     attribute with the same value.[^387] When assigning the value of an
     "id" or "name" attribute use the purpose of the data that the
     attribute's tag relates to, not how the data is to be portrayed --
     the "name" value should indicate function, not form. (For instance,
     "hotTopics" would be an appropriate value for an "id" or "name"
     attribute, but "whiteOnRed" would not be an appropriate
     value.)[^388]

(14) When linking to a Web page that has a primary language[^389] that
     is different from the primary language of the current page, include
     an "hreflang" attribute[^390] in the \<a href\> tag that created
     the link.[^391]

(15) An \<a\> tag should not be nested within another \<a\> tag.[^392]

[]{#__RefHeading___Toc216010063 .anchor}**\<listing\> tags** *see HTML*

[]{#__RefHeading___Toc216010064 .anchor}**Lists**

(1) In unordered lists:

```{=html}
<!-- -->
```
(a) Consider using a graphic or a typographic symbol other than the
    default (see, e.g., [Rep. Trent Frank's "Awards"
    page](http://www.house.gov/franks/awards.shtml)).[^393]

(b) When using graphics as bullets, use \<ul\> and \<li\> tags with the
    Cascading Style Sheets "list-style-image" property.[^394]

(c) When specifying a typographic symbol to be used as a bullet (e.g.,
    circle (○) or square ()), use the style sheets "list-style-type"
    property; and do not use the "type" attribute of the \<li\> or
    \<ul\> tags. Likewise, when specifying the style of the numbering in
    an ordered list (e.g., Arabic numerals, Roman numerals, lower case
    letters, or upper case letters), use the style sheets
    "list-style-type" property; and do not use the "type" attribute of
    the \<li\> or \<ol\> tags.[^395]

```{=html}
<!-- -->
```
(2) The words that convey the most information should be at the
    beginning of each item in a list -- preferably in the first two
    words.[^396]

(3) Lists of links can be boring and convey the (potentially false)
    impression that your website is not rich in content. Instead of
    presenting lists of links, consider inserting a sentence (or short
    paragraph) with each that explains what it is about.[^397]

(4) Lists should be in alphabetical order, unless there is a reason to
    organize them in a different manner.[^398]

(5) The \<ul\> tag should be used instead of the \<dir\> tag or the
    \<menu\> tag.[^399]

(6) The "compact" attribute of the \<li\>, \<ol\>, and \<ul\> tags
    should not be used.[^400]

(7) Ideally, the "counter-reset" property of style sheets should be used
    (rather than the "start" attribute of the \<ol\> tag or the "value"
    attribute of the \<li\> tag) to change the numbering in an ordered
    list.[^401] Note, however, Internet Explorer 6.0 does not support
    the "counter-reset" property.[^402]

[]{#__RefHeading___Toc216010065 .anchor}** Listserv and E-Newsletters**
*see also Contact Information and Techniques #(2)*

(1) Offices with electronic newsletters should be encouraged to use the
    HIR Listserv service to maintain their subscriber lists.[^403]

(2) Forms to subscribe to an e-newsletter should ask for either (1) just
    the subscriber's e-mail address; or (2) just the name and e-mail
    address of the subscriber.[^404]

(3) Forms to subscribe to an e-newsletter should indicate (or link to a
    page that indicates) what potential subscribers can expect to get if
    they subscribe (e.g., expected frequency, size, and subjects).[^405]

(4) Where a form uses a checkbox or radio button to subscribe to an
    e-newsletter, the box (or radio) button **is not** to be pre-set to
    "subscribe".[^406]

[]{#__RefHeading___Toc216010066 .anchor}**Load time** *see Download
Time*

[]{#__RefHeading___Toc216010067 .anchor}**Lorem Ipsum** *see Layout
#(4)*

[]{#__RefHeading___Toc216010068 .anchor}**\<map\> tags** *see Image
Maps*

[]{#__RefHeading___Toc216010069 .anchor}** Maps and Directions** *see
also Image Maps; Navigation #(8)*

(1) Consider including maps and directions to the office's district and
    Washington offices.[^407]

(2) Include in each Member site, a map of the Member's district.[^408]
    Where the map shows towns, counties, and other sites, it is
    recommended that the references to those localities on the district
    map be made into links[^409] to either those localities'
    websites[^410] or (preferably) into links to pages on the Member's
    website that provide information about the locality and include a
    link to the locality's website.[^411]

[]{#__RefHeading___Toc216010070 .anchor}**Margins and Padding** *see
also Alignments; Centering; and Layout*

(1) With all block elements (\<div\>, \<p\>, etc.) consider specifying
    the style sheet "margin" and "padding" properties, since different
    browsers provide different default values for these two properties.

(2) To eliminate any default margins that a browser may place around the
    edges of a Web page, rather than using

> \<body leftmargin=\"0\" marginwidth=\"0\" topmargin=\"0\"
> marginheight=\"0\"\>
>
> use the following style sheet properties with the \<body\> tag:
>
> margin:0;
>
> padding:0;
>
> The "marginwidth" and "marginheight" attributes are proprietary
> attributes for Netscape. The "leftmargin" and "topmargin" attributes
> are proprietary attributes for Internet Explorer. None of those four
> attributes are compliant with the W3C XHTML 1.0 (2^nd^ edition)
> standard.[^412] The style sheet \"margin:0; padding:0;\" properties,
> on the other hand, are W3C CSS and WCAG[^413] compliant.

(3) Rather than using the "margin-top", "margin-right", "margin-bottom",
    or "margin-left" style sheet properties, use the "margin"
    property.[^414]

(4) Rather than using the "padding-top", "padding -right", "padding
    -bottom", or "padding -left" style sheet properties, use the
    "padding" property.[^415]

[]{#__RefHeading___Toc216010071 .anchor}**Mastheads** *see Banners*

[]{#__RefHeading___Toc216010072 .anchor}**Meeting with Member** *see
Contact Information and Techniques #(4)*

[]{#__RefHeading___Toc216010073 .anchor}**\<menu\> tags** *see Lists
#(5)*

[]{#__RefHeading___Toc216010074 .anchor}**\<meta\> tags and \<link\>
tags**

(1) To the extent practical, each page of a House website should include
    the meta data tags set out in Appendix 4: *\<meta\> and Related
    Tags* of this document.[^416]

(2) Each \<link\> and \<meta\> tag should end with "/\>".[^417]

[]{#__RefHeading___Toc216010075 .anchor}** Military (Active Duty,
Reserves, and National Guard)** *see District Information #(5); Service
Academy Nominations; and Veterans*

Member offices (and other House offices that have constituencies in the
armed services)[^418] should be encouraged to include a page(s) on their
website devoted to military benefits. See, e.g., the "[Active Duty,
Reserves, National
Guard](http://drake.house.gov/militaryservices/ad.htm)" page of Rep.
Thelma Drake's website[^419] and Rep. Rush Holt's "[Guard and
Reserves](http://holt.house.gov/NationalGuard.shtml)" page.

[]{#__RefHeading___Toc216010076 .anchor}** Missing and Exploited
Children**

Member offices should consider including a link to their state's page
from the National Center for Missing and Exploited Children.[^420]

[]{#__RefHeading___Toc216010077 .anchor}**MP3 files** *see Multimedia
files and Audio files*

[]{#__RefHeading___Toc216010078 .anchor}** Multimedia files and Audio
files** *see also Banners #(3); Graphics; and \<object\> tag #(3)*

(1) In Member websites, consider including multimedia files of the
    Member's floor speeches.[^421]

(2) Links to audio files and multimedia files, when practical, should
    indicate the size of the files and their playing time.

(3) Any page that links to a multimedia file (or an audio file) should
    include access to software that allows the file to be
    accessed.[^422] One technique for doing this is to include a link on
    each page to a "tool box" page on the site that contains links to
    the software.[^423] Multimedia players are available at:

    -   Quick Time = <http://www.apple.com/quicktime/download/win.html>

    -   Real Player = <http://www.real.com/>

    -   VLC Media Player = <http://www.videolan.org/vlc/>

    -   Windows Media Player =
        <http://www.microsoft.com/downloads/Browse.aspx?displaylang=en&categoryid=4>

> Note that if any of the links to the software point to a non-House of
> Representatives website, an appropriate exit message needs to be
> given.[^424]

(4) Files that include audio need to provide access to a written
    transcript.[^425]

(5) Whenever possible, multimedia files that include audio should have
    closed captioning that coordinates a transcript of the words with
    the action. Where closed captioning is not available, the transcript
    needs to use some other technique to coordinate the words with the
    action in order to comply with § 508 of the Rehabilitation
    Act.[^426]

(6) To provide accessibility to persons who are both blind and deaf,
    transcripts (accessible, for instance, through a refreshable Braille
    display) should be audio described, i.e., they should include a
    description of any actions depicted in the visuals.[^427]

(7) When embedding a multimedia file that calls up a viewer (e.g.,
    Windows Media Viewer for .wmv files), include instructions as to how
    to activate and control the viewer.[^428]

(8) Avoid using auto-loading multimedia files where the user does not
    have advance notice that the file will load.[^429]

(9) Rather than using an \<a href\> tag to link directly to a .wmv (or
    similar) file directly (and thereby spawning a new window for the
    multimedia plug in),[^430] use an \<iframe\> (or similar technique)
    to have the viewer play on the current page. For examples, see the
    homepages of [Rep. Ron Klein](http://klein.house.gov/) and the
    [Immigration Reform Caucus](http://www.house.gov/bilbray/irc/).

[]{#__RefHeading___Toc216010079 .anchor}**Name attribute**

(1) With \<a\>, \<form\>, \<frame\>, \<iframe\>, \<img\>, or \<map\>
    tags, an "id" attribute should normally be used instead of a "name"
    attribute.[^431] If it is necessary to use a "name" attribute with
    these tags, then the tag should also have an "id" attribute with the
    same value.[^432]

(2) If it is necessary to use a "name" attribute, when assigning the
    value of the "name" attribute use the purpose of the data that the
    attribute's tag relates to, not how the data is to be portrayed --
    the "name" value should indicate function, not form. For instance,
    "hotTopics" would be an appropriate value for a "name" attribute,
    but "whiteOnRed" would not be an appropriate value.[^433]

[]{#__RefHeading___Toc216010080 .anchor}**National Guard** *see Military
(Active Duty, Reserves, and National Guard)*

[]{#__RefHeading___Toc216010081 .anchor}** Navigation** *see also
Accesskey attribute; Biographies #(3);Flags #(4); Linking; Printing;
Privacy Policy #(2); and RSS*

(1) When designing the main navigation, consider including navigation
    that targets audiences of particular interest to the office. See,
    e.g., [Mike Rogers of Alabama](http://www.house.gov/mike-rogers/)'s
    website,[^434] which targets military personnel, immigrants,
    seniors, small businesses, students, and veterans.[^435]^,^ [^436]

(2) The top banner should be a link to the homepage.[^437] The
    alternative of using the top banner as a skip-navigation link means
    that either

    -   the "alt" attribute of the image does not contain the text in
        the image (e.g., "Congressman Jones, representing the 39^th^
        district of Delaware"); or

    -   the "alt" attribute gives no indication where the link goes to.

> While it is possible that the "title" attribute in the \<a href\> tag
> could be used to indicate where the link is going, having conflicting
> "title" and "alt" attributes may be more complicated than assistive
> technology browsers can meaningfully process.
>
> Note: where background graphics constitute part of the banner, they
> should be part of the link to the home page.

(3) There needs to be a mechanism to allow users of assistive
    technologies to skip past the navigation links.[^438] One approach
    to this is placing a clear gif (with an "alt" attribute of "skip to
    main content") before the first navigation button and making the
    image a hypertext link to the first piece of text after the
    navigation links.[^439]

(4) At the bottom of the main content, consider having a link that goes
    back to the top of the main content.[^440]

(5) Labels on navigation links should be personal/friendly, e.g.,

-   "Where I Stand" (rather than "Issues")[^441]

-   "How I Voted"

-   "How Can I Help You" (rather than "Constituent Services" or
    "Casework")[^442]

-   "My Background" (rather than "Biography")

-   "Contact Me" (rather than "Contact" or "Send an electronic message")

-   "Our District" or "My District" (rather than "The Second District")

(6) Where practical, supplement navigation buttons (or links) with
    relevant icons.[^443] See, e.g., the website of [Rep. Jim
    Jordan](http://jordan.house.gov/).

(7) In addition to having navigation buttons across the top or down the
    side, each page should have a text-only version across the bottom of
    the page.[^444]^,^ [^445]

(8) Each web site should include a site map.[^446]

(9) Consider making the first primary navigation button a link to the
    site's homepage[^447]. The remaining navigation should be in
    alphabetical order, unless there is a reason not to do so.

(10) When the main content of a page is divided into multiple sections,
     consider having a jump menu near the top of the page and links to
     go back to the jump menu at the end of each section.

(11) The formatting of navigation links should be consistent throughout
     the site.[^448]

(12) JavaScripts, VBScripts, and other scripts should not be used as the
     exclusive way to navigate to the pages on the website.[^449] In
     addition to accessibility problems that this causes, many indexing
     spiders (including the indexing spider used by the House search
     engine) are not able to follow scripted links.

(13) Where a portion of a website is made up of several pages (or
     subportions, e.g., the "Issues" portion of a website which might
     consist of an introductory page and then separate pages for each
     issue), consider providing links to each of the subportions from
     each of the subportions.[^450]

(14) The navigation of a site should be designed with the goal that
     every page in the site is accessible from every other page in the
     site with no more than three clicks.[^451]

(15) Avoid using drop-down navigation that is activated (and only stays
     activated) on a mouse over (or hover) -- that type of navigation is
     difficult to use by people with motor and/or vision disabilities.
     Instead of using drop-down navigation that disappears when the
     cursor is moved, either (1) require a mouse click (or equivalent)
     to open or close the menu, or (2) replace the drop down with a link
     to a separate page that explains the options formerly contained in
     the drop-down.[^452]

[]{#__RefHeading___Toc216010082 .anchor}**Newsletters** *see Listserv
and E-Newsletters*

[]{#__RefHeading___Toc216010083 .anchor}**Numbers** *see Roman Numerals*

[]{#__RefHeading___Toc216010084 .anchor}**\<object\> tag**[^453] *see
also Alignment; \<applet\> tags; Banners #(3); Centering; \<embed\>*

*tags; and \<param\> tags*

(1) The width of borders around objects should be set by style
    sheets,[^454] not by the "border" attribute of the \<object\>
    tag.[^455]

(2) When setting a buffer between an object and surrounding text, do not
    use the hspace or vspace attributes of the \<object\> tag -- instead
    use style-sheets.[^456]

(3) When using an \<object\> tag to display a multimedia file, include a
    "type" attribute, e.g., type=\"video/x-ms-wmv\" for .wmv
    files.[^457]

[]{#__RefHeading___Toc216010085 .anchor}**Office Hours** *see Contact
Information and Techniques #(3)*

[]{#__RefHeading___Toc216010086 .anchor}**onBlur** *see Event Handlers*

[]{#__RefHeading___Toc216010087 .anchor}**onClick** *see Event Handlers*

[]{#__RefHeading___Toc216010088 .anchor}**onFocus** *see Event Handlers*

[]{#__RefHeading___Toc216010089 .anchor}**onKeyPress** *see Event
Handlers*

[]{#__RefHeading___Toc216010090 .anchor}**onMouseOut** *see Event
Handlers*

[]{#__RefHeading___Toc216010091 .anchor}**onMouseOver** *see Event
Handlers*

[]{#__RefHeading___Toc216010092 .anchor}**Op-eds** *see Articles and
Op-eds*

[]{#__RefHeading___Toc216010093 .anchor}**\<optgroup\> tags** *see
forms*

[]{#__RefHeading___Toc216010094 .anchor}**Padding** *see Margins and
Padding*

[]{#__RefHeading___Toc216010095 .anchor}** Page Program**

(1) Member offices should be encouraged to provide information about how
    to apply to become a Congressional Page.[^458] Offices may want to
    include a link to the Page Program website maintained by the Clerk
    of the House,[^459] or incorporate text from the site into their own
    site.

(2) The Page Program page should be linked to from both the Constituent
    Services page and from the Kid's page.

[]{#__RefHeading___Toc216010096 .anchor}**\<param\> tags**

Each \<param\> tag should end with "/\>".[^460]

[]{#__RefHeading___Toc216010097 .anchor}** Parents**

Member offices (and other House offices that deal regularly with
parents)[^461] should be encouraged to include a page(s) on their
website devoted to information for parents. See, e.g., the "[Parents and
Teachers](http://www.house.gov/mike-rogers/kids.shtml#pt)" section of
Rep. Mike Rogers of Alabama's "Kids" page. Note that this page may be
similar to the site's student information page -- but with the
information in an order oriented toward the needs of parents.[^462]

[]{#__RefHeading___Toc216010098 .anchor}**PDF Files**

(1) Links to PDF files, when practical, should indicate the size of the
    files.

(2) Any page that links to a PDF file should include a link to software
    that allows the file to be displayed.[^463] Note that if the link to
    the software points to a non-House of Representatives website, an
    appropriate [exit
    message](http://onlinecao.house.gov/webassistance/html/ht_exit_msg.htm)
    needs to be given.[^464]

(3) All input fields (including radio buttons and checkboxes) on a PDF
    should have a tooltip[^465] explanation of what information should
    be provided in the field.[^466]

(4) Each PDF file should include sufficient identifying material in its
    text so that it is clear to a viewer who arrived at the document
    through a search engine, what the document is.[^467]

[]{#__RefHeading___Toc216010099 .anchor}**Phone Numbers** *see Contact
Information and Techniques #(6)*

[]{#__RefHeading___Toc216010100 .anchor}** Photo Album** *see also
Linking #(7)*

(1) When setting up the layout for a photo album (or photo gallery)
    consider making it interactive, e.g., these models:

-   [Ath Slide JavaScripted Photo
    Gallery[^468]](http://www1.house.gov:801/mmiller2/photoplay/Ath_Slide.shtml)^,^
    [^469]

-   [Simple Slide Show Photo
    Gallery](http://www1.house.gov:801/mmiller2/photoplay/simpleslideshow.shtml)

-   [Hoverbox Photo
    Gallery](http://www1.house.gov:801/mmiller2/photoplay/hoverbox.shtml)

-   [Joshua Ink CSS Style Photo
    Gallery](http://www1.house.gov:801/mmiller2/photoplay/joshuaink.shtml)

-   [Leftish Photo
    Gallery](http://www1.house.gov:801/mmiller2/photoplay/leftish.shtml)

-   [Toppish Photo
    Gallery](http://www1.house.gov:801/mmiller2/photoplay/toppish.shtml)

-   [Lightbox2](http://www.huddletogether.com/projects/lightbox2/) (see,
    e.g., [Rep. Sheila Jackson Lee's photo
    gallery](http://jacksonlee.house.gov/photos.shtml) --- be sure to
    make the instructions keyboard oriented (using arrow keys), rather
    than mouse oriented[^470])

-   [SmoothGallery](http://smoothgallery.jondesign.net/what/)

(2) Consider dividing a Member's photo album into sections (including
    one devoted to recognizing constituents[^471]). See, for instance,
    Rep. Jeff Fortenberry's photo album which is divided into "[Working
    for
    Nebraska](http://fortenberry.house.gov/photos_washington.shtml)",
    "[Nebraska Breakfast
    Gallery](http://fortenberry.house.gov/photos_breakfast.shtml)", and
    "[Nebraska
    Visitors](http://fortenberry.house.gov/photos_visitors.shtml)".

[]{#__RefHeading___Toc216010101 .anchor}**Picas** *see Fonts #(2); and
Layout*

[]{#__RefHeading___Toc216010102 .anchor}**PICS (Platform for Internet
Content Selection)** *see \<meta\> tags and \<link\> tags*

[]{#__RefHeading___Toc216010103 .anchor}**Pixels** *see Fonts #(2); and
Layout*

[]{#__RefHeading___Toc216010104 .anchor}**\<plaintext\> tags** *see
HTML*

[]{#__RefHeading___Toc216010105 .anchor}**Points** *see Fonts #(2); and
Layout*

[]{#__RefHeading___Toc216010106 .anchor}**Polish language material**
*see Government Resources #(2); Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216010107 .anchor}**Political Language** *see also
Election Campaign material*

The [*Committee's Congressional
Handbook*](http://cha.house.gov/committee_handbook.aspx#content) (Web
Site Regulations, Content*,* § 1*)*, issued by the House Administration
Committee, provides that "The content of a Member's website: 1. May not
include personal, political, or campaign information."[^472] Some
offices have adopted the policy of not using words such as "elected" on
their website.

[]{#__RefHeading___Toc216010108 .anchor}** Polls and Surveys**

(1) Offices should consider including polls or surveys on their
    website[^473] See, e.g., the survey on the homepage of [Rep. Ray
    LaHood](http://www.house.gov/lahood/).

(2) When using the "real time results" in a form_proc-based survey, the
    survey pages (including the view results page) should reside in the
    HIR Unix Web server.

(3) Surveys should indicate when they started and when the most recent
    response was received. (See, e.g., the "See vote results" link on
    the website of [Rep. David
    Wu](http://www.house.gov/wu/index.shtml).)

(4) Offices should consider displaying the results of their surveys in
    graphic form (see, e.g., [Rep. David Wu](http://www.house.gov/wu/)'s
    "Vote Results" page).

[]{#__RefHeading___Toc216010109 .anchor}**Pop-up Windows**

Pop-up windows should not be used, unless there is a substantial reason
to have them.[^474] (One of the relatively rare instances when there is
a substantial reason to use a pop-up window is with a link to an outside
page that provides information that will be used to fill out a form --
for example, a link to the U.S. Postal Service's [Zip Code Lookup
page](http://zip4.usps.com/zip4/welcome.jsp) when it is used to find a
nine-digit zip code for a form that needs zip+4.)

[]{#__RefHeading___Toc216010110 .anchor}**Portuguese language material**
*see Babel Fish; Government Resources #(2); Language of Text: and
Linking #(14)*

[]{#__RefHeading___Toc216010111 .anchor}**Postal Abbreviations** *see
Abbreviations and Acronyms; and Forms #(12)*

[]{#__RefHeading___Toc216010112 .anchor}**Postal Addresses** *see
Contact Information and Techniques #(6) and #(12)*

[]{#__RefHeading___Toc216010113 .anchor}**\<pre\> tags**

Instead of using the "width" attribute in \<pre\> tags, use the style
sheets "width" property (with the value set in ems).[^475]

[]{#__RefHeading___Toc216010114 .anchor}**Presidential Greetings** *see
Greetings*

[]{#__RefHeading___Toc216010115 .anchor}**Press Releases** *see also
Biographies #(1); Issues and Voting Information #(4); and WIDA*

(1) Offices should be encouraged to have their press releases available
    on their website and to make them available in chronological order
    and in subject order.[^476]

(2) Offices should be encouraged to use
    [WIDA](http://housenet.house.gov/keywords/wida) for putting press
    releases on their site.

(3) Press releases should have the same navigation links and banner as
    the rest of the site.[^477]

[]{#__RefHeading___Toc216010116 .anchor}**Printing**

(1) Consider using a print style sheet that excludes the main navigation
    links and anything else that would not be relevant to a printed
    page.[^478] If the banner is going to be excluded, be sure to add
    substitute in at least the name of the office where the banner was.

(2) When specifying a serif font for screen display, consider specifying
    Times New Roman, rather than Georgia. When specifying a sans-serif
    font for screen display, consider specifying Arial, rather than
    Verdana. Georgia and Verdana were designed for screen display,
    whereas Times New Roman and Arial were designed for printing.[^479]

[]{#__RefHeading___Toc216010117 .anchor}**Privacy Act Release Form**
*see Constituent Services #(4)*

[]{#__RefHeading___Toc216010118 .anchor}** Privacy Policy and Cookies**
*see also Babel Fish*

(1) Every website should have its own page setting out its privacy
    policy, i.e., how the office handles personal information that the
    office receives through its website. In addition to having a privacy
    notice written in English, there should also be a machine-readable
    (P3P) version of the notice.[^480] A model privacy notice is set out
    in Appendix 6 of this document.

(2) Ideally, there should be a link to the office's privacy policy on
    every page of the website.[^481] At a minimum, the link should be in
    a clear and prominent place on the homepage and next to each form
    that requests personal information.[^482]

(3) Offices should be encouraged not to use cookies unless there is a
    "compelling need".[^483] If an office does use cookies, the office
    should be strongly encouraged to provide notice of this in their
    privacy policy.

(4) Links to a website's privacy policy are **not** required to include
    a rel=\"privacy\" attribute in the \<a href\> tag.[^484]

[]{#__RefHeading___Toc216010119 .anchor}**Pseudo-classes** *see Style
Sheets #(4)*

[]{#__RefHeading___Toc216010120 .anchor}**Punctuation** *see Apostrophes
and Quotation Marks; and Quotations #(1)*

[]{#__RefHeading___Toc216010121 .anchor}**Punjabi language material**
*see Government Resources #(2); Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216010122 .anchor}**Quotations** *see also
Apostrophes and Quotation Marks*

(1) Instead of using three periods to indicate an ellipsis (i.e., ". .
    ."), use the Unicode-compliant representation for an ellipsis:
    &#x2026;

(2) The \<blockquote\> tag should be used for all indented quotations
    and should not be used for any other purpose.[^485] Style sheets,
    not the \<blockquote\> tag, should be used to indent text that is
    not a quotation.[^486]

[]{#__RefHeading___Toc216010123 .anchor}**Reserves (Military)** *see
Military (Active Duty, Reserves, and National Guard)*

[]{#__RefHeading___Toc216010124 .anchor}**Reuse of Content** *see also
Browsealoud; Dates, Time, and Timeliness #(1); File Names and Extensions
#(1); Frames and Iframes; House Operating Status; Kids Pages #(2);
Legislative Material #(1)and (2); RSS(2); Veterans #(1); Visiting
Washington #(2); and WIDA #(5)*

(1) When an HTML page uses identical content in several places, consider
    using server-side includes, rather than Dreamweaver templates or
    libraries, or FrontPage Themes. Use of Dreamweaver templates or
    libraries (or use of FrontPage themes) requires that the entire site
    be loaded on to a local device in order to update content that is to
    be distributed throughout the site. With server-side includes, it is
    only necessary to have the one file being altered loaded on a local
    device.

(2) When using server-side includes, precede each include with a comment
    explaining the purpose of the include and follow each include with a
    comment indicating that that particular include has ended.

(3) Do not use \<!\--\~!CMB\--\> or \<!\--\~!CME\--\> tags within a
    server-side include.

[]{#__RefHeading___Toc216010125 .anchor}**Roman Numerals**

(1) Roman numerals should be preceded by an \<abbr\> tag with a "title"
    attribute that indicates the meaning of the numeral; and should be
    followed by a \</abbr\> tag. For instance

> World War \<abbr title=\"Two\"\>II\</abbr\>
>
> Pope John-Paul \<abbr title=\"the Second\"\>II\</abbr\>

(2) Some Roman numerals are not readily distinguishable from other Latin
    numbers. Roman numerals for the number 2, for instance, when
    displayed in a sans-serif font looks like a Latin eleven. To avoid
    this sort of confusion, consider always styling Roman numerals with
    a serif font family. The common match-ups between serif and
    sans-serif fonts are:

  ---------------------------------- ------------------------------------
  sans-serif                         serif

  Verdana                            Georgia

  Arial                              Times New Roman
  ---------------------------------- ------------------------------------

> For a more extensive list of serif/sans-serif match-ups, see Daniel
> Will-Harris' "Typefaces: that work together" at
> <http://www.will-harris.com/typepairs.htm>.

(3) The Roman numeral representations set out as 2160 to 217F (i.e.,
    &#x2160; to &#x217F;) in the Unicode 5.0 Standard,[^487] should not
    be used unless there is a substantial reason to do otherwise.[^488]

[]{#__RefHeading___Toc216010126 .anchor}**RSS**

(1) Offices using WIDA should be encouraged to make use of WIDA's RSS
    capability.[^489] This capability allows anyone who subscribes to
    your RSS feed to be automatically notified every time you add a new
    WIDA document to your website.[^490]

(2) If a website is using RSS, it is recommended that the site include a
    "What is RSS" page.[^491] CAO-Web Solutions Branch-maintained "What
    is RSS" text can automatically be inserted using a server-side
    include or by using an iframe.[^492] The "What is RSS" link should
    follow the links to the actual documents.

(3) The homepage of any website with RSS feeds (and any pages that lead
    to documents that are the subject of RSS feeds) should prominently
    include an icon (that links to the RSS.xml page) in one of the
    following formats:

```{=html}
<!-- -->
```
(a) ![](media/image9.png){width="0.2916666666666667in"
    height="0.2916666666666667in"} [^493]

(b) ![](media/image10.png){width="0.375in"
    height="0.14583333333333334in"} [^494]

(c) ![](media/image11.png){width="0.5833333333333334in"
    height="0.14583333333333334in"} [^495]

(d) ![](media/image12.png){width="0.375in"
    height="0.14583333333333334in"} [^496]

```{=html}
<!-- -->
```
(4) Each page that is part of a website that has RSS feeds should
    include (between the \<head\> and \</head\> tags), for each RSS
    feed, a \<link rel=\"alternate\" type=\"application/rss+xml\" /\>
    tag with a "title" attribute that describes the feed and an "href"
    attribute that has the URL for the RSS XML file, e.g., \<link
    rel=\"alternate\" type=\"application/rss+xml\" title=\"Headline news
    \[RSS\]\" href=\"http://www.house.gov/name/rss/news.xml\" /\>.[^497]

[]{#__RefHeading___Toc216010127 .anchor}**Russian language material**
*see Babel Fish; Government Resources #(2); Language of Text: and
Linking #(14)*

[]{#__RefHeading___Toc216010128 .anchor}**Samoan language
material**[^498] *see Government Resources #(2); Language of Text: and
Linking #(14)*

[]{#__RefHeading___Toc216010129 .anchor}**Schedule meeting with Member**
*see also Contact Information and Techniques #(4)*

[]{#__RefHeading___Toc216010130 .anchor}** Schedule of Member** *see
also Contact Information and Techniques #(4)*

Offices should be encouraged to provide highlights of the Member's
upcoming schedule on their website.[^499]^,^ [^500] (Consider laying
this information out calendar-style -- see, e.g., the calendar of the
[Committee on Natural Resources (Republican
Office)](http://republicans.resourcescommittee.house.gov/).

[]{#__RefHeading___Toc216010131 .anchor}**Scholarships** *see Student
Financial Aid*

[]{#__RefHeading___Toc216010132 .anchor}**Screen resolution** *see
Layout #(2)*

[]{#__RefHeading___Toc216010133 .anchor}**Scripts** *see also \<applet\>
tags; \<embed\> tags; Event Handlers; Forms #(13); Navigation #(12); and
\<object\> tags*

(1) Wherever there is a script that conveys information -- or where it
    conveys an important element of the website's design (e.g., when a
    script is used to present the website's banner) --, the \<script\>
    tag should be between the \<body\> tag and the \</body\> tag, and
    the \</script\> tag needs to be followed by:

```{=html}
<!-- -->
```
(a) \<noscript\>

(b) information that will displayed to users who are using browsers that
    are not supporting scripts (this information should be the
    equivalent of what constituents using browsers supporting scripts
    would have received -- it should be the information (or a link to
    it) and not merely a description of the information).[^501]

-   In the case of a script used to display multiple images, consider
    putting one of the graphics here. If appropriate, make that graphic
    a link to a separate page that displays all of the graphics.

-   When possible, the information displayed to users who are using
    browsers that are not supporting scripts **should not** state that
    the user is receiving this message because scripting is not being
    supported. What it normally should do is provide the best equivalent
    of the material that the user would have received if scripting was
    enabled.

(c) \</noscript\>

```{=html}
<!-- -->
```
(2) Every \<script\> tag should have a "type" attribute. Valid "type"
    attributes for \<script\> tags include, type=\"text/javascript\" and
    type=\"text/vbscript\". The "type" attribute performs the function
    that was previously performed by the "language" attribute -- the
    "language" attribute should not be used in \<script\> tags.[^502]

(3) Unless there is a substantial reason to do otherwise, scripts should
    not be used to open windows.[^503] (One of the relatively rare
    instances when there is a substantial reason to open a new window is
    to provide an outside page that provides information that will be
    used to fill out a form -- for example, to access the U.S. Postal
    Service's [Zip Code Lookup
    page](http://zip4.usps.com/zip4/welcome.jsp) when it is used to find
    a nine-digit zip code for a form that needs zip+4.)

[]{#__RefHeading___Toc216010134 .anchor}**Searching** *see also Banners
#(2); Dates, Time, and Timeliness #(3); File Names and Extensions #(3);
Legislative Material #(3); Navigation #(6) and (12); and PDF Files #(4)*

(1) Offices should be encouraged to include a [website search
    capability](http://housenet.house.gov/portal/server.pt?open=18&objID=602&parentname=CommunityPage&parentid=20&mode=2&in_hi_userid=2&cached=true)
    on all pages, in or near the top banner.[^504]

(2) Member websites that have a virtual URL should have the virtual URL
    on <http://www.house.gov/house/MemberWWW.shtml> - as that page
    provides the list of URL that are spidered for the HIR search
    engine.

(3) The \<isindex\> tag should not be used to create search boxes or for
    any other purpose.[^505] The \<form\> tag (along with \<input\>,
    \<textarea\>, and related tags) should be used to create search
    boxes.

(4) If the user is given the option of searching either (1) just the
    site or (2) a larger collection (e.g., all of the HOUSE.GOV domain
    or all of the Internet), then the default should be searching just
    the current site.[^506] See, e.g., the search box on [Rep. Jeff
    Fortenberry's website](http://fortenberry.house.gov/), where the
    default is "Search This Site".

[]{#__RefHeading___Toc216010135 .anchor}**\<select\> tags** *see Forms*

[]{#__RefHeading___Toc216010136 .anchor}**Server-side Includes** *see
Reuse of Content*

[]{#__RefHeading___Toc216010137 .anchor}** Service Academy
Nominations**

(1) Member offices should be encouraged to provide information about how
    to apply to apply for a nomination to a service academy.[^507]

(2) The Service Academy Nominations page should be linked to from both
    the Constituent Services page and from the Kid's (or Student's)
    page.

[]{#__RefHeading___Toc216010138 .anchor}**Site maps** *see Navigation
#(8)*

[]{#__RefHeading___Toc216010139 .anchor}**Skip-navigation links** *see
Accesskey attribute; and Navigation #(1) and (3)*

[]{#__RefHeading___Toc216010140 .anchor}**Small Businesses** *see
Business Assistance*

[]{#__RefHeading___Toc216010141 .anchor}**Social Bookmarking**

Office should consider including social bookmarks on their site.[^508]
Sample coding for social bookmarks is set out in Appendix 1 of this
document.

[]{#__RefHeading___Toc216010142 .anchor}**Social Security numbers**

Offices should not request that users of their website send Social
Security numbers by unsecured Web form or e-mail.[^509] Where an office
needs to have a Social Security number (e.g., for a Privacy Act release
form or for a White House tour request), use a secured form.[^510] If it
is not possible to use a secured form consider using a form that will
generate a document to be postal mailed (or faxed) to the office by the
person filling out the form -- see, e.g., [Rep. Neil Abercrombie's
casework authorization
form](http://www.house.gov/abercrombie/casework.shtml).

[]{#__RefHeading___Toc216010143 .anchor}**Spanish language
material**[^511] *see Babel Fish; Disaster Preparation Information;
Government Resources #(2); Grants and Federal Domestic Assistance;*
*Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216010144 .anchor}**Special Characters** *see
Character Entities*

[]{#__RefHeading___Toc216010145 .anchor}**Strike-through text**

Either style sheets[^512] or \<del\> tags, should be used to label
struck-through text. The \<s\> tag or \<strike\> tag should not be used
for this or any other purpose. [^513]

[]{#__RefHeading___Toc216010146 .anchor}** Student Financial Aid**

(1) Member offices (and other House offices that deal regularly with
    students, or with people who finance students)[^514], that are
    hosted on an HIR Web server should be encouraged to include the
    [CRS-maintained "Financial Aid for Students"
    page](http://housenet.house.gov/portal/server.pt?open=18&objID=600&parentname=CommunityPage&parentid=20&mode=2&in_hi_userid=2&cached=true)
    in their website. Offices not hosted on an HIR Web server should be
    encouraged to iframe the page.[^515]

(2) The Student Financial Aid page should be linked to from both the
    Constituent Services page and from the Kid's page.

[]{#__RefHeading___Toc216010147 .anchor}**Style Sheets** *see also Aural
Style Sheets; Browser Compatibility; Centering; File Names and
Extensions #(5); Fonts; Graphics #(4); Headings; Layout; Lists #(1);
Printing; Tables #(3); Tools for Validating Web Sites #(2); and
Underlining*

(1) websites need to be readable with style sheets turned off in order
    to comply with § 508 of the Rehabilitation Act.[^516]

(2) When using style sheets to create one or more columns of text, be
    sure to have padding between the left and right edges of the text
    and whatever is adjacent to the text.

(3) Be cautious when using \@import to call up a style sheet, as Jaws
    (in default mode, prior to version 8) does not read style sheets
    delivered through \@import.[^517]

(4) When pseudo-classes are used in a style sheet, they should be in the
    order: link, visited, hover, active.[^518] There is currently not
    agreement when precisely where the focus pseudo-class should be
    placed with respect to link, visited, hover, and active.[^519]

(5) When assigning the name of a class (or the value of an "d"
    attribute), use the purpose of the data that will be in the class,
    not how the data is to be portrayed -- the class name should
    indicate function, not form. For instance, "hotTopics" would be an
    appropriate class name, but "whiteOnRed" would not be an appropriate
    class name.[^520]

```{=html}
<!-- -->
```
(6) External style sheets should always be used when the style sheet
    contains any of the following character strings:[^521]

> \<
>
> \]\]\>
>
> \--

(7) Do not use HTML comments (e.g., \<!\-- text \--\>) to hide style
    sheets from older browsers, as XML-compliant browsers may treat the
    style sheet as a comment.[^522]

[]{#__RefHeading___Toc216010148 .anchor}**Subcommittees** *see Committee
Assignments and Caucus memberships; and Committee Websites*

[]{#__RefHeading___Toc216010149 .anchor}**Support Office Websites** *see
"About" page*

[]{#__RefHeading___Toc216010150 .anchor}**Tables** *see also Alignment;
and Layout*

(1) Row and column headings in tables should use \<th\> tags instead of
    \<td\> tags. Additionally, the \<th\> tag for each row heading
    should have a scope=\"row\" attribute, and the \<th\> tag for each
    column heading should have scope=\"col\" attribute.[^523]

(2) In complex tables (i.e., tables with nested column or row headings
    and subheadings), each heading (i.e., each \<th\> tag) should have
    an "id" attribute and each cell of the table (i.e., each \<td\> tag)
    should have a "headers" attribute that associates the cell with the
    appropriate headers.[^524]

(3) Style sheets should be used for layout, rather than using \<table
    border=\"0\"\> tags.[^525]

(4) Heights and widths within a table should be set with the style sheet
    "height" and "width" properties, not with the "height" and "width"
    attributes of the tags.[^526]

(5) Rather than using the "nowrap" attribute to disable automatic
    wrapping of text in table cells, use the style sheets property
    "white-space:nowrap".[^527]

(6) When using tables, consider including a sort feature.[^528]

(7) Each \<col\> tag should end with "/\>".[^529]

[]{#__RefHeading___Toc216010151 .anchor}**Tagalog language material**
*see Government Resources #(2); Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216010152 .anchor}**Tags (general rules)**

(1) Every start tag must have a close tag (e.g., for every \<p\>, there
    must be a \</p\>. Every "empty" tag (i.e., tags that are
    self-contained, e.g., \<area\>, \<base\>, \<br\>, \<col\>,
    \<frame\>, \<hr\>, \<img\>, \<input\>, \<link\>, \<meta\>, and
    \<param\>) should end with "/\>", e.g., \<area alt=\"Smithfield\"
    coords=\"1,1,10,10\" href=\"Smithfield.shtml\" /\>.[^530]

(2) All tags must be completely nested -- i.e., a tag that starts within
    an open tag/close tag pair, must itself be closed before the outer
    pair is closed -- e.g., \<div\>\<p\>\</p\>\</div\> is valid, but
    \<div\>\<p\>\</div\>\</p\> is not.[^531]

(3) All tag element names must be in lower case ("\<meta\>" not
    "\<META\>").[^532]

[]{#__RefHeading___Toc216010153 .anchor}**Telephone Numbers** *see
Contact Information and Techniques #(6) and #(12)*

[]{#__RefHeading___Toc216010154 .anchor}**\<textarea\> tags** *see
Forms*

[]{#__RefHeading___Toc216010155 .anchor}**Text-only pages and sites**

Having a text-only website, that parallels the content of the HTML
version of the site, **does not** satisfy the requirement of providing
an accessible website.[^533]

[]{#__RefHeading___Toc216010156 .anchor}**Thai language material** *see
Government Resources #(2); Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216010157 .anchor}**Titles** *see also Headings;
Graphics #(5); Tables #(1)*

(1) Each file should contain one (and only one) \<title\> tag. The
    \<title\> tag should be between the \<head\> tag and the \</head\>
    tag.[^534]

(2) The content of \<title\> tags should be unique for each page on the
    site, if practical.[^535]

(3) The words that convey the most information should be at the
    beginning of each title -- preferably in the first two words.[^536]

[]{#__RefHeading___Toc216010158 .anchor}**Tools for Validating Web
Sites**

In addition to [InFocus](http://www1.house.gov:8080/ssb/login.jsp),
consider using the following free tools:

(1) [W3C Markup Validation Service](http://validator.w3.org/) -- will
    check for compliance with the W3C HTML and XHTML standards.[^537]

(2) [W3C CSS Validator](http://jigsaw.w3.org/css-validator/) -- will
    check for compliance with the W3C Cascading Style Sheets standards
    (will only work on files that are compliant with at least one of the
    W3C[^538] HTML or XHTML standards).[^539]

(3) [W3C Link Checker](http://validator.w3.org/checklink) -- will test
    the links for unusual conditions, including 404 errors.[^540]

(4) [Vischeck](http://www.vischeck.com/vischeck/vischeckImage.php) --
    will simulate how images (or Web pages) look to people with
    different types of colorblindness.

(5) [Contrast
    Analyzer](http://www.paciellogroup.com/resources/contrast-analyser.html)
    -- detects whether there is sufficient color contrast between the
    text and background colors.[^541]

(6) [Cynthia Says](http://www.contentquality.com/) -- checks for 508
    compliance and for compliance with the W3C WCAG 1.0 standard. This
    is a good supplement to InFocus, because Cynthia Says catches some
    accessibility problems that InFocus does not. (Be sure to check the
    box marked "Include the Alternative Text Quality Report").[^542]

(7) [ATRC Web Accessibility
    Checker](http://checker.atrc.utoronto.ca/servlet/Submit) - checks
    for compliance with the 508 standard, the WCAG 1.0 and draft 2.0
    standards, as well as the German and Italian national accessibility
    standards. (Be sure to use the "change guideline" link to get to the
    page that specifies the standards that you are going to test
    against.)

(8) [Readability Test](http://juicystudio.com/services/readability.php)
    -- calculates the approximate grade level of the writing on a Web
    page using the Guuning-Fox Index and Flesch/Flesch--Kincaid
    Readability Tests (Flesch Reading Ease and Flesch--Kincaid Grade
    Level.[^543]

(9) [Web Accessibility
    Toolbar](http://www.visionaustralia.org.au/ais/toolbar/) -- provides
    an easy way to turn off style sheets or JavaScripts; resize browser
    windows; render pages in black and white; display headings and
    lists; test event handlers against accessibility rules; simulate a
    Lynx browser; simulate various vision disabilities; display language
    attributes; etc.

[]{#__RefHeading___Toc216010159 .anchor}**Tours** *see Visiting
Washington*

[]{#__RefHeading___Toc216010160 .anchor}**Typeface** *see Fonts*

[]{#__RefHeading___Toc216010161 .anchor}**Ukrainian language material**
*see Government Resources #(2); Language of Text: and Linking #(14)*

[]{#__RefHeading___Toc216010162 .anchor}** Unclaimed Property**

On Member websites, consider including material concerning the Member's
state's unclaimed property office. The National Association of Unclaimed
Property Administrators maintains a page that links to the offices of
each state and territory at
[[http://www.unclaimed.org/RightFrame.asp?VisitorType=owner&SectionName=find_property]{.underline}](http://www.unclaimed.org/RightFrame.asp?VisitorType=owner&SectionName=find_property).

[]{#__RefHeading___Toc216010163 .anchor}**Under Construction** *see also
Layout #(4)*

"Under construction" icons and notices should not be used on Web page.
If it is absolutely necessary to indicate that a page or feature is
coming soon, then indicate when the material is expected to be there --
even better, provide a Web form that people can use to request to be
notified when the promised material has been posted.[^544]

[]{#__RefHeading___Toc216010164 .anchor}**Underlining** *see also
Linking #(11)*

(1) Style sheets[^545], not \<u\> tags, should be used to achieve
    underlining. [^546]

(2) Do not use underlining for emphasis in normal text. Underlining
    should normally be reserved for hypertext links.[^547] Text to be
    emphasized should be preceded by an \<em\> tag and followed by a
    \</em\> tag; and style sheets should be used to specify font weight,
    font size, and color.[^548]

[]{#__RefHeading___Toc216010165 .anchor}**U.S. Code**[^549]

(1) Whenever a section of the U.S. Code is referred to on a Web page, it
    is recommended that the reference link to the full text of the
    section.[^550]

(2) URLs for individual sections of the U.S. Code should normally be in
    the format

> http://uscode.house.gov/quicksearch/get.plx?title=**TT**&section=**SS**
>
> where **TT** is replaced with the title number[^551] and **SS** is
> replaced with the section number[^552]. For example, the URL for the
> Privacy Act (which is title 5, section 552a of the U.S. Code) would
> be:
>
> <http://uscode.house.gov/quicksearch/get.plx?title=5&section=552a>

(3) When a U.S. Code citation is given in legal citation style (e.g., 5
    U.S.C. § 552a), a "title" attribute should be included in the \<a
    href\> tag that links to the full text of the section -- expanding
    the citation shorthand into text, e.g.,

> \<a
> href=\"http://uscode.house.gov/quicksearch/get.plx?title=5&section=552a\"
> title=\"title 5, section 552a of the United States Code\"\>5 U.S.C.
> &#167; 552a\</a\>
>
> (Note, that "&#167;" will display as a section symbol, i.e., "§".)

[]{#__RefHeading___Toc216010166 .anchor}**Upper case letters** *see
Capital letters*

[]{#__RefHeading___Toc216010167 .anchor}**Urchin** *see Usage
Statistics*

[]{#__RefHeading___Toc216010168 .anchor}**URLs**

The URL for every page of every House website (including the websites of
Members, Committees, Leadership, Officers, and Support Offices) should
begin with either [WWW.HOUSE.GOV](http://WWW.HOUSE.GOV/) or should be in
the style **OfficeName**.HOUSE.GOV where **OfficeName** is derived from
the office's name.[^553] Any office requesting a URL that does not
conform to either of those styles must have written authorization from
the Committee on House Administration (majority).[^554]

[]{#__RefHeading___Toc216010169 .anchor}**Usage Statistics**

Offices hosted on any of the HIR Web servers should be urged to examine
their site's usage statistics through
[Urchin](http://onlinecao.house.gov/webassistance/manage/mg_stats_urchin.htm).

[]{#__RefHeading___Toc216010170 .anchor}**USA.gov** *see FirstGov*

[]{#__RefHeading___Toc216010171 .anchor}**Validation Tools** *see Tools
for Validating Web Sites*

[]{#__RefHeading___Toc216010172 .anchor}**VBScript** *see Forms #(13)
and (14); Navigation #(12); and Scripts*

[]{#__RefHeading___Toc216010173 .anchor}**vCard** *see Contact
Information and Techniques #(12)*

[]{#__RefHeading___Toc216010174 .anchor}** Veterans**

(1) Member offices (and other House offices that deal regularly with
    veterans)[^555] should be encouraged to include a page(s) on their
    website devoted to veterans' benefits.[^556] The text of a CAO-Web
    Solutions Branch-maintained FAQ that links to appropriate pages on
    the websites of the Department of Veterans Affairs and the National
    Archives and Records Administration can automatically be inserted
    using a server-side include or by using an iframe.[^557]

(2) The Library of Congress' Veterans History Project[^558] is
    attempting to collect and preserve stories of wartime service of
    veterans of

    -   World War I (1914-1920),

    -   World War II (1939-1946),

    -   Korean War (1950-1955),

    -   Vietnam War (1961-1975),

    -   Persian Gulf War (1990-1995), and

    -   Afghanistan and Iraq conflicts (2001-present).

> Consider, on Member websites (and on the websites of other House
> offices that deal regularly with veterans)[^559], including either a
> link to the Project[^560] or providing a form on the Member's website
> that constituents can use to participate in the Project (see. e.g.,
> the "Fifth District War Heroes Project" portion of the ["Veterans"
> page on Rep. Steve King's
> website](http://www.house.gov/steveking/issue_veterans.shtm)).

(3) On Member websites (and on the websites of other House offices that
    deal regularly with veterans)[^561], consider including a link to
    the Department of Veterans Affairs' National Gravesite
    Locator.[^562]

(4) On Member websites, consider including a link to the office of
    veterans affairs of the Member's state.[^563]

[]{#__RefHeading___Toc216010175 .anchor}**Vietnamese language
material**[^564] *see Government Resources #(2); Language of Text: and
Linking #(14)*

[]{#__RefHeading___Toc216010176 .anchor}** Visiting Washington** *see
also Federal Bureau of Investigation tours; and Newseum*

(1) Member offices should be encouraged to include a secure form[^565]
    on their website for constituents to request tours of the U.S.
    Capitol building and other Washington, DC landmarks and
    attractions.[^566]

(2) Rather than linking to the CAO-Web Solutions Branch-maintained
    "[Washington, DC -- Tourist
    Information](http://www.house.gov/house/tour_dc.shtml)" page and/or
    the CAO-Web Solutions Branch-maintained "[Visiting
    DC](http://www.house.gov/house/Visitor.shtml)" page, offices should
    be encouraged to place the text of either or both those pages into a
    page on their own website (by using a server-side include or an
    iframe).[^567]

(3) Links to external sites for this portion of a website should
    normally go to the external sites' tour (or visitor) page, rather
    than to their home page (e.g., go to
    <http://www.supremecourtus.gov/visiting/visiting.html>, rather than
    to <http://www.supremecourtus.gov/>).

[]{#__RefHeading___Toc216010177 .anchor}**Voice** *see Multimedia files
and Audio files; and Word Choice*

[]{#__RefHeading___Toc216010178 .anchor}**Voting Information** *see
Issues and Voting Information*

[]{#__RefHeading___Toc216010179 .anchor}** Waste**

Offices may want to consider including a page on what they are doing to
combat waste. See, e.g., Rep. Tom Feeney's "[Washington Waste
Watchers](http://www.house.gov/feeney/washingtonwastewatchers.shtml)"
page.

[]{#__RefHeading___Toc216010180 .anchor}**Web Designer** *see Commercial
References*

[]{#__RefHeading___Toc216010181 .anchor}**Welcome Messages** *see
Homepage*

[]{#__RefHeading___Toc216010182 .anchor}**White House tours** *see
Visiting Washington*

[]{#__RefHeading___Toc216010183 .anchor}**WIDA** *see also Blogs; Events
Schedule; Floor Statements; Issues and Voting Information #(2); Press
Releases; and Schedule of Member*

(1) Because WIDA-generated pages (including index pages) reside in a
    different directory than the rest of the website, it is important to
    verify that any relative links (including relative graphic links)
    still work, once site is on the production Web server.

(2) Where you have a link with a date range, be sure the documents
    linked to really conform to the date range.

(3) Offices using WIDA should be encouraged to use the WIDA "issues"
    feature[^568] to:

    a.  generate a WIDA list page that is in issue order;[^569] and

    b.  place a WIDAinc[^570] on each of the pages in the "issues"
        section of their website that deal with the issues broken out by
        WIDA issue category.

(4) When using a WIDAinc with the "More" option, make use of the
    "Template" option and include in the template something along the
    lines of: \<a href=\"{HTMLFILE_LINK}\" title=\"full text of the
    press release of {DATEL}\"\>.[^571]^,^ [^572]

(5) Documents generated through WIDA should use navigation, banners, and
    footers that are identical with the rest of the website.[^573] Use
    server-side includes to provide those features. With that technique,
    future changes in the website's design (including file names,
    navigation links, banners, and footers) will not require
    republishing all of the WIDA documents in order to keep the
    navigation functioning properly.

(6) When displaying WIDA index information, consider setting the
    information up in table form, with sort functionality. See, e.g.,
    the ["News" page of the Immigration Reform
    Caucus](http://www.house.gov/bilbray/irc/news.shtml).

[]{#__RefHeading___Toc216010184 .anchor}**Word Choice** *see also
Jargon*

(1) Use a consistent voice throughout a website. For instance -- unless
    there is an important reason to do otherwise -- do not refer the
    Member as "I" in the biography, but as "Rep. Jones" in the rest of
    the website.[^574] By the same token, use words consistently
    throughout the site -- for instance, do not use "signup" in one
    place, but "sign-up" in another.[^575]

(2) The words that convey the most information should be at the
    beginning of each sentence and paragraph.[^576]

(3) To the extent practical, try to convey one idea per paragraph.[^577]

(4) Use the clearest and simplest language appropriate to convey the
    message.[^578] When a simple word and a complex word would both
    convey the same meaning, use the simple word -- unless there is a
    substantial reason to do otherwise.[^579]

(5) Use active voice, rather than passive voice.[^580]

(6) Use simple sentence structure -- rather than complex sentence
    structure -- when practical.[^581]

[]{#__RefHeading___Toc216010185 .anchor}**Write Your Representative**
*see Contact Information and Techniques #(1)*

[]{#__RefHeading___Toc216010186 .anchor}**\<xmp\> tags** *see HTML*

# Appendix 1: Social Bookmarking

Sample instructions for adding social bookmarking to House websites:

(1) On each Web page, between the \<head\> tag and the \</head\> tag,
    insert:

> \<!\-- javascript for retrieving current URL \--\>
>
> \<script type=\"text/javascript\"
> src=\"@include/get_url.js\"\>\</script\>
>
> \<!\-- javascript for exit message alert \--\>
>
> \<script type=\"text/javascript\"
> src=\"@include/exit-msg.js\"\>\</script\>

(2) On each Web page, between the \<body\> tag and the \</body\> tag,
    place the following code where the social bookmarking icon links are
    to appear:

> \<div class=\"bookmarkImages\"\>\<a id=\"digg\"
> onclick=\"getURL(\'digg\'); exitMsg()\"
> href=\"http://digg.com/submit?phase=2&amp;\" title=\"Digg!\"\>\<img
> class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/digg.png\"
> alt=\"Digg!\" title=\"Digg!\" /\>\</a\>
>
> \<a id=\"reddit\" onclick=\"getURL(\'reddit\'); exitMsg()\"
> href=\"http://reddit.com/submit?\" title=\"Reddit!\" \>\<img
> class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/reddit.png\"
> alt=\"Reddit!\" title=\"Reddit!\" /\>\</a\>
>
> \<a id=\"Delicious\" onclick=\"getURL(\'Delicious\'); exitMsg()\"
> href=\"http://del.icio.us/post?\" title=\"Del.icio.us!\"\>\<img
> class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/delicious.png\"
> alt=\"Del.icio.us!\" title=\"Del.icio.us!\" /\>\</a\>
>
> \<a id=\"Google\" onclick=\"getURL(\'Google\'); exitMsg()\"
> href=\"http://www.google.com/bookmarks/mark?op=add&amp;\"
> title=\"Google!\"\>\<img class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/google.png\"
> alt=\"Google!\" title=\"Google!\" /\>\</a\>
>
> \<a id=\"Live\" onclick=\"getURL(\'Live\'); exitMsg()\"
> href=\"https://favorites.live.com/quickadd.aspx?marklet=1&amp;mkt=en-us&amp;top=0&amp;\"
> title=\"Live!\"\>\<img class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/live.png\"
> alt=\"Live!\" title=\"Live!\" /\>\</a\>
>
> \<a id=\"Facebook\" onclick=\"getURL(\'Facebook\'); exitMsg()\"
> href=\"http://www.facebook.com/share.php?\" title=\"Facebook!\"\>\<img
> class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/facebook.png\"
> alt=\"Facebook!\" title=\"Facebook!\" /\>\</a\>
>
> \<a id=\"Slashdot\" onclick=\"getURL(\'Slashdot\'); exitMsg()\"
> href=\"http://slashdot.org/bookmark.pl?\" title=\"Slashdot!\" \>\<img
> class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/slashdot.png\"
> alt=\"Slashdot!\" title=\"Slashdot!\" /\>\</a\>
>
> \<a id=\"Netscape\" onclick=\"getURL(\'Netscape\'); exitMsg()\"
> href=\"http://www.netscape.com/submit/?\" title=\"Netscape!\"
> target=\"\_blank\"\>\<img class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/netscape.png\"
> alt=\"Netscape!\" title=\"Netscape!\" /\>\</a\>
>
> \<a id=\"Technorati\" onclick=\"getURL(\'Technorati\'); exitMsg()\"
> href=\"http://technorati.com/faves/?\" title=\"Technorati!\"\>\<img
> class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/technorati.png\"
> alt=\"Technorati!\" title=\"Technorati!\" /\>\</a\>
>
> \<a id=\"StumbleUpon\" onclick=\"getURL(\'StumbleUpon\'); exitMsg()\"
> href=\"http://www.stumbleupon.com/submit?\"
> title=\"StumbleUpon!\"\>\<img class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/stumbleupon.png\"
> alt=\"StumbleUpon!\" title=\"StumbleUpon!\" /\>\</a\>
>
> \<a id=\"Spurl\" onclick=\"getURL(\'Spurl\'); exitMsg()\"
> href=\"http://www.spurl.net/spurl.php?\" title=\"Spurl!\"\>\<img
> class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/spurl.png\"
> alt=\"Spurl!\" title=\"Spurl!\" /\>\</a\>
>
> \<a id=\"Wists\" onclick=\"getURL(\'Wists\'); exitMsg()\"
> href=\"http://wists.com/r.php?\" title=\"Wists!\"\>\<img
> class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/wists.png\"
> alt=\"Wists!\" title=\"Wists!\" /\>\</a\>
>
> \<a id=\"Simpy\" onclick=\"getURL(\'Simpy\'); exitMsg()\"
> href=\"http://www.simpy.com/simpy/LinkAdd.do?\"
> title=\"Simpy!\"\>\<img class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/simpy.png\"
> alt=\"Simpy!\" title=\"Simpy!\" /\>\</a\>
>
> \<a id=\"Newsvine\" onclick=\"getURL(\'Newsvine\'); exitMsg()\"
> href=\"http://www.newsvine.com/\_tools/seed&amp;save?\"
> title=\"Newsvine!\"\>\<img class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/newsvine.png\"
> alt=\"Newsvine!\" title=\"Newsvine!\" /\>\</a\>
>
> \<a id=\"Blinklist\" onclick=\"getURL(\'Blinklist\'); exitMsg()\"
> href=\"http://www.blinklist.com/index.php?Action=Blink/addblink.php&amp;\"
> title=\"Blinklist!\"\>\<img class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/blinklist.png\"
> alt=\"Blinklist!\" title=\"Blinklist!\" /\>\</a\>
>
> \<a id=\"Furl\" onclick=\"getURL(\'Furl\'); exitMsg()\"
> href=\"http://www.furl.net/storeIt.jsp?\" title=\"Furl!\" \>\<img
> class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/furl.png\"
> alt=\"Furl!\" title=\"Furl!\" /\>\</a\>
>
> \<a id=\"Blogmarks\" onclick=\"getURL(\'Blogmarks\'); exitMsg()\"
> href=\"http://blogmarks.net/my/new.php?mini=1&amp;simple=1&amp;\"
> title=\"Blogmarks!\"\>\<img class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/blogmarks.png\"
> alt=\"Blogmarks!\" title=\"Blogmarks!\" /\>\</a\>
>
> \<a id=\"Yahoo\" onclick=\"getURL(\'Yahoo\'); exitMsg()\"
> href=\"http://myweb2.search.yahoo.com/myresults/bookmarklet?\"
> title=\"Yahoo!\"\>\<img class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/yahoo.png\"
> alt=\"Yahoo!\" title=\"Yahoo!\" /\>\</a\>
>
> \<a id=\"Netvouz\" onclick=\"getURL(\'Netvouz\'); exitMsg()\"
> href=\"http://www.netvouz.com/action/submitBookmark?\"
> title=\"Netvouz!\"\>\<img class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/netvouz.png\"
> alt=\"Netvouz!\" title=\"Netvouz!\" /\>\</a\>
>
> \<a id=\"Magnolia\" onclick=\"getURL(\'Magnolia\'); exitMsg()\"
> href=\"http://ma.gnolia.com/beta/bookmarklet/add?\"
> title=\"Ma.gnolia!\"\>\<img class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/magnolia.png\"
> alt=\"Ma.gnolia!\" title=\"Ma.gnolia!\" /\>\</a\>
>
> \<a id=\"FeedMeLinks\" onclick=\"getURL(\'FeedMeLinks\'); exitMsg()\"
> href=\"http://feedmelinks.com/categorize?from=toolbar&amp;op=submit&amp;\"
> title=\"FeedMeLinks!\"\>\<img class=\"bookmarkImage\"
> src=\"http://www.house.gov/include_content/images/socialBookmarkings/feedmelinks.png\"
> alt=\"FeedMeLinks!\" title=\"FeedMeLinks!\" /\>\</a\>
>
> \</div\>

(3) In the screen style sheet, consider adding the following properties:

> .bookmarkImages {text-align:center; margin: 0 auto;}
>
> .bookmarkImage {border-style: none;}

(4) In the \@include directory, create a file exit-msg.js with the
    following content:

> // JavaScript External Link Exit Message
>
> function exitMsg(){
>
> alert(\"You are now leaving the U.S. House of Representatives website.
> Thank you for visiting. Neither this office, whose site contains the
> link, nor the U.S. House of Representatives is responsible for the
> content of the non-House site you are about to access.\")
>
> }

(5) In the \@include directory, create a file get_url.js with the
    following content:

> // Retrieve Current URL and title \--\>
>
> function getURL(site) {
>
> var thisdoc = document.location;
>
> var thisdoctitle = document.title;
>
> // alert(document.getElementById(site).href);
>
> if (site == \"digg\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"url=\" + thisdoc + \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"reddit\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"url=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Delicious\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"url=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Google\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"bkmk=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Live\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"url=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Facebook\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"u=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Slashdot\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"url=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Netscape\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"U=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Technorati\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"add=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"StumbleUpon\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"url=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Spurl\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"url=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Wists\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"r=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Simpy\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"href=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Newsvine\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"u=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Blinklist\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"Url=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Furl\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"u=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Blogmarks\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"url=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Yahoo\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"u=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Netvouz\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"url=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"Magnolia\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"url=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> if (site == \"FeedMeLinks\") {
>
> document.getElementById(site).href=document.getElementById(site).href
> +
>
> \"url=\" + thisdoc+ \"&title=\" + thisdoctitle;
>
> // alert(document.getElementById(site).href);
>
> // alert(document.title);
>
> }
>
> }

# Appendix 2: Federal Judicial Branch

Most House Member websites include a page on contacting Federal
agencies. Many of these include some of the Federal courts. One way to
personalize those pages is to include links to the specific U.S. Court
of Appeal, U.S. District Court, and U.S. Bankruptcy Court that have
jurisdiction within the Member's congressional district.

**U.S. Courts of Appeals**

The United States is divided into 12 judicial circuits: The 1^st^
through 11^th^ circuits and the District of Columbia circuit. Each of
the 12 circuits has a U.S. Court of Appeals. These courts are generally
referred to as the:

> U.S. Court of Appeals for the 1^st^ Circuit
>
> U.S. Court of Appeals for the 2^nd^ Circuit
>
> .
>
> .
>
> .
>
> U.S. Court of Appeals for the 11^th^ Circuit
>
> U.S. Court of Appeals for the District of Columbia Circuit.

The following is a list of all the circuit numbers by state:

Alabama -- 11

Alaska -- 9

American Samoa -- 9

Arizona -- 9

Arkansas -- 8

California -- 9

Colorado -- 10

Connecticut -- 2

Delaware -- 3

District of Columbia --

DC

Florida -- 11

Georgia -- 11

Guam -- 9

Hawaii -- 9

Idaho -- 9

Illinois -- 7

Indiana -- 7

Iowa -- 8

Kansas -- 10

Kentucky -- 6

Louisiana -- 5

Maine -- 1

Maryland -- 4

Massachusetts -- 1

Michigan -- 6

Minnesota -- 8

Mississippi -- 5

Missouri -- 8

Montana -- 9

Nebraska -- 8

Nevada -- 9

New Hampshire -- 1

New Jersey -- 3

New Mexico -- 10

New York -- 2

North Carolina -- 4

North Dakota -- 8

Northern Mariana

Islands -- 9

Ohio -- 6

Oklahoma -- 10

Oregon -- 9

Pennsylvania -- 3

Puerto Rico -- 1

Rhode Island -- 1

South Carolina -- 4

South Dakota -- 8

Tennessee -- 6

Texas -- 5

Utah -- 10

Vermont -- 2

Virgin Islands -- 3

Virginia -- 4

Washington -- 9

West Virginia -- 4

Wisconsin -- 7

Wyoming -- 10

The U.S. Courts of Appeals have a uniform naming convention for their
URLs:

> [[http://www.ca**\[CIRCUIT\]**.uscourts.gov/]{.underline}]()

so that the U.S. Court of Appeals for the 1^st^ Circuit is at
[[http://www.ca1.uscourts.gov/]{.underline}](http://www.ca1.uscourts.gov/);
the U.S. Court of Appeals for the 2^nd^ Circuit is
[[http://www.ca2.uscourts.gov/]{.underline}](http://www.ca2.uscourts.gov/);
etc.

**U.S. District Courts and U.S. Bankruptcy Courts**

The United States is divided into approximately 100 judicial districts.
Every state and territory contains at least one U.S. judicial district.
Some states contain several judicial districts. Each judicial district
has one U.S. District Court and one U.S. Bankruptcy Court. Some examples
of U.S. District Courts are:

> U.S. District Court for the District of Alaska
>
> U.S. District Court for the Northern District of California
>
> U.S. District Court for the Eastern District of Virginia

Some examples of U.S. Bankruptcy Courts are:

> U.S. Bankruptcy Court for the District of Alaska
>
> U.S. Bankruptcy Court for the Northern District of California
>
> U.S. Bankruptcy Court for the Eastern District of Virginia

Which judicial district a particular congressional district is in
depends on what county (and state) the congressional district is in.
Once you know all of the counties that are entirely or partially in a
Member's congressional district,[^582] go to

[[http://pacer.psc.uscourts.gov/lookup.html]{.underline}](http://pacer.psc.uscourts.gov/lookup.html)

and enter the state and county information. The system will supply you
with the name of the judicial district for that county (as well as
confirming the judicial circuit for the state). Some congressional
districts include parts of more than one judicial district, so it is
important to test all of the counties from the congressional district.

The U.S. District Courts have a uniform naming convention for their
URLs:

> [[http://www.**\[STATE POSTAL ABBREVIATION\]\[ONE LETTER CODE
> INDICATING PART OF THE STATE\]**d.uscourts.gov/]{.underline}]()

so the U.S. District Court for the District of Alaska is
[[http://www.akd.uscourts.gov/]{.underline}](http://www.akd.uscourts.gov/);
the U.S. District Court of the Northern District of California is
[[http://www.cand.uscourts.gov/]{.underline}](http://www.cand.uscourts.gov/);
the U.S. District Court for the Eastern District of Virginia is
[[http://www.vaed.uscourts.gov/]{.underline}](http://www.vaed.uscourts.gov/);
etc.

The U.S. Bankruptcy Courts have a similar naming convention for their
URLs:

> \<[[http://www.**\[STATE POSTAL ABBREVIATION\]\[ONE LETTER CODE
> INDICATING PART OF THE STATE\]**b.uscourts.gov/]{.underline}]()\>

so the U.S. Bankruptcy Court for the District of Alaska is
[[http://www.akb.uscourts.gov/]{.underline}](http://www.akb.uscourts.gov/);
the U.S. Bankruptcy Court of the Northern District of California is
[[http://www.canb.uscourts.gov/]{.underline}](http://www.canb.uscourts.gov/);
the U.S. Bankruptcy Court for the Eastern District of Virginia is
[[http://www.vaeb.uscourts.gov/]{.underline}](http://www.vaeb.uscourts.gov/);
etc.

> **Note:** In the Commonwealth of the Northern Mariana Islands, the
> functions of the U.S. District Court and the U.S. Bankruptcy Court are
> consolidated into a single court -- the U.S. District Court for the
> Northern Mariana Islands. The website for this court is
> <http://www.nmid.uscourts.gov/>.

**Other Federal courts**

There are several courts of national jurisdiction (and judicial branch
offices) that you may also want to include in Member websites:

-   U.S. Tax Court,
    [[http://www.ustaxcourt.gov/]{.underline}](http://www.ustaxcourt.gov/)

-   U.S. Court of Federal Claims,
    [[http://www.uscfc.uscourts.gov/]{.underline}](http://www.uscfc.uscourts.gov/)

-   U.S. Court of International Trade, <http://www.cit.uscourts.gov/>

-   Judicial Panel on Multidistrict Litigation,
    <http://www.jpml.uscourts.gov/>

-   U.S. Court of Appeals for the Federal Circuit,
    http://www.cafc.uscourts.gov/

-   U.S. Court of Appeals for Veterans Claims,
    [[http://www.vetapp.gov/]{.underline}](http://www.vetapp.gov/)

-   U.S. Court of Appeals for the Armed Forces,
    <http://www.armfor.uscourts.gov/index.html>

-   U.S. Supreme Court,
    [[http://www.supremecourtus.gov/]{.underline}](http://www.supremecourtus.gov/)

> Other Federal Judicial Agencies:

-   Administrative Office of the U.S. Courts,
    [[http://www.uscourts.gov/]{.underline}](http://www.uscourts.gov/)

-   Federal Judicial Center,
    [[http://www.fjc.gov/]{.underline}](http://www.fjc.gov/)

-   U.S. Sentencing Commission,
    [[http://www.ussc.gov/]{.underline}](http://www.ussc.gov/)

Additionally, there is a very good tutorial on the Federal court system
(compiled by the Federal Judicial Center) at
[[http://www.fjc.gov/federal/courts.nsf]{.underline}](http://www.fjc.gov/federal/courts.nsf).

# Appendix 3: Caucus Web Sites

**Websites of those caucuses (registered with the House Administration
Committee as of November 8, 2007) that have websites:**[^583]

-   21st Century Health Care Caucus -
    [http://www.patrickkennedy.house.gov/index.asp?Type=NONE&SEC=%7BE19E1409-D06A-4492-A5E7-6DC029BF8C11%7D](http://www.patrickkennedy.house.gov/index.asp?Type=NONE&SEC={E19E1409-D06A-4492-A5E7-6DC029BF8C11})

```{=html}
<!-- -->
```
-   9/11 Commission Caucus -
    <http://maloney.house.gov/index.php?option=com_issues&task=view_issue&issue=2&Itemid=35>

-   Addiction, Treatment and Recovery Caucus -
    <http://www.house.gov/ramstad/caucus/Addiction/AddictionINTRO.htm>

-   Bipartisan, Bicameral Congressional Task Force on Alzheimer's
    Disease -
    <http://markey.house.gov/index.php?option=com_content&task=blogcategory&id=236&Itemid=66>

-   Blue Dog Coalition -
    <http://www.house.gov/ross/BlueDogs/bluedogs.shtml>

-   California Democratic Congressional Delegation -
    <http://lofgren.house.gov/cdcd/index.aspx>

-   Coalition for Autism Research and Education -
    <http://www.house.gov/doyle/autism.shtml>

-   Congressional Asian Pacific American Caucus -
    <http://honda.house.gov/capac/>

-   Congressional Automotive Caucus -
    <http://www.house.gov/kildee/auto_caucus.shtml>

-   Congressional Bike Caucus -
    <http://blumenauer.house.gov/Issues/CaucusSummary.aspx?NewsID=995>

-   Congressional Black Caucus -
    <http://www.house.gov/kilpatrick/cbc/index.shtml>

-   Congressional Brain Injury Task Force -
    <http://www.pascrell.house.gov/display2.cfm?id=1270>

-   Congressional Caucus on Armenian Issues -
    <http://www.house.gov/pallone/armeniancaucus.shtml>

-   Congressional Caucus on Hellenic Issues -
    <http://maloney.house.gov/index.php?option=com_issues&task=view_issue&issue=12&Itemid=35>

-   Congressional Caucus on the Judicial Branch -
    [<http://schiff.house.gov/judicialcaucus/>]{.underline}

-   Congressional Caucus to Fight and Control Methamphetamine -
    <http://www.house.gov/larsen/meth/>

-   Congressional China Caucus -
    <http://www.house.gov/forbes/AboutRandy/chinacaucus.htm>

-   Congressional Climate Change Caucus -
    <http://www.house.gov/olver/climatechange/index.html>

-   Congressional Coastal Caucus -
    <http://www.house.gov/pallone/coastalcaucs.shtml>

-   Congressional E-911 Caucus -
    <http://www.house.gov/shimkus/911home.htm>

-   Congressional Ethiopia and Ethiopian-Americans -
    <http://www.honda.house.gov/ethiopiacaucus.shtml>

-   Congressional Hispanic Caucus - <http://www.house.gov/baca/chc/>

-   Congressional International Anti-Piracy Caucus -
    <http://schiff.house.gov/antipiracycaucus/>

-   Congressional Internet Caucus (Advisory Committee) -
    <http://www.netcaucus.org/>

-   Congressional Kidney Caucus -
    <http://www.house.gov/mcdermott/kidneycaucus/>

-   Congressional Labor and Working Families Caucus -
    <http://lindasanchez.house.gov/laborcaucus/index.cfm>

-   Congressional Mental Health Caucus -
    <http://www.napolitano.house.gov/mhcaucus/>

-   Congressional Native American Caucus -
    <http://www.house.gov/kildee/native_american_ca.shtml>

-   Congressional Prayer Caucus -
    <http://www.house.gov/forbes/prayercaucus.htm>

-   Congressional Progressive Caucus - <http://cpc.lee.house.gov/>

-   Congressional Rural Housing Caucus -
    <http://hinojosa.house.gov/crhc/index.shtml>

-   Congressional Shipbuilding Caucus -
    <http://www.house.gov/joanndavis/shipbuildingcaucus/> [^584]

-   Congressional Steel Caucus -
    <http://www.house.gov/english/steelcaucus.shtml>

-   Congressional Victims Rights - Caucus <http://vrc.poe.house.gov/>

-   Congressional Vision Caucus - <http://www.house.gov/green/cvc/>

-   Congressional Western Caucus -
    <http://chriscannon.house.gov/wc/index.htm>

-   Electronic Warfare Working Group -
    <http://www.house.gov/pitts/ew.htm>

-   Generic Drug Equity Caucus -
    <http://calvert.house.gov/genericdrug.asp>

-   House Baltic Caucus -
    <http://www.house.gov/shimkus/baltic/baltic.shtml>

-   House Cancer Caucus - <http://www.house.gov/pryce/hccaucus.html>

-   House Rural Health Care Coalition -
    [http://www.pomeroy.house.gov/index.asp?Type=B_BASIC&SEC=%7B998F12BA-9704-463E-9F61-3EB414CBDA2C%7D](http://www.pomeroy.house.gov/index.asp?Type=B_BASIC&SEC={998F12BA-9704-463E-9F61-3EB414CBDA2C})

-   Immigration Reform Caucus - <http://www.house.gov/bilbray/irc/>

-   Law Enforcement Caucus -
    <http://www.house.gov/stupak/lawenforcement.shtml>

-   LGBT Equality Caucus - <http://lgbt.tammybaldwin.house.gov/>

-   Medical Technology Caucus -
    <http://www.house.gov/ramstad/caucus/Medtech/medical03.htm>

-   Modeling and Simulation Caucus -
    <http://forbes.house.gov/Biography/mscaucus.htm>

-   National Guard and Reserve Components Caucus -
    <http://stevebuyer.house.gov/ReserveCaucus/ngrcdir.html>

-   Public Broadcasting Caucus -
    <http://blumenauer.house.gov/Issues/CaucusSummary.aspx?NewsID=986&IssueID=0>

-   Republican Study Committee -
    <http://www.house.gov/hensarling/rsc/index.shtml>

-   Silk Road Caucus - <http://www.house.gov/pitts/silkroad.htm>

-   Victory in Iraq Caucus --

> <http://joewilson.house.gov/index.cfm?SectionID=69&ParentID=3&SectionTypeID=2&SectionTree=3,69>

**Websites of those caucuses (not registered with the House
Administration Committee as of November 8, 2007) that have websites:**

-   30 Something Working Group -
    <http://www.speaker.gov/30something/index.html>

-   Bipartisan Disabilities Caucus -
    <http://www.house.gov/ramstad/caucus/Disbility/disadv.htm>

-   Congressional Andean Region Caucus -
    <http://crowley.house.gov/issues/andean.htm>

-   Congressional Bangladeshi Caucus -
    <http://crowley.house.gov/issues/bangladeshi.htm>

-   Congressional Caucus on Fetal Alcohol Spectrum Disorders -
    <http://www.house.gov/pallone/fasd_caucus/>

-   Congressional Caucus on Sri Lanka and Sri Lankan Americans -
    <http://www.house.gov/pallone/srilankancaucus.shtml>

-   Congressional Croatian Caucus -
    <http://www.house.gov/radanovich/CroatianCaucus/>

-   Congressional Diabetes Caucus -
    <http://www.house.gov/degette/diabetes/index.html>

-   Congressional Entertainment Industries Caucus -
    <http://www.house.gov/watson/cec/>

-   Congressional Manufactured Housing Caucus -
    <http://calvert.house.gov/manufhousing.asp>

-   Congressional Privacy Caucus -
    <http://markey.house.gov/index.php?option=com_content&task=blogcategory&id=253&Itemid=81>

-   Congressional Rural Caucus -
    [http://www.house.gov/johnpeterson/ruralcaucus/CRC%20index.html](http://www.house.gov/johnpeterson/ruralcaucus/CRC index.html)

-   Congressional Task Force on International HIV/AIDS -
    <http://www.house.gov/mcdermott/issues_hivaids.shtml>

-   Congressional Wine Caucus - <http://www.house.gov/radanovich/wine/>

-   Democratic Women's Working Group,
    <http://www.speaker.gov/dwwg/index.html>

-   Former State Legislative Leaders Working Group -
    <http://www.house.gov/larson/sll.htm>

-   Green Scissors Caucus -
    <http://blumenauer.house.gov/Issues/CaucusSummary.aspx?NewsID=910&IssueID=0>

-   House Digital Divide Caucus -
    <http://www.house.gov/larson/digitaldivide/>

-   International Conservation Caucus -
    <http://www.royce.house.gov/internationalconservation/contact.htm>

-   Kashmir Forum - <http://www.house.gov/pitts/kashmir.htm>

-   Lewis and Clark Bicentennial Caucus -
    <http://blumenauer.house.gov/Issues/CaucusSummary.aspx?NewsID=983&IssueID=0>

-   Livable Communities Task Force -
    <http://blumenauer.house.gov/Issues/CaucusSummary.aspx?NewsID=1077&IssueID=0>

-   Results Caucus -
    <http://sessions.house.gov/Issues/Issue/?IssueID=1000>

# Appendix 4: \<meta\> and Related Tags

[Checkpoint 13.2 \[priority 2\] of the
W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-use-metadata) *Web
Content Accessibility Guidelines 1.0* provides that an accessible
website should "Provide metadata to add semantic information to pages
and sites." The following is a suggested list of tags for use by offices
of the U.S. House of Representatives. The list is designed to get the
best return for the time invested in inserting the tags into Web pages.
The tags are based on the following standards:

-   [Dublin Core Metadata Element Set, Version 1.1
    (revised)](http://dublincore.org/documents/dces/), Dublin Core
    Metadata Initiative; [^585]

-   [Platform for Internet Content Selection](http://www.w3.org/PICS/)
    (PICS) standard as promulgated by the Word Wide Web Consortium and
    implemented by [SafeSurf](http://www.safesurf.com/classify/) and the
    [Internet Content Rating
    Association](http://www.icra.org/webmasters/) (ICRA); and

-   [Robot meta-tag
    standard](http://www.robotstxt.org/wc/meta-notes.html), Spidering
    BOF Group (1996 Distributed Indexing/Searching Workshop of the World
    Wide Web Consortium).

The following list is divided into three parts. The first part consists
of tags that can be expected to remain consistent throughout a website.
The second part consists of tags that may change with each Web page. The
third part consists of content for the labels.rdf file needed to comply
with the current implementations of ICRA PICS labels and Dublin Core.

*Note*: When using these examples, replace text in ***red bold
italics*** with text appropriate for your office\'s Web pages.

**Tags That Are Likely to Remain Constant Throughout a Web Site**[^586]

+----------------------------------------------+-----------------------+
| **HTML Code**                                | **D                   |
|                                              | escription/Comments** |
+==============================================+=======================+
| \<link rel=\"schema.DC\"                     | Identifies the        |
| href=\"http://purl.org/DC/elements/1.1/\"    | location of the       |
| /\>\                                         | schemas for the       |
| \<link rel=\"schema.DCTERMS\"                | Dublin Core 1.1       |
| href=\"http://purl.org/DC/TERMS/\" /\>       | (revised), VW96, and  |
|                                              | ICRA PICS meta tags.  |
| \<link rel=\"meta\" href=\"labels.rdf\"      |                       |
| type=\"application/rdf xml\" title=\"ICRA    |                       |
| labels\" /\>                                 |                       |
+----------------------------------------------+-----------------------+
| \<link                                       | Replace               |
| h                                            | ***http://www.h       |
| ref=\"***http://www.house.gov/writerep/***\" | ouse.gov/writerep/*** |
| rel=\"EDITOR\" title=\"Feedback form\" /\>   | with the URL of the   |
|                                              | electronic form that  |
|                                              | constituents can use  |
|                                              | to contact the        |
|                                              | office.[^587]         |
+----------------------------------------------+-----------------------+
| \<meta http-equiv=\"Reply-To\"               | Your public e-mail    |
| content=\"***john.doe@mail.house.gov***\"    | address. If you do    |
| /\>\                                         | not have one, delete  |
| \<link                                       | these tags.[^588]     |
| h                                            |                       |
| ref=\"mailto:***john.doe@mail.house.gov***\" |                       |
| rel=\"AUTHOR\" title=\"Feedback by e-mail\"  |                       |
| /\>                                          |                       |
+----------------------------------------------+-----------------------+
| \<meta http-equiv=\"PICS-Label\"             | Identifies your site  |
| content=\'(PICS-1.1\                         | as **not**            |
| \"http://www.classify.org/safesurf/\" L gen  | containing: a chat    |
| true for\                                    | room, profanity,      |
| \"***http://www.house.gov/doe/***\" r        | heterosexual or       |
| (SS\~\~000 1))\' /\>\                        | homosexual themes,    |
| \<meta http-equiv=\"pics-Label\"             | nudity or sexual      |
| content=\'(pics-1.1                          | material, violence,   |
| \"http://www.icra.org/pics/vocabularyv03/\"  | bigotry, promotion or |
| l gen true for\                              | glorification of drug |
| \"***http://www.house.gov/doe/***\" r (n 0 s | use, other adult      |
| 0 v 0 l 0 oa 0 ob 0 oc 0 od 0 oe 0 of 0 og 0 | themes, gambling,     |
| oh 0 c 0) gen true for\                      | promotion of tobacco  |
| \"***http://www.house.gov/doe/***\" r (n 0 s | use, promotion of     |
| 0 v 0 l 0 oa 0 ob 0 oc 0 od 0 oe 0 of 0 og 0 | alcohol use,          |
| oh 0 c 0))\' /\>                             | promotion of weapon   |
|                                              | use, promotion of     |
|                                              | harm against people,  |
|                                              | material that might   |
|                                              | be perceived as       |
|                                              | setting a bad example |
|                                              | for children, or      |
|                                              | material that might   |
|                                              | disturb young         |
|                                              | children.\" Replace   |
|                                              | ***http://            |
|                                              | www.house.gov/doe/*** |
|                                              | with the name of the  |
|                                              | main URL of your      |
|                                              | website (on Member    |
|                                              | websites, this is     |
|                                              | normally either       |
|                                              | ***http://member's    |
|                                              | name.house.gov*** or  |
|                                              | ***http://w           |
|                                              | ww.house.gov/member's |
|                                              | name/***).            |
+----------------------------------------------+-----------------------+
| \<meta name=\"DC.subject.classification\"    | Library of Congress   |
| scheme=\"DCTERMS.LCSH\" content=\"United     | subject heading for   |
| States. Congress\" /\>                       | the page. ***United   |
|                                              | States. Congress***   |
|                                              | can be used as the    |
|                                              | LOC subject heading   |
|                                              | for any congressional |
|                                              | Web page. For more    |
|                                              | specific Library of   |
|                                              | Congress subject      |
|                                              | headings (as well as  |
|                                              | more specific Library |
|                                              | of Congress           |
|                                              | classification        |
|                                              | numbers and Dewy      |
|                                              | Decimal System        |
|                                              | classification        |
|                                              | numbers), see the     |
|                                              | [Library of Congress  |
|                                              | Online                |
|                                              | Catalog](http         |
|                                              | ://catalog.loc.gov/). |
+----------------------------------------------+-----------------------+
| \<meta name=\"DC.subject.classification\"    | Library of Congress   |
| scheme=\"DCTERMS.LCC\" content=\"JK1021\"    | classification number |
| /\>                                          | ***JK1021*** can be   |
|                                              | used as the LOC       |
|                                              | classification number |
|                                              | for any congressional |
|                                              | Web page. For more    |
|                                              | specific Library of   |
|                                              | Congress              |
|                                              | classification        |
|                                              | numbers, see the      |
|                                              | [Library of Congress  |
|                                              | Online                |
|                                              | Catalog](http         |
|                                              | ://catalog.loc.gov/). |
+----------------------------------------------+-----------------------+
| \<meta name=\"DC.subject.classification\"    | Dewy Decimal System   |
| scheme=\"DCTERMS.DDC\" content=\"328\" /\>   | classification number |
|                                              | ***328*** can be used |
|                                              | as the Dewy Decimal   |
|                                              | classification number |
|                                              | for any congressional |
|                                              | Web page. For more    |
|                                              | specific Dewy Decimal |
|                                              | System classification |
|                                              | numbers, see the      |
|                                              | [Library of Congress  |
|                                              | Online                |
|                                              | Catalog](http         |
|                                              | ://catalog.loc.gov/). |
+----------------------------------------------+-----------------------+
| \<meta name=\"DC.format.medium\"             | Use on any page with  |
| scheme=\"DCTERMS.IMT\" content=\"text/html\" | an .htm, .html,       |
| /\>                                          | .shtm, or .shtml      |
|                                              | extension.            |
+----------------------------------------------+-----------------------+
| \<meta name=\"DC.coverage.spatial\"          | Identifies the        |
| scheme=\"DCTERMS.ISO3166\" content=\"US\"    | national geographic   |
| /\>\                                         | coverage of the page  |
| \<meta name=\"DC.coverage.spatial\"          | as the United States. |
| scheme=\"DCTERMS.TGN\" content=\"United      |                       |
| States (C,V)\" /\>                           |                       |
+----------------------------------------------+-----------------------+
| \<link                                       | Location of the       |
| href=\"http://www.house.gov/***doe***/\"     | homepage of your      |
| rel=\"top\" title=\"home page of ***John W.  | website.              |
| Doe***\" /\>                                 |                       |
+----------------------------------------------+-----------------------+
| \<meta http-equiv=\"Content-Type\"           | Identifies the        |
| content=\"text/html; charset=***UTF-8***\"   | character set using   |
| /\>                                          | the standards set by  |
|                                              | the Internet Assigned |
|                                              | Numbers Authority     |
|                                              | (IANA). Of the [IANA  |
|                                              | sanctioned character  |
|                                              | sets](http:/          |
|                                              | /www.iana.org/assignm |
|                                              | ents/character-sets), |
|                                              | the World Wide Web    |
|                                              | Consortium suggests   |
|                                              | using the Unicode     |
|                                              | UTF-8                 |
|                                              | standard.[^589]^,^    |
|                                              | [^590] Note:          |
|                                              | selection of a        |
|                                              | character set **does  |
|                                              | not** affect the      |
|                                              | typefaces you select  |
|                                              | -- it only determines |
|                                              | which characters are  |
|                                              | valid characters.     |
+----------------------------------------------+-----------------------+
| \<!\-- Web designer: ***Jane Smith***        | Replace ***Jane       |
| (***House Information Resources***); site    | Smith*** with the     |
| published: ***date site was published***     | name of the           |
| \--\>                                        | designer(s) of the    |
|                                              | website. Replace      |
|                                              | ***House Information  |
|                                              | Resources*** with the |
|                                              | name of the company   |
|                                              | that the designer     |
|                                              | works for.[^591]      |
|                                              | Replace ***date site  |
|                                              | was published*** with |
|                                              | the date that the     |
|                                              | entire site was       |
|                                              | published (rather     |
|                                              | than the date any     |
|                                              | particular page was   |
|                                              | later added or        |
|                                              | modified on).         |
+----------------------------------------------+-----------------------+
| \<meta name=\"DC.creator\" content=\"United  | Your office.          |
| States. Congress. House of Representatives.  |                       |
| Office of ***Representative John W. Doe***\" |                       |
| /\>\                                         |                       |
| \<meta name=\"author\"                       |                       |
| content=\"***Representative John W. Doe***,  |                       |
| United States House of Representatives\" /\> |                       |
|                                              |                       |
| \<meta http-equiv=\"Owner\"                  |                       |
| content=\"***Representative John W. Doe***,  |                       |
| United States House of Representatives\" /\> |                       |
+----------------------------------------------+-----------------------+
| \<meta name=\"DC.rights\" content=\"United   | Copyrights in         |
| States Government work under 17 USC secs.    | congressional         |
| 105, 403\" /\>                               | publications are      |
|                                              | controlled by         |
|                                              | sections              |
|                                              | [105](ht              |
|                                              | tp://uscode.house.gov |
|                                              | /quicksearch/get.plx? |
|                                              | title=17&section=105) |
|                                              | and                   |
|                                              | [403](ht              |
|                                              | tp://uscode.house.gov |
|                                              | /quicksearch/get.plx? |
|                                              | title=17&section=403) |
|                                              | of title 17 of the    |
|                                              | United States Code.   |
+----------------------------------------------+-----------------------+
| \<meta name=\"DC.relation.conformsTo\"       | The web page that     |
| content=\"***Members\'*** Congressional      | lists what standards  |
| Handbook (Web Sites standards), Committee on | your site conforms.   |
| House Administration of the U.S. House of    | House committee       |
| Representatives; Technical Standards for     | websites should       |
| Web-based Intranet and Internet Information  | conform to the        |
| and Applications issued pursuant to section  | ***Committees'        |
| 508 of the Rehabilitation Act of 1973,       | Congressional         |
| Architectural and Transportation Barriers    | Handbook***, rather   |
| Compliance Board, 36 C.F.R. section 1194.22; | than to the           |
| Web Content Accessibility Guidelines (WCAG)  | ***Members'           |
| 1.0, World Wide Web Consortium (W3C);        | Congressional         |
| Platform for Internet Content Selection      | Handbook***.          |
| (PICS) standard as promulgated by the Word   |                       |
| Wide Web Consortium and implemented by       |                       |
| SafeSurf and the Internet Content Rating     |                       |
| Association; Dublin Core 1.1 (revised) meta  |                       |
| tag standard, Dublin Core Metadata           |                       |
| Initiative; Robot meta-tag standard,         |                       |
| Spidering BOF Group (1996 Distributed        |                       |
| Indexing/Searching Workshop of the World     |                       |
| Wide Web Consortium); XHTML 1.0              |                       |
| Specification (2nd edition), World Wide Web  |                       |
| Consortium; Children\'s Online Privacy       |                       |
| Protection Act of 1998 (15 U.S.C. chapter    |                       |
| 91); Children\'s Online Privacy Protection   |                       |
| Rule (16 C.F.R. part 312)\" /\>              |                       |
+----------------------------------------------+-----------------------+

**Tags That May Vary With Each Page Within a Web Site**

  ---------------------------------------------------------------------------------------------------------------------------------------------
  **HTML Code**                                                **Description/Comments**
  ------------------------------------------------------------ --------------------------------------------------------------------------------
  \<meta name=\"DC.title\" content=\"***Welcome!***\" /\>      Insert the title of the page.

  \<meta name=\"DC.description.abstract\"                      Brief description of the content (or purpose) of the page. Use the same
  content=\"***description of page of the Honorable John W.    description in both tags.
  Doe, Congressman from the \_\_th congressional district of   
  your state***\" /\>\                                         
  \<meta name=\"description\" content=\"***description of page 
  of the Honorable John W. Doe, Congressman from the \_\_th    
  congressional district of your state***\" /\>                

  \<meta name=\"keywords\" content=\"House of Representatives, List of words or phrases that may be useful to someone searching for your Web
  Congress, Representative ***John Doe, other important        page. Use synonyms for important words that may not actually appear in the text
  words***\" /\>                                               of you Web page.[^592]

  \<meta name=\"DC.identifier\" scheme=\"DCTERMS.URI\"         Insert the URL of the page.
  content=\"***http://www.house.gov/doe/pagename.htm***\" /\>  

  \<meta name=\"DC.date.modified\" scheme=\"DCTERMS.WTN8601\"  Date the page was last modified. Use the format yyyy-mm-dd.[^593]
  content=\"***2002-12-02***\" /\>                             

  \<meta name=\"DC.relation.isFormatOf\"                       If a copy of this page in a different format (e.g., a large font version, or a
  scheme=\"DCTERMS.URI\"                                       graphics-free version) exists, then use this tag to identify where it is. In the
  content=\"***http://www.house.gov/doe/OtherPageName.htm***   \<link\> tag, use:\
  /\>                                                              type=\"***text/html***\" for .htm, .html, .shtm, or .shtml files,\
                                                                   type=\"***image/jpeg***\" for .jpg files,\
                                                                   type=\"***image/gif***\" for .gif files, or\
                                                                   type=\"***application/pdf***\" for .pdf files

  \<meta name=\"DC.language\" scheme=\"DCTERMS.RFC4646\"       Identifies the language primarily used on the page as English (United States
  content=\"***en-US***\" /\>\                                 style). If your page is in another language, replace ***es-US*** according to
  \<meta http-equiv=\"Content-Language\"                       the instructions set out in Appendix 5: *Language Identification* of this
  content=\"***en-US***\" /\>                                  document.

  \<meta name=\"DC.type\" scheme=\"DCTERMS.DCMIType\"          Identifies that the page is primarily a non-interactive, text page. If the page
  content=\"***Text***\" /\>                                   is primarily an interactive form, then replace ***Text*** with
                                                               ***InteractiveResource***. If the page is primarily a graphic, replace
                                                               ***Text*** with ***Image***. For additional possible values, see the Dublin Core
                                                               Metadata Initiative's [DCMI Type
                                                               Vocabulary](http://dublincore.org/documents/dcmi-type-vocabulary/index.shtml)

  \<meta name=\"DC.rights.accessRights\"                       If the page is not to be available to the general public, replace ***public***
  content=\"***public***\" /\>                                 with a description of who may have access.

  \<meta name=\"robots\" content=\"***INDEX, FOLLOW***\" /\>   Allows the HIR indexing software (and other indexing software, e.g.,
                                                               [Google](http://www.google.com/support/webmasters/bin/answer.py?answer=61050))
                                                               to make your Web page searchable and to follow any links on your page. If your
                                                               page is primarily an interactive form, replace ***FOLLOW*** with ***NOFOLLOW***.
  ---------------------------------------------------------------------------------------------------------------------------------------------

#  {#section-1}

**Content of the labels.rdf file**

Each site should include a labels.rdf file containing the following XML
code:

\<?xml version=\"1.0\" encoding=\"iso-8859-1\"?\>

\<rdf:RDF

  xmlns:rdf=\"http://www.w3.org/1999/02/22-rdf-syntax-ns#\"

  xmlns:rdfs=\"http://www.w3.org/2000/01/rdf-schema#\"

  xmlns:dc=\"http://purl.org/dc/elements/1.1/\"

  xmlns:dcterms=\"http://purl.org/dc/terms/\"

  xmlns:label=\"http://www.w3.org/2004/12/q/contentlabel#\"

  xmlns:icra=\"http://www.icra.org/rdfs/vocabularyv03#\"\>

  \<rdf:Description rdf:about=\"\"\>

    \<dc:creator rdf:resource=\"http://www.icra.org\" /\>

    \<dcterms:issued\>2007-8-27\</dcterms:issued\>

   
\<label:authorityFor\>http://www.icra.org/rdfs/vocabularyv03#\</label:authorityFor\>

  \</rdf:Description\>

#   {#section-2}

# Appendix 5: Language Identification Codes [^594]

If the material is in English (as used in the United States), then the
language code is:

> en-US

If the material is **not** in English (as used in the United States),
then to determine the language code:

(1) find out from the person who supplied you with the text:

```{=html}
<!-- -->
```
(a) What language is the material in?

(b) Is the material in a version of the language that is associated with
    a particular country or region (e.g., Spanish as spoken in Mexico
    vs. Spanish as spoken throughout Latin America vs. Spanish as spoken
    in Spain)?

(c) If the material is text (as opposed to being audio), what alphabet
    (or script) is the material in?

```{=html}
<!-- -->
```
(2) Go to the IANA Language Subtag Registry at:

> <http://www.iana.org/assignments/language-subtag-registry>

(3) In the Registry, the information for language subtags is identified
    as **Type: language**. For instance:

> **Type:** language
>
> **Subtag:** fr
>
> **Description:** French
>
> **Added:** 2005-10-16
>
> **Suppress-Script:** Latn
>
> Find the appropriate language subtag and use this as the first part of
> the language tag.

(4) In the Registry, the information for alphabet subtags is identified
    as **Type: script**. Find the appropriate script subtag.

```{=html}
<!-- -->
```
(a) If the script subtag [is the same]{.underline} as the
    **Suppress-Script** value from the language subtag, then do not use
    the script tag. E.g., fr = French written with the Latin alphabet.

(b) If the script subtag [is not the same]{.underline} as the
    **Suppress-Script** value from the language subtag, then add a dash
    and the script subtag. E.g., ja-Latn = Japanese written with the
    Latin alphabet.

```{=html}
<!-- -->
```
(5) In the Registry, the information for country or region subtags is
    identified as **Type: region**.

```{=html}
<!-- -->
```
(a) If the language is normally associated with just one country (and
    the material is in that country's version of the language), then do
    not use the region subtag. E.g., ja = Japanese as used in Japan.

(b) Otherwise, add a dash and the region subtag. E.g.,

    -   es-PR = Spanish as used in Puerto Rico;

    -   es-419 = Spanish as used in Latin America;

    -   zh-Hant-TW = Chinese as used in Taiwan, written with traditional
        Han script.

> **Examples:**

  ------------- ---------------------------------------------------------
  en-US         English as used in the United States

  es-PR         Spanish[^595] as used in Puerto Rico

  es-MX         Spanish as used in Mexico

  es-419        Spanish as used in Latin America

  ar            Arabic[^596] (written in Arabic script)[^597]

  ar-Latn       Arabic, written in Latin script

  hy            Armenian[^598] (written in Armenian script)[^599]

  hy-Latn       Armenian written in Latin script

  ch            Chamorro (as used in Guam)

  zh-Hans-CN    Chinese[^600] as used in the Peoples Republic of China,
                written in simplified Han script[^601]

  zh-Hant-TW    Chinese as used in Taiwan, written in traditional Han
                script

  cho           Choctaw

  nl            Dutch[^602] (Flemish)

  fr-US         French as used in the United States[^603] (including
                Acadian)

  fr-CA         French as used in Canada

  de            German[^604]

  el            Greek (modern)[^605] (written in Greek script)[^606]

  ht            Haitian Creole[^607]

  haw           Hawaiian

  he            Hebrew[^608] (written in Hebrew script)[^609]

  he-Latn       Hebrew, written in Latin script

  hi            Hindi[^610] (written in Devanagari script)[^611]

  hi-Latn       Hindi, written in Latin script

  hmn-Hmng      Hmong,[^612] written in Pahawh Hmong script[^613]

  hmn-Latn      Hmong, written in Latin script

  it            Italian[^614]

  ja            Japanese[^615] (written in Han, Hiragana,[^616] and
                Katakana[^617] script)

  ja-Latn       Japanese, written in Latin script

  ko-Hang       Korean[^618], as written in Hangeul script[^619]^,^
                [^620]

  ko-Hani       Korean, as written in Hanja script

  ko-Latn       Korean, as written in Latin script

  lo            Lao[^621] (written in Lao script)[^622]

  lo-Latn       Lao, written in Latin script

  nv            Navajo

  fa            Persian (Farsi)[^623] (as written in Arabic script)[^624]

  fa-Latn       Persian (Farsi), as written in Latin script

  pl            Polish[^625]

  pt            Portuguese[^626]

  pt-BR         Portuguese as used in Brazil

  pa            Punjabi[^627] (written in Gurmukhi script)[^628]

  pa-Latn       Punjabi, written in Latin script

  ru            Russian[^629] (written in Cyrillic script)[^630]

  ru-Latn       Russian, written in Latin script

  sm            Samoan[^631]

  tl            Tagalog[^632] (as used in the Philippines, written in
                Latin script)

  tl-Tglg       Tagalog (as used in the Philippines), written in Tagalog
                script[^633]

  th            Thai[^634] (written in Thai script)[^635]

  th-Latn       Thai, written in Latin script

  uk            Ukrainian[^636] (written in Cyrillic script)

  uk-Latn       Ukrainian, written in Latin script

  vi            Vietnamese[^637]
  ------------- ---------------------------------------------------------

#  Appendix 6: Model Privacy Policy 

#  {#section-3}

# **English Language Version**[^638]

  -----------------------------------------------------------------------
  The following text should be placed in an HTML file (preferably with a
  .shtml extension):

  -----------------------------------------------------------------------

**\<h1\>Privacy Policy\</h1\>**

**\<p\>**We respect the privacy of our visitors and all those who come
in contact with our office **&#8212;** be it in-person, through our
website, or by mail, phone, or email. We therefore try to collect only
such personal information as is needed to provide the information,
service, or assistance that you request.**\</p\>**

**\<h2\>Information We Collect Automatically\</h2\>**

**\<p\>**If you visit our websites to browse, read, or download
information:**\<ul\>**

> **\<li\>**Your Web browser automatically sends us (and we may retain)
> information such as the:**\<ul\>**
>
> **\<li\>**Internet domain through which you access the Internet
> (**\<abbr title=\"for instance\"\>**e.g.**\</abbr\>**,
> yourServiceProvider.com if you use a commercial Internet service
> provider, or yourSchool.edu if you use an Internet account from your
> school);**\</li\>**
>
> **\<li\>**Internet Protocol address of the computer you are
> using;**\</li\>**
>
> **\<li\>**type of browser software and operating system you are
> using;**\</li\>**
>
> **\<li\>**date and time you access our site; and**\</li\>**
>
> **\<li\>**the Internet address of the site from which you linked
> directly to our site.**\</li\>\</ul\>\</li\>**
>
> **\<li\>**We will use this information as aggregate data to help us
> maintain this site, **\<abbr title=\"for
> instance\"\>**e.g.**\</abbr\>**, to determine the number of visitors
> to different sections of our site, to ensure the site is working
> properly, and to help us make our site more accessible and
> useful.**\</li\>**
>
> **\<li\>**We will not use this information to identify individuals,
> except for site security or law enforcement purposes.**\</li\>**
>
> **\<li\>**The office that maintains the Web server that our website
> resides on also has access to this information and is governed by its
> own **\<a href=\"\[URL of the Web host's privacy
> policy**[^639]**\]**\" **title=\"privacy policy of \[insert name of
> organization hosting Web site**[^640]**\]\"\>**privacy
> policy**\</a\>**. **\</li\>\</ul\>\</p\>**

**\<h2\>Other Information We Collect\</h2\>**

**\<p\>**If you choose to identify yourself (or otherwise provide us
with personal information) when you call us, write to us, send us
e-mail, or use our online forms:**\<ul\>**

-   

> **\<li\>**We will collect (and may retain) any personally identifying
> information, such as your name, street address, email address, and
> phone number, and any other information you provide to us. We will use
> this information to try to fulfill your request and may use it provide
> you with additional information at a later time. We will not disclose
> such information to third parties, except as specified in this privacy
> policy.**\</li\>**
>
> **\<li\>**If you request information, services, or assistance, we may
> disclose your personal information to those third parties that (in our
> judgment) are appropriate in order to fulfill your request. If, when
> you provide us with such information, you specify that you do not want
> us to disclose the information to third parties, we will honor your
> request. Note, however, that If you do not provide such information,
> it may be impossible for us to refer, respond to or fulfill your
> request.**\</li\>**

+-----------------------------------------------------------------------+
| Offices that store E-Newsletter distribution lists on servers outside |
| of HOUSE.GOV should add:                                              |
|                                                                       |
| \<li\>**If you sign up for** \[name of the office's e-newsletter\]**, |
| your subscription data (including your name and e-mail address) will  |
| be stored on a server outside of our office. The company that         |
| maintains that server may also have access to that information and is |
| governed by its own** \<a href=\"\[URL of the distribution service's  |
| privacy policy\]\" title=\"privacy policy of \[insert name of the     |
| distribution service\]\"\>**privacy policy**\</a\>.\</li\>            |
+-----------------------------------------------------------------------+

> **\<li\>**If your communication relates to a law enforcement matter,
> we may disclose the information to law enforcement agencies that we
> deem appropriate.**\</li\>\</ul\>\</p\>**

**\<h2\>How Long We Keep Information\</h2\>**

**\<p\>**We may keep information that will collect for an unlimited
period of time.**\</p\>**

**\<h2\>Security\</h2\>**

**\<p\>**Please note that electronic communication, particularly e-mail,
is not necessarily secure against interception. Please **\<strong\>do
not\</strong\>** send sensitive data (**\<abbr title=\"for
instance\"\>**e.g.**\</abbr\>**, Social Security, bank account, or
credit card numbers) by e-mail.**\</p\>**

###############################  {#section-4 .unnumbered}

+-----------------------------------------------------------------------+
| **Offices that want to rigorously comply with OMB Guidance for        |
| Implementing the Privacy Provisions of the E-Government Act of 2002   |
| (OMB Memorandum M-03-22) should insert the following:**               |
|                                                                       |
| #####################  {#section-5 .unnumbered}                       |
|                                                                       |
| **\<h2\>Privacy Act\</h2\>**                                          |
|                                                                       |
| **\<p\>**Although our office is not covered by the **\<a              |
| href=\"[http://uscode.house.g                                         |
| ov/quicksearch/get.plx?title=5&section=552a]{.underline}\"\>**Privacy |
| Act**\</a\>**, we will attempt to treat your information as if the    |
| Privacy Act applied to it.**\</p\>**                                  |
+-----------------------------------------------------------------------+

**\<h2\>Cookies\</h2\>**

**\<p\>**We do not use persistent **&#8220;**cookies**&#8221;** on this
website. **\[if session cookies are used, (1) indicate that here; (2)
indicate what information is collected; (3) indicate what the
information is used for; (4) provide an explanation what session cookies
are, e.g., "Session cookies are temporary files that are erased when you
close all browsers."; and (5) indicate if accepting cookies is voluntary
or mandatory for using the site (or for using a specific portion of the
website), e.g., "Accepting session cookies on our site is voluntary; you
may still use the site if you decline cookies."\]\</p\>**

###############################  {#section-6 .unnumbered}

**\<h2\>Contacting Us\</h2\>**

**\<p\>**If you would like to contact us concerning our privacy policy
or our use of information collected through this website, please contact
us at:**\</p\>**

> **\<p class=\"contactInfo\"\>\[Name of office\]\<br /\>**
>
> **\[Street Address\]\<br /\>**
>
> **\[City, State, and Zip Code\]\</p\>**
>
> **\<p class=\"contactInfo\"\>**By telephone: **\[telephone
> number\]\</p\>**
>
> **\<p class=\"contactInfo\"\>**By e-mail: **\[public e-mail address or
> URL for contact form\]\</p\>**

# **P3P Reference File**[^641]

  -----------------------------------------------------------------------
  The following text should be placed in an XML file named w3c/p3p.xml:

  -----------------------------------------------------------------------

\<?xml version=\"1.0\" ?\>

\<META xmlns=\"http://www.w3.org/2000/12/P3Pv1\"\>

\<POLICY-REFERENCES\>

\<EXPIRY max-age=\"**86400**\" /\>

\<POLICY-REF about=\"**\[URL of the P3P policy file, e.g.,
http://jones.house.gov/p3p/privacy.xml\]**\"\>

\<INCLUDE\>/\*\</INCLUDE\>

\<EXCLUDE\>\</EXCLUDE\>

\</POLICY-REF\>

\</POLICY-REFERENCES\>

\</META\>

+-----------------------------------------------------------------------+
| **Note c**oncerning **\<EXPIRY max-age=\"86400\" /\>:**               |
|                                                                       |
| "max-age=\"86400\"" means that this XML file will not change in the   |
| next 24 hours (86,400 seconds = 24 hours). **If, you decide to change |
| this file**, replace "max-age" with "date" and replace "86400" with   |
| the expiration date and time of this XML file, in the format: Thu, 02 |
| Aug 2007 13:00:00 GMT                                                 |
+-----------------------------------------------------------------------+

# **P3P Policy File**[^642]

  -----------------------------------------------------------------------
  The following text should be placed in an XML file named
  w3c/policy.xml:

  -----------------------------------------------------------------------

\<?xml version=\"1.0\" ?\>

\<POLICIES xmlns=\"http://www.w3.org/2000/12/P3Pv1\"\>

> \<POLICY name=\"default\" discuri=\"**\[URL the English language
> version of your privacy notice\]**\" xml:lang=\"en-US\"\>
>
> \<ENTITY\>
>
> \<DATA-GROUP\>
>
> \<DATA ref=\"#business.name\"\>**\[Name of your office\]**\</DATA\>
>
> \<DATA ref=\"#business.contact-info.postal.street\"\>**\[Street
> address\]**\</DATA\>
>
> \<DATA
> ref=\"#business.contact-info.postal.city\"\>**\[city\]**\</DATA\>
>
> \<DATA
> ref=\"#business.contact-info.postal.stateprov\"\>**\[state\]**\</DATA\>
>
> \<DATA ref=\"#business.contact-info.postal.postalcode\"\>**\[zip
> code\]**\</DATA\>
>
> \<DATA
> ref=\"#business.contact-info.postal.country\"\>**\[country\]**\</DATA\>
>
> \<DATA
> ref=\"#business.contact-info.telecom.telephone.intcode\"\>1\</DATA\>
>
> \<DATA
> ref=\"#business.contact-info.telecom.telephone.loccode\"\>**\[your
> telephone area code\]**\</DATA\>
>
> \<DATA
> ref=\"#business.contact-info.telecom.telephone.number\"\>**\[your
> 7-digit telephone number\]**\</DATA\>
>
> \<DATA ref=\"#business.contact-info.telecom.fax.intcode\"\>1\</DATA\>
>
> \<DATA ref=\"#business.contact-info.telecom.fax.loccode\"\>**\[your
> fax area code\]**\</DATA\>
>
> \<DATA ref=\"#business.contact-info.telecom.fax.number\"\>**\[your
> 7-digit fax number\]**\</DATA\>
>
> \<DATA ref=\"#business.contact-info.online.email\"\>**\[your office's
> public e-mail address, if any\]**\</DATA\>
>
> \<DATA ref=\"#business.contact-info.online.uri\"\>**\[URL for your
> electronic contact form or use:
> http://www.house.gov/writerep/\]**\</DATA\>
>
> \</DATA-GROUP\>
>
> \</ENTITY\>
>
> \<ACCESS\>
>
> \<none /\>
>
> \</ACCESS\>

+-----------------------------------------------------------------------+
| "*\<ACCESS\>\<none /\>\</ACCESS\>*" indicates that the users of the   |
| website do not have the right to access this data about them          |
| collected through the site. The other options set out in [§ 3.2.5 of  |
| the W3C](http://www.w3.org/TR/P3P/#ACCESS) *Platform For Privacy      |
| Preferences 1.0 (P3P1.0) Specification* are:                          |
|                                                                       |
| -   \<all /\> - users have the right to access this data about them   |
|     collected through the site                                        |
|                                                                       |
| -   \<contact and other /\> - users have the right to access this     |
|     online and physical contact information about them as well as to  |
|     certain other identified data                                     |
|                                                                       |
| -   \<ident-contact /\> - users have the right to access this online  |
|     and physical contact information (e.g., postal address) about     |
|     them collected through the site.                                  |
|                                                                       |
| -   \<other-dent /\> - user have the right to access other identified |
|     data collected through this website.                              |
+-----------------------------------------------------------------------+

> \<DISPUTES-GROUP\>
>
> \<DISPUTES resolution-type=\"service\" service=\"**\[URL for your
> contact page\]**\"\>
>
> \<LONG-DESCRIPTION\>If you have concerns about our privacy policy (or
> about its implementation), please contact us at **\[your phone
> number\]**\</LONG-DESCRIPTION\>
>
> \<REMEDIES\>
>
> \<correct /\>
>
> \</REMEDIES\>
>
> \</DISPUTES\>
>
> \</DISPUTES-GROUP\>
>
> \<STATEMENT\>
>
> \<CONSEQUENCE\>If you visit our websites to browse, read, or download
> information, your Web browser automatically sends us (and we may
> retain) information such as (1) the Internet domain through which you
> access the Internet (e.g., yourServiceProvider.com if you use a
> commercial Internet service provider, or yourSchool.edu if you use an
> Internet account from your school); (2) the Internet Protocol address
> of the computer you are using; (3) the type of browser software and
> operating system you are using; (4) the date and time you access our
> site; and (5) the Internet address of the site from which you linked
> directly to our site. We will use this information as aggregate data
> to help us maintain this site, e.g., to determine the number of
> visitors to different sections of our site, to ensure the site is
> working properly, and to help us make our site more accessible and
> useful. We will not use this information to identify individuals,
> except for site security or law enforcement purposes. The office that
> maintains the Web server that our website resides on also has access
> to this information and is governed by its own privacy
> policy.\</CONSEQUENCE\>
>
> \<PURPOSE\>
>
> \<current /\>
>
> \<admin /\>
>
> \<develop /\>
>
> \<other-purpose\>site security or law enforcement\</other-purpose\>
>
> \</PURPOSE\>

  -----------------------------------------------------------------------
  "*\<PURPOSE\>\<current /\>\<admin /\>\<develop /\>\<other-purpose\>site
  security or law enforcement\</other-purpose\>\</PURPOSE\>*" indicates
  that the information collected through the site will be used (1) to
  accomplish the task that the information was provided to the office to
  accomplish, (2) to administer the site, (3) to make improvements to the
  site, or (4) site security or law enforcement. A complete list of the
  possible values for the \<PURPOSE\> element is set out at [§ 3.3.4 of
  the W3C](http://www.w3.org/TR/P3P/#PURPOSE) *Platform for Privacy
  Preferences 1.0 (P3P1.0) Specification*.

  -----------------------------------------------------------------------

> \<RECIPIENT\>
>
> \<ours /\>

  -----------------------------------------------------------------------
  The \<ours /\> tag within the \<RECIPIENT\> element indicates that the
  office that owns the website has access to the information.

  -----------------------------------------------------------------------

> \<other-recipient\>
>
> \<recipient-description\>In addition to our office, House Information
> Resources (the computer staff of the United States House of
> Representatives) may have access to this information. Their privacy
> policy is set out at http://www.house.gov/house/privacy.shtml. **\[If
> the website is hosted by a vendor add: Additionally, \[name of vendor
> providing Web hosting services to the office\], which maintains the
> Web server that our website resides on, may have access to this
> information. Their privacy policy is set out at \[URL of vendor's
> privacy policy\].\]**\</recipient-description\>
>
> \</other-recipient\>
>
> \<unrelated\>
>
> \<recipient-description\>law enforcement\</recipient-description\>
>
> \</unrelated\>

  -----------------------------------------------------------------------
  "*\<unrelated\>\<recipient-description\>law
  enforcement\</recipient-description\> \</unrelated\>*" indicates that
  the information collected through the site may be released to law
  enforcement agencies.

  -----------------------------------------------------------------------

> \<unrelated\>
>
> \<recipient-description\>anyone you authorize us to release
> information to\</recipient-description\>
>
> \</unrelated\>

  -----------------------------------------------------------------------
  "*\<unrelated\>\<recipient-description\>anyone you authorize us to
  release information to\</recipient-description\>\</unrelated\>*"
  indicates that the information collected through the site may be
  released to anyone authorized by the person originally providing the
  information. For instance, if a constituent asks that a House office to
  intervene on their behalf with a government agency, and authorizes the
  office to use information provided by the constituent (e.g., the
  constituent's name, age, or telephone number), the office may provide
  that information to the government agency.

  -----------------------------------------------------------------------

> \</RECIPIENT\>
>
> \<RETENTION\>
>
> \<indefinitely /\>
>
> \</RETENTION\>

  -----------------------------------------------------------------------
  "*\<RETENTION\>\<indefinitely /\>\</RETENTION\>*" indicates that
  information collected through the site may be retained indefinitely. A
  complete list of the possible values for the \<RETENTION\> element is
  set out at [§ 3.3.6 of the W3C](http://www.w3.org/TR/P3P/#RETENTION)
  *Platform for Privacy Preferences 1.0 (P3P1.0) Specification*.

  -----------------------------------------------------------------------

> \<DATA-GROUP\>
>
> \<DATA ref=\"#dynamic.miscdata\"\>
>
> \<CATEGORIES\>
>
> \<physical /\>
>
> \<online /\>
>
> \<purchase /\>
>
> \<computer /\>
>
> \<navigation /\>
>
> \<interactive /\>
>
> \<content /\>
>
> \<state /\>
>
> \<preference /\>
>
> \<government /\>
>
> \</CATEGORIES\>

  -----------------------------------------------------------------------
  A complete set of the possible values of the \<CATEGORIES\> element is
  set out at [§ 3.4 of the W3C](http://www.w3.org/TR/P3P/#Categories)
  *Platform for Privacy Preferences 1.0 (P3P1.0) Specification*.

  -----------------------------------------------------------------------

> \</DATA\>
>
> \</DATA-GROUP\>
>
> \</STATEMENT\>
>
> \</POLICY\>
>
> \</POLICIES\>

+-----------------------------------------------------------------------+
| **Note:**                                                             |
|                                                                       |
| If the site uses cookies, add the following tags after                |
| \</RETENTION\>. A complete set of possible values for the             |
| \<CATEGORIES\> element is set out at [§ 3.4 of the                    |
| W3C](http://www.w3.org/TR/P3P/#Categories) *Platform for Privacy      |
| Preferences 1.0 (P3P1.0) Specification*.                              |
|                                                                       |
| > \<DATA ref=\"#dynamic.cookies\"\>                                   |
| >                                                                     |
| > \<CATEGORIES\>                                                      |
| >                                                                     |
| > **\<physical /\>\<uniqueid /\>\<state /\>\<preference /\>**         |
| >                                                                     |
| > \</CATEGORIES\>                                                     |
| >                                                                     |
| > \</DATA\>                                                           |
+-----------------------------------------------------------------------+

# **P3P \<link\>**[^643]

Between the \<head\> tag and the \</head\> tag on each page on the
website (not just on the Privacy Policy page), add:

> \<link rel=\"P3Pv1\" href=\"**\[URL of the policy reference file\]**\"
> /\>

For example: \<link rel=\"P3Pv1\"
href=\"http://jones.house.gov/w3c/p3p.xml\" /\>

# **P3P compact policy**[^644]

If your site uses cookies, include a \<meta\> tag along the lines of the
following example on each HTML page of your site, between the \<head\>
and \</head\> tags:

> \<meta http-equiv=\'P3P\' content=\'policyref=**\[URL of the P3P
> reference file, e.g., http://www.house.gov/doe/w3c/p3p.xml\]**,
> CP=\"**CUR ADM DEV OTP OUR OTR UNR IND PHY ONL UNI PUR COM NAV INT CNT
> STA PRE GOV DSP NON COR**\"\' /\>

A complete list of the "CP" attribute values is at [§ 4.2 of the W3C
Platform for Privacy
Preferences](http://www.w3.org/TR/P3P/#compact_policy_vocabulary) *1.0
(P3P1.0) Specification*.

[^1]: Dr. Ben Shneiderman, writing in the U.S. Department of Health and
    Human Services' *Research-Based Web Design & Usability Guidelines*,
    2^nd^ edition, pages iv to v, observes:

    > the greatest benefits from \[web design\] . . . guidelines will
    > accrue to those who create effective processes for their
    > implementation. My advice is to recognize the Guidelines as a
    > 'living document' and then apply the four Es: education,
    > enforcement, exemption, and enhancement.
    >
    > **Education:** Delivering a document is only the first stage in
    > making an organization's guidelines process effective. Recipients
    > will have to be motivated to read it, think about it, discuss it,
    > and even complain about it. Often a live presentation followed by
    > a discussion can be effective in motivating use of guidelines.
    >
    > **Enforcement:** While many designers may be willing to consider
    > and apply the guidelines, they will be more diligent if there is a
    > clear process of interface review that verifies that the
    > guidelines have been applied. This has to be done by a
    > knowledgeable person and time has to be built into the schedule to
    > handle deviations or questions.
    >
    > **Exemption:** Creative designers may produce innovative
    > compelling Web page designs that were not anticipated by the
    > Guidelines writers. To support creative work, managers should
    > balance the enforcement process with an exemption process that is
    > simple and rapid.
    >
    > **Enhancement:** No document is perfect or complete, especially a
    > guidelines document in a fast changing field like information
    > technology. This principle has two implications. First, it means
    > that \[the\] . . . organization should produce an annual revision
    > that improves the Guidelines and extends them to cover novel
    > topics. Second, it means that adopting organizations should
    > consider adding local guidelines keyed to the needs of their
    > community. This typically includes guidelines for how the
    > organization logo, colors, titles, employee names, contact
    > information, etc. are presented. Other common additions are style
    > guides for terminology, templates for information, universal
    > usability requirements, privacy policies, and legal guidance.

[^2]: [Checkpoint 4.2 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WCAG10/#tech-expand-abbr) *Web Content
    Accessibility Guidelines 1.0* provides that accessible websites need
    to "\[s\]pecify the expansion of each abbreviation or acronym in a
    document where it first occurs."

    For more information on the \<abbr\> tag, see "[Accessible Web
    Pages: Abbreviations and
    Acronyms](http://intranet.house.gov/xd03_training/ecybercongress/summer2005/accessible_web_pages.shtml),"
    *e-CyberCongress Connection*, summer 2005. A more rigorous approach
    based on current standards as well as the draft W3C [*Web Content
    Accessibility Guidelines 2.0*](http://www.w3.org/TR/WCAG20/) and the
    draft W3C [*XHTML 2.0 Specification*](http://www.w3.org/TR/xhtml2/),
    is set out in Colin Lieberman's "[The Accessibility Hat Trick:
    Getting Abbreviations
    Right,](http://www.alistapart.com/articles/hattrick)" A List Apart
    (January 16, 2006).

[^3]: Acronyms are words formed from the initial letter(s) of the phrase
    they originally represented -- for instance NASA (**N**ational
    **A**eronautics and **S**pace **A**dministration), COPPA
    (**C**hildren's **O**nline **P**rivacy **P**rotection **A**ct), and
    radar (**ra**dio **d**etecting **a**nd **r**anging). Acronyms are
    normally pronounced as they are spelled, while abbreviations
    normally are pronounced as the word that they are abbreviating
    (e.g., "Dr." is normally pronounced "Doctor" (or "Drive", depending
    on the context) and not "dir").

[^4]: [Checkpoint 4.2 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WCAG10/#tech-expand-abbr) *Web Content
    Accessibility Guidelines 1.0* provides that accessible websites need
    to "\[s\]pecify the expansion of each abbreviation or acronym in a
    document where it first occurs."

    For more information on the \<acronym\> tag, see "[Accessible Web
    Pages: Abbreviations and
    Acronyms](http://intranet.house.gov/xd03_training/ecybercongress/summer2005/accessible_web_pages.shtml),"
    *e-CyberCongress Connection*, summer 2005.

[^5]: See, for instance, the ["About" page of the House Science and
    Technology Committee](http://science.house.gov/about/default.htm)
    (formerly the Democratic Office of the Science Committee). The
    Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=55)
    (p. 45) praises the website for

    > showcasing information in a way that improves the users' sense of
    > the depth and breadth of the committee's duties. Users can browse
    > easily through the detailed description of the committee's
    > jurisdiction . . .

    The report ([page
    47](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=57))
    also praises the website of the [House Majority
    Leader](http://majorityleader.house.gov/about_the_whip/the_whip_s_role/)
    (which was then the website of the House Democratic Whip) for their
    inclusion of information on the role of the office.

[^6]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=54)
    (p. 44) praises the 109^th^ Congress website of the House Budget
    Committee (now the [Republican Office of the Budget
    Committee](http://www.house.gov/budget_republicans/budgettutorial.shtml))
    for providing "a general introduction for newcomers" while being
    primarily "geared toward an audience of experts familiar wit the
    budget process."

    The report (page 45) also praises the website of the 109^th^
    Congress website of the House Science Committee Democratic Office
    (now the website of the [Science and Technology
    Committee](http://science.house.gov/about/default.htm))

[^7]: Jakob Nielsen, in "[*About Us* Information on
    Websites](http://www.useit.com/alertbox/about-us-pages.html)"
    (September 29, 2008), notes:

    > Representing a\[n\] . . . organization on the Internet is one of a
    > website\'s most important jobs. Effectively explaining the . . .
    > \[organization's\] purpose and what it stands for provides
    > essential support for any of the other website goals.
    >
    > Unfortunately, while most websites offer an *AboutUs* section,
    > they often do a poor job communicating the crucial information it
    > should contain. . . .
    >
    > To direct users to your *About Us* section, I recommend offering a
    > **homepage link** labeled either *About \<name-of-company\>* or
    > *About Us*. This link need not be the most prominent on the
    > homepage, but it should be present and easily visible. In our
    > studies \[of websites of government agencies, non-profits, and
    > various size for-profits,\] users had trouble locating . . .
    > \[organization\] information when the link had a nonstandard name,
    > like *Info Center*, or when it was placed near graphical elements
    > that looked [like advertisements and was thus
    > ignored](http://www.useit.com/alertbox/banner-blindness.html).
    >
    > We recommend providing *About Us* information at **4 levels of
    > detail:**

    **Tagline** on the homepage: A few words or a brief sentence
    summarizing what the organization does.

    **Summary:** 1-2 paragraphs at the top of the main *About Us* page
    that offer a bit more detail about the organization\'s goal and main
    accomplishments.

    **Fact sheet:** A section following the summary that elaborates on
    its key points and other essential facts about the organization.

    **Detailed information:** Subsidiary pages with more depth for
    people who want to learn more about the organization.

    Jakob Nielsen and Hoa Loranger, in *Prioritizing Web Usability*,
    2006 (p. 115) recommend that the *About* information also include:

    The organization\'s top executive or official

    Correct contact information

    The organization\'s philosophy

    Historical timeline and milestones

[^8]: See, e.g., [Rep. Jesse Jackson, Jr.'s accessibility
    policy](http://www.house.gov/jackson/Privacy.shtml#accessibility).

[^9]: [Checkpoint 9.5 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-keyboard-shortcuts)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    web sites should:

    > Provide keyboard shortcuts to important links (including those in
    > [*[client-side image
    > maps]{.underline}*](http://www.w3.org/TR/WAI-WEBCONTENT/wai-pageauth.html#image-map)),
    > form controls, and groups of form controls. . . .
    >
    > For example, in HTML, specify shortcuts via the "accesskey"
    > attribute.

    To implement the W3C standard, the Government of the United Kingdom
    has adopted the following standards for accesskey attributes
    ([*Illustrated Handbook for Web Management
    Teams*](http://www.cabinetoffice.gov.uk/e-government/resources/handbook/html/2-4.asp#2.4.4),
    § 2.4.4):

    > S -- Skip navigation\
    > 1 -- Home page\
    > 2 -- What's new\
    > 3 -- Site map\
    > 4 -- Search\
    > 5 -- Frequently Asked Questions (FAQ)\
    > 6 -- Help\
    > 7 -- Complaints procedure\
    > 8 -- Terms and conditions\
    > 9 -- Feedback form\
    > 0 -- Access key details

    The Canadian Government's [*Common Look and Feel* standards best
    practices](http://www.tbs-sct.gc.ca/clf-nsi/6/skip_e.asp) -- which
    largely follows the W3C standard -- on the other hand, provides
    that:

    > Following the identification of a conflict between the Access keys
    > previously recommended on the CLF \[(Common Look and Feel)\] Web
    > site for site navigation on GoC \[(Government of Canada)\] Web
    > sites, and the proprietary assignment of access keys being used in
    > commercially available software, e.g. speech enabled Web browsers,
    > the CLF Access Working Group has made the following
    > recommendations for amendment to the CLF best practices:

    The use of Access Keys M, 1 and 2 be eliminated, and the use of any
    other access keys is discouraged because there is no way of knowing
    which access keys conflict with any assistive technology or other
    applications installed and running on users' desktops.

    An extensive review of ALT-character combinations that are already
    defined for various browsers and screen readers is set out at John
    Foliot's "[Using Accesskeys -- Is it worth
    it?](http://www.wats.ca/show.php?contentid=32)" WATS.ca, October
    2006. Virtually no characters appear to be unclaimed.

    Additional material on use of the "accesskey" attribute can be found
    at:

    "[Accesskey standards](http://www.clagnut.com/blog/193)," by Richard
    Rutter

    "[Accesskeys and Reserved Keystroke
    Combinations](http://www.wats.ca/show.php?contentid=43)"

    "[Using accesskey Attribute in HTML Forms and
    Links](http://www.cs.tut.fi/~jkorpela/forms/accesskey.html)" by
    Jukka Korpela.

[^10]: [Section 4.2 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.2)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that "XHTML
    documents must use lower case for all HTML element and attribute
    names." [Checkpoint 11.1 \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^11]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=55)
    (pages 43, 46, 47, and 94) identifies including up-to-date
    information about the office's legislative and other accomplishments
    (particularly from the current Congress) as an element of a
    successful Congressional website. The report ([pages 62, 67, 71, 74,
    and
    75](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=74))
    particularly praises [Rep. Tom Allen's
    website](http://tomallen.house.gov/index.cfm?ParentID=9&SectionID=72&SectionTree=7,9,72)
    for "an interactive map shows the Congressman's activities and
    accomplishments by county"; [Rep. J. Randy Forbes's
    website](http://forbes.house.gov/Issues/) for its "issues section
    \[which\] describes the Congressman's most recent actions and
    accomplishments on each of his priority issues"; Rep. Patrick
    Murphy's "[local
    issues](http://www.patrickmurphy.house.gov/index.php?option=com_content&task=view&id=36&Itemid=69)"
    page which highlights the congressman's accomplishments on local
    issues; [Rep. Cliff Stearns's Web](http://www.house.gov/stearns/)
    site for providing information on his accomplishments; and [Sen.
    John Cornyn's
    website](http://cornyn.senate.gov/public/index.cfm?FuseAction=IssueStatements.KeyIssues)
    for "a list of accomplishments and an updated description of his
    work on each issue in the current Congress."

[^12]: The Congressional Management Foundation's [*Congress Online 2003:
    Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=31)
    (page 23) praises Rep. Chaka Fattah's website "section called '*How
    Government Works'* that explores the impact of the federal
    government in his district, explains how citizens' tax dollars are
    spent, and answers general questions about Congress". Also, see Rep.
    Jesse Jackson, Jr.'s ["Accomplishments"
    page](http://www.house.gov/jackson/AwardedGrants.shtml).

[^13]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=47)
    (page 37) praises Rep. Carolyn Maloney's site for providing
    information on her accomplishments (her website has "My Work in
    Congress" as a major navigation button. That section includes a
    "[Legislative
    Accomplishments](http://maloney.house.gov/index.php?option=com_content&task=view&id=733&Itemid=37)"
    page).

[^14]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    (Sections
    [11.2.1](http://www.w3.org/TR/html4/struct/tables.html#h-11.2.1),
    [11.2.2](http://www.w3.org/TR/html4/struct/tables.html#h-11.2.2),
    [13.7.4](http://www.w3.org/TR/html4/struct/objects.html#h-13.7.4),
    [15.1.2](http://www.w3.org/TR/html4/present/graphics.html#h-15.1.2),
    [15.3](http://www.w3.org/TR/html4/present/graphics.html#h-15.3), and
    [17.10](http://www.w3.org/TR/html4/interact/forms.html#adef-align-LEGEND)
    of the W3C *HTML 4.01 Specification* designate the "align" attribute
    of the following tags as deprecated attributes: \<caption\>,
    \<div\>, \<h1\> to \< h6\>, \<hr\>, \<iframe\>, \<img\>, \<legend\>,
    \<object\>, \<p\>, and \<table\>).

[^15]: To align left, use: margin: 0 auto 0 0

    To align right, use: margin: 0 0 0 auto

    Note: In Internet Explorer 6 and 7, the "auto" value of the "margin"
    property is only supported when the browser is in Standards Mode
    (Internet Explorer's Standards Mode is the equivalent of Mozilla's
    Almost Standards Mode). To ensure that IE7 is in Standards Mode, use
    one of the XHTML 1.0 \<!DOCTYPE\> declarations from the W3C
    [*Recommended List of
    DTDs*](http://www.w3.org/QA/2002/04/valid-dtd-list.html). To ensure
    that IE6 is in Standards Mode, use one of the XHTML 1.0 \<!DOCTYPE\>
    declarations from the W3C *[Recommended List of
    DTDs](http://www.w3.org/QA/2002/04/valid-dtd-list.html)* and make
    sure that the \<!DOCTYPE\> declaration is the first thing in the
    file. For additional \<!DOCTYPE\> declarations that are compatible
    with Internet Explorer being in Standards Mode, see Henri Sivonen's
    [*Activating the Right Layout Mode Using the Doctype
    Declaration*](http://hsivonen.iki.fi/doctype/).

[^16]: A CAO-WSB analysis of www.house.gov usage for July 9 to 15, 2008,
    indicates that the following browsers each accounted for at least
    0.1% of the identifiable, non-robot access to the site:

    Internet Explorer 7.x 46.32%

    Internet Explorer 6.x 30.30%

    Firefox 2.x 13.15%

    Firefox 3.x 5.01%

    Internet Explorer 5.x 1.39%

    Firefox 1.x 0.45%

    Safari 0.35%

    Opera 0.21%

    Netscape 7.x 0.11%

[^17]: See [§
    17.10](http://www.w3.org/TR/html4/interact/forms.html#h-17.10) of
    the W3C *HTML 4.01 Specification*. ([Checkpoint 3.2 \[priority 2\]
    of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-grammar)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "validate to published formal grammars.")

[^18]: [Checkpoint 11.1 \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

    [Section C.12 of the
    W3C](http://www.w3.org/TR/xhtml1/guidelines.html#C_12) *XHTML 1.0
    (2^nd^ edition) Specification* provides that:

    > In both SGML and XML, the ampersand character (\"&\") declares the
    > beginning of an entity reference (e.g., &reg; for the registered
    > trademark symbol \"®\"). Unfortunately, many HTML user agents have
    > silently ignored incorrect usage of the ampersand character in
    > HTML documents - treating ampersands that do not look like entity
    > references as literal ampersands. XML-based user agents will not
    > tolerate this incorrect usage, and any document that uses an
    > ampersand incorrectly will not be \"valid\", and consequently will
    > not conform to this specification. In order to ensure that
    > documents are compatible with historical HTML user agents and
    > XML-based user agents, ampersands used in a document that are to
    > be treated as literal characters must be expressed themselves as
    > an entity reference (e.g. \"&amp;\"). For example, when the href
    > attribute of the a element refers to a CGI script that takes
    > parameters, it must be expressed as
    > http://my.site.dom/cgi-bin/myscript.pl?class=guest&amp;name=user
    > rather than as
    > http://my.site.dom/cgi-bin/myscript.pl?class=guest&name=user.

[^19]: [Checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 13.4 of the
    W3C](http://www.w3.org/TR/html4/struct/objects.html#edef-APPLET)
    *HTML 4.01 Specification* designates the \<applet\> tag as a
    deprecated element).

[^20]: For additional information, see David Wheeler's "[Curling Quotes
    in HTML, SGML, and
    XML](http://www.dwheeler.com/essays/quotes-in-html.html)."

[^21]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=58)
    (pages 46 and 95) identifies having an archive of the Member's
    "columns or op-ed pieces" as an element of a successful
    Congressional website. The report ([pages
    73](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=85)
    and 75) praises the website of Sen. Chris Dodd for cross referencing
    to his op-eds throughout the site.

    See also [Rep. Jesse Jackson, Jr.'s
    website](http://www.house.gov/jackson/News.shtml#speeches), which
    has articles available by issue or in chronological order.

[^22]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=58)
    (page 46) observes that:

    > The most important thing to consider is presenting the wealth of
    > information the office produces in the most usable way possible.
    > Virtually all offices already allow the press access to the most
    > recent information by providing press releases arranged by date.
    > But many users are interested in specific topics or issues. It is
    > much more likely that they want to know the latest news or action
    > on their topic of interest---say, the environment or the war in
    > Iraq---than they want to see the last three press releases or
    > floor speeches the Member has released. Organize all of the press
    > resources by topic and type. Users are more likely to read
    > articles and watch or listen to video or audio if they don't have
    > to wade through an endless chronological list of unidentifiable
    > files. While this meets the needs of the press, keep in mind that
    > other key audiences, like lobbyists, academics, and interested
    > constituents will also be served by this information.

[^23]: Examples of websites that include material on the Artistic
    Discovery Contest include [Rep. Neil
    Abercrombie](http://www.house.gov/abercrombie/art_competition.shtml),
    [Rep. Robert
    Aderholt](http://aderholt.house.gov/?sectionid=35&sectiontree=3,35),
    [Rep. Tom
    Cole](http://www.cole.house.gov/congressional-art-competition.html),
    [Rep. Jim
    Cooper](http://www.cooper.house.gov/index.php?option=com_content&task=view&id=13&Itemid=28),
    [Rep. Bill
    Delahunt](http://www.house.gov/delahunt/artcomppictures.shtml),
    [Rep. Mike Honda](http://honda.house.gov/artistic-discovery.shtml),
    [Rep. Jesse Jackson,
    Jr.](http://www.house.gov/jackson/artistic-discovery.shtml), [Rep.
    Rick Larsen](http://www.house.gov/larsen/help/art.shtml), [Rep.
    Dennis Moore](http://moore.house.gov/service.asp?service_ID=7), and
    [Rep. Devin
    Nunes](http://nunes.house.gov/index.cfm?FuseAction=ConstituentServices.CongressionalArtCompetition).

[^24]: [Checkpoint 11.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-latest-w3c-specs)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "Use W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

    [Section 4.4 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.4) *XHTML
    1.0 Specification (2^nd^ edition)* provides that "\[a\]ll attribute
    values must be quoted, even those which appear to be numeric."

[^25]: [Checkpoint 11.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-latest-w3c-specs)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "Use W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

    [Section 4.2 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.2) *XHTML
    1.0 Specification (2^nd^ edition)* provides that "XHTML documents
    must use lower case for all HTML element and attribute names."

[^26]: [Checkpoint 11.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-latest-w3c-specs)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "Use W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

    [Section 4.5 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.5) *XHTML
    1.0 Specification (2^nd^ edition)* provides that "Attribute-value
    pairs must be written in full. Attribute names such as compact and
    checked cannot occur in elements without their value being
    specified."

[^27]: Line breaks in the "title" attributes of \<link rel=\"alternate\"
    type=\"application/rss+xml\"\> tags display as empty boxes (□) in
    ![](media/image13.png){width="0.16666666666666666in"
    height="0.16666666666666666in"} dropdown menu in Internet Explorer
    7.

[^28]: [Checkpoint 11.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-latest-w3c-specs)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "Use W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

    [Section C.5 of the W3C](http://www.w3.org/TR/xhtml1/#C_5) *XHTML
    1.0 Specification (2^nd^ edition)* recommends "Avoid line breaks and
    multiple white space characters within attribute values. These are
    handled inconsistently by user agents."

[^29]: [Checkpoint 11.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-latest-w3c-specs)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "Use W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

    [Section 4.11 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.11)
    *XHTML 1.0 Specification (2^nd^ edition)* provides that "HTML 4 and
    XHTML both have some attributes that have pre-defined and limited
    sets of values (e.g. the type attribute of the input element). In
    SGML and XML, these are called *enumerated attributes*. Under HTML
    4, the interpretation of these values was *case-insensitive*, so a
    value of TEXT was equivalent to a value of text. Under XML, the
    interpretation of these values is *case-sensitive*, and in XHTML 1
    all of these values are defined in lower-case."

[^30]: Aural Style Sheets should be used with caution. [Checkpoint 11.2
    \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    [Section A.1 of the
    W3C](http://www.w3.org/TR/CSS21/aural.html#aural-media-group)
    *Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification*
    provides that aural style sheets are deprecated.

[^31]: See, e.g., "[Dozens of U.S. Senators are Quietly Tracking Visits
    to their Web Sites even Though they have Publicly Pledged Not to Do
    So](http://news.com.com/Congress+hands+caught+in+the+cookie+jar/2163-1028_3-6020711.html?tag=nl)"
    by Declan McCullagh and Anne Broache, CNET News.com, January 6,
    2006.

[^32]: The [*Committees' Congressional
    Handbook*](http://cha.house.gov/committee_handbook.aspx#general5)
    (Web Site Regulations, General, § 5), issued by the House
    Administration Committee, provides that:

    > HIR will display an exit notice stating that users are leaving the
    > House of Representatives prior to linking to a non-House of
    > Representatives Web site. The exit notice will include a
    > disclaimer that neither Members nor the House are responsible for
    > the content of linked sites. Member offices maintaining their
    > sites on the Public web server are required to incorporate the
    > exit notice into their external links.

    Instructions for implementing the exit message can be found at
    HouseNet → Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance/) → HTML
    → Exit Message to External Web Sites.

[^33]: The [*Committees' Congressional
    Handbook*](http://cha.house.gov/committee_handbook.aspx#general5)
    (Web Site Regulations, General, § 5), issued by the House
    Administration Committee, provides that:

    > HIR will display an exit notice stating that users are leaving the
    > House of Representatives, prior to linking to a non-House of
    > Representatives Web site. The exit notice will include a
    > disclaimer that neither the committee nor the House is responsible
    > for the content of linked sites. Committees maintaining their
    > sites on the Public web server are required to incorporate the
    > exit notice into their external links.

[^34]: See <http://www.altavista.com/help/babelfish/babel_help>.

[^35]: Use the "background" property, rather than the "background-color"
    property.

    [Section 9.1 of the
    W3C](http://www.w3.org/TR/WCAG10-CSS-TECHS/#style-color-contrast)
    *CSS Techniques for Web Content Accessibility Guidelines 1.0*
    provides that "If specifying a foreground color, always specify a
    background color as well (and vice versa)."

[^36]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 15.1.1 of the
    W3C](http://www.w3.org/TR/html4/present/graphics.html#h-15.1.1)
    *HTML 4.01 Specification* designates the "bgcolor" attribute as a
    deprecated attribute).

[^37]: Use the "background" style sheets property, rather than the
    "background-image" property..

[^38]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 7.5.1 of the
    W3C](http://www.w3.org/TR/html4/struct/global.html#h-7.5.1) *HTML
    4.01 Specification* designates the "background" attribute as a
    deprecated attribute).

[^39]: [Checkpoint 2.2 \[priority 2 for images, priority 3 for text\]\]
    of the W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[e\]nsure 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."

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) identifies providing contrast between text and background
    as an element of a successful Congressional website. The report
    further notes that "While it seems basic, it is essential to present
    the content in a way that all users can read. Stay away from fonts,
    colors, or backgrounds that make the text difficult to read."

[^40]: [Guideline 1.4.6 \[level AAA\] of the World Wide Web Consortium's
    Web Content Accessibility Guidelines 2.0 (April 20, 2008, candidate
    recommendation)](http://www.w3.org/TR/WCAG20/#visual-audio-contrast7)
    provides that:

    > The visual presentation of
    > [text](http://www.w3.org/TR/WCAG20/#textdef%23textdef) and [images
    > of
    > text](http://www.w3.org/TR/WCAG20/#images-of-textdef%23images-of-textdef)
    > has a [contrast
    > ratio](http://www.w3.org/TR/WCAG20/#contrast-ratiodef%23contrast-ratiodef)
    > of at least 7:1, except for the following: . . .

    **Large Print:**
    [Large-scale](http://www.w3.org/TR/WCAG20/#larger-scaledef%23larger-scaledef)
    text and images of large-scale text have a contrast ratio of at
    least 5:1;

    **Incidental:** Text or images of text that are part of an inactive
    [user interface
    component](http://www.w3.org/TR/WCAG20/#user-interface-componentdef%23user-interface-componentdef),
    that are [pure
    decoration](http://www.w3.org/TR/WCAG20/#puredecdef%23puredecdef),
    that are [incidental text in an
    image](http://www.w3.org/TR/WCAG20/#incidentaltextdef%23incidentaltextdef),
    or that are not visible to anyone, have no minimum contrast
    requirement.

    **Logotypes:** Text that is part of a logo or brand name has no
    minimum contrast requirement.

    Another respected standard for determining the contrast between
    background and foreground is set out at [checkpoint 2.2 of the
    W3C](http://www.w3.org/TR/AERT#color-contrast) *Techniques for
    Accessibility Evaluation and Repair Tools* (April 26, 2000 working
    draft).

[^41]: Contrast Analyser 2.0 is available at
    <http://www.paciellogroup.com/resources/contrast-analyser.html>.

[^42]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(a))
    provide that "A text equivalent for every non-text element shall be
    provided (e.g., via \"alt\", \"longdesc\", or in element content)."

    [Checkpoint 1.1 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-text-equivalent) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should:

    > 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.

[^43]: Roger Hudson's "[Text Alternatives for
    Images](http://www.usability.com.au/resources/image-text.cfm)"
    (September 2003) recommends that Web designers **"**Avoid
    unnecessary terms. Don\'t use words like \'link\' or \'click here\'
    for images that are links. Screen readers will indicate if something
    is a link or not."

[^44]: Roger Hudson's "[Text Alternatives for
    Images](http://www.usability.com.au/resources/image-text.cfm)"
    (September 2003) recommends that Web designers not **"**use the
    image file name as the alt. Alternative text like \"02_cc_68.gif\",
    or even \"building.jpg\" are neither descriptive nor helpful."

[^45]: *Prioritizing Web Usability*, by Jakob Nielsen and Hoa Loranger,
    2006 (p. 27) recommends that the name (or logo) of the office
    sponsoring a website appear in the upper left corner of each Web
    page. The recommendation is designed to accommodate users who
    initially arrive at an interior page of a website (e.g., through a
    search engine). The recommendation notes:

    > Don't assume that users have followed a drill-down path to arrive
    > at the current page. They may have taken a different path than
    > what you intended and not have seen information that was contained
    > on higher-level pages.

[^46]: As with any moving image on a website, the regulations under §
    508 of the Rehabilitation Act of 1973 ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(j))
    provide that accessible Web pages "shall be designed to avoid
    causing the screen to flicker with a frequency greater than 2 Hz and
    lower than 55 Hz." [Checkpoint 7.1 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-flicker) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should:

    > [*[Until user
    > agents]{.underline}*](http://www.w3.org/TR/WAI-WEBCONTENT/wai-pageauth.html#until-user-agents)
    > allow users to control flickering, avoid causing the screen to
    > flicker. . . .
    >
    > **Note.** People with photosensitive epilepsy can have seizures
    > triggered by flickering or flashing in the 4 to 59 flashes per
    > second (Hertz) range with a peak sensitivity at 20 flashes per
    > second as well as quick changes from dark to light (like strobe
    > lights).

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (pages 40) also notes that:

    > While moving text and animations may look flashy, they can impair
    > the readability of the information, distract the user, and reduce
    > the usefulness of the site.

[^47]: Notes on how to implement this feature using iframes can be found
    in the "[IFRAME fading
    photo's](http://intranet.house.gov/htbin/blog_inc?BLOG,xd01_wsbblog,blog,999,All,Item not found,ID=060801_0194,TEMPLATE=postingdetail.shtml#COMMENTS)"
    section of the WSB Blog.

[^48]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(*l*))
    provide that

    > When pages utilize scripting languages to display content, or to
    > create interface elements, the information provided by the script
    > shall be identified with functional text that can be read by
    > assistive technology.

    Similarly, [Checkpoint 6.3 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-scripts) *Web Content
    Accessibility Guidelines 1.0* provides that an accessible website
    should:

    > 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.

[^49]: See also, the banner for [Rep. Mike Rogers of
    Alabama](http://www.house.gov/mike-rogers/).

[^50]: See, e.g., <http://www1.house.gov:801/oh14_latourette/>.

    The Congressional Management Foundation's 1999 report *Building Web
    Sites Constituents Will Use* (page 17) notes that:

    > It's extremely important that you identify every page of your site
    > as yours. However, using a banner that takes up 1/3 or more of the
    > screen serves no purpose and makes it difficult and frustrating
    > from users to read the information there're after because they
    > have to keep scrolling past the irrelevant banner in order to get
    > it.

    The Foundation's [*Congress Online 2003: Turning the Corner on the
    Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=62)
    (page 54) report goes on to say:

    > . . . using a banner or graphics that take up most of the screen
    > serves no purpose. It also makes it difficult and frustrating for
    > users to read the information they're after because they have to
    > keep scrolling to get the information they are seeking. At least
    > two thirds of every page on your site should contain useful
    > information.

[^51]: An alternative technology that can be used, if appropriate, is
    Scalable Vector Graphics. For information on SVG, see the W3C
    website at <http://www.w3.org/Graphics/SVG/>.

[^52]: To deal with users whose browsers are not supporting style
    sheets, Ross Howard's "[High-Resolution Image
    Printing](http://www.alistapart.com/articles/hiresprinting)," A List
    Apart (September 5, 2005), suggests using the "height" and "width"
    attributes of the \<img\> tag at "1". In the print style sheet, he
    suggests using the desired values for the "height" and "width"
    properties associated with the \<img\> banner to override the
    "height" and "width" attributes.

[^53]: Consider using "masthead" as an alternative to "banner".

[^54]: [Section 12.4 of the
    W3C](http://www.w3.org/TR/REC-html40/struct/links.html#h-12.4) *HTML
    4.01 Specification* provides that "When present, the
    [[BASE]{.underline}](http://www.w3.org/TR/REC-html40/struct/links.html#edef-BASE)
    element must appear in the
    [[HEAD]{.underline}](http://www.w3.org/TR/REC-html40/struct/global.html#edef-HEAD)
    section of an HTML document, before any element that refers to an
    external source. The path information specified by the
    [[BASE]{.underline}](http://www.w3.org/TR/REC-html40/struct/links.html#edef-BASE)
    element only affects URIs in the document where the element
    appears." ([Checkpoint 3.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-grammar)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "validate to published formal grammars.")

    Notwithstanding the W3C specification, some versions of Internet
    Explorer (prior to version 7.0) supported multiple \<base\> tags
    between the \<body\> and \</body\> tags. This support stopped with
    IE 7.0.

[^55]: [Section 4.6 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.6)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that "Empty
    elements must either have an end tag or the start tag must end with
    /\>. For instance, \<br/\> or \<hr\>\</hr\>." [Checkpoint 11.1
    \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^56]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=58)
    (pages 46) identifies providing an official biography as an element
    of a successful Congressional website.

[^57]: The Congressional Management Foundation's January 2002 report
    [*Congress Online: Assessing and Improving Capitol Hill Web
    Sites*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2002.pdf#page=22)
    (p. 16), recommends that "Every congressional Web site should
    include a biography and photo of the Member or Chairman as
    background information. Promotional materials are also appropriate
    in the Member information section of a congressional Web site,
    because it is what visitors are looking for when they click to it.
    Audiences are seeking to learn about the Member\'s priorities,
    interests, accomplishments, experience, and expertise."

[^58]: Rep. Rush Holt's biography, for example, mentions that he was
    awarded a patent for a solar energy device -- and links to the text
    of the patent at the U.S. Patent and trademark Office's website.

[^59]: See, for instance, the "[About the
    Leader](http://www.majorityleader.gov/about_the_whip/)" navigation
    and page on the website of the House Majority Leader. The
    Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=57)
    (page 47) praises that site (which was then the website of the House
    Democratic Whip) for including information on the role of the
    office.

[^60]: The Congressional Management Foundation's [*Congress Online 2003:
    Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=56)
    (page 48) recommends that Congressional websites include information
    on what a "Member, Chair, or Leader does on a given day." The
    [October 10, 2006 issue of the Congressional Management Foundation's
    *Congress Online*
    newsletter](http://www.cmfweb.org/CongressOnline101006.asp) praises
    Rep. José Serrano's "[The Job of a
    Congressman](http://www.house.gov/serrano/pdf/RepJob-booklet-web.pdf)"
    and Rep. Adam Smith's "[A Day in the
    Life](http://www.house.gov/adamsmith/students/day.shtml)." The CMF's
    [*2006 Gold Mouse Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=40)
    (p. 30) praises Rep. Brian Baird's website for having "[A Day on
    Capitol Hill](http://www.house.gov/baird/resources/day.shtml)"
    slideshow; praises ([page
    35](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=45))
    Rep. John Larson's website for linking to the Indiana University
    Center on Congress's "[Members of Congress and What They
    Do](http://congress.indiana.edu/learn_about/topic/members_of_congress.php)"
    page. The CMF's [*2007 Gold Mouse Report: Lessons from the Best Web
    Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=54)
    (page 42) identifies providing information on "what a Member does"
    as an element of a successful Congressional website; praises ([page
    67](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=79))
    the "[A Day in the Life of Congressman Randy
    Forbes](http://www.house.gov/sites/members/va04_forbes/newsroom/audiocenter/A Day in the life of Rep Forbes.mp3)"
    audio column on the website of Rep. J. Randy Forbes; and notes
    ([page
    21](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=33))
    that only 6% of House websites include information about what a
    Member does. Other examples of similar material include Rep. Bud
    Cramer's "[A Typical
    Week](http://cramer.house.gov/HoR/AL05/About+Bud/A+Typical+Week/A+typical+week.htm)"
    and former-Rep. Lee Hamilton's "[The Job of a
    Congressman](http://congress.indiana.edu/radio_commentaries/job_of_congressman.php)".

[^61]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=70)
    (pages 60 and 67) notes that

    > Congressional Web sites can demonstrate accountability by
    > providing voting records, rationales for key votes, and schedules
    > -- and they can do so without overburdening their staffs. Your
    > constituents are not interested in knowing about every meeting
    > that takes place or every vote taken. Stick to the most relevant
    > and current information: meetings with constituents, public Member
    > appearances in the district or state, committee hearings, the
    > House and Senate floor schedule.
    >
    > Most citizens do not understand, or are not familiar with, the
    > intricacies of the congressional schedule. In our research with
    > constituents, they assumed that their elected officials were
    > golfing or on vacation when Congress is in recess. While there
    > isn't much legislative activity to report during recesses, you can
    > correct this misperception by posting a schedule of town hall
    > meetings, reorganizing your home page content, or providing a
    > preview of what the Member, committee, Leader, or Congress will be
    > doing after the break. Every August we see scores of congressional
    > Web sites that haven't been updated since mid-July. Don't let
    > yours be one of them.

    The Congressional Management Foundation's [*Congress Online 2003:
    Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=31)
    (page 23) also praises the website for Rep. Earl Blumenauer for
    including the Congressman's weekly schedule.

[^62]: [Rep. Cynthia McKinney's
    website](http://web.archive.org/web/20060421022800/http:/www.house.gov/mckinney/monthly_calendar.shtml)
    used WIDA to provide her schedule.

[^63]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=23)
    (page 13) notes that:

    > The Internet is a fast-paced medium, and users expect up-to-date
    > information. No matter how well designed a site is or how much
    > content it has, it's not going to be useful for visitors if the
    > most current information they can find is six months, or even a
    > year old..

[^64]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=68)
    (p. 58) notes that:

    > While it shouldn't be the primary focus of the site, every
    > congressional website should include a section that contains
    > information about the Member's (or Leader's or committee's)
    > priorities, interests, accomplishments, experience, and expertise.

    The report (on [page
    32](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=42))
    praises the [biography section of Rep. Marion Berry's
    website](http://www.house.gov/berry/biography.shtml) for
    highlighting the Congressman's issues and accomplishments; praises
    (on [page
    40](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=50))
    the [biography on Rep. Charlie Norwood's
    website](http://www.connectingtocongress.org/snapshot/www.house.gov/norwood/bio.shtml)
    for clearly detailing his accomplishments and priorities; and
    praises (on [page
    69](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=79))
    the [biography section of Rep. John Mica's
    website](http://www.house.gov/mica/Micabio.shtml) for highlighting
    the Congressman's accomplishments and areas of interest.

[^65]: The Congressional Management Foundation, in its [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=93)
    (page 83) identifies having a blog as one of the elements of a well
    formed Congressional website. Before deciding whether to have a
    blog, however, the CMF report (page 71) recommends that offices
    consider the following:

    > **Can we dedicate the resources that would be necessary to
    > launch---and sustain---a blog?** The most precious resource in
    > most congressional offices is time--especially the Member's time.
    > A blog requires constant attention and staff resources--in most
    > cases taking the staffer away from other projects or duties. To be
    > a truly effective blogger requires a time commitment to
    > regularly--even daily--update and post new content to the blog. It
    > will also take staff time to read through and publish reader
    > comments and to respond when necessary. Be sure you are ready to
    > make the commitment; too many Members have launched blogs that
    > fall by the wayside because of insufficient resources.
    >
    > **Are we willing to allow constituents and other members of the
    > public to post comments to the blog?** A vast majority of the
    > mainstream blogs allow the moderator or other user to start a
    > "thread" to which viewers can comment. Will the office allow
    > comments--the good and the bad, the complimentary and the not so
    > complimentary? Good management policies will need to put in place
    > and enforced by the Member's staff to make sure the medium is not
    > abused or
    >
    > too one-sided.
    >
    > **Does the Member have something to say that isn't being said
    > somewhere else?** While blogs are becoming more and more prevalent
    > every day, not every Member should have a blog. People read blogs
    > because they provide information that they do not get from
    > traditional media sources. If the Member is worried about
    > alienating people and not willing to speak "off script," the blog
    > is
    >
    > probably not a good idea. Blogs are expected to provide unfiltered
    > and informal communication and personal perspective. In a world of
    > scripted speeches and carefully thought-out talking points, this
    > is a valid concern for Members and staff. Also, it is critical
    > that a blog be more than a different way to list press releases,
    > otherwise blog enthusiasts--your intended audience--will be the
    > first to
    >
    > notice and the last to return.
    >
    > **If we aren't ready for our own blog, what about guest blogging,
    > or special event blogging?** Many Members have been successful
    > players in the world of blogs by chiming in, or guest blogging, on
    > other mainstream blogs. Another alternative is for the Member to
    > publish a blog or trip diary during a significant event, like a
    > CODEL to Iraq, that chronicles the Member's impressions of what
    > they encounter. These blogs are a good way for Members to enter
    > into the blogosphere without overwhelming staff and running out of
    > interesting and relevant things to say.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=33)
    (page 21) indicates that 10% of House Member websites had blogs by
    mid-2007.

[^66]: The availability of the House Web Log Utility was announced on
    [December 11, 2006, through a Dear Colleague letter from the
    Chairman of the House Administration
    Committee](http://www.house.gov/webassistance/po_dc_12-11-06.pdf).

    For more information on the House Web Log Utility, see HouseNet →
    Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance/) →
    Tools → Blog.

[^67]: [Section 3.1 of the
    W3C](http://www.w3.org/TR/WCAG10-HTML-TECHS/#text-emphasis) *HTML
    Techniques for Web Content Accessibility Guidelines 1.0* provides
    that "The proper HTML elements should be used to mark up emphasis:
    [EM](http://www.w3.org/TR/WCAG10-HTML-TECHS/#edef-EM%23edef-EM) and
    [STRONG](http://www.w3.org/TR/WCAG10-HTML-TECHS/#edef-STRONG%23edef-STRONG).
    The [B](http://www.w3.org/TR/WCAG10-HTML-TECHS/#edef-B%23edef-B) and
    [I](http://www.w3.org/TR/WCAG10-HTML-TECHS/#edef-I%23edef-I)
    elements should not be used; they are used to create a visual
    presentation effect. The EM and STRONG elements were designed to
    indicate structural emphasis that may be rendered in a variety of
    ways (font style changes, speech inflection changes, etc.) ."

    Perhaps the one legitimate exception to this standard (and even
    then, one to be used with care) is when you are reproducing text
    that originally existed as non-World Wide Web printed text. As Paul
    Ford notes in "[Processing
    Processing](http://www.ftrain.com/ProcessingProcessing.html#3-anchor)"
    (September 2, 2003) (cited in Jeffrey Zeldman's, *Designing With Web
    Standards* (2^nd^ edition, \[2006\], p. 175):

    > When I\'m publishing content from 1901 and it\'s in italics, it\'s
    > in *italics,* not emphasized. Typography has a semantics that is
    > subtle, changing, and deeply informed by history.

[^68]: Jakob Nielsen and Hoa Loranger, in *Prioritizing Web Usability*,
    2006 (p. 275) note that:

    > Highlighting carefully chosen keywords can attract readers'
    > attention to specific areas of the page. Using design treatments
    > such as boldface or colored text adds emphasis and draws the eye
    > to important elements . . . . Highlighting entire sentences or
    > long phrases slows readers down, so single out just those words
    > and phrases that communicate key points. Emphasizing too many
    > items with color highlight or bold test causes diminishing
    > returns; nothing stands out; and the page just looks busy.

[^69]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=48)
    (page 38) praises Rep. Jeff Miller's website for putting "important
    information in bold."

[^70]: [Section 1.2.1 of the
    W3C](http://www.w3.org/TR/WCAG10-HTML-TECHS/#document-headers) *HTML
    Techniques for Web Content Accessibility Guidelines 1.0* provides
    that "Since some users skim through a document by navigating its
    headings, it is important to use them appropriately to convey
    document structure. Users should order heading elements properly.
    For example, in HTML, H2 elements should follow H1 elements, H3
    elements should follow H2 elements, etc. Content developers should
    not \"skip\" levels (e.g., H1 directly to H3). Do not use headings
    to create font effects; use [style sheets to change font
    styles](http://www.w3.org/TR/WCAG10-CSS-TECHS/#style-fonts) for
    example."

    In the Jaws screen reader, Insert+F6 generates a list of headers.

[^71]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 15.1.3 of the
    W3C](http://www.w3.org/TR/html4/present/graphics.html#h-15.1.3.2)
    *HTML 4.01 Specification* designates the "clear" attribute of the
    \<br\> tag as a deprecated attribute).

[^72]: [Section 4.6 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.6)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that "Empty
    elements must either have an end tag or the start tag must end with
    /\>. For instance, \<br/\> or \<hr\>\</hr\>."

    [Checkpoint 11.1 \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^73]: Websites that are hosted on the HIR UNIX server (and do not use a
    virtual URL) are encouraged to use the server-side include:

    > \<!\--#include
    > virtual=\"/house/subpage_content/browsealoud_content.html\" \--\>

    All other sites can use code along the lines of:

    > \<iframe
    > src=\"http://www.house.gov/house/subpage_content/browsealoud_content.html\"
    >
    > scrolling=\"auto\" style=\"width:35em;height:32em;\"
    > frameborder=\"0\" title=\"About the Browsealoud
    > plug-in\"\>\<ul\>\<li\>\<a
    >
    > href=\"http://www.house.gov/house/browsealoud.shtml\"\>About The
    > Browsealoud Plug-In\</a\>\</li\>\</ul\>\</iframe\>

    Using the \<include\> or \<iframe\> is preferable to just linking to
    the House's "About The Browsealoud Plug-In" page. Using \<include\>
    or \<iframe\> retains the consistent look and feel of the rest of
    the office's website. A consistent look and feel assists with
    compliance with [Checkpoint 13.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* which provides that an
    accessible website should "Use navigation mechanisms in a consistent
    manner."

    [Section 4 of the
    W3C](http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation) *Core
    Techniques for Web Content Accessibility Guidelines 1.0* further
    provides that:

    > A consistent style of presentation on each page allows users to
    > locate navigation mechanisms more easily but also to skip
    > navigation mechanisms more easily to find important content. This
    > helps people with learning and reading disabilities but also makes
    > navigation easier for all users. Predictability will increase the
    > likelihood that people will find information at your site, or
    > avoid it when they so desire.
    >
    > Examples of structures that may appear at the same place between
    > pages:

    navigation bars

    the primary content of a page

    > . . .
    >
    > A navigation mechanism creates a set of paths a user may take
    > through your site. Providing navigation bars, site maps, and
    > search features all increase the likelihood that a user will reach
    > the information they seek at your site. If your site is highly
    > visual in nature, the structure might be harder to navigate if the
    > user can\'t form a mental map of where they are going or where
    > they have been. To help them, content developers should describe
    > any navigation mechanisms. It is crucial that the descriptions and
    > site guides be accessible since people who are lost at your site
    > will rely heavily on them.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site:** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. ***Sen. John Cornyn***'s Web site is a
    > model of clearly and consistently organized information. The menu
    > headers and options are clear, and they stay the same throughout
    > the site.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^74]: <http://www.house.gov/images/browsaloud.gif>

[^75]: <http://www.house.gov/include_content/images/audio1.gif>

[^76]: <http://www.house.gov/include_content/images/leftnav_readtome.gif>

[^77]: <http://www.house.gov/include_content/images/baloud1.gif>

[^78]: <http://www.house.gov/include_content/images/logo_browsealoud.gif>

[^79]: For additional material on this subject, see the [letter from the
    World Wide Web Consortium to the U.S. Copyright Office concerning
    "37 CFR Part 202 \[Docket No. RM 2005-9\]," (August 22,
    2005)](http://www.w3.org/2005/08/22-w3c-prereg-standards-comments.html).

    Jeffrey Zeldman, in the second edition \[2006\] of *Designing With
    Web Standards* (pp. 33 & 37), notes that:

    > In a misguided effort to reduce expenses, an increasing number of
    > sites are designed to work only in Internet Explorer, and
    > sometimes only on the Windows platform, thus locking out 15-25% of
    > their potential visitors and customers. . . .
    >
    > I won't pretend to understand the business model of a company that
    > would say no to up to a quarter of its potential customers. And
    > the sheer number of customers lost by this myopic approach should
    > boggle the mind of any rational business owner or noncorporate
    > agency with a mandate to serve the public.
    >
    > Say you don't mind losing up to 25% of the people who choose to
    > visit your site. The "IE-only" approach still makes no sense
    > because there's no guarantee that IE (or even desktop browsers as
    > a category) will continue to dominate web space. For one thing, as
    > I write these words, Firefox continues to take market share away
    > from IE. For another, more people are getting their internet fix
    > via mobile devices, In the U.S., desktop browsing still far
    > outweighs mobile use; in Japan the reverse is true. While the
    > numbers are continually changing, the trend favors mobile
    > ([www.gotomobile.com](http://www.gotomobile.com/)). As ubiquitous
    > computing gains acceptance and creates new markets, the notion of
    > designing to the quirks of *any* individual desktop browser seems
    > more and more 20^th^ century and less and less intelligent.

    Zeldman also notes in "[99% of Websites Are
    Obsolete](http://www.digital-web.com/articles/999_of_websites_are_obsolete/)"
    (September 4, 2002):

    > Some years \[ago\] . . ., Netscape\'s Navigator browser enjoyed a
    > market share greater than Microsoft\'s Internet Explorer does
    > today. At the time, conventional wisdom held that Netscape\'s was
    > the only browser that mattered, and developers coded accordingly.
    > Untold millions of dollars later, the market changed.
    > Netscape-only sites were dumped in the landfill beside the
    > Information Superhighway.

[^80]: [Appendix A (items 4 to 7) of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#validation) *Web Content
    Accessibility Guidelines 1.0* recommends that websites be validated
    as accessible by use of various tools, including:

    Use a text-only browser or emulator.

    Use multiple graphic browsers, with:

    sounds and graphics loaded,

    graphics not loaded,

    sounds not loaded,

    no mouse,

    frames, scripts, style sheets, and applets not loaded

    Use several browsers, old and new.

    Use a self-voicing browser, a screen reader, magnification software,
    a small display, etc.

[^81]: Zytrax' "[Browser ID (User-Agent)
    Strings](http://www.zytrax.com/tech/web/browser_ids.htm)" is a
    useful tool for identifying the browser types associated with
    specific Web server log entries.

[^82]: Jakob Nielsen and Hoa Loranger in their *Prioritizing Web
    Usability*, 2006 (page 94) look at the question of where the cutoff
    should be in testing browser compatibility:

    > Is it worth testing your Web site . . . in order to cater to . . .
    > two percent of the market . . .? We would probably . . . say
    > "yes," at least for bigger Web sites for which a two percent
    > increase in business is worth more than a few tests and easy
    > fixes. Smaller sites, on the other hand, might decide that the . .
    > . return is insufficient to bother testing on \[small-share
    > browsers\]. . . . As always, with a limited budget, you must
    > choose your battles.

    For a different approach to identifying browsers that should be
    tested against, see "[Graded Browser
    Support](http://developer.yahoo.net/yui/articles/gbs/gbs.html)" by
    Nate Koechley.

[^83]: The [Congressional Management
    Foundation's](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=54)
    *Congress Online 2003: Turning the Corner on the Information Age*
    (p. 46) notes that "Committees and leadership offices with natural
    constituencies can also provide service information online. The
    *House Committee on Veterans' Affairs* Web site provides information
    on veterans' benefits for its key audience."

[^84]: For instructions for how to include the CRS-maintained "Business
    Opportunities with the Federal Government" material on a House
    website, see:

    > <http://housenet.house.gov/portal/server.pt?open=18&objID=600&parentname=CommunityPage&parentid=20&mode=2&in_hi_userid=2&cached=true>

[^85]: Using the \<include\> or \<iframe\> is preferable to just linking
    to the generic "Doing Business with the Federal Government" page.
    Using \<include\> or \<iframe\> retains the consistent look and feel
    of the rest of the office's website. A consistent look and feel
    assists with compliance with [Checkpoint 13.4 \[ priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* which provides that an
    accessible website should "\[u\]se navigation mechanisms in a
    consistent manner."

    [Section 4 of the
    W3C](http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation) *Core
    Techniques for Web Content Accessibility Guidelines 1.0* further
    provides that:

    > A consistent style of presentation on each page allows users to
    > locate navigation mechanisms more easily but also to skip
    > navigation mechanisms more easily to find important content. This
    > helps people with learning and reading disabilities but also makes
    > navigation easier for all users. Predictability will increase the
    > likelihood that people will find information at your site, or
    > avoid it when they so desire.
    >
    > Examples of structures that may appear at the same place between
    > pages:

    navigation bars

    the primary content of a page

    > . . .
    >
    > A navigation mechanism creates a set of paths a user may take
    > through your site. Providing navigation bars, site maps, and
    > search features all increase the likelihood that a user will reach
    > the information they seek at your site. If your site is highly
    > visual in nature, the structure might be harder to navigate if the
    > user can\'t form a mental map of where they are going or where
    > they have been. To help them, content developers should describe
    > any navigation mechanisms. It is crucial that the descriptions and
    > site guides be accessible since people who are lost at your site
    > will rely heavily on them.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site:** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. ***Sen. John Cornyn***'s Web site is a
    > model of clearly and consistently organized information. The menu
    > headers and options are clear, and they stay the same throughout
    > the site.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^86]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=49)
    (page 39) notes that "One of the keys to a successful Web site is
    building it around specifically targeted audiences" and praises the
    "[For \> Small
    Business](http://www.moore.house.gov/group.asp?group_id=2)" page on
    Rep. Dennis Moore's website. The report (page 34) also praises the
    small business section of the website of [Rep. Mike
    Honda](http://honda.house.gov/smallbusiness.shtml) and the "[Doing
    Business in
    Vermont](http://leahy.senate.gov/vermont/business/contacts.html)"
    page of the website of Sen. Patrick Leahy.

[^87]: The [November 12, 1997
    minutes](http://www.w3.org/XML/9712-reports.html#ID47) of the W3C's
    XML Working Group, for instance, notes that "Defining all keywords
    as uppercase would have the advantage of providing a very simple
    rule. For some W\[orking\] G\[roup\] members, the primary (and
    successful) objection to this approach was the familiar one that
    all-uppercase is unappealing and resembles shouting."

    Jakob Nielsen in "[Right-Justified Navigation Menus Impede
    Scannability](http://www.useit.com/alertbox/navigation-menu-alignment.html)"
    (April 28, 2008) also notes that using all caps "reduces legibility
    by about 10%. When you **mix cases**, the ascenders and decenders
    produce varied letterforms, while all caps produce boxy shapes.
    Users recognize words faster when you preserve traditional word
    shapes."

[^88]: "CAPTCHA" is the acronym for "Completely Automated Public Turing
    test to tell Computers and Humans Apart".

[^89]: [Section 1 of the W3C's WAI Protocols and Formats Working Group
    note](http://www.w3.org/TR/turingtest/#problem) *Inaccessibility of
    CAPTCHA: Alternatives to Visual Turing Tests on the Web*, November
    23, 2005, notes that:

    > This type of visual and textual verification comes at a huge price
    > to users who are blind, visually impaired or dyslexic. Naturally,
    > this image has no text equivalent accompanying it, as that would
    > make it a giveaway to computerized systems. In many cases, these
    > systems make it impossible for users with certain disabilities to
    > create accounts, write comments, or make purchases on these sites,
    > that is, CAPTCHAs fail to properly recognize users with
    > disabilities as human.

[^90]: [Section 3 of the W3C's WAI Protocols and Formats Working Group
    note](http://www.w3.org/TR/turingtest/#solutions) *Inaccessibility
    of CAPTCHA: Alternatives to Visual Turing Tests on the Web*,
    November 23, 2005, offers several additional alternatives.

[^91]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=54)
    (page 45) notes that

    > "Casework" is Hill jargon. Constituents will better understand
    > what the office can do if the Web site employs phrases such as
    > "Help with a problem you are having with a Federal Agency," "What
    > this office can do for you," or "Assistance with a government
    > problem," rather than using the term "casework." Sometimes
    > constituents may not even be aware that congressional offices can
    > help them. Describing what an office can and cannot do to help
    > constituents is as important as explaining how to initiate that
    > assistance.

    Section 5.1(4) of the W3C [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#writing-style)
    recommends "Avoid slang, jargon, and specialized meanings of
    familiar words, unless defined within your document" to implement
    [WCAG 1.0 checkpoint
    14.1](http://www.w3.org/TR/WCAG10/#tech-simple-and-straightforward)
    \[priority 1\], that accessible websites should "\[u\]se the
    clearest and simplest language appropriate for a site\'s content."

[^92]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 15.1.2 of the
    W3C](http://www.w3.org/TR/html4/present/graphics.html#edef-CENTER)
    *HTML 4.01 Specification* designates the \<center\> tag as a
    deprecated element. Sections
    [11.2.1](http://www.w3.org/TR/html4/struct/tables.html#h-11.2.1),
    [11.2.2](http://www.w3.org/TR/html4/struct/tables.html#h-11.2.2),
    [13.7.4](http://www.w3.org/TR/html4/struct/objects.html#h-13.7.4),
    [15.1.2](http://www.w3.org/TR/html4/present/graphics.html#h-15.1.2),
    [15.3](http://www.w3.org/TR/html4/present/graphics.html#h-15.3), and
    [17.10](http://www.w3.org/TR/html4/interact/forms.html#adef-align-LEGEND)
    of the W3C *HTML 4.01 Specification* designate the "align" attribute
    of the following tags as deprecated attributes: \<caption\>,
    \<div\>, \<h1\> to \< h6\>, \<hr\>, \<iframe\>, \<img\>, \<legend\>,
    \<object\>, \<p\>, and \<table\>).)

[^93]: Use the "background" property, rather than the
    "background-position" property.

[^94]: In Internet Explorer 6 and 7, the "auto" value of the "margin"
    property is only supported when the browser is in Standards Mode
    (Internet Explorer's Standards Mode is the equivalent of Mozilla's
    Almost Standards Mode). To ensure that IE7 is in Standards Mode, use
    one of the XHTML 1.0 \<!DOCTYPE\> declarations from the W3C
    [*Recommended List of
    DTDs*](http://www.w3.org/QA/2002/04/valid-dtd-list.html). To ensure
    that IE6 is in Standards Mode, use one of the XHTML 1.0 \<!DOCTYPE\>
    declarations from the W3C *[Recommended List of
    DTDs](http://www.w3.org/QA/2002/04/valid-dtd-list.html)* and make
    sure that the \<!DOCTYPE\> declaration is the first thing in the
    file. For additional \<!DOCTYPE\> declarations that are compatible
    with Internet Explorer being in Standards Mode, see Henri Sivonen's
    [*Activating the Right Layout Mode Using the Doctype
    Declaration*](http://hsivonen.iki.fi/doctype/).

[^95]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(a))
    provide that "A text equivalent for every non-text element shall be
    provided (e.g., via \"alt\", \"longdesc\", or in element content)."

    [Checkpoint 1.1 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-text-equivalent) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should:

    > 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. . . .
    >
    > For example, in HTML:

    Use \"alt\" for the IMG, INPUT, and APPLET elements, or provide a
    text equivalent in the content of the OBJECT and APPLET elements.

    For complex content (e.g., a chart) where the \"alt\" text does not
    provide a complete text equivalent, provide an additional
    description using, for example, \"longdesc\" with IMG or FRAME, a
    link inside an OBJECT element, or a [description
    link](http://www.w3.org/TR/WAI-WEBCONTENT/#d-link%23d-link).

    For image maps, either use the \"alt\" attribute with AREA, or use
    the MAP element with A elements (and other text) as content.

[^96]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(c))
    provide that "Web pages shall be designed so that all information
    conveyed with color is also available without color, for example
    from context or markup." An identical standard is set out in
    [Checkpoint 2.1 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-color-convey) *Web
    Content Accessibility Guidelines 1.0*.

[^97]: Lynda Weinman in [*The Browser-Safe Web
    Palette*](http://www.lynda.com/hex.html), acknowledges that "A lot
    of people credit me with the browser-safe palette, but it\'s a
    misplaced honor (if you can call it that!). I do have the
    distinction of being the first author to identify and publish the
    colors - but I can\'t take credit for creating them. . . . Though
    this might seem blasphemous to older readers of my books, or loyal
    website visitors, I believe it\'s safe to design without the
    palette. I believe this because so few computer users view the web
    in 256 colors anymore."

[^98]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 7.5.1 of the
    W3C](http://www.w3.org/TR/html4/struct/global.html#h-7.5.1) *HTML
    4.01 Specification* designates the "text" attribute as a deprecated
    attribute).

[^99]: [Section 3.2.4 of the
    W3C](http://www.w3.org/TR/html401/intro/sgmltut.html#h-3.2.4) *HTML
    4.01 Specification* provides that:

    > HTML comments have the following syntax:
    >
    > \<!\-- this is a comment \--\>
    >
    > \<!\-- and so is this one,
    >
    > which occupies more than one line \--\>
    >
    > White space is not permitted between the markup declaration open
    > delimiter(\"\<!\") and the comment open delimiter (\"\--\"), but
    > is permitted between the comment close delimiter (\"\--\") and the
    > markup declaration close delimiter (\"\>\"). A common error is to
    > include a string of hyphens (\"\-\--\") within a comment. Authors
    > should avoid putting two or more adjacent hyphens inside comments.

    [Checkpoint 3.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-grammar)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "validate to published formal grammars."

[^100]: The [*Members' Congressional
    Handbook*](http://cha.house.gov/official_and_representational_expenses_continued.aspx#Content)
    (Web Sites, Content, § 5), issued by the House Administration
    Committee, provides that:

    > The content of a Member's Web site: . . .
    >
    > 5\. May not include any advertisement for any private individual,
    > firm, or corporation, or imply in any manner that the government
    > endorses or favors any specific commercial product, commodity, or
    > service.

    An identical requirement is contained in the [*Committee's
    Congressional
    Handbook*](http://cha.house.gov/committee_handbook.aspx#content)
    (Web Site Regulations, Content, § e).

[^101]: [Rep. Earl Blumenauer has a Caucuses
    page](http://blumenauer.house.gov/index.php?option=com_content&task=view&id=279&Itemid=161)
    that links off the Issues section of his website. Rep. Blumenauer's
    Caucuses page lists all of the caucuses that he serves on. For the
    three caucuses that he is particularly involved with there are links
    to individual pages on his website that describe of the purpose and
    accomplishments of that caucus.

    The [Congressional Caucuses page of Rep. Illeana
    Ros-Lehtinen](http://www.house.gov/ros-lehtinen/cong-caucuses.shtml),
    provides a description of the purpose of each of the caucuses she
    co-chairs.

    A reasonably comprehensive list of caucus websites is set out in
    Appendix 3: *Caucus Web Sites* of this document.

[^102]: Most subcommittees have at least one Web page within their full
    committee's website.

[^103]: The [Congressional Management
    Foundation's](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=54)
    *Congress Online 2003: Turning the Corner on the Information Age*,
    (p. 46) praises [Rep. Mike Honda's
    website](http://honda.house.gov/mikeincongress.shtml) for indicating
    the Congressman's committee assignments. Rep. Honda has links to the
    committees and subcommittees that he serves on (indicating which
    subcommittee he serves as ranking member) and also links to the
    caucuses that he chairs.

[^104]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=45)
    (page 35) praises Rep. John Larson's "[Committees and
    Caucuses](http://www.house.gov/larson/committees.htm)" page because
    it "lists the committees on which he serves and explains the nature
    of their work" and praises Rep. Charlie Norwood's "[Committee
    Assignments](http://www.connectingtocongress.org/snapshot/www.house.gov/norwood/committees.shtml)"
    page because it "does not simply list the committees on which he
    serves, but also explains which issues are under their
    jurisdiction."

[^105]: Published Congressional committee hearing transcripts (and other
    materials) are available through the U.S Government Printing
    Office's GPO Access at
    <http://www.gpoaccess.gov/congress/index.html>. Because there is
    often a substantial delay between when a hearing is held and when
    the transcripts are published by the Government Printing Office,
    some committees also include the prepared statements that witnesses
    submit to the committee prior to the hearing. (see, e.g., the [House
    Agriculture Committee's hearings
    page](http://agriculture.house.gov/hearings/index.html) which has
    both the prepared statements and the GPO printed transcripts).

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=54)
    (pages 44 to 46) praises the House Budget Committee, Science
    Committee (Democratic Office), and Ways and Means Committee for
    including on their websites the transcripts of the hearings held by
    the committee. The report (on [page
    68](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=78))
    notes that only 28% of congressional committee websites included
    hearing transcripts.

[^106]: Instructions for using Thomas to link to all of the reports
    issued by a committee are set out at
    <http://www.congress.gov/help/THOMAS_links/comm.html#commcommittee>.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=56)
    (pages 46 and 49) praises the Ways and Means Committee and the
    Judiciary Committee for including the full text of their committee
    reports on their sites.

[^107]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=59)
    (page 49) praises the House Judiciary Committee for including the
    full text of its rules on its site.

[^108]: See, e.g., the individual subcommittee pages on the website of
    the [Natural Resources Committee (Republican
    Office)](http://republicans.resourcescommittee.house.gov/).

[^109]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=43)
    (pages 35) notes that "The goal of most minority offices is to use
    the Web to 'get their message out' to the public, press, and other
    congressional staff." It goes on to praise the minority website of
    the Government Reform Committee for including:

    Information on their "*special investigations*" that showcase their
    efforts to have their voice heard on the diverse issues that fall
    within their jurisdiction;

    *Interactive calculators*, designed to differentiate between the
    majority and the minority party's plans for Social Security and
    Prescription Drugs, make the site more interesting to visitors; and

    An Enron "*tip line*" allows citizens to submit information online
    and feel that they can contribute to the work of the minority
    office.

    The [report (page
    42)](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=50)
    also praises the [Energy and Commerce Committee (Democratic
    Office)](http://web.archive.org/web/20061205203830/www.house.gov/commerce_democrats/)
    for providing "statements, dissenting views, correspondence, and
    other information in a detailed and non-confrontational manner."

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=91)
    (page 79) praises Republican Office of the Senate Committee on
    Environment and Public Works for having "content \[that\] is also
    fully integrated and cross-referenced throughout the site. For
    instance, the issues section contains a brief statement by the
    Ranking Member, related press releases and speeches, as well as
    related facts of the day and blog posts."

[^110]: Icons to indicate compliance with other standards can be found
    at

    other W3C standards - <http://www.w3.org/QA/Tools/Icons>

    Dublin Core metadata standard - <http://dublincore.org/about/>

    W3C Web Content Accessibility Guidelines (and/or Section 508 of the
    Rehabilitation Act of 1973) as validated by HiSoft's "Cynthia Says"
    accessibility tester -
    <http://www.cynthiasays.com/org/cynthiatested.htm>

    ICRA implementation of the W3C PICS standard -
    <http://www.icra.org/_en/buttons/>

    SafeSurf implementation of the W3C PICS standard -
    <http://www.safesurf.com/safewave.htm>

    Microformat Standards (including hCard) -
    <http://microformats.org/wiki/buttons>

    Section 508 of the Rehabilitation Act of 1973:

    > ![](media/image14.png){width="0.9895833333333334in"
    > height="0.3229166666666667in"}

    Examples of compliance icons can be found on the websites of [Rep.
    Frank Lucas](http://www.house.gov/lucas/index.shtml) (508 Bobby
    Approved), [Rep. Buck McKeon](http://mckeon.house.gov/) (Bobby
    Approved), [Rep. Jim
    Saxton](http://www.house.gov/saxton/site-tools.shtml) (W3C XHTML 1.0
    checked), and the [LGBT Equality
    Caucus](http://lgbt.tammybaldwin.house.gov/) (W3C WCAG version 1.0,
    level AA).

[^111]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=29)
    (pages 21 and 25) praises the "Highlighting Delawareans" page on
    Senator Tom Carper's website for "posting constituent photo
    galleries and congratulating constituents on their accomplishments";
    and the website of Representative Richard Pombo for having "An
    extensive gallery of constituent photos". See also the ["Photo
    Album" on Rep. Marsha Blackburn's
    website](http://www.house.gov/blackburn/photoalbum.shtml).

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=93)
    (page 83) identifies including "photos of constituents on the home
    page" as an element of a well-formed Congressional website.

[^112]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=93)
    (page 83) identifies having an "Answers FAQ regarding constituent
    casework" and providing "guidance on how constituents can initiate
    casework" as two elements of well-designed Congressional websites.
    The report ([pages 30 to
    38](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=40))
    praises Rep. Brian Baird's website for having "an informative FAQ
    section, which contains casework questions, \[and\] an [example of
    an actual case](http://www.house.gov/baird/cs/agency.shtml)"; Rep.
    John Linder's website for providing a
    "[casework](http://linder.house.gov/index.cfm?FuseAction=Resources.Home&Resource_id=2BC9E53F-657A-4648-A032-37E80B88B611)
    section takes his constituents step-by-step through the process of
    determining eligibility and opening up a case"; and [Rep. Xavier
    Becerra](http://becerra.house.gov/HoR/CA31/Constituent+Services/Casework+Page.htm)'s
    website for providing

    > \[a\] constituent services section \[that\] guides users through
    > every step in the casework process. The site allows users
    > determine whether the office can help, takes them through FAQs
    > that give them the tools to resolve an issue on their own, and
    > gives clear guidance on what information the office needs in order
    > to open a case.

    The report also notes that "Congressman \[Mike\] Honda's [casework
    section](http://honda.house.gov/helpwithfederalagencies.shtml)
    accommodates those who may be unaccustomed to governmental
    operations"; praises the website of [Rep. John
    Larson](http://www.house.gov/larsen/help/casework.shtml) for having
    a "casework assistance \[section\] that is geared toward informing
    uninitiated users."; praises the constituent services section of
    [Rep. Marion
    Berry](http://www.house.gov/berry/services/helpwithafederalagency.shtml)'s
    website for providing "both FAQs for selected agencies and the steps
    necessary to initiate an agency inquiry"; praises [Rep. Jeff
    Miller](http://jeffmiller.house.gov/index.cfm?FuseAction=FAQs.Home)'s
    website for providing "easily accessible" constituent FAQs; and
    ([page
    50](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=60))
    praises the "\[i\]nteractive casework section" of [Rep. Brian
    Higgins' website](http://higgins.house.gov/casework.asp).

    The Foundation's [*Congress Online 2003: Turning the Corner on the
    Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=64),
    (p. 57) praises [Rep. Steve Rothman's
    website](http://www.rothman.house.gov/index.php?option=com_content&task=view&id=29&Itemid=39)
    for providing a "step-by-step casework guide. . . to help citizens
    who need assistance from federal agencies."

    Rep. Jim Moran's
    "[Casework](https://forms.house.gov/moran/casework.shtml)" page also
    provides step-by-step directions for getting help with Federal
    agency problems -- including a FAQ.

[^113]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 61) notes that "Congressional jargon and the legislative
    process can be difficult for most people off the Hill to understand.
    Focus on making the information on your site understandable, rather
    than impressive and official-sounding."

    [Rep. Jesse Jackson,
    Jr.](http://www.house.gov/jackson/ConstituentServices.shtml) uses
    "How I Can Help You". [Rep. Ben
    Chandler](http://chandler.house.gov/) uses "How Can We Help You?".
    [Rep. Spencer Bachus](http://bachus.house.gov/hor/al06/) uses
    "Helping You". [Rep. Frank
    Pallone](http://www.house.gov/pallone/index.shtml) uses "How Can I
    Help". [Rep. Ginny
    Brown-Waite](http://brown-waite.house.gov/ConstituentServices/) uses
    "How Can Ginny Help You?" [Rep. Dennis
    Moore](http://moore.house.gov/services.asp) uses "Assistance".

[^114]: Instructions for using CAO-Web Solutions Branch's form_proc
    software to do this are available on HouseNet at HouseNet →
    Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance/) → HTML
    → FormProc.

    Form_proc is the software suggested in Congressional Management
    Foundation's [*Congress Online 2003: Turning the Corner on the
    Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=65),
    (p. 57): "House offices can also simplify their e-mail management by
    utilizing the customized Web-based forms available from House
    Information Resources (i.e. for tour requests, scheduling requests,
    casework, feedback, etc.)."

[^115]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=23)
    (page 11) notes that:

    > Citizens typically access congressional Web sites for a specific
    > reason. Seeking assistance from the Senator or Representative is
    > one of them. When they access a Web site they are seeking
    > information online, not offline. It is essential that
    > congressional offices provide information and guidance about
    > constituent services online, rather than requiring citizens to
    > contact the office by phone to get answers to even basic
    > constituent service questions.

    The report ([page
    39](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=51))
    goes on to recommend that "a site should provide easy and quick
    access to contact information including each office's telephone
    number, address, as well as a link to an e-mail contact form on
    every page. This is a standard for Web sites in Congress and the
    Internet at large, so it is more likely that users will expect the
    information on every page".

[^116]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=93)
    (page 83) identifies including "a casework privacy release form" as
    an element in a well constructed Congressional website. Nonetheless,
    the report ([page
    4](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=14))
    indicates that "30.9% of all Member websites do not have a
    self-service privacy release form available for constituents."

[^117]: Instructions for setting up secure forms are set out at HouseNet
    → Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance) →
    Features and Scripts → Online Forms -- Secure Forms.

[^118]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=80)
    (page 68) praises [Rep. Mike Honda's
    website](http://honda.house.gov/helpwithfederalagencies.shtml) for
    including "Extensive links and clear information about federal
    agencies, state and local government, and community service
    providers is offered for problems that fall outside the office's
    jurisdiction."

[^119]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 61) notes that "Congressional jargon and the legislative
    process can be difficult for most people off the Hill to understand.
    Focus on making the information on your site understandable, rather
    than impressive and official-sounding."

[^120]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) notes that:

    > When users are interested in a topic, they want everything related
    > to it, without having to start a new search in every section of
    > the site. Even simply linking to related sections of your Web site
    > and cross-referencing your content can go a long way toward making
    > your site usable.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=62)
    (page 50) further notes that "Putting time and effort into one
    feature or element of the website and then posting it only in one
    place increases the likelihood it gets overlooked."

[^121]: The May 2006 edition of the FTC's report also mentions the
    consumer protection pages on the websites of [Rep. Spencer
    Bachus](http://bachus.house.gov/HoR/AL06/Helping+You/Consumer+Information/),
    [Rep. Bob
    Goodlatte](http://www.house.gov/goodlatte/consumerfraud.htm), [Rep.
    Sue
    Kelly](http://web.archive.org/web/20060207192318/suekelly.house.gov/consumerprotection.asp),
    and [Rep. Dennis
    Moore](http://moore.house.gov/service.asp?service_ID=9).

[^122]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=67)
    (page 57) notes that:

    > Many offices use their Web sites to direct constituents to contact
    > them offline for the information and services they are seeking.
    > Yet, people who choose the Web as their method of contacting a
    > congressional office are doing so precisely because they prefer to
    > have their needs met online. Respond to their needs accordingly,
    > and you will find you have more satisfied "customers," at less
    > effort and expense to the office than you ever thought possible.

    When the Foundation's 2003 report was compiled ([*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=55),
    (p. 47)), 97% of House Member, committee, and leadership websites
    provided this capability.

[^123]: Instructions for using CAO-Web Solutions Branch's form_proc
    software to do this are available on HouseNet at HouseNet →
    Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance/) → HTML
    → FormProc.

    Form_proc is the software suggested in Congressional Management
    Foundation's [*Congress Online 2003: Turning the Corner on the
    Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=65),
    (p. 57): "House offices can also simplify their e-mail management by
    utilizing the customized Web-based forms available from House
    Information Resources (i.e. for tour requests, scheduling requests,
    casework, feedback, etc.)."

[^124]: Using a form on the Member's site is preferable to just linking
    to the House [Write Your Representative
    page](http://www.house.gov/writerep/), because keeping within the
    Member's site retains the consistent look and feel. A consistent
    look and feel assists with compliance with [Checkpoint 13.4
    \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* which provides that an
    accessible website should "\[u\]se navigation mechanisms in a
    consistent manner."

    [Section 4 of the
    W3C](http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation) *Core
    Techniques for Web Content Accessibility Guidelines 1.0* further
    provides that:

    > A consistent style of presentation on each page allows users to
    > locate navigation mechanisms more easily but also to skip
    > navigation mechanisms more easily to find important content. This
    > helps people with learning and reading disabilities but also makes
    > navigation easier for all users. Predictability will increase the
    > likelihood that people will find information at your site, or
    > avoid it when they so desire.
    >
    > Examples of structures that may appear at the same place between
    > pages:

    navigation bars

    the primary content of a page

    > . . .
    >
    > A navigation mechanism creates a set of paths a user may take
    > through your site. Providing navigation bars, site maps, and
    > search features all increase the likelihood that a user will reach
    > the information they seek at your site. If your site is highly
    > visual in nature, the structure might be harder to navigate if the
    > user can\'t form a mental map of where they are going or where
    > they have been. To help them, content developers should describe
    > any navigation mechanisms. It is crucial that the descriptions and
    > site guides be accessible since people who are lost at your site
    > will rely heavily on them.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site:** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. ***Sen. John Cornyn***'s Web site is a
    > model of clearly and consistently organized information. The menu
    > headers and options are clear, and they stay the same throughout
    > the site.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^125]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=76)
    (page 66) praises the [explanation provided on Rep. John Larson's
    website](http://www.larson.house.gov/index.php?option=com_content&task=view&id=710&Itemid=1).

[^126]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=39),
    (p. 31) praises Sen. Mary Landrieu's website for offering on-line
    subscriptions to several different newsletters.

[^127]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=98)
    (page 86) praises the website of Rep. Ed Perlmutter for having a
    "'Staff Biographies' section \[that\] provides constituents with a
    look at who works for the Congressman, as well as background
    information about them," The report ([pages 64 and
    74](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=76))
    also praises the "[Contact: Staff
    Directory](http://www.house.gov/burton/Contact/staff_directory.htm)"
    page of Rep. Dan Burton and the "[Staff
    List](http://stearns.house.gov/Contact/StaffList.html)" page of Rep.
    Cliff Stearns. The report ([page
    21](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=33))
    additionally indicates that 25% of House Member, committee, and
    leadership office websites provide this type of information.

    The "[Staff Policy](http://www.house.gov/pickering/policy/)" page of
    Rep. Chip Pickering's website includes the title of each staffer and
    a link to a [list of
    issues](http://www.house.gov/pickering/policy/StaffEntire.htm) --
    indicating which staffer is responsible for which issue area. The
    "[Current Staff](http://www.house.gov/andrews/contact_staff.shtml)"
    page of Rep. Robert Andres' website includes the title of each
    staffer, a description of the areas that each staffer is responsible
    for, and which office each staffer is in.

[^128]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=57)
    (page 45) identifies providing guidance on scheduling a meeting as
    an element of a successful Congressional website. The report ([pages
    65 to
    74](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=77))
    praises the sites of Reps. [Christopher
    Carney](http://www.carney.house.gov/scheduling.shtml), [Brad
    Ellswoth](http://www.ellsworth.house.gov/index.php?option=com_content&task=view&id=127&Itemid=),
    [Mark
    Ferguson](http://ferguson.house.gov/index.cfm?FuseAction=ConstituentServices.MeetingRequest),
    and [Mike
    Thompson](http://mikethompson.house.gov/services/scheduling.shtml)
    for providing either a form for requesting a meeting with the
    Congressman or providing instructions as to how to request such a
    meeting.

[^129]: See e.g., [Rep. Devin Nunes's "Invitation Requests"
    page](http://nunes.house.gov/index.cfm?FuseAction=ConstituentServices.InvitationRequests),
    and [Rep. Jesse Jackson, Jr.'s "Contact Me to Schedule a Speaking
    Engagement"
    page](http://www.house.gov/jackson/ContactReSpeaking.shtml).

[^130]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=76)
    (page 66) recommends that:

    > Every congressional Web site should prominently display basic
    > contact information, including telephone and fax numbers, the
    > office's physical addresses, office hours, and their e-mail
    > address or a link to their contact form. The emerging standard is
    > to have this information on the bottom of every Web page. The more
    > detailed and helpful the contact information, the better.
    > Surprisingly, only 5.0% of Senate Member sites and 11.4% of House
    > Member sites list their office hours.

    Jakob Nielsen, in "[About Us Information on
    Websites](http://www.useit.com/alertbox/about-us-pages.html),"
    (September 29, 2008) notes that "some sites seem to deliberately
    hide address listings and phone numbers. Doing so will backfire,
    though, because users view such sites as having very low
    credibility."

[^131]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=59)
    (page 49) praises the "[Rhode Island
    Office](http://langevin.house.gov/RI_office.shtml)" and "[D.C.
    Office](http://langevin.house.gov/DC_office.shtml)" sections of Rep.
    Jim Langevin's website. The two sections separate out information
    relevant to the Washington office from information relevant to the
    district office.

[^132]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=76)
    (page 66) recommends that:

    > Every congressional Web site should prominently display basic
    > contact information, including telephone and fax numbers, the
    > office's physical addresses, office hours, and their e-mail
    > address or a link to their contact form. The emerging standard is
    > to have this information on the bottom of every Web page. The more
    > detailed and helpful the contact information, the better.

[^133]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=58)
    (page 50) recommends that Congressional websites "**Post clear
    e-mail and correspondence policies.** Clear policies regarding email
    correspondence reassure citizens that the office will process their
    communications efficiently. [*Sen. Jeff Bingaman's (D-NM)* e-mail
    policy](http://bingaman.senate.gov/contact/topics.cfm) tells
    constituents how their correspondence is handled internally within
    the office and sets expectations for when they can expect a response
    from the Senator."

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=76)
    (page 66) similarly recommends that Congressional websites "**Post
    clear e-mail and correspondence policies** . . . ***Sen. Jeff
    Bingaman***'s site goes the extra mile, with a contact section that

    offers four different ways of contacting him: e-mail, postal mail,
    phone, or walk-in. His site also indicates which method is most
    effective for each type of request."

[^134]: [Item 22
    of](https://secadmin5.us.house.gov/checklists/HISPUB 007.1.56 - Website Developement.pdf#page=5)
    *The United States House of Representatives Information Security
    Publication -- Web Site Developers Security Checklist* (HISPUB
    007.1.56, August 2008) provides that "Web forms to email a link to a
    friend need to be secured so that they can't be used to relay or
    spoof email."

    Note, that prior to the issuance of the HISPUB, the Congressional
    Management Foundation's [*2006 Gold Mouse Report: Recognizing the
    Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=49)
    (page 39) praised Rep. Dennis Moore's website for including an
    "'inform a friend' feature \[that\] allows users to share the site
    with others via e-mail"

[^135]: A technique for district address validation, using HIR
    form_proc, is set out at HouseNet → Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance) → HTML
    → FormProc..

[^136]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=67)
    (page 57) notes that:

    > people who choose the Web as their method of contacting a
    > congressional office are doing so precisely because they prefer to
    > have their needs met online. Respond to their needs accordingly,
    > and you will find you have more satisfied "customers," at less
    > effort and expense to the office than you ever thought possible.

[^137]: The hCard Microformat Standard is set out at
    <http://microformats.org/wiki/hcard>. Also included are links to
    authoring tools and applications that make use of hCard formatted
    data. For additional geographic applications, see also
    <http://microformats.org/wiki/adr#Implementations>.

    The hCard Microformat Standard is based on [RFC
    2426](http://www.faqs.org/rfcs/rfc2426.html) (the vCard MIME
    Directory Profile) and is consistent with the W3C (X)HTML
    specification.

[^138]: Use of the "visibility:hidden;" style sheets property is to deal
    with an apparent bug in Window-Eyes, which causes Window-Eyes to
    read text styled "display:none;background:url", unless it is also
    styled "visibility:hidden". For more information, see Gez Lemon's
    "[Screen Readers and
    display:none](http://juicystudio.com/article/screen-readers-display-none.php),"
    Juicy Studios (October 12, 2007).

[^139]: [Section 7.5.6 of the
    W3C](http://www.w3.org/TR/html401/struct/global.html#h-7.5.6) *HTML
    4.01 Specification* provides that "The
    [[ADDRESS]{.underline}](http://www.w3.org/TR/html401/struct/global.html#edef-ADDRESS)
    element may be used by authors to supply contact information for a
    document or a major part of a document such as a form."

    [Section 1.1.2 of the
    W3C](http://www.w3.org/TR/WCAG10-HTML-TECHS/#document-meta) *HTML
    Techniques for Web Content Accessibility Guidelines 1.0* suggests
    using the \<address\> element to satisfy [checkpoint 13.2 \[priority
    2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-use-metadata) *Web
    Content Accessibility Guidelines 1.0*, which provides that an
    accessible website should "Provide metadata to add semantic
    information to pages and sites."

[^140]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=51)
    (page 39) recommends that "a site should provide easy and quick
    access to contact information including each office's telephone
    number, address, as well as a link to an e-mail contact form on
    every page."

[^141]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=59)
    (page 49) praises Rep. Jim Langevin's "[Rhode Island
    Office](http://langevin.house.gov/RI_office.shtml)" page, which
    includes a "How to Get Help from Our Office" link.

[^142]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=64)
    (page 56) praises Rep. Earl Blumenauer's "[Effective
    Advocacy](http://blumenauer.house.gov/index.php?option=com_content&task=view&id=251&Itemid=133)"
    page for advising "citizens about how to communicate effectively
    with Congress, by telling them what to ask, who to ask, how to ask,
    and how to follow-up." See also, the "Help Filing a Case with My
    Office" portion of Rep. Marion Berry's "[Help With a Federal
    Agency](http://www.house.gov/berry/services/helpwithafederalagency.shtml)"
    page.

    The [October 10, 2006, issue of the Congressional Management
    Foundation's *Congress Online*
    Newsletter](http://www.cmfweb.org/CongressOnline101006.asp) praises
    Rep. Lincoln Davis' "[Communicate
    Effectively](http://www.house.gov/lincolndavis/wired/communicate.htm)"
    page.

    See also, footnote Error: Reference source not found.

[^143]: [Title 17, § 102(a) of the U.S.
    Code](http://uscode.house.gov/quicksearch/get.plx?title=17&section=102)
    provides that copyrightable material includes (but is not limited
    to) the following categories:

    \(1\) literary works;

    \(2\) musical works, including any accompanying words;

    \(3\) dramatic works, including any accompanying music;

    \(4\) pantomimes and choreographic works;

    \(5\) pictorial, graphic, and sculptural works;

    \(6\) motion pictures and other audiovisual works;

    \(7\) sound recordings; and

    \(8\) architectural works.

[^144]: [Title 17, § 105 of the U.S.
    Code](http://uscode.house.gov/quicksearch/get.plx?title=17&section=105)
    provides that:

    > Copyright protection under this title is not available for any
    > work of the United States Government, but the United States
    > Government is not precluded from receiving and holding copyrights
    > transferred to it by assignment, bequest, or otherwise.

    House Report 94-1476, [pages
    58](http://en.wikisource.org/wiki/Page:H.R._Rep._No._94-1476_(1976)_Page_058.djvu)
    to 59, (the House Judiciary Committee report for the legislation
    that enacted title 17) goes on to note that:

    > The general prohibition against copyright in section 105 applies
    > to \"any work of the United States Government,\" which is defined
    > in section 101 as \"a work prepared by an officer or employee of
    > the United States Government as part of that person\'s official
    > duties.\" Under this definition a Government official or employee
    > would not be prevented from securing copyright in a work written
    > at that person\'s own volition and outside his or her duties, even
    > though the subject matter involves the Government work or
    > professional field of the official or employee. Although the
    > wording of the definition of \"work of the United States
    > Government\" differs somewhat from that of the definition of
    > \"work made for hire,\" the concepts are intended to be construed
    > in the same way. . . . \[I\]t can be assumed that, where a
    > Government agency commissions a work for its own use merely as an
    > alternative to having one of its own employees prepare the work,
    > the right to secure a private copyright would be withheld.

[^145]: Sample code for doing this can be found at the Indiana
    University Webmaster's [Server-Side Includes
    Tutorial](http://www.indiana.edu/~wmhome/tool_guide_info/ssitutorial.shtml#time).

[^146]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=71)
    (page 61) notes that "Congressional jargon and the legislative
    process can be difficult for most people off the Hill to understand.
    Focus on making the information on your site understandable, rather
    than impressive and official-sounding."

[^147]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=23)
    (page 11) notes that:

    > The Internet is a fast-paced medium, and users expect up-to-date
    > information. No matter how well-designed a site is or how
    > extensive its content, it's not going to be useful for visitors if
    > the most current information they can find is a year old.

    The [January 30, 2006 edition of the Congressional Management
    Foundation's *Congress Online*
    newsletter](http://web.archive.org/web/20070203034459/http:/www.cmfweb.org/congressonline013006.asp)
    further notes:

    **Outdated links.** A lot of House sites have outdated or incorrect
    links. The most frustrating ones were those linking to bills,
    sponsorships, and co-sponsorships from the 108^th^ Congress (and,
    occasionally, earlier Congresses); dead links to the Clerk's Web
    site; THOMAS search engines that search the wrong Congress; and
    those linking to INS (it changed to USCIS in 2003!). Web sites
    continually change, so it's important to periodically review any
    link that goes off your site, especially at the beginning of each
    Congress so you don't have visitors looking at old information.

    **Outdated content.** We also saw an overwhelming amount of outdated
    content on Member Web sites, such as issue information referring to
    bills from previous Congresses as though they were current
    legislation. This is troublesome because few constituents will know
    that it's the 109^th^ Congress (not the 108^th^, 107^th^, or
    106^th^) or bother to search THOMAS to double-check. Instead, they
    will take the information on their Representative's Web site at face
    value and trust it. Congress is confusing enough to most people
    without outdated Member sites making it worse!

[^148]: In *Prioritizing Web Usability*, 2006 (page 152), Jakob Nielsen
    and Hoa Loranger recommend that:

    > Whenever you show dates on a Web site, remember to use the
    > international date format, spelling out the name of the month
    > instead of representing it by a number. Different countries have
    > different conventions for writing dates by numerals. In France,
    > for example, 5/4 would be April 5, not May 4.

[^149]: See, e.g., Rep. Anna Eshoo's "[Digital Television (DTV)
    Transition
    FAQ](http://eshoo.house.gov/index.php?option=com_content&task=view&id=400&Itemid=43)". 

[^150]: See, e.g., the "[Ready for Digital Television
    (DTV)](http://www.house.gov/mike-rogers/digital-tv.shtml)?" page on
    the website of Rep. Mike Rogers of Alabama.

    Concerning providing at least a brief explanation before providing a
    link, the Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=44)
    (page 34) praises the federal government links on Rep. Mike Honda's
    website because Rep. Honda's site "complements them with brief
    descriptions of the general areas those agencies cover."

[^151]: The [October 10, 2006, issue of the Congressional Management
    Foundation's *Congress Online*
    Newsletter](http://www.cmfweb.org/CongressOnline101006.asp) praises
    Rep. Mary Bono's website for including information on earthquake
    preparedness information on [earthquake
    preparedness](http://bono.house.gov/HomePage/earthquake.htm). Rep.
    Dan Boren's website includes information on [ice storm
    preparedness](http://www.boren.house.gov/ice.shtml). USA.gov
    (formerly FirstGov) has a wealth of information on disaster
    preparedness and current disasters at
    <http://www.usa.gov/Citizen/Topics/PublicSafety/Disasters.shtml> (in
    English) and at
    <http://www.usa.gov/gobiernousa/Temas/Desastres.shtml> (in Spanish)
    -- organized by subject. Rep. Gus Bilirakus' website includes
    information on [hurricane
    preparedness](http://bilirakis.house.gov/index.php?option=com_content&task=view&id=350&Itemid=146).

[^152]: For techniques on how to compile a history of a congressional
    district, see [*Congressional Districts: How to Compile Histories of
    Their Composition and
    Representation*](http://www.congress.gov/erp/rl/pdf/97-1052.pdf),
    Congressional Research Service report 97-1052 GOV (December 9,
    1997).

[^153]: The [March 25, 2003 Dear
    Colleague](http://www.house.gov/webassistance/po_dc_03-25-03.htm)
    from the Chairman and Ranking Member of the House Administration
    Committee, concerning "Supporting Our Troops Web Sites," provides
    that:

    > In publishing web site links consistent with House rules, official
    > sites should direct constituents to informational materials, and
    > not locations containing only solicitations. By doing so, Members
    > can avoid engaging in solicitations which is prohibited under
    > House rules, including solicitations for money, volunteerism, or
    > other things of value.

[^154]: Use of this strategy is consistent with verbal guidance provided
    by the staff of the House Franking Commission at their January 7,
    2008, briefing on franking reform to the House System Administrators
    Association.

[^155]: The ["Wine Links" page of the Congressional Wine
    Caucus](http://www.radanovich.house.gov/wine/links.htm) states (in
    red text) that

    > \*\*Please note that the links on the following pages will take
    > you outside of The Congressional Wine Caucus\' official website. 
    > The Congressional Wine Caucus does not control the content of
    > these websites, nor do these links constitute an endorsement by
    > the Congressional Wine Caucus.  They are presented here for
    > informational purposes only.\*\*

    [Rep. Christopher Shays' "Resources"
    page](http://www.house.gov/shays/resources/) provides that:

    > *These links are being provided as a convenience and for
    > informational purposes only; they do not constitute an endorsement
    > or an approval by Congressman Christopher Shays of any of the
    > products, services or opinions of the corporation or organization
    > or individual. Congressman Christopher Shays bears no
    > responsibility for the accuracy, legality or content of the
    > external site or for that of subsequent links. Contact the
    > external site for answers to questions regarding its content.*

[^156]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=32)
    (page 24) notes that "Too many congressional Web sites are generic
    --- they fail to reflect the personality of the Member and the
    distinctiveness of the district or state." The Congressional
    Management Foundation's [*2007 Gold Mouse Report: Lessons from the
    Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=107)
    (page 95) identifies having "information about local or district
    resources" as an element of a well-formed Congressional website.

[^157]: Sources for this information include:

    Bureau of Land Management - <http://www.blm.gov/wo/st/en.html>

    Department of Housing and Urban Development:
    <http://www.hud.gov/localoffices.cfm>

    Department of Veterans Affairs:
    <http://www1.va.gov/directory/guide/home.asp?isFlash=1>

    Equal Employment Opportunity Commission:
    <http://www.eeoc.gov/offices.html>

    Federal Bureau of Investigation:
    <http://www.fbi.gov/contact/fo/fo.htm>

    Internal Revenue Service:
    <http://www.irs.gov/localcontacts/index.html>

    Minority Business Development Agency:
    <http://www.mbda.gov/?section_id=1&parent_bucket_id=151&content_id=2264>

    National Archives and Records Administration:
    <http://www.archives.gov/locations/states.html>

    National Forest Service -
    <http://www.fs.fed.us/recreation/map/finder.shtml>

    Small Business Administration:
    <http://www.sba.gov/localresources/index.html>

    Social Security Administration: <http://www.ssa.gov/regions/>

    U.S. Citizenship and Immigration Services:
    <https://egov.uscis.gov/crisgwi/go?action=offices>

    U.S. Geological Survey -- Water Resources Offices:
    <http://www.usgs.gov/contact_us/>

    U.S. Park Service:
    [http://www.nps.gov/findapark/#](http://www.nps.gov/findapark/)

[^158]: The references can either be on a separate page linked from the
    Constituent services, District, and Federal Government pages of the
    site, or they can be in a server-side include that is picked up by a
    page in each of those sections.

[^159]: Web pages devoted to individual congressional districts can be
    found at the Census Bureau's Fast Facts for Congress site at
    <http://fastfacts.census.gov/home/cws/main.html>.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=93)
    (p. 83) identifies providing "District/state demographic statistics"
    as an element of a well-formed Congressional website.

[^160]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=40)
    (page 30) praises [Rep. Brian
    Baird](http://www.house.gov/baird/about/about.shtml)'s website for
    having "specific content for each county in his district, discussing
    local issues and problems and how he is addressing them."

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=74)
    (page 62) praises [Rep. Tom Allen's
    website](http://tomallen.house.gov/index.cfm?ParentID=9&SectionID=72&SectionTree=7,9,72)
    for "an interactive map shows the Congressman's activities and
    accomplishments by county."

    See also., [Rep. Dan Boren's "Second Congressional District of
    Oklahoma" page](http://www.house.gov/boren/district.shtml), [Rep.
    Bud Cramer's "5^th^ District of Alabama"
    page](http://cramer.house.gov/HoR/AL05/5th+District.htm?SecLnk=5thDistrict),
    [Rep. Jeff Fortenberry's "Nebraska's First Congressional District"
    page](http://fortenberry.house.gov/ne01.shtml), and [Rep. Adam
    Schiff's "California's 20^th^ Congressional District"
    page](http://schiff.house.gov/HoR/CA29/The+29th+District/).

[^161]: See, e.g., Mike Rogers of Alabama's "[Moving
    In?](http://www.house.gov/mike-rogers/moving_in.shtml)" page.

[^162]: [Checkpoint 11.1 \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

    XHTML 1.0 is the successor to HTML 4.01. [Section 3.1.1(4) of the
    W3C](http://www.w3.org/TR/xhtml1/#strict) *XHTML 1.0 (2^nd^ edition)
    Specification* provides that:

    > There must be a DOCTYPE declaration in the document prior to the
    > root element \[i.e., prior to the \<html\> tag\]. The public
    > identifier included in the DOCTYPE declaration must reference one
    > of the three DTDs found in
    > [DTDs](http://www.w3.org/TR/xhtml1/#dtds%23dtds) using the
    > respective Formal Public Identifier. The system identifier may be
    > changed to reflect local system conventions.
    >
    > \<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Strict//EN\"
    > \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\"\>
    >
    > \<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"
    > \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\"\>
    >
    > \<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Frameset//EN\"
    > \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd\"\>

[^163]: [Section 3.1.1 of the W3C](http://www.w3.org/TR/xhtml1/#strict)
    *XHTML 1.0 Specification* *(2^nd^ edition)* provides that:

    > An XML declaration \[e.g., \<?xml version=\"1.0\"
    > encoding=\"utf-8\"?\>,\] is not required in all XML documents;
    > however XHTML document authors are strongly encouraged to use XML
    > declarations in all their documents. Such a declaration is
    > required when the character encoding of the document is other than
    > the default UTF-8 or UTF-16 and no encoding was determined by a
    > higher-level protocol.

    [Section C.1 of the W3C](http://www.w3.org/TR/xhtml1/#C_1) *XHTML
    1.0 (2^nd^ edition) Specification*, however cautions that:

    > some user agents \[e.g., Internet Explorer 6\] interpret the XML
    > declaration to mean that the document is unrecognized XML rather
    > than HTML, and therefore may not render the document as expected.
    > For compatibility with these types of legacy browsers, you may
    > want to avoid using processing instructions and XML declarations.
    > Remember, however, that when the XML declaration is not included
    > in a document, the document can only use the default character
    > encodings UTF-8 or UTF-16.

    An XML declaration, therefore, should not be used on House Web pages
    as long as Internet Explorer 6 holds a significant market-share of
    browsers accessing those sites. Preceding the \<!DOCTYPE\>
    declaration with an \<?xml\> declaration (or anything else -- even a
    blank line) in Windows 6 or Opera 7 results in those browsers going
    into quirks mode, even when there is a valid \<!DOCTYPE\>
    declaration. A WSB analysis of www.house.gov usage for July 9 to 15,
    2008, indicates that Internet Explorer 6 accounted for 30.30% of the
    identifiable, non-robot access to the site (Opera usage added
    another 0.21% for a total of almost 31% of
    [www.house.gov](http://www.house.gov/) visitors).

[^164]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=63)
    (page 55) recommends that:

    > Your site should load in 15 seconds or less using a standard
    > Internet connection. Bear in mind that**,** despite the growing
    > availability of broadband connections, the majority of wired
    > households in America still use a 56kbps or slower modem to
    > connect to the Internet.

    [J.D. Power and Associates reported on September 20,
    2006](http://www.jdpower.com/jdpcc/global/content/include/index.asp),
    that 44% of residential ISP customers subscribe to a dial-up
    service.

[^165]: The Sunlight Foundation's 2007 [Congressional Web Site
    Investigation
    Project](http://www.sunlightlabs.com/research/sites/results/index.php)
    indicated that (as of March 26, 2007) 6 House Member websites were
    providing earmark information on their websites:

    [Rep. Tammy
    Baldwin](http://tammybaldwin.house.gov/majorAccomplishments.html)

    [Rep. Kevin
    Brady](http://www.house.gov/brady/2007_appropriations_lead.shtml)

    [Rep. Jim Cooper](http://cooper.house.gov/legislative/fy2007.htm)

    [Rep. John
    Culberson](http://culberson.house.gov/VotingRecord.aspx?Section=84)

    Rep. Darrell Issa

    [Rep. Jesse Jackson,
    Jr.](http://www.house.gov/jackson/AwardedGrants.shtml)

    See also Rep. Dan Boren's "[Congressional earmarks for Oklahoma\'s
    Second Congressional
    District](http://boren.house.gov/earmarks109.shtml)" page and Rep.
    Kirsten Gillibrand's "[Sunlight
    Report](http://www.gillibrand.house.gov/index.php?option=com_content&task=view&id=131&Itemid=31)"
    page.

[^166]: The July 26, 2006 Advisory Memorandum of the House Committee on
    Standards of Official Conduct ([Use of Campaign Funds and
    Campaign-Founded Resources for Official House
    Purposes](http://www.house.gov/ethics/m_campaign_funds_use_7_06.htm))
    provides that Congressional office websites are not to be paid for
    with campaign funds. Offices with questions about the extent of that
    prohibition should be urged to contact the Committee for either
    informal advice or for a formal written opinion.

[^167]: The [*Members' Congressional
    Handbook*](http://cha.house.gov/official_and_representational_expenses_continued.aspx#Content)
    (Web Sites, Content, §§ 1-2), issued by the House Administration
    Committee, provides that:

    > The content of a Member's Web site:
    >
    > 1\. May not include personal, political, or campaign information.
    >
    > 2\. May not be directly linked or refer to Web sites created or
    > operated by a campaign or any campaign related entity including
    > political parties and campaign committees.

    The [*Committee's Congressional
    Handbook*](http://cha.house.gov/committee_handbook.aspx#content)
    (Web Site Regulations, Content, §§ a-b). issued by the House
    Administration Committee, provides that:

    > The content of a committee Web site may not:
    >
    > a\. Include personal, political, or campaign information.
    >
    > b\. Be directly linked or refer to Web sites created or operated
    > by campaign or any campaign related entity, including political
    > parties and campaign committees.

[^168]: [Item 22
    of](https://secadmin5.us.house.gov/checklists/HISPUB 007.1.56 - Website Developement.pdf#page=5)
    *The United States House of Representatives Information Security
    Publication -- Web Site Developers Security Checklist*, HISPUB
    007.1.56, August 2008, provides that "Web forms to email a link to a
    friend need to be secured so that they can't be used to relay or
    spoof email."

    Note, that prior to the issuance of the HISPUB, the Congressional
    Management Foundation's [*2006 Gold Mouse Report: Recognizing the
    Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=49)
    (page 39) praised Rep. Dennis Moore's website for including an
    "'inform a friend' feature \[that\] allows users to share the site
    with others via e-mail"

[^169]: Jeffrey Zeldman's, *Designing With Web Standards* (2^nd^
    edition, \[2006\]), p.153, notes that support for the \<object\> tag
    "has long been known not to work reliably in Internet Explorer."

[^170]: Use of proprietary tags that are not W3C XHTML compliant also
    makes a Web page non-compliant with [Checkpoint 11.1 \[priority 2\]
    of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-latest-w3c-specs)
    *Web Content Accessibility Guidelines 1.0* which provides that
    accessible websites should "\[u\]se W3C technologies when they are
    available and appropriate for a task and use the latest versions
    when supported."

    For an attempt at using the \<object\> tag so that works well across
    browsers, see Elizabeth Castro's "[Bye Bye
    Embed](http://alistapart.com/articles/byebyeembed), " A List Apart
    (July 11, 2006).

[^171]: [Checkpoint 11.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-latest-w3c-specs)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "Use W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

    [Section 4.2 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.2) *XHTML
    1.0 (2^nd^ edition) Specification* provides that "XHTML documents
    must use lower case for all HTML element and attribute names. This
    difference is necessary because XML is case-sensitive e.g. \<li\>
    and \<LI\> are different tags."

[^172]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(*l*))
    provide that "When pages utilize scripting languages to display
    content, or to create interface elements, the information provided
    by the script shall be identified with functional text that can be
    read by assistive technology." [Checkpoint 6.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-keyboard-operable-scripts)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should, "\[f\]or scripts and applets, ensure that
    event handlers are input device-independent." [Checkpoint 9.3
    \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-device-independent-events)
    *Web Content Accessibility Guidelines 1.0* further provides that an
    accessible website should, "\[f\]or scripts, specify logical event
    handlers rather than device-dependent event handlers."

    [Section 12.4 of the
    W3C](http://www.w3.org/TR/WCAG10-HTML-TECHS/#directly-accessible-scripts)
    *HTML Techniques for Web Content Accessibility Guidelines 1.0*
    provides that if an "onclick" event handler must be used, that there
    also be a redundant "onkeypress" event handler should also be used
    in the same element (i.e., in the same tag). [Section 2(SCR20) of
    the W3C](http://www.w3.org/TR/WCAG20-TECHS/#SCR20) *Techniques for
    WCAG 2.0*, however, takes the position that "Although click is in
    principle a mouse event handler, most HTML user agents process this
    event when the control is activated, regardless of whether it was
    activated with the mouse or the keyboard. In practice, therefore, it
    is not necessary to duplicate this event." Additionally, *Techniques
    for WCAG 2.0* also notes problems with the implementation of
    onkeypress (see also Jared Smith's "[Onclick and
    Onkeypress](http://www.webaim.org/discussion/mail_message.php?id=3876),"
    WebAim (November 6, 2003) and Maurice Fanechi (et al's) "[The
    Trouble with
    Onclick](http://www.accessifyforum.com/viewtopic.php?p=14210),"
    Accessify Forum (October 12, 2004)).

[^173]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(*l*))
    provide that "When pages utilize scripting languages to display
    content, or to create interface elements, the information provided
    by the script shall be identified with functional text that can be
    read by assistive technology."

    [Checkpoint 6.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-keyboard-operable-scripts)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should, "\[f\]or scripts and applets, ensure that
    event handlers are input device-independent."

[^174]:
    ###########  **[Section 12.4 of the W3C](http://www.w3.org/TR/WCAG10-HTML-TECHS/#directly-accessible-scripts) *HTML Techniques for Web Content Accessibility Guidelines 1.0*** provides that: {#section-12.4-of-the-w3c-html-techniques-for-web-content-accessibility-guidelines-1.0-provides-that .unnumbered}

    > Some event handlers, when invoked, produce purely decorative
    > effects such as highlighting an image or changing the color of an
    > element\'s text. Other event handlers produce much more
    > substantial effects, such as carrying out a calculation, providing
    > important information to the user, or submitting a form. For event
    > handlers that do more than just change the presentation of an
    > element, content developers should do the following:

    Use application-level event triggers rather than user
    interaction-level triggers. In HTML 4.01, application-level event
    attributes are \"onfocus\", \"onblur\" (the opposite of
    \"onfocus\"), and \"onselect\". Note that these attributes are
    designed to be device-independent, but are implemented as keyboard
    specific events in current browsers.

[^175]: The U.S. Access Board's [*Guide to the Section 508 Standards for
    Electronic and Information
    Technology*](http://www.access-board.gov/sec508/guide/1194.22.htm#(l))
    (§ 1194.22(*l*)) recommends that "onmouseout" be used sparingly and
    that "onblur" be avoided.

[^176]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation."

    Note: Support of the style sheets a:hover property in some browsers
    requires that the browser be functioning in Standards Mode. To
    maximize the likelihood that a browser is functioning in Standards
    Mode, use one of the XHTML 1.0 \<!DOCTYPE\> declarations from the
    W3C [*Recommended List of
    DTDs*](http://www.w3.org/QA/2002/04/valid-dtd-list.html). To ensure
    that Internet Explorer 6 (Windows) and Opera 7 are functioning in
    Standards Mode, also make sure that the \<!DOCTYPE\> declaration is
    the first thing in the file. For information, see Peter-Paul Koch's
    [*Quirks mode and strict
    mode*](http://www.quirksmode.org/css/quirksmode.html) and Henri
    Sivonen's [*Activating the Right Layout Mode Using the Doctype
    Declaration*](http://hsivonen.iki.fi/doctype/).

[^177]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(*l*))
    provide that "When pages utilize scripting languages to display
    content, or to create interface elements, the information provided
    by the script shall be identified with functional text that can be
    read by assistive technology."

    [Checkpoint 6.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-keyboard-operable-scripts)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should, "\[f\]or scripts and applets, ensure that
    event handlers are input device-independent."

[^178]:
    ###########  **[Section 12.4 of the W3C](http://www.w3.org/TR/WCAG10-HTML-TECHS/#directly-accessible-scripts) *HTML Techniques for Web Content Accessibility Guidelines 1.0*** provides that: {#section-12.4-of-the-w3c-html-techniques-for-web-content-accessibility-guidelines-1.0-provides-that-1 .unnumbered}

    > Some event handlers, when invoked, produce purely decorative
    > effects such as highlighting an image or changing the color of an
    > element\'s text. Other event handlers produce much more
    > substantial effects, such as carrying out a calculation, providing
    > important information to the user, or submitting a form. For event
    > handlers that do more than just change the presentation of an
    > element, content developers should do the following:

    Use application-level event triggers rather than user
    interaction-level triggers. In HTML 4.01, application-level event
    attributes are \"onfocus\", \"onblur\" (the opposite of
    \"onfocus\"), and \"onselect\". Note that these attributes are
    designed to be device-independent, but are implemented as keyboard
    specific events in current browsers.

[^179]: The U.S. Access Board's [*Guide to the Section 508 Standards for
    Electronic and Information
    Technology*](http://www.access-board.gov/sec508/guide/1194.22.htm#(l))
    (§ 1194.22(*l*)) recommends that "onmouseover" be used only if the
    information it provides is duplicated by some other method and
    recommends that "onfocus" be avoided.

[^180]: The favicon is the image that will appear on some Web browsers
    in the URL status box (next to the URL) and in some browsers with
    the favorites (or bookmark) list, next to the name of each saved Web
    file link.

[^181]: The URL for the default House favicon (the Great Seal of the
    United States) is:

    <http://www.house.gov/favicon.ico>

[^182]: Traditionally, favicons are named "favicon.ico" and are located
    in the root directory. This is not a requirement, however, as long
    as the favicon has a .ico extension and each page of the website has
    a \<link rel=\"SHORTCUT ICON\" /\> tag with an "href" attribute".

[^183]: Jakob Nielsen's *Designing Web Usability*, 2000 (page 249),
    recommends:

    > make sure all URLs live forever and continue to point to relevant
    > pages. Do not move pages around; instead keep them at the same
    > URL. It is very annoying for authors of other sites when their
    > links either stop working or turn into pointers to something
    > different because the original pages has been moved and replaced
    > with something new.

[^184]: For more information as to the impact of file (and subdirectory)
    names on search engine ranking, see "[Filename with Underscore or
    Dash](http://www.movable-type-weblog.com/archive/entry/filename-with-underscore-or-dash.html)"
    Moveable Type Weblog (March 20, 2005).

[^185]: The [*Members' Congressional
    Handbook*](http://cha.house.gov/official_and_representational_expenses_continued.aspx#WebSites)
    (Web Sites, § 5), issued by the House Administration Committee,
    provides that:

    > HIR will display an exit notice stating that users are leaving the
    > House of Representatives prior to linking to a non-House of
    > Representatives Web site. The exit notice will include a
    > disclaimer that neither Members nor the House are responsible for
    > the content of linked sites. Member offices maintaining their
    > sites on the Public web server are required to incorporate the
    > exit notice into their external links.

    Instructions for implementing the exit message can be found at
    HouseNet → Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance) → HTML
    → Exit Message to External Web Sites.

[^186]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=54)
    (page 46) recommends that "\[v\]isitors to Member sites should also
    be able to initiate basic service requests -- for flags, tours,
    photos, and documents, for example . . . "

    The CMF report (page 57) goes on to note that:

    > Many offices use their Web sites to direct constituents to contact
    > them offline for the information and services they are seeking.
    > Yet, people who choose the Web as their method of contacting a
    > congressional office are doing so precisely because they prefer to
    > have their needs met online. Respond to their needs accordingly,
    > and you will find you have more satisfied "customers," at less
    > effort and expense to the office than you ever thought possible.

[^187]: Rep. Jane Harman's
    "[Services](http://www.house.gov/harman/services/)" page uses "Fly a
    Flag over the Capitol".

[^188]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=55)
    (page 43) indicates that providing Floor statements or speeches is
    one of the elements of a successful congressional website. At the
    time the report was compiled, 69% of all House Member, committee,
    and leadership websites included this information ([page
    21](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=33)).

[^189]: Instructions for linking to specific documents in the
    Congressional Record are available at
    <http://www.congress.gov/help/THOMAS_links/cr.html>.

[^190]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=58)
    (page 46) observes that:

    > The most important thing to consider is presenting the wealth of
    > information the office produces in the most usable way possible.
    > Virtually all offices already allow the press access to the most
    > recent information by providing press releases arranged by date.
    > But many users are interested in specific topics or issues. It is
    > much more likely that they want to know the latest news or action
    > on their topic of interest---say, the environment or the war in
    > Iraq---than they want to see the last three press releases or
    > floor speeches the Member has released. Organize all of the press
    > resources by topic and type. Users are more likely to read
    > articles and watch or listen to video or audio if they don't have
    > to wade through an endless chronological list of unidentifiable
    > files. While this meets the needs of the press, keep in mind that
    > other key audiences, like lobbyists, academics, and interested
    > constituents will also be served by this information.

[^191]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 15.2.2 of the
    W3C](http://www.w3.org/TR/html4/present/graphics.html#h-15.2.2)
    *HTML 4.01 Specification* designates the \<font\> tag as a
    deprecated element).

[^192]: In particular, this best practice is not intended to apply to
    style sheets where the value of the "media" property is "print". Use
    of points, picas, centimeters, or inches in that type of style sheet
    is appropriate.

[^193]: [Checkpoint 3.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-relative-units) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se relative rather than absolute units in
    markup language attribute values and style sheet property values.
    \[Priority 2\]

    > For example, in CSS, use \'em\' or percentage lengths rather than
    > \'pt\' or \'cm\', which are absolute units. If absolute units are
    > used, validate that the rendered content is usable (refer to the
    > [section on
    > validation](http://www.w3.org/TR/WCAG10/#validation))."

[^194]: These may be set by the font-size, color, and font-family
    properties of style sheets.

[^195]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 15.2.2 of the
    W3C](http://www.w3.org/TR/html4/present/graphics.html#edef-BASEFONT)
    *HTML 4.01 Specification* designates the \<basefont\> tag as a
    deprecated element).

[^196]: For information on the history of the Georgia and Verdana type
    faces, see Daniel Will-Harris' [*Georgia & Verdana Typefaces
    designed for the screen
    (finally)*](http://www.will-harris.com/verdana-georgia.htm).

[^197]: For a list of the names of equivalent fonts, see the comp.fonts
    FAQ, part 5, subject 1.32, at
    <http://www.faqs.org/faqs/fonts-faq/part5/>.

[^198]: [Section 15.3 of the
    W3C](http://www.w3.org/TR/CSS21/fonts.html#font-family-prop)
    *Cascading Style Sheets 2.1 Specification* provides that "Style
    sheet designers are encouraged to offer a generic font family as a
    last alternative." CSS 2.1 supports the following generic font
    families: serif, sans-serif, cursive, fantasy, and monospace.

[^199]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) identifies providing "the ability to change text size" as
    an element of a successful Congressional website. The report ([pages
    67 and
    76](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=79))
    singles out those features on the websites of [Rep. J. Randy
    Forbes](http://forbes.house.gov/) and [Sen. Orin
    Hatch](http://hatch.senate.gov/).

[^200]: Instructions for setting up secure forms are set out at HouseNet
    → Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance) →
    Features and Scripts → Online Forms -- Secure Forms.

[^201]: Luke Wroblewski, in *Web Form Design*, 2008, page 19 recommends
    that "Since the point of just about every form is to get it filled
    in, make it abundantly clear how people can accomplish that goal."

    Steve Krug, in *Don't Make Me Think* (2^nd^ ed., 2006), page 47
    recommends that:

    > Your objective should always be to eliminate instructions entirely
    > by making everything self-explanatory, or as close to it as
    > possible. When instructions are absolutely necessary, cut them
    > back to the bare minimum.

[^202]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(n))
    provide that "When electronic forms are designed to be completed
    on-line, the form shall allow people using assistive technology to
    access the information, field elements, and functionality required
    for completion and submission of the form, including all directions
    and cues."

[^203]: Luke Wroblewski in *Web Form Design* (2008), p. 78 ---
    commenting on indicating that a field is required or that a field is
    optional --- notes that "Neither indicator is particularly useful
    when the input fields are either all required or optional fields
    adds unnecessary information to the form that people then have to
    pause and consider."

[^204]: This technique should only be used with caution to flag optional
    fields in forms that primarily contain required fields. As Caroline
    Jarrett, co-author of *Forms that Work* (2008), suggests in
    <http://www.formsthatwork.com/questionsanswers/asterisk.asp> that
    marking optional fields with an asterisk in those circumstances
    "makes sense but it is also a bad idea", noting that:

    > The problem is that most users spend most of their time on web
    > sites other than yours, and on forms other than yours. Their
    > experience on other web sites habituates them to the idea that an
    > asterisk means a field is required.

[^205]: Consider #FFFFCC.

[^206]: This technique should only be used with caution to flag optional
    fields in forms that primarily contain required fields. See,
    generally, the comments by *Forms that Work* co-author Caroline
    Jarrett at
    <http://www.formsthatwork.com/questionsanswers/asterisk.asp>.

[^207]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(c))
    provide that "Web pages shall be designed so that all information
    conveyed with color is also available without color, for example
    from context or markup." An identical standard is set out in
    [Checkpoint 2.1 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-color-convey) *Web
    Content Accessibility Guidelines 1.0*.

[^208]: Jakob Nielsen, in "[Guidelines for Visualizing
    Links](http://www.useit.com/alertbox/20040510.html)" (May 10, 2004)
    recommends:

    > Don\'t underline any text that\'s not a link, even if your links
    > aren\'t underlined. **Reserve underlining for links**. Because
    > underlines provide a strong perceived affordance of clickability,
    > users will be confused and disappointed if underlined text
    > doesn\'t have an actual affordance to match this perception.

[^209]: The National Information Library Service of Australia's
    "[Accessible Forms &
    Tables](http://www.visionaustralia.org.au/docs/services/Tables_and_Forms.ppt#8)"
    provides that accessible forms should:

    > Provide explanatory information *before* it is used:\
    > "♦ indicates required fields".

[^210]: Luke Wroblewski, in "[Web Application Form
    Design](http://www.lukew.com/resources/articles/web_forms.html)"
    (January 22, 2005) recommends:

    > When the time to complete a form needs to be minimized and the
    > data being collected is mostly familiar to users (for instance,
    > entering a name, address, and payment information in a check-out
    > flow), a vertical alignment of labels and input fields is likely
    > to work best. Each label and input field is grouped by vertical
    > proximity and the consistent alignment of both input fields and
    > labels reduces eye movement and processing time. Users only need
    > to move in one direction: down.

[^211]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(n))
    provide that "When electronic forms are designed to be completed
    on-line, the form shall allow people using assistive technology to
    access the information, field elements, and functionality required
    for completion and submission of the form, including all directions
    and cues."

[^212]: The standard set out in [§ 1303(b)(1)(C) of the Children's
    Online Privacy Protection Act of
    1998](http://uscode.house.gov/quicksearch/get.plx?title=15&section=6502)
    (COPPA) prohibits conditioning participation in an activity though a
    website on "disclosing more personal information than is reasonably
    necessary to participate in such activity".

    Just as in the case of § 508 of the Rehabilitation Act,
    Congressional offices are not statutorily required to abide by the
    requirements of COPPA. Just as with § 508, however, Congressional
    offices that do not abide by COPPA's standards risk being
    embarrassed if their non-compliance is publicized.

[^213]: Luke Wroblewski, in *Web Form Design*, 2008, page 22 notes that:

    > People need to parse every question you ask them, formulate their
    > response to that question, and then enter their response into the
    > space you have provided. The best way to speed up that process is
    > not to ask the question at all. That means if you want to be
    > vigilant about optimizing your forms, put every question you are
    > asking people to the test. Do you really need to ask this
    > question?

[^214]: Steve Krug's *Don't Make Me Think* (2^nd^ ed., 2006), p. 21
    notes that:

    > When we're creating sites, we act as though people are going to
    > pore over each page, reading our finely crafted text, figuring out
    > how we've organized things, and weighing their options before
    > deciding which link to lick.
    >
    > What they actually do most of the time (if we're lucky) is
    > *glance* at each new page, scan *some* of the text, and click on
    > the first link that catches their interest or vaguely resembles
    > the thing they're looking for. There are usually large parts of
    > the page they don't even look at.

    Jakob Nielsen and Hoa Loranger in their *Prioritizing Web
    Usability*, 2006 (page 35) further note that users of a website
    spend an average of 27 seconds on each interior page that they view
    and less than half of that time is used to read the main content
    area.

[^215]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(n))
    provide that "When electronic forms are designed to be completed
    on-line, the form shall allow people using assistive technology to
    access the information, field elements, and functionality required
    for completion and submission of the form, including all directions
    and cues."

    [Checkpoint 12.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-associate-labels)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should:

    > Associate labels explicitly with their controls. \[Priority 2\]
    >
    > For example, in HTML use LABEL and its \"for\" attribute.

    Note that it is **not** necessary to have the \<label\> tag
    immediately before the \<input\>, \<select\>, or \<textarea\> tag.
    [Checkpoint 10.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-unassociated-labels)
    *Web Content Accessibility Guidelines 1.0* provides that:

    > [*[Until user
    > agents]{.underline}*](http://www.w3.org/TR/WAI-WEBCONTENT/wai-pageauth.html#until-user-agents)
    > 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\]
    >
    > The label must immediately precede its control on the same line
    > (allowing more than one control/label per line) or be in the line
    > preceding the control (with only one label and one control per
    > line).

    The Ohio State University Web Accessibility Center's "[Test of
    Methods for Hidden Label Information in
    Forms](http://www.wac.ohio-state.edu/tutorials/forms/hiding-labels.htm)"
    indicates that Jaws 5.0, Window-Eyes 5.0, and Home Page Reader 3.021
    are all able to make explicit associations between labels and form
    controls. Nevertheless, Paul Bohman, Director of Products and
    Services of WebAIM (Web Accessibility in Mind) at Utah State
    University
    [recommends](http://www.webaim.org/discussion/mail_message.php?id=6682)
    that \<label\> tags immediately precede the \<input\>, \<select\>,
    or \<textarea\> tags because even though

    > the explicit association of the label with the form control works
    > very well when the user \*tabs through\* the form, even when the
    > label and form element are in completely different parts of the
    > page; but such a separation is still a problem if the user just
    > \*listens to the page straight through\* without interacting with
    > the form (i.e. tabbing between form elements).

[^216]: In "[Wrapping Form
    Labels](http://www.wac.ohio-state.edu/tutorials/forms/examples/wrap-labels.htm),"
    the Web Accessibility Center of Ohio State University suggests this
    technique in order to optimize accessibility by Jaws users.

[^217]: For a further discussion of these (and other) techniques, see
    Gez Lemon's "[Invisible Form
    Prompts](http://juicystudio.com/article/invisible-form-prompts.php),"
    Juicy Studio, September 18, 2004.

[^218]: [Checkpoint 12.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-group-information)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should:

    > Divide large blocks of information into more manageable groups
    > where natural and appropriate. \[Priority 2\]
    >
    > For example, in HTML, use OPTGROUP to group OPTION elements inside
    > a SELECT . . .

    The regulations under § 508 of the Rehabilitation Act of 1973 ([36
    C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(n))
    provide that "When electronic forms are designed to be completed
    on-line, the form shall allow people using assistive technology to
    access the information, field elements, and functionality required
    for completion and submission of the form, including all directions
    and cues."

[^219]: [Checkpoint 4.2](http://www.w3.org/TR/WCAG10/#tech-expand-abbr)
    \[priority 3\] of the W3C *Web Content Accessibility Guidelines 1.0*
    provides that accessible websites need to "\[s\]pecify the expansion
    of each abbreviation or acronym in a document where it first
    occurs."

[^220]: Jakob Nielsen's "[Does User Annoyance
    Matter?](http://www.useit.com/alertbox/annoyances.html)" (March 26,
    2007) notes that:

    > Making users suffer a drop-down menu to enter state abbreviations
    > is one of many small annoyances that add up to a less efficient,
    > less pleasant user experience. It's worth fixing as many of these
    > usability irritants as you can. . . . .
    >
    > Sites offer drop-downs for state abbreviations under the theory
    > that doing so prevents input errors. But that\'s not true: menus
    > are more error prone than typing because the **mouse scroll
    > wheel** often makes users inadvertently change the state field\'s
    > content after they\'ve moved their gaze elsewhere on the screen.
    > In contrast, everybody knows how to type their own state\'s two
    > letters, and it\'s always faster to enter this information through
    > the keyboard than the mouse.

[^221]: [Checkpoint 6.3 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-scripts) *Web Content
    Accessibility Guidelines 1.0* provides that an accessible website
    should:

    > 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. . . .
    >
    > For example, ensure that links that trigger scripts work when
    > scripts are turned off or not supported (e.g., do not use
    > \"javascript:\" as the link target). If it is not possible to make
    > the page usable without scripts, provide a text equivalent with
    > the NOSCRIPT element, or use a server-side script instead of a
    > client-side script, or provide an alternative accessible page as
    > per [checkpoint
    > 11.4](http://www.w3.org/TR/WCAG10/#tech-alt-pages%23tech-alt-pages).
    > [Refer also to guideline
    > 1](http://www.w3.org/TR/WCAG10/#gl-provide-equivalents%23gl-provide-equivalents).

[^222]: Instructions for using form-proc are set out at HouseNet →
    Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance) →
    Features and Scripts → Online Forms -- Basic Instructions.

[^223]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(n))
    provide that "When electronic forms are designed to be completed
    on-line, the form shall allow people using assistive technology to
    access the information, field elements, and functionality required
    for completion and submission of the form, including all directions
    and cues."

    [Checkpoint 6.3 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-scripts) *Web Content
    Accessibility Guidelines 1.0* provides that an accessible website
    should:

    > 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. . . .
    >
    > For example, ensure that links that trigger scripts work when
    > scripts are turned off or not supported (e.g., do not use
    > \"javascript:\" as the link target). If it is not possible to make
    > the page usable without scripts, provide a text equivalent with
    > the NOSCRIPT element, or use a server-side script instead of a
    > client-side script, or provide an alternative accessible page as
    > per [checkpoint
    > 11.4](http://www.w3.org/TR/WCAG10/#tech-alt-pages%23tech-alt-pages).
    > [Refer also to guideline
    > 1](http://www.w3.org/TR/WCAG10/#gl-provide-equivalents%23gl-provide-equivalents).

[^224]: [Checkpoint 10.4 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-place-holders) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should, "[*[\[u\]ntil user
    agents]{.underline}*](http://www.w3.org/TR/WAI-WEBCONTENT/wai-pageauth.html#until-user-agents)
    handle empty controls correctly, include default, place-holding
    characters in edit boxes and text areas." Donna Smillie (Web
    Accessibility Consultant for the Royal National Institute for the
    Blind (UK)), however,
    [indicates](http://www.integriert-studieren.jku.at/eac-tf3/archiv/msg00073.html)
    that she is "Not aware of any user agents currently in use which
    have difficulty in handling empty form controls correctly. If
    anything, problems now tend to be presented for some users when
    default values are provided in edit boxes and text areas" (November
    29, 2003). Jim Hatcher, in *Constructing Accessible Web Sites*
    (2002, p. 141) also notes that:

    > It used to be, when screen readers literally "read the screen",
    > that they had difficulty detecting an input field that was blank.
    > Now that screen readers use **Microsoft Active Accessibility
    > (MSAA)** or the **Document Object Model (DOM)** of the browser,
    > they do not have that problem anymore. The usefulness of
    > Checkpoint 10.4 has passed.

    For a contrasting opinion of whether Checkpoint 10.4 is no longer
    applicable, see "[Place Holding Text in Form
    Inputs](http://blackwidows.co.uk/blog/?p=34)" Spider Trax, July 20,
    2005.

[^225]: [Checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 4.10 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.10)
    *XHTML 1.0 (2^nd^ edition) Specification* designates the "name"
    attribute of the \<form\> tag as a deprecated attribute and also
    provides that "XHTML 1.0 documents MUST use the id attribute when
    defining fragment identifiers" within \<form\> tags).

[^226]: Section 1 of the W3C [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure) provides
    that:

    > When designing a document or series of documents, content
    > developers should strive first to identify the desired structure
    > for their documents before thinking about how the documents will
    > be presented to the user. Distinguishing the structure of a
    > document from how the content is presented offers a number of
    > advantages, including improved accessibility, manageability, and
    > portability.

    Jeffrey Zeldman's, *Designing With Web Standards* (2^nd^ edition,
    \[2006\]), p.180, recommends that

    > Semantic or meta-structural names (names that explain the function
    > performed by elements contained within) are best. You would feel
    > pretty silly having labeled a part of your site "orangebox" when
    > the client decides to go with blue. You would feel sillier still
    > revising your style sheets under a deadline six months from now
    > and trying desperately to remember whether "Gladys" was a
    > navigational area, a sidebar, a search form, or what.

[^227]: [Section 17.2.1 of the
    W3C](http://www.w3.org/TR/html4/interact/forms.html#h-17.2.1) *HTML
    4.01 Specification* provides that for every group of radio buttons,
    there should be at least one \<input type=\"radio\"\> tag with a
    "checked" attribute. [Section 4.5 of the
    W3C](http://www.w3.org/TR/xhtml1/#h-4.5) *XHTML 1.0 (2^nd^ edition)
    Specification* provides that all attributes must be given values
    (e.g., checked=\"checked\" not just: checked). [Checkpoint 11.1
    \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^228]: [Section 17.6.1 of the
    W3C](http://www.w3.org/TR/html4/interact/forms.html#h-17.6.1) *HTML
    4.01 Specification* provides that for every \<select\> tag, there
    should be at least one \<option\> tag with a "selected" attribute.
    [Section 4.5 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.5) *XHTML
    1.0 (2^nd^ edition) Specification* provides that all attributes must
    be given values (e.g., selected=\"selected\" not just: selected).
    [Checkpoint 11.1 \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^229]: [Section 4.6 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.6)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that "Empty
    elements must either have an end tag or the start tag must end with
    /\>. For instance, \<br/\> or \<hr\>\</hr\>." [Checkpoint 11.1
    \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^230]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page77)
    (page 65) praises the [forms
    library](http://www.carney.house.gov/formslibrary.shtml) on Rep.
    Christopher Carney's website, which "allows users to quickly
    identify and easily fill out the relevant forms."

    See also the "[Forms
    Library](http://moran.house.gov/forms-library.shtml)" of Rep. Jim
    Moran.

[^231]: For further material on use of iframes, see the [WSB Iframes
    Blog](http://intranet.house.gov/htbin/blog_inc?BLOG,xd01_wsbblog,blog/IFRAME,999,All,No Category found,TEMPLATE=blog_bycat.shtml).

[^232]: The [*Members' Congressional
    Handbook*](http://cha.house.gov/official_and_representational_expenses_continued.aspx#WebSites)
    (Web Sites, § 5), issued by the House Administration Committee,
    provides that:

    > HIR will display an exit notice stating that users are leaving the
    > House of Representatives prior to linking to a non-House of
    > Representatives Web site. The exit notice will include a
    > disclaimer that neither Members nor the House are responsible for
    > the content of linked sites. Member offices maintaining their
    > sites on the Public web server are required to incorporate the
    > exit notice into their external links.

    Instructions for implementing the exit message can be found at
    HouseNet → Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance) → HTML
    → Exit Message to External Web Sites.

[^233]: [Checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0*, further, provides that
    accessible websites should "\[a\]void deprecated features of W3C
    technologies." ([Section 4.10 of the
    W3C](http://www.w3.org/TR/xhtml1/#h-4.10) *XHTML 1.0 (2^nd^ edition)
    Specification* designates the "name" attribute of the \<frame\> and
    \<iframe\> tags as a deprecated attribute and also provides that
    "XHTML 1.0 documents MUST use the id attribute when defining
    fragment identifiers" within \<frame\> and \<iframe\> tags).

[^234]: Section 1 of the W3C [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure) provides
    that:

    > When designing a document or series of documents, content
    > developers should strive first to identify the desired structure
    > for their documents before thinking about how the documents will
    > be presented to the user. Distinguishing the structure of a
    > document from how the content is presented offers a number of
    > advantages, including improved accessibility, manageability, and
    > portability.

    Jeffrey Zeldman's, *Designing With Web Standards* (2^nd^ edition,
    \[2006\]), p.180, recommends that

    > Semantic or meta-structural names (names that explain the function
    > performed by elements contained within) are best. You would feel
    > pretty silly having labeled a part of your site "orangebox" when
    > the client decides to go with blue. You would feel sillier still
    > revising your style sheets under a deadline six months from now
    > and trying desperately to remember whether "Gladys" was a
    > navigational area, a sidebar, a search form, or what.

[^235]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(i))
    provide that "Frames shall be titled with text that facilitates
    frame identification and navigation."

    [Checkpoint 12.1 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-frame-titles) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[t\]itle each frame to facilitate frame
    identification and navigation." [Section 10 of the
    W3C](http://www.w3.org/TR/WCAG10-HTML-TECHS/#frames) *HTML
    Techniques for Web Content Accessibility Guidelines 1.0* provides
    that \<frame\>, \<frameset\>, and \<iframe\> tags are all
    implementations of frames.

[^236]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(a))
    provide that "A text equivalent for every non-text element shall be
    provided (e.g., via \"alt\", \"longdesc\", or in element content)."

    [Checkpoint 1.1 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-text-equivalent) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should:

    > 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. . . .
    >
    > For example, in HTML:

    Use \"alt\" for the IMG, INPUT, and APPLET elements, or provide a
    text equivalent in the content of the OBJECT and APPLET elements.

    For complex content (e.g., a chart) where the \"alt\" text does not
    provide a complete text equivalent, provide an additional
    description using, for example, \"longdesc\" with IMG or FRAME, a
    link inside an OBJECT element, or a [description
    link](http://www.w3.org/TR/WAI-WEBCONTENT/#d-link%23d-link).

    For image maps, either use the \"alt\" attribute with AREA, or use
    the MAP element with A elements (and other text) as content.

    [Section 13.8 of the
    W3C](http://www.w3.org/TR/html401/struct/objects.html#adef-alt)
    *HTML 4.01 Specification* provides that \<img\> tags and \<area\>
    tags must have "alt" attributes.

[^237]: [Section 4.6 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.6)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that "Empty
    elements must either have an end tag or the start tag must end with
    /\>. For instance, \<br/\> or \<hr\>\</hr\>." [Checkpoint 11.1
    \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^238]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=93)
    (page 83) recommends that Congressional websites include FAQs about
    Congress and FAQs regarding constituent casework. The report ([pages
    30 to 38, 56 and
    59](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=40))
    praises the casework FAQs of Reps. [Brian
    Baird](http://www.house.gov/baird/cs/faq.shtml), Xavier Becerra,
    Marion Berry, John Larson, John Linder, and Ed Royce; the
    Congressional FAQ of Rep. Mike Honda; the FAQ on Internet Myths on
    Rep. John Larson's website; and the FAQ section of Sen. Patty
    Murray's website. The report ([page
    60](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=70))
    also praises the Budget Committee (Democratic Office) [budget
    FAQ](http://www.house.gov/budget_democrats/budget_facts/Faq_june07.pdf).

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=62)
    (page 50) suggests that "Past letters written to constituents
    explaining the Member's stance and actions on an issue can populate
    the issues page and inform an FAQ."

    [*Research-Based Web Design & Usability
    Guidelines*](http://www.usability.gov/pdfs/chapter2.pdf#page=2),
    2^nd^ edition, page 10, (compiled by the U.S. Department of Health
    and Human Services), identifies providing "a useful set of
    frequently asked questions (FAQ) and answers" as one of the elements
    that project credibility in a website.

[^239]: See also, the websites of [Rep. Carolyn B.
    Maloney](http://maloney.house.gov/), [Rep. Mike Rogers of
    Alabama](http://www.house.gov/mike-rogers/faqs.shtml), and [Rep.
    Chris Van Hollen](http://vanhollen.house.gov/HoR/MD08/FAQ/).

[^240]: See also, the frequently asked questions portion of Rep. John
    Linder's "[Academy
    Nominations](http://linder.house.gov/index.cfm?FuseAction=Resources.Home&Resource_id=E1BA9747-DEA4-450C-BEAB-E577937E3C27)"
    page.

[^241]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=32)
    (page 24) notes that "Too many congressional Web sites are generic
    --- they fail to reflect the personality of the Member and the
    distinctiveness of the district or state." The Congressional
    Management Foundation's [*2007 Gold Mouse Report: Lessons from the
    Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=107)
    (page 95) identifies having "information about local or district
    resources as an element of a well-formed Congressional website."

[^242]: <http://www.pueblo.gsa.gov/multilanguage/multilang.htm>.

[^243]: Concerning coding of foreign language material (and links to
    foreign language material), see "Language of Text", below.

[^244]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=107)
    (page 95) identifies having a link to FirstGov (now USA.gov) as an
    element of a well-formed Congressional website.

[^245]: The [Congressional Management
    Foundation's](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=54)
    *Congress Online 2003: Turning the Corner on the Information Age*
    (p. 46) notes that "Committees and leadership offices with natural
    constituencies can also provide service information online. The
    *House Committee on Veterans' Affairs* website provides information
    on veterans' benefits for its key audience."

[^246]: Using the \<include\> or \<iframe\> is preferable to just
    linking to the generic Federal Grants page. Using \<include\> or
    \<iframe\> retains the consistent look and feel of the rest of the
    office's website. A consistent look and feel assists with compliance
    with [Checkpoint 13.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* which provides that an
    accessible website should "\[u\]se navigation mechanisms in a
    consistent manner."

    [Section 4 of the
    W3C](http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation) *Core
    Techniques for Web Content Accessibility Guidelines 1.0* further
    provides that:

    > A consistent style of presentation on each page allows users to
    > locate navigation mechanisms more easily but also to skip
    > navigation mechanisms more easily to find important content. This
    > helps people with learning and reading disabilities but also makes
    > navigation easier for all users. Predictability will increase the
    > likelihood that people will find information at your site, or
    > avoid it when they so desire.
    >
    > Examples of structures that may appear at the same place between
    > pages:

    navigation bars

    the primary content of a page

    > . . .
    >
    > A navigation mechanism creates a set of paths a user may take
    > through your site. Providing navigation bars, site maps, and
    > search features all increase the likelihood that a user will reach
    > the information they seek at your site. If your site is highly
    > visual in nature, the structure might be harder to navigate if the
    > user can\'t form a mental map of where they are going or where
    > they have been. To help them, content developers should describe
    > any navigation mechanisms. It is crucial that the descriptions and
    > site guides be accessible since people who are lost at your site
    > will rely heavily on them.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site:** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. ***Sen. John Cornyn***'s Web site is a
    > model of clearly and consistently organized information. The menu
    > headers and options are clear, and they stay the same throughout
    > the site.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^247]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(a))
    provide that "A text equivalent for every non-text element shall be
    provided (e.g., via \"alt\", \"longdesc\", or in element content)."

    [Checkpoint 1.1 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-text-equivalent) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should:

    > 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. . . .
    >
    > For example, in HTML:

    Use \"alt\" for the IMG, INPUT, and APPLET elements, or provide a
    text equivalent in the content of the OBJECT and APPLET elements.

    For complex content (e.g., a chart) where the \"alt\" text does not
    provide a complete text equivalent, provide an additional
    description using, for example, \"longdesc\" with IMG or FRAME, a
    link inside an OBJECT element, or a [description
    link](http://www.w3.org/TR/WAI-WEBCONTENT/#d-link%23d-link).

    For image maps, either use the \"alt\" attribute with AREA, or use
    the MAP element with A elements (and other text) as content.

    [Section 13.8 of the
    W3C](http://www.w3.org/TR/html401/struct/objects.html#adef-alt)
    *HTML 4.01 Specification* provides that \<img\> tags and \<area\>
    tags must have "alt" attributes.

[^248]: Various standards have been suggested for how long an "alt"
    attribute should be before a "longdesc" attribute should also be
    used. The 100 to 125 character standard was recommended by Jon
    Brundage of
    [TecAccess](http://www.tecaccess.net/content/aboutus.shtml#company).

    Joe Clark's *[[Building Accessible
    Websites]{.underline}](http://joeclark.org/book/)* (2003), page 68,
    suggests using the "longdesc" attribute when the value of the "alt"
    attribute exceeds 1,024 characters.

    [Standard 1.8 of the New York State Government's Mandatory
    Technology Standard
    S04-001](http://www.oft.state.ny.us/policy/s04-001/files/Web_Access_Standards_Final.pdf#page=4)
    ("Accessibility of State Agency Web-based Intranet and Internet
    Information and Applications," October 25, 2006) provides that the
    "longdesc" attribute should be used when the value of the "alt"
    attribute exceeds 150 characters.

    [Statewide Policy P130 Rev. 1.0 (Attachment A) from the Arizona
    Information Technology
    Agency](http://gita.state.az.us/policies_standards/html/p130_web_site_accessibility_policy.htm)
    (September 15, 2006) suggests using the "longdesc" attribute when
    the value of the "alt" attribute exceeds 12 words.

    The default on [[HiSoft's Cynthia
    Says]{.underline}](http://www.contentquality.com/About Reports/Alt Quality.htm)
    accessibility validating software to recommend use of the "longdesc"
    attribute is when the value of the "alt" attribute exceeds 81
    characters.

[^249]: Roger Hudson's "[Text Alternatives for
    Images](http://www.usability.com.au/resources/image-text.cfm)"
    (September 2003) recommends that Web designers "Avoid unnecessary
    terms. Don\'t use words like \'link\' or \'click here\' for images
    that are links. Screen readers will indicate if something is a link
    or not." Note that [checkpoint 13.8 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-front-loading) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[p\]lace distinguishing information at the
    beginning of headings, paragraphs, lists, etc."

[^250]: Roger Hudson's "[Text Alternatives for
    Images](http://www.usability.com.au/resources/image-text.cfm)"
    (September 2003) recommends that Web designers not "use the image
    file name as the alt. Alternative text like \"02_cc_68.gif\", or
    even \"building.jpg\" are neither descriptive nor helpful."

[^251]:
    ###########  [**Section 7 of the W3C**](http://www.w3.org/TR/WCAG10-CSS-TECHS/#text-not-images) ***CSS Techniques for Web Content Accessibility Guidelines 1.0*** provides that: {#section-7-of-the-w3c-css-techniques-for-web-content-accessibility-guidelines-1.0-provides-that .unnumbered}

    > Content developers should use style sheets to style text rather
    > than representing text in images. Using text instead of images
    > means that the information will be available to a greater number
    > of users (with speech synthesizers, braille displays, graphical
    > displays, etc.). Using style sheets will also allow users to
    > override author styles and change colors or fonts sizes more
    > easily.
    >
    > If it is necessary to use a bitmap \[e.g., a .gif file\] to create
    > a text effect (special font, transformation, shadows, etc.) the
    > bitmap must be accessible (see the sections on [text
    > equivalents](http://www.w3.org/TR/WCAG10-TECHS/#def-text-equivalent)
    > and [alternative
    > pages](http://www.w3.org/TR/WCAG10-TECHS/#alt-page-note)).

[^252]: [Checkpoint 14.2 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-icons) *Web Content
    Accessibility Guidelines 1.0* provides that accessible websites
    should "\[s\]upplement text with graphic or auditory presentations
    where they will facilitate comprehension of the page."

[^253]: [Section 13.7.1 of the
    W3C](http://www.w3.org/TR/html4/struct/objects.html#adef-width-IMG)
    *HTML 4.01 Specification* provides that:

    > The height and width attributes give user agents an idea of the
    > size of an image or object so that they may reserve space for it
    > and continue rendering the document while waiting for the image
    > data.

[^254]: Use the "border-width" style sheets property together with the
    "border-style" property.

[^255]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 13.7.3 of the
    W3C](http://www.w3.org/TR/html4/struct/objects.html#h-13.7.3) *HTML
    4.01 Specification* designates the "border" attribute of the \<img\>
    tag as a deprecated attribute).

[^256]: The "padding-left," "padding-right," "padding-bottom," and
    "padding-top" style sheets properties provide the functionality
    previously provided by the "hspace" and "vspace" attributes.

    [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 13.7.2 of the
    W3C](http://www.w3.org/TR/html4/struct/objects.html#h-13.7.2) *HTML
    4.01 Specification* designates the "hspace" and "vspace" attributes
    as deprecated attributes).

[^257]: [Checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* further provides that
    accessible websites should "\[a\]void deprecated features of W3C
    technologies." ([Section 4.10 of the
    W3C](http://www.w3.org/TR/xhtml1/#h-4.10) *XHTML 1.0 (2^nd^ edition)
    Specification* designates the "name" attribute of the \<img\> tag as
    a deprecated attribute and also provides that "XHTML 1.0 documents
    MUST use the id attribute when defining fragment identifiers" within
    \<img\> tags).

[^258]: Section 1 of the W3C [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure) provides
    that:

    > When designing a document or series of documents, content
    > developers should strive first to identify the desired structure
    > for their documents before thinking about how the documents will
    > be presented to the user. Distinguishing the structure of a
    > document from how the content is presented offers a number of
    > advantages, including improved accessibility, manageability, and
    > portability.

    Jeffrey Zeldman's, *Designing With Web Standards* (2^nd^ edition,
    \[2006\]), p.180, recommends that

    > Semantic or meta-structural names (names that explain the function
    > performed by elements contained within) are best. You would feel
    > pretty silly having labeled a part of your site "orangebox" when
    > the client decides to go with blue. You would feel sillier still
    > revising your style sheets under a deadline six months from now
    > and trying desperately to remember whether "Gladys" was a
    > navigational area, a sidebar, a search form, or what.

[^259]: The July 26, 2006 Advisory Memorandum of the House Committee on
    Standards of Official Conduct ([Use of Campaign Funds and
    Campaign-Founded Resources for Official House
    Purposes](http://www.house.gov/ethics/m_campaign_funds_use_7_06.htm))
    provides that Congressional office websites are not to be paid for
    with campaign funds. Offices with questions about the extent of that
    prohibition should be urged to contact the Committee for either
    informal advice or for a formal written opinion.

[^260]: Anti-aliasing can be set using either (1) the aa pull-down or
    (2) Layer \> Type. **Note:** Photoshop 7.0 recommends that for the
    resolutions normally used in Web graphics, the Fractional Width
    option in the Character palette menu should be deselected.

[^261]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that an accessible
    website should "\[u\]se style sheets to control layout and
    presentation."

[^262]: [Section 4.6 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.6)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that "Empty
    elements must either have an end tag or the start tag must end with
    /\>. For instance, \<br/\> or \<hr\>\</hr\>." [Checkpoint 11.1
    \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^263]: Members including such a service on their website include [Rep.
    Howard Berman](http://www.house.gov/berman/services/greetings.shtml)
    and [Rep. John
    Tierney](http://tierney.house.gov/services/commendations).

    The House Ethics Committee's [*House Ethics
    Manual*](http://ethics.house.gov/Media/PDF/2008_House_Ethics_Manual.pdf#page=172)
    (2008 edition, pages 160-161) provides that:

    > **Letters, Mailings and Other Communications that Are Not
    > Frankable in Content.** At times Members wish to send letters or
    > mailings, or make other communications, that are not frankable in
    > content under the House Franking Regulations, and hence may not be
    > created or sent using official House resources. Examples of such
    > communications include messages to constituents that are not
    > official in nature, such as birthday greetings, holiday greetings,
    > and letters of condolence. In addition, while letters of
    > congratulations for a public distinction are frankable, other
    > letters of congratulation, such as for years of service at a
    > business, or retirement, are not. Under House Rules, a Member
    > **may** use campaign funds and resources to create and send cards,
    > letters and certificates of these types to constituents.
    >
    > However, such materials may **not** be produced in or sent from
    > any House office, and may **not** be produced or sent using any
    > other House resource, including the office equipment or staff
    > while on official time.
    >
    > ***Example 14.*** Congressman A wishes to create a \"Congressman A
    > Award of Merit\" certificate that he will present to constituents
    > who perform meritorious acts or services. The certificates may be
    > printed with campaign funds, but their content must comply with
    > the same restrictions that apply to campaign letterhead (*see*
    > discussion below on "Laws and Rules on Campaign Letterhead"). In
    > addition, official House resources may not be used to promote the
    > certificates, or in connection with their presentation.

    The House Franking Commission's [*Franking
    Manual*](http://cha.house.gov/PDFs/franking/franking2.pdf#page=21),
    (pp. 12-13), further defines an event of "public distinction":

    > **8. Congratulations**
    >
    > Section 3210(a)(3)(f) \[of title 39 of the U.S. Code\] authorizes
    > the franking of "mail matter expressing congratulations to a
    > person who has achieved some public distinction."
    >
    > The Commission emphasizes that these messages of congratulations
    > are limited to matters of public distinction as opposed to matters
    > of personal achievement. The following examples are illustrative,
    > and not all-inclusive:
    >
    > *Examples of public*
    >
    > *distinction:*
    >
    > Election or appointment Publicly notable awards and honors
    >
    > to public office Eagle Scout/Gold Star
    >
    > U.S. Citizenship Heroism
    >
    > High School Graduation Appointment to a U.S. military academy
    >
    > In the above examples, there is a public purpose to be served in
    > establishing communication with newly elected or appointed public
    > officials on a Federal, state or local level; with new citizens
    > and graduates; and with honorees for outstanding public service to
    > promote the public good.
    >
    > Letters consisting solely of birthday, wedding, anniversary,
    > retirement or condolence messages are not frankable.
    >
    > However, legislative correspondence, which otherwise is frankable,
    > may contain an incidental statement of condolence or of
    > congratulations for personal achievement. For example, a response
    > to a constituent's request for assistance in obtaining survivor
    > annuity benefits may contain an incidental statement of
    > condolence. Similarly, a letter enclosing Federal publications may
    > contain a brief congratulatory message for personal achievement,
    > provided the substance of the letter focuses on the content of the
    > publication or other officially related subject matter rather than
    > on the congratulatory remark.

    Note that neither *Campaign Activity* nor the *Franking Manual*
    specifically address whether House websites can invite constituents
    to request Member recognitions of birthdays, anniversaries, etc.
    What the *Campaign Booklet* and the *Franking Manual* do is prohibit
    (or at least restrict) the use of official funds, staff time, or
    other House resources to prepare and mail such recognitions.

[^264]: The Congressional Management Foundation's January 2002 report
    [*Congress Online: Assessing and Improving Capitol Hill Web
    Sites*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2002.pdf#page=42)
    (p. 36) praises [Rep. Mike Pence's
    website](http://mikepence.house.gov/ConstituentServices/presidentialgreetings.htm)
    for including information on Presidential greetings. See also,
    "Presidential Greetings" pages of [Rep. Steve
    Chabot](http://www.house.gov/chabot/presidentialgreetings.html),
    [Rep. John
    Linder](http://linder.house.gov/index.cfm?FuseAction=ConstituentServices.Greeting),
    [Rep. Juanita
    Millender-McDonald](http://web.archive.org/web/20060303180652/www.house.gov/millender-mcdonald/greetings.htm),
    [Rep. Dave
    Obey](http://www.obey.house.gov/index.php?option=com_content&task=view&id=54&Itemid=76),
    and [Rep. Ileana
    Ros-Lehtinen](http://ros-lehtinen.house.gov/president-greetings.shtml).

[^265]: Part of Rep. Kendrick Meek's website is in Haitian Creole; see
    <http://kendrickmeek.house.gov/index-creole.shtml>.

[^266]: Rep. Neil Abercrombie's website includes a Hawaiian version of
    the Congressman's welcome message; see
    <http://www.house.gov/abercrombie/welcomeletter_hawaiian.shtml>.

[^267]: [Checkpoint 3.5 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-logical-headings)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "\[u\]se header elements to convey
    document structure and use them according to specification."

    [Section 1.2.1 of the
    W3C](http://www.w3.org/TR/WCAG10-HTML-TECHS/#document-headers) *HTML
    Techniques for Web Content Accessibility Guidelines 1.0* provides
    that "Since some users skim through a document by navigating its
    headings, it is important to use them appropriately to convey
    document structure. Users should order heading elements properly.
    For example, in HTML, H2 elements should follow H1 elements, H3
    elements should follow H2 elements, etc. Content developers should
    not \"skip\" levels (e.g., H1 directly to H3). Do not use headings
    to create font effects; use [style sheets to change font
    styles](http://www.w3.org/TR/WCAG10-CSS-TECHS/#style-fonts) for
    example."

    In the Jaws screen reader, Insert+F6 generates a list of headers.

[^268]: [Checkpoint 13.8 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-front-loading) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[p\]lace distinguishing information at the
    beginning of headings, paragraphs, lists, etc."

    Jakob Nielsen's article "[F-Shaped Pattern For Reading Web
    Content](http://www.useit.com/alertbox/reading_pattern.html)" (April
    17, 2006), based on a study of the eye movements of 232 website
    users, recommends that Web designers:

    > **Start subheads, paragraphs, and bullet points with
    > information-carrying words** that users will notice when scanning
    > down the left side of your content . . . . They\'ll read the third
    > word on a line much less often than the first two words.

    Though Nielsen's study was based on sighted users, the technique he
    suggests is useful not only for sighted individuals, but also for
    blind individuals -- since an often-used technique in Jaws and
    Window-Eyes is to have the browser skip from heading to heading or
    from list to list.

[^269]: Jakob Nielsen and Hoa Loranger in their *Prioritizing Web
    Usability*, 2006 (page 277) recommend that headings "be short (60
    characters maximum) and meaningful."

[^270]: Usability testing conducted by Jakob Nielsen and Hoa Loranger
    and reported in their *Prioritizing Web Usability*, 2006 (page 32),
    indicates that only 23% of first-time visitors of homepages bother
    to scroll down. Second-time (and subsequent) visitors only scroll
    down 16% to 14% of the time.

[^271]: The [October 10, 2006, issue of the Congressional Management
    Foundation's *Congress Online*
    Newsletter](http://www.cmfweb.org/CongressOnline101006.asp) suggests
    that homepages:

    **Promote a Constituent Service.** The best real estate on [**Sen.
    Jeff Bingaman's (D-NM)**](http://bingaman.senate.gov/) home page is
    devoted to the constituent services provided by the office, such as
    casework and help for small businesses. You could also rotate the
    various services to coincide with important dates (flags for
    Veterans Day, student loan assistance before colleges and
    universities begin a new year) or focus on one specific area, like
    [**Rep. Mike Capuano (D-MA)**](http://www.house.gov/capuano/) is
    with his immigration casework. Though not "traditional" constituent
    services, [**Rep. Mary Bono (R-CA)**](http://bono.house.gov/) has
    information on earthquake preparedness and links to pandemic flu
    resources on her home page, while [**Rep. Jim Moran
    (D-VA)**](http://moran.house.gov/) links to CRS reports on hot
    topics, all of which are of interest to constituents.

    **Highlight a Legislative Priority.** One of [**Rep. John Peterson's
    (R-PA)**](http://www.house.gov/johnpeterson/) top priorities in
    Congress is [revitalizing rural
    communities](http://www.house.gov/johnpeterson/economy.html), such
    as those in his district, through economic development and job
    creation. This topic is front and center on his home page, giving
    constituents faster access (one less click) to his ideas for
    strengthening their communities and links to several dozen resources
    on the topic. On the other side of the Hill, [**Sen. Tom Harkin's
    (D-IA)**](http://harkin.senate.gov/) home page is currently
    highlighting his efforts to improve the mental health and wellbeing
    of veterans.

    **Focus on a Local Issue or Current Event.** October may be slow for
    legislative work, but there are always current events and local
    activities of interest to your constituents. In his special features
    section on his home page, [**Rep. Richard Baker
    (R-LA)**](http://baker.house.gov/) spotlights Louisiana's 529
    College Savings Program and LSU's ROTC program. He also highlights
    the CBS Early Show's stop in Baton Rouge as well as ongoing
    Hurricane Katrina recovery efforts. [**Rep. Carolyn Maloney
    (D-NY)**](http://maloney.house.gov/) and [**Sen. John Ensign
    (R-NV)**](http://ensign.senate.gov/) also showcase local issues on
    their home pages.

[^272]: The Congressional Management Foundation's 1999 report *Building
    Web Sites Constituents Will Use* (page 16) recommends against
    welcome messages or cover pages. The CMF report notes that:

    > Both of these practices are frustrating because they prevent
    > visitors from getting to useful information as quickly as
    > possible. They require visitors to click or scroll in order to
    > access the information they came to get, and neither of them
    > serves much purpose except to take up valuable space. "Welcome to
    > my Web site. I hope you find what you are looking for," is a waste
    > of visitors' time.

    Rep. Mike Honda has addressed this issue by not including his
    welcome message on his homepage, but instead providing a link to the
    [message](http://www.honda.house.gov/welcomemessage.shtml) -- which
    is available in text (in English, Spanish, and Vietnamese) and in
    video (at three different resolutions). [Rep. Steve
    Cohen](http://cohen.house.gov/index.php?option=com_content&task=view&id=75&Itemid=2)
    also provides a welcome message on its own page.

    Based on extensive usability testing, Jakob Nielsen and Hoa
    Loranger, in *Prioritizing Web Usability*, 2006 (p. 30) recommend
    that homepage welcome messages not exceed 10 to 20 words.

[^273]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=74)
    (page 64) recommends that when designing a homepage, "Don't
    overwhelm users by posting everything on the home page. Provide the
    most important and most requested information first."

    [*Research-Based Web Design & Usability
    Guidelines*](http://www.usability.gov/pdfs/chapter5.pdf#page=8),
    2^nd^ edition, page 41, (compiled by the U.S. Department of Health
    and Human Services), notes that:

    > Any element on the homepage that must immediately attract the
    > attention of users should be placed "above the fold." Information
    > that cannot be seen in the first screenful may be missed
    > altogether---this can negatively impact the effectiveness of the
    > Web site. If users conclude that what they see on the visible
    > portion of the page is not of interest, they may not bother
    > scrolling to see the rest of the page.

[^274]: The [*Members' Congressional
    Handbook*](http://cha.house.gov/official_and_representational_expenses_continued.aspx#WebSites)
    (Web Sites, § 2), issued by the House Administration Committee,
    provides that:

    > Member\'s Web sites must be located in the HOUSE.GOV host-domain
    > and may be maintained by either House Information Resources (HIR),
    > the Member\'s congressional office, or a private vendor.

    The [*Committees' Congressional
    Handbook*](http://cha.house.gov/committee_handbook.aspx#general5)
    (Web Site Regulations, General, § 3), issued by the House
    Administration Committee, provides that:

    > Web sites must be located in the HOUSE.GOV host-domain and may be
    > maintained either by House Information Resources (HIR), the
    > committee office, or a private vendor.

[^275]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 15.3 of the
    W3C](http://www.w3.org/TR/html4/present/graphics.html#h-15.3) *HTML
    4.01 Specification* designates the "noshade" attribute of the \<hr\>
    tag as a deprecated attribute).

    Using the "border:0" style sheet property along with the
    "background" style sheets property (to set the color) provides the
    same result in Internet Explorer 6.0, Netscape 7.1, and Firefox
    1.0.7 as using the "noshade" attribute.

[^276]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 15.3 of the
    W3C](http://www.w3.org/TR/html4/present/graphics.html#h-15.3) *HTML
    4.01 Specification* designates the "size" attribute of the \<hr\>
    tag as a deprecated attribute).

[^277]: [Section 4.6 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.6)
    *XHTML (2^nd^ edition) 1.0 Specification* provides that "Empty
    elements must either have an end tag or the start tag must end with
    /\>. For instance, \<br/\> or \<hr\>\</hr\>." [Checkpoint 11.1
    \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^278]: [Section 9.2.1 of the
    W3C](http://www.w3.org/TR/html4/struct/text.html#edef-CODE) *HTML
    4.01 Specification*, provides that the \<code\> tag "Designates a
    fragment of computer code."

[^279]: [Checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    (The W3C [*HTML 3.2
    Specification*](http://www.w3.org/TR/REC-html32#body) designates the
    \<listing\>, \<plaintext\>, and \<xmp\> tags as deprecated
    elements).

    Unlike the \<listing\>, \<plaintext\>, and \<xmp\> tags, the
    \<code\> tag and the \<pre\> tag will not display paired angle
    brackets (i.e., "\<" and "\>") in their raw state. To display either
    of those characters within a \<pre\> requires that they first be
    translated into their entity representations (e.g., &lt; or &gt;).

    The default versions of the \<code\> and \<pre\> tags differ in most
    browser implementations in that \<code\> automatically word wraps,
    while \<pre\> does not.

[^280]: [Checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 7.3 of the
    W3C](http://www.w3.org/TR/html4/struct/global.html#h-7.3) *HTML 4.01
    Specification* designates the "version" attribute of the \<html\>
    tag as a deprecated attribute)..

[^281]: [Section 3.1.1(3) of the
    W3C](http://www.w3.org/TR/xhtml1/#strict) *XHTML 1.0 Specification
    (2^nd^ edition)* provides that:

    > The root element of the document must contain an xmlns declaration
    > for the XHTML namespace
    > \[[XMLNS](http://www.w3.org/TR/xhtml1/#ref-xmlns%23ref-xmlns)\].
    > The namespace for XHTML is defined to be
    > http://www.w3.org/1999/xhtml. An example root element might look
    > like:
    >
    > \<html xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\"
    > lang=\"en\"\>

[^282]: [Checkpoint 3.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-grammar)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "validate to published formal grammars."

[^283]: Section 1 of the W3C [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure) provides
    that:

    > When designing a document or series of documents, content
    > developers should strive first to identify the desired structure
    > for their documents before thinking about how the documents will
    > be presented to the user. Distinguishing the structure of a
    > document from how the content is presented offers a number of
    > advantages, including improved accessibility, manageability, and
    > portability.

    Jeffrey Zeldman's, *Designing With Web Standards* (2^nd^ edition,
    \[2006\]), p.180, recommends that

    > Semantic or meta-structural names (names that explain the function
    > performed by elements contained within) are best. You would feel
    > pretty silly having labeled a part of your site "orangebox" when
    > the client decides to go with blue. You would feel sillier still
    > revising your style sheets under a deadline six months from now
    > and trying desperately to remember whether "Gladys" was a
    > navigational area, a sidebar, a search form, or what.

[^284]: [Section 7.5.2 of the
    W3C](http://www.w3.org/TR/html401/struct/global.html#h-7.5.2) *HTML
    4.01 Specification* requires that the value of each "id" attribute
    "must be unique in a document." [Checkpoint 3.2 \[priority 2\] of
    the W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-grammar)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "validate to published formal grammars."

[^285]: [Checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0*, however, provides that
    accessible websites should "\[a\]void deprecated features of W3C
    technologies." ([Section 4.10 of the
    W3C](http://www.w3.org/TR/xhtml1/#h-4.10) *XHTML 1.0 (2^nd^ edition)
    Specification* designates the "name" attribute of the \<map\> tag as
    a deprecated attribute and also provides that "XHTML 1.0 documents
    MUST use the id attribute when defining fragment identifiers" within
    a \<map\> tag).

[^286]: Section 1 of the W3C [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure) provides
    that:

    > When designing a document or series of documents, content
    > developers should strive first to identify the desired structure
    > for their documents before thinking about how the documents will
    > be presented to the user. Distinguishing the structure of a
    > document from how the content is presented offers a number of
    > advantages, including improved accessibility, manageability, and
    > portability.

    Jeffrey Zeldman's, *Designing With Web Standards* (2^nd^ edition,
    \[2006\]), p.180, recommends that

    > Semantic or meta-structural names (names that explain the function
    > performed by elements contained within) are best. You would feel
    > pretty silly having labeled a part of your site "orangebox" when
    > the client decides to go with blue. You would feel sillier still
    > revising your style sheets under a deadline six months from now
    > and trying desperately to remember whether "Gladys" was a
    > navigational area, a sidebar, a search form, or what.

[^287]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(f))
    provide that "Client-side image maps shall be provided instead of
    server-side image maps except where the regions cannot be defined
    with an available geometric shape." Likewise, [Checkpoint 9.1
    \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-client-side-maps)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "Provide client-side image maps instead of
    server-side image maps except where the regions cannot be defined
    with an available geometric shape."

    Jim Thatcher in *Web Accessibility: Web Standards and Regulatory
    Compliance* (2006, pp.

    204 to 205) indicates that there are no longer any geometric shapes
    can be defined in a server-side image map that cannot also be
    defined in a client-side image map and therefore "there is no case
    where a server-side map is permitted under the Section 508 provision
    §1194.22(f) or WCAG Checkpoint 9.1."

[^288]: [Section 4.5 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.5)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that all
    attributes must be given values (e.g., ismap=\"ismap\" not just:
    ismap). [Checkpoint 11.1 \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^289]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(e))
    provide that "Redundant text links shall be provided for each active
    region of a server-side image map." Likewise, [checkpoint 1.2
    \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-redundant-server-links)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[p\]rovide redundant text links for each active
    region of a server-side image map."

[^290]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(a))
    provide that "A text equivalent for every non-text element shall be
    provided (e.g., via \"alt\", \"longdesc\", or in element content)."

    [Checkpoint 1.1 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-text-equivalent) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should:

    > 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. . . .
    >
    > For example, in HTML: . . .

    For image maps, either use the \"alt\" attribute with AREA, or use
    the MAP element with A elements (and other text) as content.

[^291]: [Section 4.6 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.6)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that "Empty
    elements must either have an end tag or the start tag must end with
    /\>. For instance, \<br/\> or \<hr\>\</hr\>." [Checkpoint 11.1
    \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^292]: For the disposition of other functions formerly performed by
    INS, see <http://149.101.23.2/graphics/othergov/roadmap.htm>.

[^293]: The [January 30, 2006 edition of the Congressional Management
    Foundation's *Congress Online*
    newsletter](http://web.archive.org/web/20070203034459/http:/www.cmfweb.org/congressonline013006.asp)
    notes that "A lot of House sites have outdated or incorrect links.
    The most frustrating ones \[included\] . . . those linking to INS
    (it changed to USCIS in 2003!). Web sites continually change, so
    it's important to periodically review any link that goes off your
    site, especially at the beginning of each Congress so you don't have
    visitors looking at old information."

    A May 10 to June 9, 2006 review of House websites by the Web Systems
    Branch of House Information Resources (now CAO-Web Solutions Branch)
    indicated that 21% of House Member websites contained at least one
    reference to the INS as if the agency was still operational.

[^294]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=57)
    (pages 45 and 95) identifies "internship and Service Academy
    Nomination applications and instructions" as elements of a
    well-formed Congressional website. The report (page 68 and
    70).praises the websites of [Rep. Virginia
    Foxx](http://foxx.house.gov/?sectionid=15&sectiontree=8,15) for
    providing "substantive information on how to apply for internships";
    and [Rep. Kevin
    McCarthy](http://kevinmccarthy.house.gov/showpage.asp?ID=76) for
    providing "guidance on internship opportunities".

[^295]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=23)
    (pages 11, 41, and 50) takes the position that:

    > All sites, regardless of their audiences, need to have information
    > about legislative activities and the work of the office. This
    > should include information about legislative issues of national,
    > state, or local interest. . . .
    >
    > Typically, congressional sites have an "Issues" section which
    > contains most of that content. It can include national issues
    > (e.g. health care, war in Iraq), local issues (e.g. how the
    > clean-up of a local river or the state economy is affected by
    > federal legislation), and issues of particular importance to the
    > Member (e.g. women's rights, fiscal discipline). Each issue
    > usually has its own page with a description of the issue and the
    > Member's position and the most recent action to take place on the
    > issue, as well as the resources the office can provide related to
    > the issue---from sponsored legislation to CRS reports. . . .
    >
    > Past letters written to constituents explaining the Member's
    > stance and actions on an issue can populate the issues page . . .
    > .

    The report ([pages
    80](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=92),
    82, and 84) praises

    Rep. Eliot Engel's "'[A-Z Issues in
    Brief](http://engel.house.gov/index.cfm?SectionID=155&ParentID=154&SectionTypeID=2&SectionTree=154,155)'
    \[which\] offers an exhaustive list of issues and a brief statement
    of the Congressman's stance on each."

    Sen. Ben Nelson's "[issues
    section](http://bennelson.senate.gov/issues/index.cfm) \[which\]
    clearly emphasizes his priorities and explains them to his
    constituents"

    Rep. Bob Inglis's
    "[Issues](http://inglis.house.gov/issues.asp?content=sections/issues/featured_issues)"
    section for being "extensive and informative"

    The Congressional Management Foundation's [*Congress Online 2003:
    Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=53)
    (page 4*5*) also notes that, "Most citizens think of legislation in
    terms of broad issues, rather than specific bills. They especially
    want to understand the issues in Congress that affect them
    directly."

[^296]: Some offices have indicated a reluctance to provide detailed
    information on their Member's positions out of concern that this
    will help opposition research. The Congressional Management
    Foundation's [*2007 Gold Mouse Report: Lessons from the Best Web
    Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=55)
    (page 43) responds with:

    > Don't worry about opposition research; the Member's record is
    > readily available in any number of places online. If constituents
    > can't find a Member's stance or record on their official site,
    > they will find it elsewhere. This not only makes it look like the
    > Member has something to hide, it also allows someone other than
    > the Member to frame and explain the Member's views.

[^297]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=12)
    (page 4) notes that, "A recurring theme of our focus groups can be
    summed up in one word: accountability. Participants stated that
    Member Web sites that conveyed a sense of accountability and
    transparency deserved greater trust than those who seemed to be
    'hiding something.' Features that were deemed to inspire trust
    included: voting records, voting rationales, schedules, and unbiased
    issue information."

    The [Congressional Management
    Foundation's](http://www.congressonlineproject.org/congressonline2003.pdf#page=56)
    [*2006 Gold Mouse Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=70)
    (page 60) notes that:

    > Congressional Web sites can demonstrate accountability by
    > providing voting records, rationales for key votes, and schedules
    > -- and they can do so without overburdening their staffs.
    > Constituents are probably not interested in knowing about every
    > meeting that takes place or every vote taken. Stick to the most
    > relevant and current information: meetings with constituents,
    > public Member appearances in the district or state, committee
    > hearings, the House and Senate floor schedule.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=106)
    (page 94) identifies providing "the Member's voting record" as an
    element of a successful Congressional website. The report ([page
    21](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=33))
    indicates that 47% of House websites have this information and
    praises ([page
    76](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=88))
    the website of [Sen. John
    Thune](http://thune.senate.gov/public/index.cfm?FuseAction=Votes.Home)
    for having the "Senator's voting record . . . on the site in an
    easily readable format".

[^298]: <http://clerk.house.gov/legislative/legvotes.html>. Similar data
    is also available at GovTrack.US
    (<http://www.govtrack.us/congress/findyourreps.xpd>), C-Span
    (<http://www3.capwiz.com/c-span/votesearch.tt>), and *The Washington
    Post* (<http://projects.washingtonpost.com/congress/>).

[^299]: The [January 30, 2006 edition of the Congressional Management
    Foundation's *Congress Online*
    newsletter](http://web.archive.org/web/20070203034459/http:/www.cmfweb.org/congressonline013006.asp)
    cautions that "Web sites continually change, so it's important to
    periodically review any link that goes off your site, especially at
    the beginning of each Congress so you don't have visitors looking at
    old information."

[^300]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=62)
    (page 50) observes that "links to other Web pages or resources that
    contain specific and up-to-date information (\[e.g.,\], the Clerk's
    roll call votes page . . .) can offer additional timely information
    without any additional office resources."

[^301]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=106)
    (page 94) identifies explaining "how to read and use roll call
    votes" as an element of a successful Congressional website. The
    report ([page
    73](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=85))
    praises Rep. Adam Schiff's "[Voting
    Record](http://schiff.house.gov/HoR/CA29/Legislative+Issues/Voting+Record/)"
    page -- noting that "The link to roll call votes is preceded with a
    step by step guide to deciphering the Clerk's roll call page, as
    well as answers to frequently asked questions."

[^302]: See also, Rep. Mike Rogers of Alabama's "[Voting
    Record](http://www.house.gov/mike-rogers/voting-record.shtml)" page.

[^303]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=55)
    (pages 43 and 94) identifies providing "rationales for votes"
    (particularly recent votes from the current Congress) as an element
    of a successful Congressional website. The report notes that:

    > Citizens are always going to be interested in the Member's . . .
    > key votes. Don't worry about opposition research; the Member's
    > record is readily available in any number of places online. If
    > constituents can't find a Member's . . . record on their official
    > site, they will find it elsewhere. This not only makes it look
    > like the Member has something to hide, it also allows someone
    > other than the Member to frame and explain the Member's views.

    The report ([pages
    74](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=86)
    and 84) also praises [Rep. Cliff
    Stearns](http://www.house.gov/stearns/)' "Vites" page for including
    "A listing of recent votes, including a description of the bill, the
    Congressman's stance, and the final result, allow users to see what
    is happening in Congress."; and Rep. John Culberson's "'[This Week's
    Votes](http://culberson.house.gov/news.aspx?T=2),' which is updated
    weekly and offers users a look at key votes and how the Congressman
    voted."

[^304]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=38)
    (page 30) praises Sen. Dianne Feinstein's website for organizing her
    voting record information by issue.

[^305]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=74)
    (pages 62, 63, 79, and 80) praises the websites of:

    Rep. Tammy Baldwin, noting that "Descriptions of the issues are
    combined with links to further information in the form of related
    press releases, legislation, and links to relevant outside agencies
    and information."

    Rep. John Boozman for including "an exhaustive list of issues with
    links to related CRS reports, press releases, video, and other
    relevant documents."

    Republican Office of the Senate Committee on Environment and Public
    Works for having "content \[that\] is also fully integrated and
    cross-referenced throughout the site. For instance, the issues
    section contains a brief statement by the Ranking Member, related
    press releases and speeches, as well as related facts of the day and
    blog posts."

    Rep. Earl Blumenauer, noting that "For each issue in the issues
    section, a few brief paragraphs provide the latest information and a
    link to more information about the issue, along with clear, embedded
    links to related information which makes it very easy for visitors
    to find what they are looking for."

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=69)
    (pages 59 to 60) recommends that Congressional websites:

    **Include information on a variety of issues:** Constituents have a
    wide range of interests and priorities. Citizens' concerns about
    issues important to them should be addressed on Congressional Web
    sites. The best sites provide information on district or state
    issues, national issues, issues on which the Member is active, and
    some even include current "hot topic" issues that appear in the
    headlines at a given time.

    **Provide access to neutral sources of information:** You increase
    the value of your site and improve your credibility if you provide
    access to resources that will help visitors find answers to
    questions that your site does not address. Supporting information
    allows visitors to explore issues in greater depth, which will make
    them more likely to view you positively, even if they do not share
    your opinions and conclusions.

[^306]: See, e.g., the ["Holt on the Issues" section of Rep. Rush Holt's
    website](http://holt.house.gov/issues.shtml).

    For offices that use WIDA, use [WIDA's "issue" feature and
    WIDAinc](http://publisher.house.gov:80/publisher/housenet/technology/web_solutions/tools_folder/wida_instructions/content/wida_include__widainc_.html)
    to automatically place links to the relevant press releases on the
    appropriate issue page.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites

    > **Organize by issue type in addition to content type: *Rep. Jim
    > Langevin***'s Web site allows users seeking information about an
    > issue to view press releases, speeches, and CRS reports on the
    > subject. When users are interested in a topic, they want
    > everything related to it, without having to start a new search in
    > every section of the site. Even simply linking to related sections
    > of your Web site and cross-referencing your content can go a long
    > way toward making your site usable.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=58)
    (page 46) provides that

    > While they might not peruse the press release section,
    > incorporating press information into other sections of the site,
    > such as the issues section, can enhance the timeliness and value
    > of the entire site.

    The report ([pages
    70](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=82)
    and 76) praises the
    "[Issues](http://kevinmccarthy.house.gov/showpage.asp?ID=79)"
    sections of the websites of Rep. Kevin McCarthy for including "the
    latest press releases relating to each issue, which allows users to
    find the most recent information quickly and easily"; and Sen. Orin
    Hatch for including "relevant press releases . . . \[that\] users
    can access them by topic."

[^307]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) notes that:

    > When users are interested in a topic, they want everything related
    > to it, without having to start a new search in every section of
    > the site. Even simply linking to related sections of your Web site
    > and cross-referencing your content can go a long way toward making
    > your site usable.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=70)
    (page 58) quotes Rob Pierson, President of the House Systems
    Administrators Association and Webmaster of Rep. Mike Honda's
    four-time Mouse Award winning website, that

    > The constituent is not going to want to go to the video section
    > and look through the whole list of videos to see everything about
    > healthcare, and then go to the photos page to get all the photos
    > about healthcare," said Pierson. "What we're looking for is to
    > create issue-centered pages where you go to the healthcare page
    > and it shows you the Congressman's perspective on healthcare, it
    > shows all of the recent photos that he's posted that have been
    > tagged with a 'healthcare' tag, all of the videos of him speaking
    > on the floor of the House of Representatives about healthcare
    > issues, or blog posts that relate to healthcare, and have that all
    > in one central place. It's that kind of organization that makes it
    > easy for the constituent to find exactly what they need without
    > having to search through the whole site.

    The 2007 report ([page
    42](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=54))
    also advises:

    > Don't bury the information . . . When in doubt, put it in multiple
    > places (or in one place and link to it elsewhere). For example,
    > place links to educational information about Congress both in a
    > general section about Congress and in an "Issues" section.

[^308]: [Section 3.1 of the
    W3C](http://www.w3.org/TR/WCAG10-HTML-TECHS/#text-emphasis) *HTML
    Techniques for Web Content Accessibility Guidelines 1.0* provides
    that "The proper HTML elements should be used to mark up emphasis:
    [EM](http://www.w3.org/TR/WCAG10-HTML-TECHS/#edef-EM%23edef-EM) and
    [STRONG](http://www.w3.org/TR/WCAG10-HTML-TECHS/#edef-STRONG%23edef-STRONG).
    The [B](http://www.w3.org/TR/WCAG10-HTML-TECHS/#edef-B%23edef-B) and
    [I](http://www.w3.org/TR/WCAG10-HTML-TECHS/#edef-I%23edef-I)
    elements should not be used; they are used to create a visual
    presentation effect. The EM and STRONG elements were designed to
    indicate structural emphasis that may be rendered in a variety of
    ways (font style changes, speech inflection changes, etc.)."

    Perhaps the one legitimate exception to this standard (and even
    then, one to be used with care) is when you are reproducing text
    that originally existed as non-World Wide Web printed text. As Paul
    Ford notes in "[Processing
    Processing](http://www.ftrain.com/ProcessingProcessing.html#3-anchor)"
    (September 2, 2003) (cited in Jeffrey Zeldman's, *Designing With Web
    Standards* (2^nd^ edition, \[2006\], p. 175):

    > When I\'m publishing content from 1901 and it\'s in italics, it\'s
    > in *italics,* not emphasized. Typography has a semantics that is
    > subtle, changing, and deeply informed by history.

[^309]: Section 5.1(4) of the W3C [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#writing-style)
    recommends "Avoid slang, jargon, and specialized meanings of
    familiar words, unless defined within your document" to implement
    [WCAG 1.0 checkpoint
    14.1](http://www.w3.org/TR/WCAG10/#tech-simple-and-straightforward)
    \[priority 1\], that accessible websites should "\[u\]se the
    clearest and simplest language appropriate for a site\'s content."

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 61) notes that "Congressional jargon and the legislative
    process can be difficult for most people off the Hill to understand.
    Focus on making the information on your site understandable, rather
    than impressive and official-sounding." The Congressional Management
    Foundation's [*2007 Gold Mouse Report: Lessons from the Best Web
    Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=54)
    (page 42) also notes that "Constituents are not typically familiar
    with Hill jargon, so make sure that acronyms and terms like 'motion
    to recommit' and 'roll call votes' are explained as well."

[^310]: See also, Rep. Ginny Brown-Waite's "[Federal Job
    Postings](http://brown-waite.house.gov/ConstituentServices/jobpostings.htm)"
    page.

[^311]: For instance,

    > <http://jobsearch.usajobs.opm.gov/jobsearch.asp?re=9&vw=b&pg=1&lid=602&paygrademin=1&paygrademax=15&FedEmp=N&sort=rv&brd=3876&ss=0&FedPub=Y>

    will retrieve the Federal job announcements for Tennessee.

[^312]: The full text of the Act can be found at [title 15, chapter 91
    of the U.S.
    Code](http://uscode.house.gov/quicksearch/get.plx?title=15&chapter=91).
    The full text of the regulations issued by authority of the Act can
    be found at [title 16, part 312 of the Code of Federal
    Regulations](http://www.access.gpo.gov/nara/cfr/waisidx_05/16cfr312_05.html).
    While the Act does not, on its own terms, apply to Congressional
    websites, House offices should be encouraged to comply to avoid
    being put in the position of someone pointing to the site and asking
    why is a Congressional website not complying with the minimum
    standards that Congress has mandated for commercial websites.

[^313]: "Personal information" is defined in [§ 312.2 of the COPPA
    regulations](http://a257.g.akamaitech.net/7/257/2422/11feb20051500/edocket.access.gpo.gov/cfr_2005/janqtr/pdf/16cfr312.2.pdf)
    as:

    > individually identifiable information about an individual
    > collected online, including:
    >
    > \(a\) A first and last name;
    >
    > \(b\) A home or other physical address including street name and
    > name of a city or town;
    >
    > \(c\) An e-mail address or other online contact information,
    > including but not limited to an instant messaging user identifier,
    > or a screen name that reveals an individual's e-mail address;
    >
    > \(d\) A telephone number;
    >
    > \(e\) A Social Security number;
    >
    > \(f\) A persistent identifier, such as a customer number held in a
    > cookie or a processor serial number, where such identifier is
    > associated with individually identifiable information; or a
    > combination of a last name or photograph of the individual with
    > other information such that the combination permits physical or
    > online contacting; or
    >
    > \(g\) Information concerning the child or parents of that child
    > that the operator collects online from the child and combines with
    > an identifier described in this definition.

[^314]: The narrow exceptions to the parental consent requirement, are
    set out in [§ 312.5(c) of the COPPA
    regulations](http://a257.g.akamaitech.net/7/257/2422/11feb20051500/edocket.access.gpo.gov/cfr_2005/janqtr/pdf/16cfr312.5.pdf).

[^315]: If an office insists on asking for personal information from
    children, the office should be referred to the parental consent
    requirements set out in [§ 312.5 of the COPPA
    regulations](http://a257.g.akamaitech.net/7/257/2422/11feb20051500/edocket.access.gpo.gov/cfr_2005/janqtr/pdf/16cfr312.5.pdf).

[^316]: Similar layouts are used on the websites of [Rep. Dan
    Boren](http://boren.house.gov/kids.shtml), [Rep. Phil
    English](http://www.house.gov/english/kids.shtml), [Rep. Jeff
    Fortenberry](http://fortenberry.house.gov/kids.shtml), [Rep. Gwen
    Moore](http://www.house.gov/gwenmoore/kids.shtml), and [Rep. Randy
    Neugebauer](http://randy.house.gov/services/kids.shtml).

[^317]: Websites that are hosted on the HIR UNIX server (and do not use
    a virtual URL) should consider putting the contents of the House
    Kids page on their site by using the server-side include:

    > \<!\--#include virtual=\"/house/subpage_content/Kids_content.htm\"
    > \--\>

    All other sites can use code along the lines of:

    > \<iframe
    > src=\"http://www.house.gov/house/subpage_content/Kids_content.htm\"
    >
    > scrolling=\"auto\" style=\"width:35em;height:100em;\"
    > frameborder=\"0\" title=\"Kids' page\"\>\<ul\>\<li\>\<a
    >
    > href=\"http://www.house.gov/house/subpage_content/Kids_content.htm\"\>Kid's
    > page\</a\>\</li\>\</ul\>\</iframe\>

    Additional links can be added to the set maintained by HIR. For
    instance, a link could be added to the bottom of the HIR-maintained
    links with the following coding:

    > \<!\--#include virtual=\"/house/subpage_content/Kids_content.htm\"
    > \--\>
    >
    > \<div id=\"kids\"\>
    >
    > \<div id=\"kidsrow\" \>
    >
    > \<div id=\"kidspic\"\>\<a target=\"\_blank\"
    > href=\"http://www.house.gov/htbin/leave_site?ln_url=http://www.mywonderfulworld.org&amp;ln_desc=National+Geographic+Education+Foundation\"\>
    >
    > \<img id=\"imgkids\" src=\"images/my-wonderful-world-2.gif\"
    > alt=\"My Wonderful World\" border=\"0\" /\>\</a\>\<br /\>\<a
    > target=\"\_blank\"
    > href=\"http://www.house.gov/htbin/leave_site?ln_url=http://www.mywonderfulworld.org&amp;ln_desc=National+Geographic+Education+Foundation\"\>My
    > Wonderful World\</a\>
    >
    > \</div\>
    >
    > \</div\>
    >
    > \</div\>

    Using the \<include\> or \<iframe\> is preferable to just linking to
    the House's generic Kids' page. Using \<include\> or \<iframe\>
    retains the consistent look and feel of the rest of the office's
    website. A consistent look and feel assists with compliance with
    [Checkpoint 13.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* which provides that an
    accessible website should "Use navigation mechanisms in a consistent
    manner."

    [Section 4 of the
    W3C](http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation) *Core
    Techniques for Web Content Accessibility Guidelines 1.0* further
    provides that:

    > A consistent style of presentation on each page allows users to
    > locate navigation mechanisms more easily but also to skip
    > navigation mechanisms more easily to find important content. This
    > helps people with learning and reading disabilities but also makes
    > navigation easier for all users. Predictability will increase the
    > likelihood that people will find information at your site, or
    > avoid it when they so desire.
    >
    > Examples of structures that may appear at the same place between
    > pages:

    navigation bars

    the primary content of a page

    > . . .
    >
    > A navigation mechanism creates a set of paths a user may take
    > through your site. Providing navigation bars, site maps, and
    > search features all increase the likelihood that a user will reach
    > the information they seek at your site. If your site is highly
    > visual in nature, the structure might be harder to navigate if the
    > user can\'t form a mental map of where they are going or where
    > they have been. To help them, content developers should describe
    > any navigation mechanisms. It is crucial that the descriptions and
    > site guides be accessible since people who are lost at your site
    > will rely heavily on them.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site:** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. ***Sen. John Cornyn***'s Web site is a
    > model of clearly and consistently organized information. The menu
    > headers and options are clear, and they stay the same throughout
    > the site.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^318]: *Prioritizing Web Usability*, by Jakob Nielsen and Hoa Loranger,
    2006 (p. xxiii), notes, however, that "our usability studies with
    teenage users show that teens don't want business sites or
    government sites that are made to look as if they were created by
    teenagers when they were not."

[^319]: Similar material can be found at Rep. Vic Synder's
    "[Kids](http://www.house.gov/snyder/kids.shtml)" page and Rep. Jim
    Moran's "[Kid's Page](http://moran.house.gov/kidszone.shtml)". See
    also, Rep. Bud Cramer's "[Kid's
    Zone](http://cramer.house.gov/HoR/AL05/Kids+Zone.htm?SecLnk=KidsZone)".

[^320]: [Checkpoint 4.3 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-lang) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "Identify the primary natural language of a
    document."

[^321]: [Checkpoint
    4.1](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-changes)
    \[priority 1\] of the W3C *Web Content Accessibility Guidelines 1.0*
    provides that accessible websites should "Clearly identify changes
    in the natural language of a document\'s text and any text
    equivalents (e.g., captions)."

[^322]: [Section C.](http://www.w3.org/TR/xhtml1/#C_7)7 of the W3C
    *XHTML 1.0 Specification (2^nd^ edition)* provides "Use both the
    lang and xml:lang attributes when specifying the language of an
    element. The value of the xml:lang attribute takes precedence."

[^323]: This best practice is not intended to apply to style sheets
    where the value of the "media" property is "print". Use of points,
    picas, centimeters, or inches in that type of style sheet is
    appropriate.

[^324]: [Checkpoint 3.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-relative-units) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se relative rather than absolute units in
    markup language attribute values and style sheet property values.
    \[Priority 2\]

    > For example, in CSS, use \'em\' or percentage lengths rather than
    > \'pt\' or \'cm\', which are absolute units. If absolute units are
    > used, validate that the rendered content is usable (refer to the
    > [section on
    > validation](http://www.w3.org/TR/WCAG10/#validation))."

    ########### [**Section 3 of the W3C**](http://www.w3.org/TR/WCAG10-CSS-TECHS/#units) ***CSS Techniques for Web Content Accessibility Guidelines 1.0*,** recommends these techniques: {#section-3-of-the-w3c-css-techniques-for-web-content-accessibility-guidelines-1.0-recommends-these-techniques .unnumbered}

    Use the \"em\" unit to set font sizes.

    Use relative length units and percentages. CSS allows you to use
    relative units even in absolute positioning. Thus, you may position
    an image to be offset by \"3em\" from the top of its containing
    element. This is a fixed distance, but is relative to the current
    font size, so it scales nicely.

    Only use absolute length units when the physical characteristics of
    the output medium are known, such as bitmap images.

[^325]: Jakob Nielsen's "[Screen Resolution and Page
    Layout](http://www.useit.com/alertbox/screen_resolution.html)" (July
    31, 2006) recommends that Web designers:

    > Optimize Web pages for 1024x768, but use a liquid layout that
    > stretches well for any resolution, from 800x600 to 1280x1024.
    >
    > . . .

    **Optimize for 1024x768**, which is currently the most widely used
    screen size. Of course, the general guideline is to optimize for
    your target audience\'s most common resolution, so the size will
    change in the future. It might even be a different size now, if,
    say, you\'re designing an intranet for a company that gives all
    employees big monitors.

    **Do *not* design solely for a specific monitor size** because
    screen sizes vary among users. Window size variability is even
    greater, since users don\'t always maximize their browsers
    (especially if they have large screens).

    **Use a liquid layout** that stretches to the current user\'s window
    size (that is, avoid frozen layouts that are always the same size).

    > Currently, about **60%** of all monitors are set at **1024x768**
    > pixels. . . . In comparison, only about **17%** use **800x600** so
    > it\'s obviously less important to aim at perfection for these
    > small-display users. What\'s equally obvious, however, is that you
    > can\'t simply ignore 17% of your customer segment by providing a
    > frozen layout that requires more screen space than they have
    > available.

    ##  {#section}

    > When I say \"optimize\" I mean that your page should **look and
    > work the *best* at the most common size**. It should still look
    > *good* and work *well* at other sizes, which is why I recommend a
    > liquid layout. But it should be its best at 1024x768.
    >
    > The three main criteria in optimizing a page layout for a certain
    > screen size are:

    **Initial visibility**: Is all key information visible above the
    fold so users can see it without scrolling? This is a tradeoff
    between how many items are shown vs. how much detail is displayed
    for each item.

    **Readability**: How easy is it to read the text in various columns,
    given their allocated width?

    **Aesthetics**: How good does your page look when the elements are
    at the proper size and location for this screen size? Do all the
    elements line up correctly \-- that is, are captions immediately
    next to the photos, etc.?

[^326]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=74)
    (page 64) recommends that "At least two-thirds of every page on your
    site should contain useful information.".

[^327]: It is a long-standing tradition in the printing industry to use
    as dummy text a classical Latin excerpt from Cicero's *The Extremes
    of Good and Evil*, written in 45 B.C.E. The first two words of the
    passage are "Lorem Ipsum", which is now often used as the name for
    the text. For more, information on Lorem Ipsum, including a Lorem
    Ipsum generator to produce dummy text, see <http://www.lipsum.com/>.

    Jakob Nielsen and Hoa Loranger, in *Prioritizing Web Usability*, by,
    2006 (p. 214), however, take a somewhat different approach. They
    note that:

    > It often makes sense for designers to use place-holder text while
    > they work on visuals before the content is finalized. However,
    > legibility problems can easily be underestimated when all you see
    > is "lorem ipsum." When reviewing screens with nonsense text, you
    > simply think to yourself, text goes here. If you are not trying to
    > read it, you won't notice if it's unintelligible.
    >
    > Our guideline: If you don't have the final content available while
    > designing a Web site, at least insert representative text from the
    > current site instead of nonsense text.

[^328]: See, for instance, "[Congressional Websites: The Bright, Bland,
    and
    Bizarre](http://thehill.com/cover-stories/congressional-websites-the-bright-bland-and-bizarre-2007-06-20.html),"
    *The Hill*, June 20, 2007.

[^329]: This approach is consistent with [Item 6
    of](https://secadmin5.us.house.gov/checklists/HISPUB 007.1.56 - Website Developement.pdf#page=3)
    *The United States House of Representatives Information Security
    Publication -- Web Site Developers Security Checklist* (HISPUB
    007.1.56, August 2008) which provides that "All test, dev, backup,
    and unnecessary files should be removed from the site."

[^330]: The \<!\--\~!CMB\--\> and \<!\--\~!CME\--\> tags allow pages to
    be maintained through the HIR UNIX Content Manager. The tags are
    treated as comments by other content managers and by Web browsers.

[^331]: The Congressional Management Foundation's Foundation's [*2007
    Gold Mouse Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=106)
    (pages 94 and 21) identifies providing information on legislation
    sponsored and co-sponsored by the Member as one of the elements of a
    well-formed House Member's website. At the time the report was
    compiled, 74% of House websites contained sponsorship and
    co-sponsorship information.

[^332]: For instructions as to how to link

    to legislation sponsored by a Member, see
    <http://www.congress.gov/help/THOMAS_links/bss.html#bssmember>.

    to legislation co-sponsored by a Member, see
    <http://www.congress.gov/help/THOMAS_links/bss.html#bsscosp>

    to legislation sponsored or co-sponsored by a Member, see
    http://www.congress.gov/help/THOMAS_links/bss.html#bssspco

[^333]: For instructions as to how to link to legislation referred to a
    committee, see
    <http://www.congress.gov/help/THOMAS_links/bss.html#bsscommittee>.

[^334]: <http://clerk.house.gov/floorsummary/floor.html>

[^335]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=54)
    (pages 42 and 95) indicates that providing the current Floor
    proceedings is an element of a successful congressional website. At
    the time the report was compiled, 54% of all House Member,
    committee, and leadership websites included this information ([page
    21](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=33)).

    Since the Current House Floor Proceedings website is maintained by
    the Clerk of the House, be mindful of the [January 30, 2006 edition
    of the Congressional Management Foundation's *Congress Online*
    newsletter](http://web.archive.org/web/20070203034459/http:/www.cmfweb.org/congressonline013006.asp)
    which notes that "A lot of House sites have outdated or incorrect
    links. The most frustrating ones \[include\] . . . dead links to the
    Clerk's Web site. . . . Web sites continually change, so it's
    important to periodically review any link that goes off your site,
    especially at the beginning of each Congress so you don't have
    visitors looking at old information."

[^336]: <http://www.house.gov/house/floor/thisweek.htm>

[^337]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=27)
    (page 17) indicates that providing the chamber schedule is one of
    the elements of a well-formed congressional website. At the time the
    report was compiled, 42.7% of all House Member, committee, and
    leadership websites included this information.

[^338]: websites that are hosted on the HIR UNIX server (and do not use
    a virtual URL) are encouraged put the annual House calendar on their
    site by using the server-side include:

    > \<!\--#include
    > virtual=\"/house/subpage_content/Calendar_content.htm\"\--\>

    All other sites can use code along the lines of:

    > \<iframe
    > src=\"http://www.house.gov/house/subpage_content/Calendar_content.htm\"
    >
    > scrolling=\"auto\" style=\"width:100%; height:40em;\"
    > frameborder=\"0\" title=\"Annual House Calendar\"\>\<ul\>\<li\>\<a
    >
    > href=\"http://www.house.gov/house/House_Calendar.shtml\"\>Annual
    > House calendar\</a\>\</li\>\</ul\>\</iframe\>

    Using the \<include\> or \<iframe\> is preferable to just linking to
    the House's annual calendar page
    (<http://www.house.gov/house/House_Calendar.shtml>). Using
    \<include\> or \<iframe\> retains the consistent look and feel of
    the rest of the office's website. A consistent look and feel assists
    with compliance with [Checkpoint 13.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* which provides that an
    accessible website should "Use navigation mechanisms in a consistent
    manner."

    [Section 4 of the
    W3C](http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation) *Core
    Techniques for Web Content Accessibility Guidelines 1.0* further
    provides that:

    > A consistent style of presentation on each page allows users to
    > locate navigation mechanisms more easily but also to skip
    > navigation mechanisms more easily to find important content. This
    > helps people with learning and reading disabilities but also makes
    > navigation easier for all users. Predictability will increase the
    > likelihood that people will find information at your site, or
    > avoid it when they so desire.
    >
    > Examples of structures that may appear at the same place between
    > pages:

    navigation bars

    the primary content of a page

    > . . .
    >
    > A navigation mechanism creates a set of paths a user may take
    > through your site. Providing navigation bars, site maps, and
    > search features all increase the likelihood that a user will reach
    > the information they seek at your site. If your site is highly
    > visual in nature, the structure might be harder to navigate if the
    > user can\'t form a mental map of where they are going or where
    > they have been. To help them, content developers should describe
    > any navigation mechanisms. It is crucial that the descriptions and
    > site guides be accessible since people who are lost at your site
    > will rely heavily on them.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site:** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. ***Sen. John Cornyn's*** Web site is a
    > model of clearly and consistently organized information. The menu
    > headers and options are clear, and they stay the same throughout
    > the site.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^339]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=53)
    (pages 45 to 46) praises Rep. Mike Honda's website for having links
    to legislative schedules. [Rep. Honda's "Legislation: On the Issues"
    page](http://honda.house.gov/issues/) links to the Majority Whip's
    calendar, the current House floor proceedings, and the Democratic
    Whip's daily notice.

[^340]: <http://www.majorityleader.gov/links_and_resources/whip_resources/daily.cfm>

[^341]: <http://www.majorityleader.gov/links_and_resources/whip_resources/weekly.cfm>

[^342]: <http://majoritywhip.house.gov/daily_whipline.html>

[^343]: <http://majoritywhip.house.gov/house_calendar.html>

[^344]: <http://republicanwhip.house.gov/home.aspx#whip-notice>

[^345]: <http://republicanwhip.house.gov/home.aspx#tabbertab>

[^346]: <http://republicanwhip.house.gov/Calendar/>

[^347]: <http://thomas.loc.gov/home/bills_res.html>

[^348]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=106)
    (page 94) identifies including "a THOMAS search box or link" as an
    element of a successful Congressional website.

    Referring to "Legislation: bills and resolutions" instead of just
    referring to "Thomas" is consistent with the recommendation of the
    Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=71)
    (page 61) which notes that "Congressional jargon and the legislative
    process can be difficult for most people off the Hill to understand.
    Focus on making the information on your site understandable, rather
    than impressive and official-sounding."

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=54)
    (page 42) also notes that:

    > The most important consideration in creating legislative content,
    > of course, is ensuring that all users will understand it,
    > regardless of how frequently they visit the site. For example,
    > instead of a link that just says "THOMAS," there should be
    > something briefly explaining what THOMAS is, such as "search for
    > legislation."

[^349]: <http://thomas.loc.gov/home/r110query.html>

[^350]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=93)
    (page 83) identifies having "\[l\]inks directly to the
    *Congressional Record*" as one of the elements in a well-formed
    congressional website.

[^351]: <http://thomas.loc.gov/home/cr_help.htm>

[^352]: Consider also providing a link to the House Rules Committee's
    "Using the Congressional Record"
    (<http://www.rules.house.gov/archives/pop022299_ho3.htm>).

[^353]: <http://thomas.loc.gov/cp110/cp110query.html>

[^354]: Published Congressional committee hearing transcripts (and other
    materials) are available through the U.S Government Printing
    Office's GPO Access at
    <http://www.gpoaccess.gov/congress/index.html>.

[^355]: Consider also including the list of today's hearings compiled by
    the House Radio-Television Correspondents' Gallery
    (<http://radiotv.house.gov/hearings.shtml>).

[^356]: <http://thomas.loc.gov/home/lawsmade.toc.html>

[^357]: Consider also including the [kids' version of "How Our Laws Are
    Made"](http://clerkkids.house.gov/laws/index.html) (compiled by the
    Clerk of the House).

[^358]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=54)
    (pages 42 and 95) identifies providing information about how a bill
    becomes a law as an element of a successful Congressional website.
    The report ([page
    21](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=33))
    also notes that only 35% of House websites provide that information.
    The report ([page
    72](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=84))
    praises the website of Rep. [Paul Ryan](http://www.house.gov/ryan/)
    for providing this information.

[^359]: <http://www.rules.house.gov/house_rules_precedents.htm>

[^360]: Additional links related to the Rules and Precedents of the
    House that you might want to consider including are:

    [General Parliamentary
    Procedure](http://www.rules.house.gov/leg_process.htm) (compiled by
    the House Rules Committee),

    [House Committee
    Procedures](http://www.rules.house.gov/comm_procs.htm) (compiled by
    the House Rules Committee),

    [House Floor
    Procedures](http://www.rules.house.gov/house_protocol.htm) (compiled
    by the House Rules Committee),

    [House and Senate parliamentary
    procedure](http://www.rules.house.gov/archives/crs_reports.htm)
    (prepared by the Congressional Research Service of the Library of
    Congress),

[^361]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=68)
    (page 58) notes that:

    > Most citizens outside the Beltway have forgotten their high school
    > civics classes. Offices can do constituents a great service by
    > finding ways of making educational information easily accessible
    > throughout the site so visitors can refer to it whenever they have
    > questions.

    The Congressional Management Foundation's [*Congress Online 2003:
    Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=56)
    (page 48) further notes that:

    > Some offices provide educational information on their kids' or
    > students' pages, but kids are not the only ones who need it. *Rep.
    > Chaka Fattah (D-PA)* has a prominent section on his home page that
    > explains how government works. His site includes an actual [case
    > study](http://www.house.gov/fattah/features/how.htm) of how his
    > "GEAR UP" initiative became public law. Your site should also
    > include information about how the committee process works;
    > explanations of legislative and congressional terms; and general
    > descriptions of what a Member, Chair, or Leader does on a given
    > day.

    An example can also be found on Rep. Bud Cramer's "[How a Bill
    Becomes
    Law](http://cramer.house.gov/HoR/AL05/Issues/How+A+Bill+Becomes+A+Law/About+Congress.htm)"
    page..

[^362]: Websites that are hosted on the HIR UNIX server (and do not use
    a virtual URL) are encouraged to use the server-side include:

    > \<!\--#include
    > virtual=\"/house/subpage_content/Tying_it_all_content.htm\" \--\>

    All other sites can use code along the lines of:

    > \<iframe
    > src=\"http://www.house.gov/house/subpage_content/Tying_it_all_content.htm\"
    >
    > scrolling=\"auto\" style=\"width:35em; height:120em;\"
    > frameborder=\"0\"\>\<ul\>\<li\>\<a
    >
    > href=\"http://www.house.gov/house/Tying_it_all.shtml\"\>Tying it
    > all
    >
    > Together\</a\>\</li\>\</ul\>\</iframe\>

    Using the \<include\> or \<iframe\> is preferable to just linking to
    the House's "Legislative Process page". Using \<include\> or
    \<iframe\> retains the consistent look and feel of the rest of the
    office's website. A consistent look and feel assists with compliance
    with [Checkpoint 13.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* which provides that an
    accessible website should "Use navigation mechanisms in a consistent
    manner."

    [Section 4 of the
    W3C](http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation) *Core
    Techniques for Web Content Accessibility Guidelines 1.0* further
    provides that:

    > A consistent style of presentation on each page allows users to
    > locate navigation mechanisms more easily but also to skip
    > navigation mechanisms more easily to find important content. This
    > helps people with learning and reading disabilities but also makes
    > navigation easier for all users. Predictability will increase the
    > likelihood that people will find information at your site, or
    > avoid it when they so desire.
    >
    > Examples of structures that may appear at the same place between
    > pages:

    navigation bars

    the primary content of a page

    > . . .
    >
    > A navigation mechanism creates a set of paths a user may take
    > through your site. Providing navigation bars, site maps, and
    > search features all increase the likelihood that a user will reach
    > the information they seek at your site. If your site is highly
    > visual in nature, the structure might be harder to navigate if the
    > user can\'t form a mental map of where they are going or where
    > they have been. To help them, content developers should describe
    > any navigation mechanisms. It is crucial that the descriptions and
    > site guides be accessible since people who are lost at your site
    > will rely heavily on them.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site:** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. ***Sen. John Cornyn***'s Web site is a
    > model of clearly and consistently organized information. The menu
    > headers and options are clear, and they stay the same throughout
    > the site.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^363]: The [January 30, 2006 edition of the Congressional Management
    Foundation's *Congress Online*
    newsletter](http://web.archive.org/web/20070203034459/http:/www.cmfweb.org/congressonline013006.asp)
    notes that "A lot of House sites have outdated or incorrect links.
    The most frustrating ones were those linking \[during the 109^th^
    Congress\] to bills, sponsorships, and co-sponsorships from the
    108^th^ Congress (and, occasionally, earlier Congresses); dead links
    to the Clerk's Web site; THOMAS search engines that search the wrong
    Congress; and those linking to INS (it changed to USCIS in 2003!).
    Web sites continually change, so it's important to periodically
    review any link that goes off your site, especially at the beginning
    of each Congress so you don't have visitors looking at old
    information."

[^364]: Instructions for linking to specific legislation within Thomas
    can be found at <http://www.congress.gov/help/handles.html> .

[^365]: [*Research-Based Web Design & Usability
    Guidelines*](http://www.usability.gov/pdfs/chapter2.pdf#page=2),
    2^nd^ edition, page 10, (compiled by the U.S. Department of Health
    and Human Services), identifies providing "citatons and references"
    as one of the elements that project credibility in a website.

[^366]: Domain CONGRESS.GOV.

[^367]: The [*Members' Congressional
    Handbook*](http://cha.house.gov/official_and_representational_expenses_continued.aspx#WebSiteshttp://cha.house.gov/index.php?option=com_content&task=view&id=208)
    (Web Sites, § 5), issued by the House Administration Committee,
    provides that:

    > HIR will display an exit notice stating that users are leaving the
    > House of Representatives prior to linking to a non-House of
    > Representatives Web site. The exit notice will include a
    > disclaimer that neither Members nor the House are responsible for
    > the content of linked sites. Member offices maintaining their
    > sites on the Public web server are required to incorporate the
    > exit notice into their external links.

    An almost identical regulation appears in the [*Committees'
    Congressional
    Handbook*](http://cha.house.gov/index.php?option=com_content&task=view&id=50&Itemid=37#websitegeneral)
    (Web Site Regulations, General, § 5).

[^368]: [Checkpoint 13.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* which provides that an
    accessible website should "\[u\]se navigation mechanisms in a
    consistent manner."

    [Section 4 of the
    W3C](http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation) *Core
    Techniques for Web Content Accessibility Guidelines 1.0* further
    provides that:

    > A consistent style of presentation on each page allows users to
    > locate navigation mechanisms more easily but also to skip
    > navigation mechanisms more easily to find important content. This
    > helps people with learning and reading disabilities but also makes
    > navigation easier for all users. Predictability will increase the
    > likelihood that people will find information at your site, or
    > avoid it when they so desire.
    >
    > Examples of structures that may appear at the same place between
    > pages:

    navigation bars

    the primary content of a page

    > . . .
    >
    > A navigation mechanism creates a set of paths a user may take
    > through your site. Providing navigation bars, site maps, and
    > search features all increase the likelihood that a user will reach
    > the information they seek at your site. If your site is highly
    > visual in nature, the structure might be harder to navigate if the
    > user can\'t form a mental map of where they are going or where
    > they have been. To help them, content developers should describe
    > any navigation mechanisms. It is crucial that the descriptions and
    > site guides be accessible since people who are lost at your site
    > will rely heavily on them.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site.** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. If you have a blue navigation toolbar on
    > the left side of one page, there should be a blue navigation
    > toolbar on the left side of every page. If you have links imbedded
    > in text in one issue section, you should do the same thing in
    > every issue section. *Rep. Wayne Gilchrest (R-MD)* uses the same
    > horizontal and vertical navigation throughout his site. The only
    > thing that changes on his pages is the content.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^369]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=32)
    (page 24) praises the website of Rep. Kay Granger because of the
    site's "efforts to address constituent concerns and problems online
    rather than pushing them off to another website or directing them
    off line."

[^370]: [Checkpoint 10.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-pop-ups) *Web
    Content Accessibility Guidelines 1.0* provides that "[*[\[u\]ntil
    user
    agents]{.underline}*](http://www.w3.org/TR/WCAG10/wai-pageauth.html#until-user-agents)
    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."

    *Prioritizing Web Usability*, by Jakob Nielsen and Hoa Loranger,
    2006 (pp. 69 & 74) notes that:

    > New browser windows, . . . \[cause\] problems for users who don't
    > understand the concept of multiple windows. When possible, keep
    > your Web site in the same browser window and ensure that the Back
    > button works. Launching new windows on top of the parent window
    > can stop many users from interacting with your site. For example,
    > we've seen people accidentally click outside the parent browser
    > window and bury the new window underneath it, then try to reopen
    > the new window from the parent window and nothing appears to
    > happen. They can't find their way back to the new window and
    > conclude that the site is broken. . . .
    >
    > Users with many different types of disabilities have particular
    > problems managing extra windows. People with motor skills
    > impairments certainly don't relish having to struggle to click
    > unwanted Close boxes. And low-vision users may not even know that
    > a pop-up has appeared if they have zoomed in their screen
    > magnifier to inspect a different part of the screen. Finally,
    > blind users are severely impacted by the additional cognitive load
    > of having to cope with multiple windows and remember what
    > information was read aloud from which pop-up.

    Nielsen and Loranger, however, do recommend an exception for PDFs
    and similar types of documents (pp. 70-71).

[^371]: The [homepage of the Immigration Reform
    Caucus](http://www.house.gov/bilbray/irc/) is an example of proper
    use of the "target" attribute to control the contents of an
    \<iframe\>.

[^372]: The Congressional Management Foundation's 1999 report *Building
    Web Sites Constituents Will Use* (page 9) recommends that
    Congressional websites "**Place external and internal links
    throughout your site, rather than on a single "Links" page.** This
    ensures that visitors can instantly access the information they
    want, rather than searching for it among a long list of links."

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=44)
    (page 34) praises the website of Rep. Mike Honda because it "links
    to federal government Web sites and complements them with brief
    descriptions of the general areas those agencies cover."

[^373]: [Guideline 9 of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#gl-device-independence)
    *Web Content Accessibility Guidelines 1.0* provides accessible
    websites should:

    > Design for device-independence.

    #### Use features that enable activation of page elements via a variety of input devices.

    > [Device-independent](http://www.w3.org/TR/WCAG10/#device-independent)
    > access means that the user may interact with the user agent or
    > document with a preferred input (or output) device \-- mouse,
    > keyboard, voice, head wand, or other. If, for example, a form
    > control can only be activated with a mouse or other pointing
    > device, someone who is using the page without sight, with voice
    > input, or with a keyboard or who is using some other non-pointing
    > input device will not be able to use the form.

    Roger Hudson's "[Text Alternatives for
    Images](http://www.usability.com.au/resources/image-text.cfm)"
    (September 2003) recommends that Web designers, **"**Avoid
    unnecessary terms. Don\'t use words like \'link\' or \'click here\'
    for images that are links. Screen readers will indicate if something
    is a link or not."

[^374]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) recommends that "Links should be descriptive and clear
    enough that the user can tell where it leads."

    [Checkpoint 13.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-meaningful-links)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should:

    > Clearly identify the target of each link. \[Priority 2\]
    >
    > [*[Link
    > text]{.underline}*](http://www.w3.org/TR/WCAG10/#link-text%23link-text)
    > should be meaningful enough to make sense when read out of context
    > \-- either on its own or as part of a sequence of links. Link text
    > should also be terse.
    >
    > For example, in HTML, write \"Information about version 4.3\"
    > instead of \"click here\". In addition to clear link text, content
    > developers may further clarify the target of a link with an
    > informative link title (e.g., in HTML, the \"title\" attribute).

    Note that the Jaws screen reader can be configured so that it will
    read which ever is larger -- the text of the link or the value of
    the "title" attribute.

    An alternative technique to using the "title" attribute, that has
    been suggested is to put the additional information within \<span\>
    tags and give the tag a class (e.g. class=\"hidden\"), where the
    class places the text off screen and minimizes the size (e.g.,
    position:absolute;left:-999em; font-size:1%).

    A technique to avoid at the current time is adding the additional
    text to the link in a \<span\> with a class value that has a
    media=\"screen\" style sheet with a display:none property and a
    media=\"aural\" (or a media=\"speech\") style sheet without the
    display:none property. The Jaws screen reader (which currently has
    about 75% of the screen reader market) uses the screen style sheet
    (and not the aural (or speech) style sheet) to build its audio
    output. (See also, Gez Lemon's "Screen Readers and display:none,"
    Juicy Studio (October 12, 2007), for an apparent bug in how Jaws and
    Window-Eyes processes the "display:none" property.)

[^375]: [Checkpoint 13.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-use-metadata) *Web
    Content Accessibility Guidelines 1.0* provides that an accessible
    website should:

    > Provide metadata to add semantic information to pages and sites. .
    > . .
    >
    > **Note.** Some HTML [*[user
    > agents]{.underline}*](http://www.w3.org/TR/WCAG10/#user-agent%23user-agent)
    > can build navigation tools from document relations described by
    > the HTML LINK element and \"rel\" or \"rev\" attributes (e.g.,
    > rel=\"next\", rel=\"previous\", rel=\"index\", etc.).

[^376]: For a complete list of the standard values for the "rel" and
    "rev" attributes, see [§ 6.12 of the
    W3C](http://www.w3.org/TR/html4/types.html#h-6.12) *HTML 4.01
    Specification*.

[^377]: For example:

    > \<a href=\"another_filename.htm\" rel=\"next\"\>Next\</a\> ¦
    >
    > \<a href=\"filename.htm\" rel=\"prev\"\>Previous\</a\>

[^378]: For instance

    > \<a href=\"filename.htm\" rel=\"start\"\>Previous\</a\>

[^379]: Even though [§ 6.12 of the
    W3C](http://www.w3.org/TR/html4/types.html#h-6.12) *HTML 4.01
    Specification* includes a "start" value, it does not include an
    "end" value. An early draft document within W3C's Internet
    Engineering Task Force recommended that "end" (or "last") be valid
    values for "rel" and "rev". That proposal, however, was not adopted.
    (For the complete text of the proposal, including other suggested
    values for "rel" and "rev," see
    [[http://www.w3.org/MarkUp/draft-ietf-html-relrev-00.txt]{.underline}](http://www.w3.org/MarkUp/draft-ietf-html-relrev-00.txt).)

[^380]: Examples:

    > **Linking from the first document in the series:**
    >
    > \<a href=\"filename.htm\" rel=\"next\" rev=\"start\"\>Next\</a\>
    >
    > **Linking from the second document in the series:**
    >
    > \<a href=\"filename.htm\" rel=\"start\" rev=\"next\"
    > \>Previous\</a\> ¦
    >
    > \<a href=\"another_filename.htm\" rel=\"next\"
    > rev=\"prev\"\>Next\</a\>
    >
    > **Linking from any other document in the series:**
    >
    > \<a href=\"filename.htm\" rel=\"prev\" rev=\"next\"
    > \>Previous\</a\> ¦
    >
    > \<a href=\"another_filename.htm\" rel=\"next\"
    > rev=\"prev\"\>Next\</a\>

[^381]: Use the "a:active {color: \_\_\_\_\_\_\_}" style sheets
    property.

[^382]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 7.5.1 of the
    W3C](http://www.w3.org/TR/html4/struct/global.html#h-7.5.1) *HTML
    4.01 Specification* designates the "alink," "link," and "vlink"
    attributes of the \<body\> tag as a deprecated attribute).

    To set the color of an active link, use the "a:active {color:}"
    style sheet property. To set the color of unvisited links, use the
    "a:link {color:}" style sheet property. To set the color of visited
    links, use the "a:visited {color:}" style sheet property. There are
    important usability issues that come into play when setting the
    colors of links -- see e.g., Jakob Nielsen's "[Guidelines for
    Visualizing Links](http://www.useit.com/alertbox/20040510.html)"
    (May 10, 2004) for recommendations on specifying colors for visited
    and unvisited links. Also consider [checkpoint 13.4 \[priority 2\]
    of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0*, which provides that
    accessible websites should "\[u\]se navigation mechanisms in a
    consistent manner."

[^383]: [Checkpoint 13.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "\[u\]se navigation mechanisms in a
    consistent manner."

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 61) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site:** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. ***Sen. John Cornyn***'s Web site is a
    > model of clearly and consistently organized information. The menu
    > headers and options are clear, and they stay the same throughout
    > the site.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^384]: Jakob Nielsen's "[Change the Color of Visited
    Links](http://www.useit.com/alertbox/20040503.html)" (May 3, 2004)
    notes that:

    > Generally, Web browsers are severely deficient in supporting user
    > navigation. However, they do provide one feature that helps users
    > orient themselves: browsers let designers display links in
    > different colors, depending on whether the links lead to new pages
    > or pages that users have seen before. Changing the color of
    > visited links has been part of Web browsing since Mosaic arrived
    > in 1993, so it\'s completely standard; almost all users understand
    > it.
    >
    > Currently, **74% of websites** use different colors for visited
    > and unvisited links, making this design approach a strong
    > convention that people have come to expect.
    >
    > Hypertext **theory**, the Web\'s **history**, and current design
    > **conventions** all indicate the need to change the color of
    > visited links. Further, **empirical observations** from user
    > testing have identified several severe usability problems on sites
    > that violate this convention. When sites use the same color for
    > visited and unvisited links, users:

    unintentionally revisit the same pages repeatedly;

    get lost more easily because their understanding of each link\'s
    meaning is reduced;

    often misinterpret or overlook the difference between two similar
    links if they're unsure about which one they\'ve already visited;
    and

    give up faster because they have a reduced sense of mastery when the
    site fails to reflect their actions and thus help them navigate.

[^385]: In *Prioritizing Web Usability*, 2006 (page 97 Jakob Nielsen and
    Hoa Loranger note that "Whenever you find yourself having to give
    instructions for where users can click, you know you have a
    usability problem."

[^386]: *Prioritizing Web Usability*, by Jakob Nielsen and Hoa Loranger,
    2006 (p. 65) notes that "the bigger something is, the less time it
    takes to click on it. This is because users won't need to point as
    precisely, which takes more time."

[^387]: [Section 12.2.3 of the
    W3C](http://www.w3.org/TR/html401/struct/links.html#anchors-with-id)
    *HTML 4.01 Specification* provides that (with respect to \<a\> tags)
    "The
    [[id]{.underline}](http://www.w3.org/TR/html401/struct/global.html#adef-id)
    and
    [[name]{.underline}](http://www.w3.org/TR/html401/struct/links.html#adef-name-A)
    attributes share the same name space. . . . When both attributes are
    used on a single element, their values must be identical."
    [Checkpoint 3.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-grammar)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "validate to published formal grammars."

    [Checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* further provides that
    accessible websites should "\[a\]void deprecated features of W3C
    technologies." ([Section 4.10 of the
    W3C](http://www.w3.org/TR/xhtml1/#h-4.10) *XHTML 1.0 (2^nd^ edition)
    Specification* designates the "name" attribute of the \<a\> tag as a
    deprecated attribute).

[^388]: Section 1 of the W3C [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure) provides
    that:

    > When designing a document or series of documents, content
    > developers should strive first to identify the desired structure
    > for their documents before thinking about how the documents will
    > be presented to the user. Distinguishing the structure of a
    > document from how the content is presented offers a number of
    > advantages, including improved accessibility, manageability, and
    > portability.

    Jeffrey Zeldman's, *Designing With Web Standards* (2^nd^ edition,
    \[2006\]), p.180, recommends that

    > Semantic or meta-structural names (names that explain the function
    > performed by elements contained within) are best. You would feel
    > pretty silly having labeled a part of your site "orangebox" when
    > the client decides to go with blue. You would feel sillier still
    > revising your style sheets under a deadline six months from now
    > and trying desperately to remember whether "Gladys" was a
    > navigational area, a sidebar, a search form, or what.

[^389]: The primary language of a page is the language specified by the
    "lang" and "xml:lang" attributes of the \<html\> tag.

[^390]: The value of the "hreflang" attribute should conform to the [RFC
    4646](http://www.rfc-editor.org/rfc/rfc4646.txt) standard.
    Instructions for using that standard are set out in Appendix 5:
    *Language Identification Codes* of this document.

[^391]: [Checkpoint 4.1 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-changes)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "Clearly identify changes in the natural language of
    a document\'s text and any text equivalents (e.g., captions)."

[^392]: [Appendix B of](http://www.w3.org/TR/xhtml1/#prohibitions) the
    W3C *XHTML 1.0 (2^nd^ edition) Specification* provides that "a must
    not contain other a elements".

[^393]: Jeffrey Zeldman's, *Designing With Web Standards* (2^nd^
    edition, \[2006\]), p.232, notes when the style sheets list-style
    property is used to designate a substitute for the default bullet in
    an unordered list and both the list-style-type and the
    list-style-image values are provided in the list-style property:

    > IE/Windows and Opera/Windows users get an extra (unintended)
    > treat. The site displays the \[list-style-type designated
    > characters\] . . . first and then fills in the . . . images. The
    > effect looks like Flash or JavaScript animation, but is purely
    > accidental and a result of the order in which IE and Opera for
    > Windows load and display web page components. In other browsers,
    > users simply see the . . . \[graphic\].

[^394]: [Checkpoint 3.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-use-markup) *Web
    Content Accessibility Guidelines 1.0* provides that "\[w\]hen an
    appropriate markup language exists, use markup rather than images to
    convey information." [Checkpoint 3.6 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-list-structure) *Web
    Content Accessibility Guidelines 1.0* further provides that an
    accessible website should "\[m\]ark up lists and list items
    properly."

[^395]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 10.2 of the
    W3C](http://www.w3.org/TR/html4/struct/lists.html#h-10.2) *HTML 4.01
    Specification* designates the "type" attribute of the \<li\>,
    \<ol\>, and \<ul\> tags as deprecated attributes).

[^396]: Jakob Nielsen's article "[F-Shaped Pattern For Reading Web
    Content](http://www.useit.com/alertbox/reading_pattern.html)" (April
    17, 2006), based on a study of the eye movements of 232 website
    users, recommends that Web designers

    > **Start subheads, paragraphs, and bullet points with
    > information-carrying words** that users will notice when scanning
    > down the left side of your content . . . . They\'ll read the third
    > word on a line much less often than the first two words.

    Though Nielsen's study was based on sighted users, the technique he
    suggests is useful not only for sighted individuals, but also for
    blind individuals -- since an often-used technique in Jaws and
    Window-Eyes is to have the browser skip from heading to heading or
    from list to list.

[^397]: The Congressional Management Foundation's 1999 report *Building
    Web Sites Constituents Will Use* (page 9) recommends that
    Congressional websites "**Place external and internal links
    throughout your site, rather than on a single "Links" page.** This
    ensures that visitors can instantly access the information they
    want, rather than searching for it among a long list of links."

[^398]: [*Research-Based Web Design & Usability
    Guidelines*](http://www.usability.gov/pdfs/chapter2.pdf#page=2),
    2^nd^ edition, page 10, (compiled by the U.S. Department of Health
    and Human Services), identifies arranging a website "in a logical
    way" as one of the elements that project credibility in a website.

[^399]: [Checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 10.4 of the
    W3C](http://www.w3.org/TR/html4/struct/lists.html#edef-DIR) *HTML
    4.01 Specification* designates the \<dir\> tag and the \<menu\> tag
    as deprecated elements).

[^400]: [Checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 10.2 of the
    W3C](http://www.w3.org/TR/html4/struct/lists.html#adef-compact)
    *HTML 4.01 Specification* designates the "compact" attribute as a
    deprecated attribute).

    The W3C [*CSS 2
    Specification*](http://www.w3.org/TR/CSS2/visuren.html#compact), §
    9.2.3, provided a style sheet display:compact element. The [*CSS 2.1
    Specification*](http://www.w3.org/TR/CSS21/changes.html#q12), §
    C.2.5, however, notes that display:compact has been dropped from the
    CSS specification.

[^401]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 10.2 of the
    W3C](http://www.w3.org/TR/html4/struct/lists.html#h-10.2) *HTML 4.01
    Specification* designates the "start" and "value" attributes as
    deprecated attributes).

[^402]: A WSB analysis of www.house.gov usage for July 9 to 15, 2008,
    indicates that Internet Explorer 6 accounted for 30.30% of the
    identifiable, non-robot access to the site.

[^403]: For more information on the HIR Listserv service, see HouseNet →
    Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance) → Tools
    → Listserv.

[^404]: The standard set out in [§ 1303(b)(1)(C) of the Children's
    Online Privacy Protection Act of
    1998](http://uscode.house.gov/quicksearch/get.plx?title=15&section=6502)
    (COPPA) prohibits conditioning participation in an activity though a
    website on "disclosing more personal information than is reasonably
    necessary to participate in such activity".

    Just as in the case of § 508 of the Rehabilitation Act,
    Congressional offices are not statutorily required to abide by the
    requirements of COPPA. Just as with § 508, however, Congressional
    offices that do not abide by COPPA's standards risk being
    embarrassed if their non-compliance is publicized.

[^405]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=77)
    (page 67) recommends that Congressional offices

    > Establish a policy concerning your e-mail updates *before*
    > visitors sign-up, and stick to it. Create clear expectations
    > regarding what information citizens will receive and when they
    > will receive it. A weekly legislative update or a monthly e-mail
    > update on health care should be exactly that. An agreed-upon
    > policy will also establish clear guidelines for office staff
    > responsible for the newsletter's content and distribution.

[^406]: This is based on August 2007 verbal guidance from the staff of
    the House Franking Commission. (Identical guidance was presented by
    House Franking Commission staff at their January 7, 2008, briefing
    on franking reform to the House System Administrators Association.)

[^407]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=74)
    (pages 62) praises Rep. [Tom Allen](http://tomallen.house.gov/)'s
    website for providing "driving directions and links to maps of the
    offices in the district and in Washington."

    [Yahoo](http://help.yahoo.com/l/us/yahoo/maps/directions/maps-08.html),
    [MapQuest](http://www.mapquest.com/features/main.adp?page=lf_main),
    [Rand McNally](http://www.randmcnally.com/), and
    [Google](http://maps.google.com/support/bin/answer.py?answer=68475)
    provide the ability to automatically generate such a set of
    directions from any user-specified address in the United States.

[^408]: Congressional district maps are available from the U.S.
    Geological Survey at
    <http://www.nationalatlas.gov/printable/congress.html#list>.
    Congressional district maps are also available from the U.S. Bureau
    of the Census at
    <http://www.census.gov/geo/www/maps/cd109/cd109_individualMaps.htm>..

[^409]: Client-side image maps should be used for this function where
    possible, instead of server-side image maps. (The regulations under
    § 508 of the Rehabilitation Act of 1973 ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(f))
    provide that "Client-side image maps shall be provided instead of
    server-side image maps except where the regions cannot be defined
    with an available geometric shape." Likewise, [Checkpoint 9.1
    \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-client-side-maps)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "Provide client-side image maps instead of
    server-side image maps except where the regions cannot be defined
    with an available geometric shape.")

    Just as with external links created by \<a href\> tags, external
    links created by using image maps require exit messages to be in
    compliance with the [*Members' Congressional
    Handbook*](http://cha.house.gov/official_and_representational_expenses_continued.aspx#WebSites)
    (Web Sites, § 5), issued by the House Administration Committee,
    provides that:

    > HIR will display an exit notice stating that users are leaving the
    > House of Representatives prior to linking to a non-House of
    > Representatives Web site. The exit notice will include a
    > disclaimer that neither Members nor the House are responsible for
    > the content of linked sites. Member offices maintaining their
    > sites on the Public web server are required to incorporate the
    > exit notice into their external links.

    Instructions for implementing the exit message can be found at
    HouseNet → Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance/) → HTML
    → Exit Message to External Web Sites.

[^410]: See, e.g., [Rep. Jesse Jackson, Jr.'s district
    page](http://www.house.gov/jackson/District.shtml).

[^411]: See, e.g., [Rep. Dan Boren's "Second Congressional District of
    Oklahoma" page](http://www.house.gov/boren/district.shtml), [Rep.
    Bud Cramer's "5^th^ District of Alabama"
    page](http://cramer.house.gov/HoR/AL05/5th+District.htm?SecLnk=5thDistrict),
    [Rep. Jeff Fortenberry's "Nebraska's First Congressional District"
    page](http://fortenberry.house.gov/ne01.shtml), and [Rep. Adam
    Schiff's "California's 20^th^ Congressional District"
    page](http://schiff.house.gov/HoR/CA29/The+29th+District/).

    The Congressional Management Foundation's [*Congress Online 2003:
    Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=29)
    (page 21) praises Sen. Tom Carper's website for having a "map of
    Delaware \[that\] breaks down *local news* and *resources by
    county*, which gives constituents easy access to information
    relevant to where they live". [Sen. Harry Reid's
    homepage](http://reid.senate.gov/) has a map that links to the
    Senator's accomplishments, broken down by county.

[^412]: Use of proprietary attributes that are not W3C XHTML compliant
    also makes a Web page non-compliant with [Checkpoint 11.1 \[priority
    2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-latest-w3c-specs)
    *Web Content Accessibility Guidelines 1.0* which provides that
    accessible websites should "\[u\]se W3C technologies when they are
    available and appropriate for a task and use the latest versions
    when supported."

[^413]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation."

[^414]: [Section 8.3 of the
    W3C](http://www.w3.org/TR/CSS21/box.html#margin-properties)
    *Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification*
    provides that:

    > The
    > [[\'margin\']{.underline}](http://www.w3.org/TR/CSS21/box.html#propdef-margin)
    > property is a shorthand property for setting
    > [[\'margin-top\']{.underline}](http://www.w3.org/TR/CSS21/box.html#propdef-margin-top),
    > [[\'margin-right\']{.underline}](http://www.w3.org/TR/CSS21/box.html#propdef-margin-right),
    > [[\'margin-bottom\']{.underline}](http://www.w3.org/TR/CSS21/box.html#propdef-margin-bottom),
    > and
    > [[\'margin-left\']{.underline}](http://www.w3.org/TR/CSS21/box.html#propdef-margin-left)
    > at the same place in the style sheet.
    >
    > If there is only one value, it applies to all sides. If there are
    > two values, the top and bottom margins are set to the first value
    > and the right and left margins are set to the second. If there are
    > three values, the top is set to the first value, the left and
    > right are set to the second, and the bottom is set to the third.
    > If there are four values, they apply to the top, right, bottom,
    > and left, respectively.

[^415]: [Section 8.4 of the
    W3C](http://www.w3.org/TR/CSS21/box.html#padding-properties)
    *Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification*
    provides that:

    > The
    > [[\'padding\']{.underline}](http://www.w3.org/TR/CSS21/box.html#propdef-padding)
    > property is a shorthand property for setting
    > [[\'padding-top\']{.underline}](http://www.w3.org/TR/CSS21/box.html#propdef-padding-top),
    > [[\'padding-right\']{.underline}](http://www.w3.org/TR/CSS21/box.html#propdef-padding-right),
    > [[\'padding-bottom\']{.underline}](http://www.w3.org/TR/CSS21/box.html#propdef-padding-bottom),
    > and
    > [[\'padding-left\']{.underline}](http://www.w3.org/TR/CSS21/box.html#propdef-padding-left)
    > at the same place in the style sheet.
    >
    > If there is only one value, it applies to all sides. If there are
    > two values, the top and bottom paddings are set to the first value
    > and the right and left paddings are set to the second. If there
    > are three values, the top is set to the first value, the left and
    > right are set to the second, and the bottom is set to the third.
    > If there are four values, they apply to the top, right, bottom,
    > and left, respectively.

[^416]: [Checkpoint 13.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-use-metadata) *Web
    Content Accessibility Guidelines 1.0* provides that an accessible
    website should "Provide metadata to add semantic information to
    pages and sites."

[^417]: [Section 4.6 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.6)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that "Empty
    elements must either have an end tag or the start tag must end with
    /\>. For instance, \<br/\> or \<hr\>\</hr\>." [Checkpoint 11.1
    \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^418]: The [Congressional Management
    Foundation's](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=54)
    *Congress Online 2003: Turning the Corner on the Information Age*
    (p. 46) notes that "Committees and leadership offices with natural
    constituencies can also provide service information online. The
    *House Committee on Veterans' Affairs* website provides information
    on veterans' benefits for its key audience."

[^419]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=66)
    (page 56) praises the website of Rep. Thelma Drake for focusing on
    the needs of those in military service.

[^420]: Use the link

    > \<a
    > href=\"http://www.house.gov/htbin/leave_site?ln_url=\"http://www.missingkids.com/precreate/**SS**.html\"&ln_desc=National+Center+for+Missing+and+Exploited+Children\"\>

    Replace "**SS**" with the capitalized 2-character postal
    abbreviation for the state.

[^421]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=27)
    (page 17) indicates that providing video clips is one of the
    elements of a well-formed congressional website. At the time the
    report was compiled, only 35.6% of all House Member, committee, and
    leadership websites included this material.

    The Congressional Management Foundation's [*Congress Online 2003:
    Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=40),
    (page
    32[)](http://www.congressonlineproject.org/congressonline2003.pdf#page=56)
    praises Rep. Mike Pence for giving "short daily speeches on the
    House floor, which his office then provides on his Web site using
    low-cost, low-tech equipment. These regular audio and video updates
    show his constituents how hard he works on a daily basis."

[^422]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(m))
    provide that "When a web page requires that an applet, plug-in or
    other application be present on the client system to interpret page
    content, the page must provide a link to a plug-in or applet that
    complies with [§
    1194.21](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Software)(a)
    through (*l*)."

[^423]: Examples can be found on the Chief Administrative Officer's
    "[Site Tools and Downloads](http://cao.house.gov/sitetools.shtml)"
    page, [Rep. John Salazar's audio clips
    page](http://www.house.gov/salazar/press-audio.shtml), and [Rep.
    Heather Wilson's toolbox
    page](http://wilson.house.gov/Toolbox.aspx). Each of the pages on
    the 109^th^ Congress Speaker's website (except the homepage) have
    (on the left side) a toolbox image and "Important tools to visit
    this site" linked to a [page with links to
    plug-ins](http://web.archive.org/web/20060114204845/http:/www.speaker.gov/features/multimedia.asp).

[^424]: The [*Members' Congressional
    Handbook*](http://cha.house.gov/official_and_representational_expenses_continued.aspx#WebSites)
    (Web Sites, § 5), issued by the House Administration Committee,
    provides that:

    > HIR will display an exit notice stating that users are leaving the
    > House of Representatives prior to linking to a non-House of
    > Representatives Web site. The exit notice will include a
    > disclaimer that neither Members nor the House are responsible for
    > the content of linked sites. Member offices maintaining their
    > sites on the Public web server are required to incorporate the
    > exit notice into their external links.

    Instructions for implementing the exit message can be found at
    HouseNet → Technology → [Web
    Solutions](../housenet.house.gov/keywords/webassistance) → HTML →
    Exit Message to External Web Sites.

[^425]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(a))
    provide that "A text equivalent for every non-text element shall be
    provided (e.g., via \"alt\", \"longdesc\", or in element content)."

    [Checkpoint 1.1 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-text-equivalent) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should:

    > Provide a text equivalent for every non-text element (e.g., via
    > \"alt\", \"longdesc\", or in element content). *This includes*: .
    > . . sounds (played with or without user interaction), stand-alone
    > audio files, audio tracks of video, and video. \[Priority 1\]

[^426]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(b))
    provide that "Equivalent alternatives for any multimedia
    presentation shall be synchronized with the presentation."
    [Checkpoint 1.4 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-synchronize-equivalents)
    *Web Content Accessibility Guidelines 1.0* similarly provides that
    "\[f\]or 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."

[^427]: [Checkpoint 1.3 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-auditory-descriptions)
    *Web Content Accessibility Guidelines 1.0* provides that:

    > [Until user
    > agents](http://www.w3.org/TR/WAI-WEBCONTENT/wai-pageauth.html#until-user-agents)
    > 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.

[^428]: The late Rep. Charlie Norwood's website included the following
    instructions:

    > Pressing the \"PLAY\" button or clicking on the image above will
    > start the video. After the video has started you may start , stop,
    > or pause the video at any time.

[^429]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=74)
    (p. 64) counsels: "Stay away from auto-loading audio or video
    content---like a welcome video---on your home page."

[^430]: [Checkpoint 10.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-pop-ups) *Web
    Content Accessibility Guidelines 1.0* provides that "[*[\[u\]ntil
    user
    agents]{.underline}*](http://www.w3.org/TR/WCAG10/wai-pageauth.html#until-user-agents)
    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."

[^431]: [Checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 4.10 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.10)
    *XHTML 1.0 (2^nd^ edition) Specification* designates the "name"
    attribute of the \<a\>, \<applet\>, \<form\>, \<frame\>, \<iframe\>,
    \<img\>, and \<map\> tags as deprecated attributes).

[^432]: [Section 4.10 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.10)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that "HTML 4
    defined the name attribute for the elements a, applet, form, frame,
    iframe, img, and map. HTML 4 also introduced the id attribute. Both
    of these attributes are designed to be used as fragment identifiers.
    . . . XHTML 1.0 documents MUST use the id attribute when defining
    fragment identifiers on the elements listed above.

    [Section 12.2.3 of the
    W3C](http://www.w3.org/TR/html401/struct/links.html#anchors-with-id)
    *HTML 4.01 Specification* provides that (with \<a\> tags) the
    "[[id]{.underline}](http://www.w3.org/TR/html401/struct/global.html#adef-id)
    and
    [[name]{.underline}](http://www.w3.org/TR/html401/struct/links.html#adef-name-A)
    attributes share the same name space. . . . When both attributes are
    used on a single element, their values must be identical."

    [Checkpoint 3.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-grammar)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "validate to published formal grammars."

[^433]: Section 1 of the W3C [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure) provides
    that:

    > When designing a document or series of documents, content
    > developers should strive first to identify the desired structure
    > for their documents before thinking about how the documents will
    > be presented to the user. Distinguishing the structure of a
    > document from how the content is presented offers a number of
    > advantages, including improved accessibility, manageability, and
    > portability.

    Jeffrey Zeldman's, *Designing With Web Standards* (2^nd^ edition,
    \[2006\]), p.180, recommends that

    > Semantic or meta-structural names (names that explain the function
    > performed by elements contained within) are best. You would feel
    > pretty silly having labeled a part of your site "orangebox" when
    > the client decides to go with blue. You would feel sillier still
    > revising your style sheets under a deadline six months from now
    > and trying desperately to remember whether "Gladys" was a
    > navigational area, a sidebar, a search form, or what.

[^434]: See also, the website of [Rep. Vic
    Snyder](http://www.house.gov/snyder/).

[^435]: Rep. Steve Scalise's website targets residents of his district,
    news media, veterans, students, parents, and people who want
    information about his district.

[^436]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=65)
    (page 54) notes that:

    > The fundamental rule for the success of any communications effort,
    > including an effective Web site, is to know your audience.
    > Therefore, audience is the first building block. If you know and
    > clearly define your audience, it will be much easier to select the
    > content, the format, and the kinds of interactive and innovative
    > features to provide for your users. Every building block that
    > follows will be shaped by the users of your site.

    The report (on pages 54 to 55) identifies two overarching audiences
    -- newcomers and experts and then suggests the following as typical
    audiences:

    **Member offices:** constituents; reporters; activists; students and
    educators; and lobbyists.

    **Committee offices:** congressional staff; majority/minority staff;
    activists; lobbyists; and other professionals.

    **Leadership offices:** general public; reporters; party supporters
    on and off the Hill; congressional staff; and lobbyists and
    advocates.

    The report (on [page
    56](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=66))
    also praises [Rep. Thelma Drake](http://drake.house.gov/)'s site for
    focusing on the needs of those in military service.

[^437]: Steve Krug, in *Don't Make Me Think* (2^nd^ ed., 2006), page 66,
    notes that:

    > There's an emerging convention that the Site ID \[-- the site
    > owner's branding in the site banner--\] doubles as a button that
    > can take you to the site's Home page. It's a useful idea that
    > every site should implement, but a surprising number of users
    > still aren't aware of it.

    [*Research-Based Web Design & Usability
    Guidelines*](http://www.usability.gov/pdfs/chapter5.pdf#page=2),
    2^nd^ edition, page 35, (compiled by the U.S. Department of Health
    and Human Services), notes that:

    > Many sites place the organization's logo on the top of every page
    > and link it to the homepage. While many users expect that a logo
    > will be clickable, many other users will not realize that it is a
    > link to the homepage. Therefore, include a link labeled 'Home'
    > near the top of the page to help those users.

[^438]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(*o*))
    provide that for a website to be accessible, "\[a\] method shall be
    provided that permits users to skip repetitive navigation links."
    [Checkpoint 13.6 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-group-links) *Web
    Content Accessibility Guidelines 1.0* similarly provides that
    accessible websites need to "\[g\]roup related links, identify the
    group (for user agents), and, [*[until user
    agents]{.underline}*](http://www.w3.org/TR/WAI-WEBCONTENT/wai-pageauth.html#until-user-agents)
    do so, provide a way to bypass the group."

[^439]: For alternative approaches, see:

    "['](http://www.webaim.org/techniques/skipnav/#creating)Skip
    Navigation' Links," WebAIM, Center for Persons with Disabilities,
    Utah State University

    "[Skip Navigation Links](http://www.jimthatcher.com/skipnav.htm),"
    by Jim Thacher

[^440]: For an example, see [Rep. Altmire's](http://altmire.house.gov/)
    website.

[^441]: Another alternative is "My Work in Congress" -- see [Rep. Frank
    Pallone's website](http://www.house.gov/pallone/mywork.shtml).

[^442]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=57)
    (page 45) notes that "'Casework' is Hill jargon. Constituents will
    better understand what the office can do if the Web site employs
    phrases such as 'Help with a problem you are having with a Federal
    Agency,' 'What this office can do for you,' or 'Assistance with a
    government problem,' rather than using the term 'casework.'"

    [Rep. Jesse Jackson,
    Jr.](http://www.house.gov/jackson/ConstituentServices.shtml) uses
    "How I Can Help You". [Rep. Ben Chadler](http://chandler.house.gov/)
    uses "How Can We Help You?" and "Assistance with Federal Agencies".
    [Rep. Spencer Bachus](http://bachus.house.gov/hor/al06/) uses
    "Helping You" and "Help with Federal Agencies". [Rep. Frank
    Pallone](http://www.house.gov/pallone/index.shtml) uses "How Can I
    Help".

[^443]: [Checkpoint 14.2 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-icons) *Web Content
    Accessibility Guidelines 1.0* provides that accessible websites
    should "\[s\]upplement text with graphic or auditory presentations
    where they will facilitate comprehension of the page."

[^444]: [Checkpoint 10.5 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-divide-links) *Web
    Content Accessibility Guidelines 1.0* provides that "\[u\]ntil user
    agents (including assistive technologies) render adjacent links
    distinctly, include non-link, printable characters (surrounded by
    spaces) between adjacent links." A vertical broken pipe ("**¦**" -
    &#166;) is often used as a divider between such links.

[^445]: It is especially important that this suggestion be implemented
    on any page (including splash pages) where the only navigational
    links are through \<input\> tags or by use of scripts. Having all
    navigation links only through \<input\> tags or through scripts can
    create problems for users of assistive technologies and for search
    engine indexing spiders.

[^446]: [Checkpoint 13.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-site-description)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "\[p\]rovide information about the general
    layout of a site (e.g., a site map or table of contents)."

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (pages 40 and 95) identifies providing a site map as an element of a
    successful Congressional website. The report ([pages 64 to
    79](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=76))
    singles out the site maps on the websites of Reps. [Patrick
    Murphy](http://www.patrickmurphy.house.gov/index.php?option=com_content&task=view&id=54),
    [Adam
    Schiff](http://schiff.house.gov/HoR/CA29/Hidden+Content/Site+Map.htm),
    [Hilda Solis](http://solis.house.gov/contact/sitemap.shtml), the
    [Science and Technology
    Committee](http://science.house.gov/resources/sitemap.shtml), the
    [House Republican Conference](http://www.gop.gov/web/guest/sitemap),
    and [Sen. John
    Cornyn](http://cornyn.senate.gov/public/index.cfm?FuseAction=Home.SiteMap).

    Kim Siever's "[Spruced-Up Site
    Maps](http://alistapart.com/articles/sprucemaps)", A List Apart
    (March 30, 2005) suggests a non-boring layout for site maps.

[^447]: *Prioritizing Web Usability*, by Jakob Nielsen and Hoa Loranger,
    2006 (p. 27) recommends that each page on a website include a
    "\[d\]irect, one-click link to the homepage". [*Research-Based Web
    Design & Usability
    Guidelines*](http://www.usability.gov/pdfs/chapter5.pdf#page=2),
    2^nd^ edition, page 35, (compiled by the U.S. Department of Health
    and Human Services), recommends that web pages "include a link
    labeled 'Home' near the top of the page".

[^448]: [Checkpoint 13.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "\[u\]se navigation mechanisms in a
    consistent manner."

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site.** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. ***Sen. John Cornyn***'s Web site is a
    > model of clearly and consistently organized information. The menu
    > headers and options are clear, and they stay the same throughout
    > the site.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40), in its discussion of what are the elements of a
    successful Congressional website also notes that:

    > Consistency and clarity are key; they are the most important
    > contributions to an easily navigable site. Many users come into
    > the site in ways other than through the homepage, so consistent
    > tools will also broaden those users' experience and show them what
    > else your site has to offer.

    The report also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities". The
    report ([pages 62 to
    78](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=74))
    praises the consistent navigation on the websites of Reps. [Tom
    Allen](http://tomallen.house.gov/), [Brad
    Ellsworth](http://www.ellsworth.house.gov/), [Patrick
    Murphy](http://www.patrickmurphy.house.gov/), [Adam
    Schiff](http://schiff.house.gov/), and [Hilda
    Solis](http://solis.house.gov/), the [House Ways and Means
    Committee](http://waysandmeans.house.gov/).

[^449]: [Checkpoint 6.3 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-scripts) *Web Content
    Accessibility Guidelines 1.0* provides that an accessible website
    should:

    > 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. . . .
    >
    > For example, ensure that links that trigger scripts work when
    > scripts are turned off or not supported (e.g., do not use
    > \"javascript:\" as the link target). If it is not possible to make
    > the page usable without scripts, provide a text equivalent with
    > the NOSCRIPT element, or use a server-side script instead of a
    > client-side script, or provide an alternative accessible page as
    > per [checkpoint
    > 11.4](http://www.w3.org/TR/WCAG10/#tech-alt-pages%23tech-alt-pages).
    > [Refer also to guideline
    > 1](http://www.w3.org/TR/WCAG10/#gl-provide-equivalents%23gl-provide-equivalents).

[^450]: See, e.g., the "[Hot
    Issues](http://www.house.gov/baca/hotissues/issues.htm)" portion of
    Rep. Joe Baca's website.

    *Prioritizing Web Usability*, by Jakob Nielsen and Hoa Loranger,
    2006 (p. 27) recommends including "links to . . . resources that are
    directly relevant to the current location, but don't flood the user
    with links to all site areas or to unrelated pages."

[^451]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=61)
    (page 53) recommends that Congressional websites should:

    > **Follow the "three click rule."** To the degree possible, the
    > information architecture of your site should allow visitors to get
    > from any one page on your site to any other page in three clicks.
    > This is especially important for frequently accessed sections and
    > information, and less important for supporting information and
    > document archives.

[^452]: *Prioritizing Web Usability*, by Jakob Nielsen and Hoa Loranger,
    2006 (p. 202) notes that:

    > Vertical dropdown menus have become a widely used navigational
    > tool, mainly because they save space on screens with limited real
    > estate. Over the years, users have learned to adopt to them. While
    > dropdown menus have their advantages, they can also be
    > problematic, especially if they are long. The longer the menu
    > list, the more difficult it is to control. The further users must
    > travel down the list, . . . \[the\] more likely they are to lose
    > their place.
    >
    > It's often better to present long lists of standard hypertext
    > format, where there's more room for descriptions that help people
    > differentiate between the choices.

[^453]: For an attempt at using the \<object\> tag so that works well
    across browsers, see Elizabeth Castro's "[Bye Bye
    Embed](http://alistapart.com/articles/byebyeembed), " A List Apart
    (July 11, 2006).

[^454]: Use the "border-width" style sheets property.

[^455]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 13.7.3 of the
    W3C](http://www.w3.org/TR/html4/struct/objects.html#h-13.7.3) *HTML
    4.01 Specification* designates the "border" attribute of the
    \<object\> tag as a deprecated attribute).

[^456]: The "padding-left," "padding-right," "padding-bottom," and
    "padding-top" style sheets properties provide the functionality
    previously provided by the "hspace" and "vspace" attributes.

    [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 13.7.2 of the
    W3C](http://www.w3.org/TR/html4/struct/objects.html#h-13.7.2) *HTML
    4.01 Specification* designates the "hspace" and "vspace" attributes
    as deprecated attributes).

[^457]: Other "type" attribute values for the \<object\> tag include:

    **Extension"type" attribute
    value**.asfvideo/x-ms-asf.asxvideo/x-ms-asf.nscvideo/x-ms-asf.splapplication/futuresplash.swfapplication/x-shockwave-flash.waxaudio/x-ms-wax.wmvideo/x-ms-wm.wmaaudio/x-ms-wma.wmdapplication/x-ms-wmd.wmxvideo/x-ms-wmx.wmzapplication/x-mx-wmz.wvxvideo/x-ms-wvx

[^458]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=80)
    (page 68) praises the website of [Rep. Virginia
    Foxx](http://foxx.house.gov/?sectionid=15&sectiontree=8,15#Foxx Page)
    for providing "substantive

    information on how to apply for . . . the congressional page
    program"

    Other examples of Congressional sites with information on the Page
    Program include the websites of [Rep. Jason
    Altmire](http://altmire.house.gov/pageProgram.shtml), [Rep. Peter
    DeFazio](http://defazio.house.gov/PageInfo.shtml), [Rep. Mark
    Foley](http://www.house.gov/foley/services/page.htm), [Rep. Mark
    Green](http://www.house.gov/markgreen/congresspage.htm), [Rep. Jeb
    Hensarling](http://www.house.gov/hensarling/services/pageprogram.html),
    [Rep. Mike Honda](http://www.honda.house.gov/pagenominations.shtml),
    [Rep. John
    Linder](http://linder.house.gov/index.cfm?FuseAction=ConstituentServices.Page),
    [Rep. Frank LoBiondo](http://www.house.gov/lobiondo/pages.shtml),
    [Rep. John
    Peterson](http://www.house.gov/johnpeterson/pageprogram.html), [Rep.
    Tom Petri](http://www.house.gov/petri/pageprog.htm), [Rep. Ted
    Poe](http://www.house.gov/poe/pageinfo.htm), [Rep. Bill
    Shuster](http://www.house.gov/shuster/congpage.htm), [Rep. Michael
    Turner](http://www.house.gov/apps/list/hearing/oh03_turner/col_040319_page.html),
    and [Rep. Diane
    Watson](http://www.house.gov/watson/new/page_program.shtml).

[^459]: <http://pageprogram.house.gov/>

[^460]: [Section 4.6 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.6)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that "Empty
    elements must either have an end tag or the start tag must end with
    /\>. For instance, \<br/\> or \<hr\>\</hr\>." [Checkpoint 11.1
    \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^461]: The [Congressional Management
    Foundation's](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=54)
    *Congress Online 2003: Turning the Corner on the Information Age*
    (p. 46) notes that "Committees and leadership offices with natural
    constituencies can also provide service information online. The
    *House Committee on Veterans' Affairs* website provides information
    on veterans' benefits for its key audience."

[^462]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=49)
    (page 39) notes that "One of the keys to a successful Web site is
    building it around specifically targeted audiences" and praises the
    "[For \> Parents](http://www.moore.house.gov/group.asp?group_id=7)"
    page on Rep. Dennis Moore's website.

[^463]:
    ###  For instance, [**http://www.adobe.com/products/acrobat/readstep2.html**](http://www.adobe.com/products/acrobat/readstep2.html).

    The regulations under § 508 of the Rehabilitation Act of 1973 ([36
    C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(m))
    provide that "When a web page requires that an applet, plug-in or
    other application be present on the client system to interpret page
    content, the page must provide a link to a plug-in or applet that
    complies with [§
    1194.21](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Software)(a)
    through (*l*)."

[^464]: The [*Members' Congressional
    Handbook*](http://cha.house.gov/official_and_representational_expenses_continued.aspx#WebSites)
    (Web Sites, § 5), issued by the House Administration Committee,
    provides that:

    > HIR will display an exit notice stating that users are leaving the
    > House of Representatives prior to linking to a non-House of
    > Representatives Web site. The exit notice will include a
    > disclaimer that neither Members nor the House are responsible for
    > the content of linked sites. Member offices maintaining their
    > sites on the Public web server are required to incorporate the
    > exit notice into their external links.

    Instructions for implementing the exit message can be found at
    HouseNet → Technology → [Web
    Solutions](../housenet.house.gov/keywords/webassistance) → HTML →
    Exit Message to External Web Sites.

[^465]: Tooltips for input fields in a PDF perform the same function for
    PDF files as "title" attributes in \<input\>, \<select\>, or
    \<textarea\> tags perform in HTML files. (Note: PDF does not have an
    equivalent to the HTML \<label\> tag.)

[^466]: [Checkpoint 12.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-associate-labels)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]ssociate labels explicitly with their
    controls."

    The regulations under § 508 of the Rehabilitation Act of 1973 ([36
    C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(n))
    provide that "When electronic forms are designed to be completed
    on-line, the form shall allow people using assistive technology to
    access the information, field elements, and functionality required
    for completion and submission of the form, including all directions
    and cues."

    The Social Security Administration's *Guide to Accessible PDF
    Documents and Forms* (April 2006), page 36, recommends that the
    tooltips for input fields on PDFs:

    Include only enough information in the tooltip for users to know
    what input is expected and how to complete the field correctly,

    Indicate form inputs which are required.

    Indicate if special keystrokes are required to perform a function.

    . . . should not state the input type or state \[e.g., that this is
    a checkbox\]; this information is passed programmatically to
    assistive technology.

[^467]: *Prioritizing Web Usability*, by Jakob Nielsen and Hoa Loranger,
    2006 (p. 36), notes that:

    > When we let users loose to go anywhere they wanted on the Web \[to
    > find the answers to research questions\], they went to a search
    > engine 88 percent of the time. Only in 12 percent of cases did
    > they go straight to a Web site that they hoped would help them
    > with their problem.

[^468]: As written, the [Ath Slide JavaScripted Photo
    Gallery](http://www1.house.gov:801/mmiller2/photoplay/Ath_Slide.shtml)
    does not work when scripting is turned off -- which is not compliant
    with regulation [36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(*l*)
    of § 508 of the Rehabilitation Act of 1973 ("When pages utilize
    scripting languages to display content, or to create interface
    elements, the information provided by the script shall be identified
    with functional text that can be read by assistive technology."), To
    make the coding compliant, add (after the \</script\> tag): a
    \<noscript\> tag, followed by an ordered (or unordered) list of the
    links and captions of the photos, followed by a \</noscript\> tag.
    For an example, see Rep. Bill Delahunt's "[Art Discovery
    Contest](http://www.house.gov/delahunt/artcomppictures.shtml)" page.

[^469]: The [Ath Slide JavaScripted Photo
    Gallery](http://www1.house.gov:801/mmiller2/photoplay/Ath_Slide.shtml)
    allows HTML coding to be included in the photograph captions. If
    using this feature, only use single quotation marks to include
    attribute values -- do not use double quotation marks. If you want
    to use quotation marks in the text of the caption, use the entity
    name, decimal representation, or hexadecimal representation instead
    of the actual character (e.g., use &#8220; for an open double
    quotation mark, or &#8221; for a double close quotation mark).

[^470]: [Checkpoint 9.5 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-keyboard-shortcuts)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    web sites should:

    > Provide keyboard shortcuts to important links (including those in
    > [*[client-side image
    > maps]{.underline}*](http://www.w3.org/TR/WAI-WEBCONTENT/wai-pageauth.html#image-map)),
    > form controls, and groups of form controls.

[^471]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=29)
    (pages 21 and 25) praises the "Highlighting Delawareans" page on
    Senator Tom Carper's website for "posting constituent photo
    galleries and congratulating constituents on their accomplishments";
    and the website of Representative Richard Pombo for having "An
    extensive gallery of constituent photos". See also the ["Photo
    Album" on Rep. Marsha Blackburn's
    website](http://www.house.gov/blackburn/photoalbum.shtml).

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=93)
    (page 83) identifies including "photos of constituents on the home
    page" as an element of a well-formed Congressional website.

[^472]: The [*Committee's Congressional
    Handbook*](http://cha.house.gov/committee_handbook.aspx#content)
    (Web Site Regulations, Content, § a). issued by the House
    Administration Committee, provides an identical restriction on House
    committee websites.

[^473]: Instructions for developing polls and surveys (using HIR
    form_proc) are available at
    <http://onlinecao/webassistance/html/ht_survey.htm>.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=77)
    (page 67) recommends that Congressional websites:

    > **Let constituents' voices be heard through online surveys and
    > polls:** Online surveys and polls offer quick and easy ways for
    > constituents to register their opinions. Constituents not only
    > feel engaged by the Member's office, but the inclusion of survey
    > questions can cut down on the amount of mail an office receives
    > because constituents understand that their views have been
    > registered. Of course, the more timely the survey questions, the
    > more effective the tool.

    The report ([pages 32 to
    40](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=42))
    specifically praises the websites of [Rep. Marion
    Berry](http://www.house.gov/berry/survey.shtml), [Rep. John
    Linder](http://linder.house.gov/), [Rep. Jeff
    Miller](http://jeffmiller.house.gov/), and [Rep. Charlie
    Norwood](http://www.connectingtocongress.org/snapshot/www.house.gov/norwood/index.html)
    for their use of polls and surveys.

[^474]: [Checkpoint 10.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-pop-ups) *Web
    Content Accessibility Guidelines 1.0* provides that "[*[\[u\]ntil
    user
    agents]{.underline}*](http://www.w3.org/TR/WCAG10/wai-pageauth.html#until-user-agents)
    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."

    *Prioritizing Web Usability*, by Jakob Nielsen and Hoa Loranger,
    2006 (pp. 69 & 74) notes that:

    > New browser windows, . . . \[cause\] problems for users who don't
    > understand the concept of multiple windows. When possible, keep
    > your Web site in the same browser window and ensure that the Back
    > button works. Launching new windows on top of the parent window
    > can stop many users from interacting with your site. For example,
    > we've seen people accidentally click outside the parent browser
    > window and bury the new window underneath it, then try to reopen
    > the new window from the parent window and nothing appears to
    > happen. They can't find their way back to the new window and
    > conclude that the site is broken. . . .
    >
    > Users with many different types of disabilities have particular
    > problems managing extra windows. People with motor skills
    > impairments certainly don't relish having to struggle to click
    > unwanted Close boxes. And low-vision users may not even know that
    > a pop-up has appeared if they have zoomed in their screen
    > magnifier to inspect a different part of the screen. Finally,
    > blind users are severely impacted by the additional cognitive load
    > of having to cope with multiple windows and remember what
    > information was read aloud from which pop-up.

    Nielsen and Loranger, however, do recommend an exception for PDFs
    and similar types of documents (pp. 70-71).

[^475]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 9.3.4 of the
    W3C](http://www.w3.org/TR/html4/struct/text.html#h-9.3.4) *HTML 4.01
    Specification* designates the "width" attribute of the \<pre\> tag
    as a deprecated attribute).

[^476]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=58)
    (page 46) observes that:

    > The most important thing to consider is presenting the wealth of
    > information the office produces in the most usable way possible.
    > Virtually all offices already allow the press access to the most
    > recent information by providing press releases arranged by date.
    > But many users are interested in specific topics or issues. It is
    > much more likely that they want to know the latest news or action
    > on their topic of interest---say, the environment or the war in
    > Iraq---than they want to see the last three press releases or
    > floor speeches the Member has released. Organize all of the press
    > resources by topic and type. Users are more likely to read
    > articles and watch or listen to video or audio if they don't have
    > to wade through an endless chronological list of unidentifiable
    > files. While this meets the needs of the press, keep in mind that
    > other key audiences, like lobbyists, academics, and interested
    > constituents will also be served by this information.

    The report ([page
    21](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=33))
    indicates that 96% of House websites provide press releases in
    chronological order and 35% of House websites provide press releases
    in subject order.

[^477]: [Checkpoint 13.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "\[u\]se navigation mechanisms in a
    consistent manner."

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site.** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. ***Sen. John Cornyn***'s Web site is a
    > model of clearly and consistently organized information. The menu
    > headers and options are clear, and they stay the same throughout
    > the site.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^478]: For suggestions as to how to set up such a style sheet, see Eric
    Meyer's "[CSS Design: Going to
    Print](http://alistapart.com/stories/goingtoprint/)", published in A
    List Apart, May 10, 2002.

[^479]: For information on the history of the Georgia and Verdana type
    faces, see Daniel Will-Harris' [*Georgia & Verdana Typefaces
    designed for the screen
    (finally)*](http://www.will-harris.com/verdana-georgia.htm).

[^480]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (pages 40 and 95) identifies providing a privacy statement as an
    element of a successful Congressional website. The report ([page
    21](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=33))
    also notes that 61% of House Member, committee, and leadership
    websites have privacy statements.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=77)
    (page 67) provides that "Privacy statements should be included on
    every Web site, but currently only 55.49% of congressional offices
    provide them. They should be written in user-friendly language that
    is designed to put visitors at ease about the information the site
    is collecting. If a Web site requires the user's name and address
    before they can correspond with the office, the privacy statement
    should explain why the information is being collected and what will
    happen to it later. It is especially important to describe the steps
    that the office will take to safeguard any personal information it
    obtains."

    The Congressional Management Foundation's [*Congress Online 2003:
    Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=59)
    (page 51) goes on to say that, "A good example to follow is that of
    *Sen. Debbie Stabenow (D-MI)*. She posts an extensive privacy policy
    and her website is P3P-enabled. This means that when users visit her
    site, their browsers will automatically check her policy against
    their preferences."

[^481]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=33)
    (page 21) notes that 51% of House Member, committee, and leadership
    websites have links to their privacy statement on each page.

[^482]: The regulations issued pursuant to COPPA (the Children\'s Online
    Privacy Protection Act), set out at [16 C.F.R. §
    312.4](http://a257.g.akamaitech.net/7/257/2422/11feb20051500/edocket.access.gpo.gov/cfr_2005/janqtr/pdf/16cfr312.4.pdf)(b)(1),
    provide that:

    >     (1) *Placement of the notice.* (i) The link to the \[website's
    > privacy policy\] notice must be clearly labeled as a notice of the
    > website\['s\] . . . information practices . . .\
    >     (ii) The link to the notice must be placed in a clear and
    > prominent place and manner on the home page of the website . . .\
    >     (iii) The link to the notice must be placed in a clear and
    > prominent place and manner at each area on the website . . . where
    > \[users of the website\] . . . directly provide, or are asked to
    > provide, personal information, and in close proximity to the
    > requests for information in such area.

    The Federal Trade Commission's Federal Register statement issuing
    the Children's Online Privacy Protection Rule ([64 Fed. Reg.
    59894](http://frwebgate.access.gpo.gov/cgi-bin/getdoc.cgi?dbname=1999_register&docid=99-27740-filed.pdf#page=8))
    explains that:

    > "Clear and prominent" means that the link must stand out and be
    > noticeable to the site's visitors through the use, for example, of
    > a larger font size in a different color on a contrasting
    > background. The Commission does not consider "clear and prominent"
    > a link that is in small print at the bottom of the home page, or a
    > link that is indistinguishable from a number of other, adjacent
    > links.

[^483]:
    ###########  There is a wide-spread misconception that Federal government offices are prohibited by law from using cookies (see, e.g., "White House Web Site Uses Forbidden Cookies Too," Associated Press, December 30, 2005, [**http://www.foxnews.com/story/0,2933,180177,00.html**](http://www.foxnews.com/story/0,2933,180177,00.html)). The regulations issued by the Office of Management and Budget pursuant to § 208 of the E-Government Act of 2002 ([**OMB Memoranum M-03-22**](http://www.whitehouse.gov/omb/memoranda/print/m03-22.html), § III(D)(2)(a)(v)) permits the use of session cookies. It also permits the head of an agency to authorize the use of persistent cookies in that agency's website if the agency head declares there is a "compelling need" to use the technology and the site's privacy policy makes it clear what information is being collected, the purpose and use of the information, who will the information be disclosed to, and what will be done to safeguard the information. Nonetheless, given the public perception that it is illegal for government sites to use cookies, avoiding cookies may save a House office from embarrassment (see also "Hands in the cookie jar," by Declan McCullagh, CNET News.com, January 6, 2006, [**http://news.com.com/Infographic+Caught+with+hands+in+the+cookie+jar/2009-1028_3-6020368.html**](http://news.com.com/Infographic+Caught+with+hands+in+the+cookie+jar/2009-1028_3-6020368.html)). {#there-is-a-wide-spread-misconception-that-federal-government-offices-are-prohibited-by-law-from-using-cookies-see-e.g.-white-house-web-site-uses-forbidden-cookies-too-associated-press-december-30-2005-httpwww.foxnews.comstory0293318017700.html.-the-regulations-issued-by-the-office-of-management-and-budget-pursuant-to-208-of-the-e-government-act-of-2002-omb-memoranum-m-03-22-iiid2av-permits-the-use-of-session-cookies.-it-also-permits-the-head-of-an-agency-to-authorize-the-use-of-persistent-cookies-in-that-agencys-website-if-the-agency-head-declares-there-is-a-compelling-need-to-use-the-technology-and-the-sites-privacy-policy-makes-it-clear-what-information-is-being-collected-the-purpose-and-use-of-the-information-who-will-the-information-be-disclosed-to-and-what-will-be-done-to-safeguard-the-information.-nonetheless-given-the-public-perception-that-it-is-illegal-for-government-sites-to-use-cookies-avoiding-cookies-may-save-a-house-office-from-embarrassment-see-also-hands-in-the-cookie-jar-by-declan-mccullagh-cnet-news.com-january-6-2006-httpnews.com.cominfographiccaughtwithhandsinthecookiejar2009-1028_3-6020368.html. .unnumbered}

[^484]: To be compliant with [§ 6.12 of the
    W3C](http://www.w3.org/TR/html4/types.html#h-6.12) *HTML 4.01
    Specification*, Web pages that use the rel=\"privacy\" attribute
    either in an \<a\> tag or in a \<link\> tag, should have the
    following attribute in the \<head\> tag:

    > profile=\"http://lists.w3.org/Archives/Public/www-html/1997Sep/0046.html\"

    ([Checkpoint 3.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-grammar)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "validate to published formal grammars.")

[^485]: [Checkpoint 3.7 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-quotes) *Web Content
    Accessibility Guidelines 1.0* provides that accessible websites
    should:

    > \[m\]ark up quotations. Do not use quotation markup for formatting
    > effects such as indentation. \[Priority 2\]
    >
    > For example, in HTML, use the Q and BLOCKQUOTE elements to markup
    > short and longer quotations, respectively.

    [Section 1 of the
    W3C](http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure) *Core
    Techniques for Web Content Accessibility Guidelines 1.0* further
    provides that:

    > in HTML, even though the BLOCKQUOTE element may cause indented
    > text in some browsers, it is designed to identify a quotation, not
    > create a presentation side-effect. BLOCKQUOTE elements used for
    > indentation confuse users and search robots alike, who expect the
    > element to be used to mark up block quotations.

[^486]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation."

[^487]: See <http://unicode.org/charts/PDF/U2150.pdf>.

[^488]: The [*Unicode 5.0
    Standard*](http://unicode.org/versions/Unicode5.0.0/ch15.pdf#page=13)
    (p. 499) provides:

    > ***Roman Numerals.*** For most purposes, it is preferable to
    > compose the Roman numerals from sequences of the appropriate Latin
    > letters. However, the uppercase and lowercase variants of the
    > Roman numerals through 12, plus L, C, D, and M, have been encoded
    > for compatibility with East Asian standards. Unlike sequences of
    > Latin letters, these symbols remain upright in vertical layout.
    > Additionally, in certain locales, compact date formats use Roman
    > numerals for the month, but may expect the use of a single
    > character.

    Additionally, Internet Explorer 6 (which, according to a July 9 to
    15, 2008 CAO-WSB analysis constituted 30.30% of www.house.gov
    access) treats &#x2160; to &#x217F; as unidentifiable characters.
    Browsealoud 4 does not honor &#x2160; to &#x217F;, even if they are
    encapsulated by \<abbr\> tags (While Browsealoud 4 normally honors
    \<abbr\> tags, it does not honor them if they are only encapsulating
    blanks -- Browsealoud 4 treats &#x2160; to &#x217F; as if they were
    blanks).

[^489]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=60)
    (pages 48. 49, and 95) identifies having an RSS feed as an element
    of a well-formed Congressional website. The report ([pages 63, 64,
    68, 69. 70, 73, 75, 79,
    82](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=75))
    praises Rep. Xavier Becerra, Rep. Dan Burton, Rep. Mike Honda, Rep.
    James Linder, Rep. Carolyn Maloney, Rep. Ed Markey, Rep. Kevin
    McCarthy, Rep. Hilda Solis, Sen. John Cornyn, Sen Chris Dodd, House
    Republican Conference, House Committee on Oversight and Government
    Reform. The report ([page
    21](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=33))
    also indicates that only 24% of House Member, committee, and
    leadership offices have RSS feeds.

[^490]: For more information, see "WIDA RSS Capability" [at](../at)
    HouseNet → Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance) → Tools
    → WIDA.

[^491]: Examples of "What is RSS" pages can be found at the websites of
    [Rep. Marcy
    Kaptur](http://www.kaptur.house.gov/index.php?option=com_content&task=view&id=142),
    [Rep. Carolyn
    Maloney](http://maloney.house.gov/index.php?option=com_content&task=view&id=27&Itemid=48),
    the [House Administration Committee](http://cha.house.gov/rss.aspx),
    and the [W3C Web Accessibility
    Initiative](http://www.w3.org/WAI/highlights/about-rss.html).

[^492]: Websites that are hosted on the HIR UNIX server (and do not use
    a virtual URL) are encouraged to use the server-side include:

    > \<!\--#include virtual=\"/include_content/rss.html\" \--\>.

    All other sites can use code along the lines of:

    > \<iframe src=\"http://www.house.gov/include_content/rss.html\"
    > frameborder=\"0\" scrolling=\"auto\"
    > style=\"width:35em;height:50em;\" title=\"What is Real Simple
    > Syndication?\" \>\<ul\>\<li\>\<a
    > href=\"http://www.house.gov/include_content/rss.html\"\>What is
    > Real Simple Syndication?\</a\>\</li\>\</ul\>\</iframe\>

    Using the \<include\> or \<iframe\> is preferable to just linking to
    the House's "What is RSS" page. Using \<include\> or \<iframe\>
    retains the consistent look and feel of the rest of the office's
    website. A consistent look and feel assists with compliance with
    [Checkpoint 13.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* which provides that an
    accessible website should "\[u\]se navigation mechanisms in a
    consistent manner."

    [Section 4 of the
    W3C](http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation) *Core
    Techniques for Web Content Accessibility Guidelines 1.0* further
    provides that:

    > A consistent style of presentation on each page allows users to
    > locate navigation mechanisms more easily but also to skip
    > navigation mechanisms more easily to find important content. This
    > helps people with learning and reading disabilities but also makes
    > navigation easier for all users. Predictability will increase the
    > likelihood that people will find information at your site, or
    > avoid it when they so desire.
    >
    > Examples of structures that may appear at the same place between
    > pages:

    navigation bars

    the primary content of a page

    > . . .
    >
    > A navigation mechanism creates a set of paths a user may take
    > through your site. Providing navigation bars, site maps, and
    > search features all increase the likelihood that a user will reach
    > the information they seek at your site. If your site is highly
    > visual in nature, the structure might be harder to navigate if the
    > user can\'t form a mental map of where they are going or where
    > they have been. To help them, content developers should describe
    > any navigation mechanisms. It is crucial that the descriptions and
    > site guides be accessible since people who are lost at your site
    > will rely heavily on them.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site.** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. If you have a blue navigation toolbar on
    > the left side of one page, there should be a blue navigation
    > toolbar on the left side of every page. If you have links imbedded
    > in text in one issue section, you should do the same thing in
    > every issue section. *Rep. Wayne Gilchrest (R-MD)* uses the same
    > horizontal and vertical navigation throughout his site. The only
    > thing that changes on his pages is the content.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^493]: The [RSS Advisory Board
    recommends](http://www.rssboard.org/news/41/vote-support-common-feed-icon)
    using this icon.

[^494]: \<span style=\"border:1px solid;border-color:#FC9 #630 #330
    #F96;padding:0 3px;font:bold 12px
    verdana,sans-serif;color:#FFF;background:#F60;text-decoration:none;margin:0;\"\>RSS\</span\>

[^495]: \<span style=\"border:1px solid;border-color:#FC9 #630 #330
    #F96;padding:0 3px;font:bold 12px
    verdana,sans-serif;color:#FFF;background:#F60;text-decoration:none;margin:0;\"\>RSS
    2.0\</span\>

[^496]: \<span style=\"border:1px solid;border-color:#FC9 #630 #330
    #F96;padding:0 3px;font:bold 12px
    verdana,sans-serif;color:#FFF;background:#F60;text-decoration:none;margin:0;\"\>XML\</span\>

[^497]: Pages with this tag, when viewed in Firefox, will show a special
    \"live bookmark\" icon in the URL area. Pages with this tag when
    viewed in Internet Explorer 7 will make the RSS icon active. 
    The icon in both browsers becomes a drop-down list of available
    feeds that you can do with as desired.

[^498]: Rep. Neil Abercrombie's website includes a Samoan version of the
    Congressman's welcome message; see
    <http://www.house.gov/abercrombie/welcomeletter_samoan.shtml>.

[^499]: See, e.g., Rep. Mike Capuano's "[Mike's
    Schedule](http://www.house.gov/capuano/schedules/mikes_schedule.shtml)"
    which provides a sampling of his schedule.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=70)
    (pages 60 and 67) notes that

    > Congressional Web sites can demonstrate accountability by
    > providing voting records, rationales for key votes, and schedules
    > -- and they can do so without overburdening their staffs.
    > Constituents are probably not interested in knowing about every
    > meeting that takes place or every vote taken. Stick to the most
    > relevant and current information: meetings with constituents,
    > public Member appearances in the district or state, committee
    > hearings, the House and Senate floor schedule . . .
    >
    > Most citizens do not understand, or are not familiar with, the
    > intricacies of the congressional schedule. In our research with
    > constituents, they assumed that their elected officials were
    > golfing or on vacation when Congress is in recess. While there
    > isn't much legislative activity to report during recesses, you can
    > correct this misperception by posting a schedule of town hall
    > meetings, reorganizing your home page content, or providing a
    > preview of what the Member, committee, Leader, or Congress will be
    > doing after the break. Every August we see scores of congressional
    > Web sites that haven't been updated since mid-July. Don't let
    > yours be one of them.

    The report (on [page
    57](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=67))
    notes that only " 9.1% of Member sites had a district or state
    schedule and only 7.3% had such information posted within the last
    month".

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=60)
    (page 48) identifies providing the Member's schedule as an element
    of a successful Congressional website.

[^500]: [Rep. Cynthia McKinney's
    website](http://web.archive.org/web/20060421022800/http:/www.house.gov/mckinney/monthly_calendar.shtml)
    used WIDA to provide her schedule.

[^501]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(a)
    and (*l*)) provide that "A text equivalent for every non-text
    element shall be provided (e.g., via \"alt\", \"longdesc\", or in
    element content). . . . When pages utilize scripting languages to
    display content, or to create interface elements, the information
    provided by the script shall be identified with functional text that
    can be read by assistive technology."

    [Checkpoint 1.1 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-text-equivalent) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should:

    > 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. . . .
    >
    > For example, in HTML:

    Use \"alt\" for the IMG, INPUT, and APPLET elements, or provide a
    text equivalent in the content of the OBJECT and APPLET elements.

    For complex content (e.g., a chart) where the \"alt\" text does not
    provide a complete text equivalent, provide an additional
    description using, for example, \"longdesc\" with IMG or FRAME, a
    link inside an OBJECT element, or a [description
    link](http://www.w3.org/TR/WAI-WEBCONTENT/#d-link%23d-link).

    For image maps, either use the \"alt\" attribute with AREA, or use
    the MAP element with A elements (and other text) as content.

    [Checkpoint 6.2 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-dynamic-source) *Web
    Content Accessibility Guidelines 1.0* provides that an accessible
    website should "Ensure that equivalents for dynamic content are
    updated when the dynamic content changes."

    [Checkpoint 6.3 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-scripts) *Web Content
    Accessibility Guidelines 1.0* provides that an accessible website
    should:

    > 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. . . .
    >
    > For example, ensure that links that trigger scripts work when
    > scripts are turned off or not supported (e.g., do not use
    > \"javascript:\" as the link target). If it is not possible to make
    > the page usable without scripts, provide a text equivalent with
    > the NOSCRIPT element, or use a server-side script instead of a
    > client-side script, or provide an alternative accessible page as
    > per [checkpoint
    > 11.4](http://www.w3.org/TR/WCAG10/#tech-alt-pages%23tech-alt-pages).
    > [Refer also to guideline
    > 1](http://www.w3.org/TR/WCAG10/#gl-provide-equivalents%23gl-provide-equivalents).

[^502]: [Checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 18.2.1 of the
    W3C](http://www.w3.org/TR/html4/interact/scripts.html#h-18.2.1)
    *HTML 4.01 Specification* designates the "language" attribute of the
    \<script\> tag as a deprecated attribute).

    The "language" attribute should not be confused with the "lang"
    attribute that specifies the human language of associated text
    (e.g., \<span lang=\"fr\"\>oui\</span\>) or the "hreflang" attribute
    that specifies the primary language of a page being linked to, e.g.,

    > \<a href=\"http://www.parl.gc.ca/common/index.asp?Language=F\"
    > hreflang=\"fr-CA\"\>Parliament of Canada\</a\>

[^503]: [Checkpoint 10.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-pop-ups) *Web
    Content Accessibility Guidelines 1.0* provides that "[*[\[u\]ntil
    user
    agents]{.underline}*](http://www.w3.org/TR/WCAG10/wai-pageauth.html#until-user-agents)
    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."

    *Prioritizing Web Usability*, by Jakob Nielsen and Hoa Loranger,
    2006 (pp. 69 & 74) notes that:

    > New browser windows, . . . \[cause\] problems for users who don't
    > understand the concept of multiple windows. When possible, keep
    > your Web site in the same browser window and ensure that the Back
    > button works. Launching new windows on top of the parent window
    > can stop many users from interacting with your site. For example,
    > we've seen people accidentally click outside the parent browser
    > window and bury the new window underneath it, then try to reopen
    > the new window from the parent window and nothing appears to
    > happen. They can't find their way back to the new window and
    > conclude that the site is broken. . . .
    >
    > Users with many different types of disabilities have particular
    > problems managing extra windows. People with motor skills
    > impairments certainly don't relish having to struggle to click
    > unwanted Close boxes. And low-vision users may not even know that
    > a pop-up has appeared if they have zoomed in their screen
    > magnifier to inspect a different part of the screen. Finally,
    > blind users are severely impacted by the additional cognitive load
    > of having to cope with multiple windows and remember what
    > information was read aloud from which pop-up.

    Nielsen and Loranger, however, do recommend an exception for PDFs
    and similar types of documents (pp. 70-71).

[^504]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) identifies providing a functional search capability as an
    element of a successful Congressional website. The report (page 22)
    also notes that 63% of House websites provide search capabilities.

    *Prioritizing Web Usability*, by Jakob Nielsen and Hoa Loranger,
    2006 (pp. 27 and 142) recommends that a search capability be
    provided in the upper right corner of each page.

[^505]: [Checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies."
    ([Section 17.8 of the
    W3C](http://www.w3.org/TR/html4/interact/forms.html#edef-ISINDEX)
    *HTML 4.01 Specification* and [§ C.6 of the
    W3C](http://www.w3.org/TR/xhtml1/#C_6) *XHTML 1.0 (2^nd^ edition)
    Specification* designate the \<isindex\> tag as a deprecated
    element).

[^506]: Jakob Nielsen and Hoa Loranger's *Prioritizing Web Usability*,
    2006, p.143, recommends:

    > Don't offer the option of searching the entire Web. Web users
    > already have their own favorite search engines, and when they want
    > to search the Web, they'll go to those. Searching anything beyond
    > your own site simply clutters up you pages. The only exception is
    > if you have multiple Web sites. If so, a multi-site Search may be
    > in order, but beware that it will complicate your user interface
    > and reduce usability because people expect Web sites to offer
    > single-site Search.

[^507]: The Congressional Management Foundation's [*Congress Online
    2003: Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=54)
    (page 46) recommends that "Visitors to Member sites should . . . be
    able to initiate basic service requests . . . and to solicit
    assistance with academy nominations and internship processes."

    The CMF report (page 57) goes on to note that:

    > Many offices use their Web sites to direct constituents to contact
    > them offline for the information and services they are seeking.
    > Yet, people who choose the Web as their method of contacting a
    > congressional office are doing so precisely because they prefer to
    > have their needs met online. Respond to their needs accordingly,
    > and you will find you have more satisfied "customers," at less
    > effort and expense to the office than you ever thought possible.

    Rep. John Linder's "[Academy
    Nominations](http://linder.house.gov/index.cfm?FuseAction=Resources.Home&Resource_id=E1BA9747-DEA4-450C-BEAB-E577937E3C27)"
    page takes visitors step-by-step through the process and also
    includes a set of frequently asked questions.

[^508]: See, e.g., [Rep. Buck McKeon](http://mckeon.house.gov/)'s
    website.

[^509]: [Item 21
    of](https://secadmin5.us.house.gov/checklists/HISPUB 007.1.56 - Website Developement.pdf#page=4)
    *The United States House of Representatives Information Security
    Publication -- Web Site Developers Security Checklist*, HISPUB
    007.1.56, August 2008, which was written before secured forms were
    easily available to House offices, provides that "All web forms must
    include direction for public users to not pass any sensitive data
    via the web form."

[^510]: Instructions for setting up secure forms are set out at HouseNet
    → Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance) →
    Features and Scripts → Online Forms -- Secure Forms.

[^511]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=80)
    (page 68) praises the website of [Rep. Mike
    Honda](http://www.honda.house.gov/paginaPrincipal.shtml) for
    providing information in Spanish. Several Members of the House have
    websites that are completely or substantially bilingual
    (English/Spanish), including [Rep. Jim
    Costa](http://www.costa-es.house.gov/), [Rep. Linda
    Sanchez](http://lindasanchez.house.gov/spanish/index.cfm), [Rep.
    Loretta Sanchez](http://www.lorettasanchez-es.house.gov/), and
    [Resident Commissioner Luis
    Fortuña](http://www.house.gov/fortuno/NewSite2/esp/index.shtml).

[^512]: Use the "text-decoration: line-through" style sheets property.

[^513]: [Checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies
    ([Section 15.2.1 of the
    W3C](http://www.w3.org/TR/html4/present/graphics.html#edef-S) *HTML
    4.01 Specification* designates the \<s\> and \<strike\> tags as
    deprecated elements).

[^514]: The [Congressional Management
    Foundation's](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=54)
    *Congress Online 2003: Turning the Corner on the Information Age*
    (p. 46) notes that "Committees and leadership offices with natural
    constituencies can also provide service information online. The
    *House Committee on Veterans' Affairs* website provides information
    on veterans' benefits for its key audience."

[^515]: Using the \<include\> or \<iframe\> is preferable to just
    linking to the generic "Student Financial Aid" page. Using
    \<include\> or \<iframe\> retains the consistent look and feel of
    the rest of the office's website. A consistent look and feel assists
    with compliance with [Checkpoint 13.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* which provides that an
    accessible website should "\[u\]se navigation mechanisms in a
    consistent manner."

    [Section 4 of the
    W3C](http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation) *Core
    Techniques for Web Content Accessibility Guidelines 1.0* further
    provides that:

    > A consistent style of presentation on each page allows users to
    > locate navigation mechanisms more easily but also to skip
    > navigation mechanisms more easily to find important content. This
    > helps people with learning and reading disabilities but also makes
    > navigation easier for all users. Predictability will increase the
    > likelihood that people will find information at your site, or
    > avoid it when they so desire.
    >
    > Examples of structures that may appear at the same place between
    > pages:

    navigation bars

    the primary content of a page

    > . . .
    >
    > A navigation mechanism creates a set of paths a user may take
    > through your site. Providing navigation bars, site maps, and
    > search features all increase the likelihood that a user will reach
    > the information they seek at your site. If your site is highly
    > visual in nature, the structure might be harder to navigate if the
    > user can\'t form a mental map of where they are going or where
    > they have been. To help them, content developers should describe
    > any navigation mechanisms. It is crucial that the descriptions and
    > site guides be accessible since people who are lost at your site
    > will rely heavily on them.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site:** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. ***Sen. John Cornyn***'s Web site is a
    > mode l of clearly and consistently organized information. The menu
    > headers and options are clear, and they stay the same throughout
    > the site.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^516]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(d))
    provide that "Documents shall be organized so they are readable
    without requiring an associated style sheet." A virtually identical
    standard is set out in [Checkpoint 6.1 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-order-style-sheets)
    *Web Content Accessibility Guidelines 1.0*.

[^517]: For more information on how Jaws interacts with style sheets,
    see "[Does JAWS support cascading style sheets
    (CSS)](http://www.freedomscientific.com/fs_support/BulletinView.cfm?QC=1165)?"
    Freedom Scientific (February 1, 2007).

[^518]: For a technical explanation of why this is needed, based on
    priorities within CSS, see Eric Meyer's explanation at
    <http://meyerweb.com/eric/css/link-specificity.html>.

[^519]: For more information on this issue, see
    <http://www.webmasterworld.com/forum83/9334.htm>.

[^520]: Section 1 of the W3C [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#structure) provides
    that:

    > When designing a document or series of documents, content
    > developers should strive first to identify the desired structure
    > for their documents before thinking about how the documents will
    > be presented to the user. Distinguishing the structure of a
    > document from how the content is presented offers a number of
    > advantages, including improved accessibility, manageability, and
    > portability.

    Jeffrey Zeldman's, *Designing With Web Standards* (2^nd^ edition,
    \[2006\]), p.180, recommends that

    > Semantic or meta-structural names (names that explain the function
    > performed by elements contained within) are best. You would feel
    > pretty silly having labeled a part of your site "orangebox" when
    > the client decides to go with blue. You would feel sillier still
    > revising your style sheets under a deadline six months from now
    > and trying desperately to remember whether "Gladys" was a
    > navigational area, a sidebar, a search form, or what.

[^521]: [Checkpoint 11.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-latest-w3c-specs)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "Use W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

    [Section C.4 of the W3C](http://www.w3.org/TR/xhtml1/#C_4) *XHTML
    1.0 Specification (2^nd^ edition)* recommends "Use external scripts
    if your script uses \< or & or \]\]\> or \--."

[^522]: [Checkpoint 11.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-latest-w3c-specs)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "Use W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

    [Section C.4 of the W3C](http://www.w3.org/TR/xhtml1/#C_4) *XHTML
    1.0 Specification (2^nd^ edition)* notes that "XML parsers are
    permitted to silently remove the contents of comments. Therefore,
    the historical practice of 'hiding' scripts and style sheets within
    'comments' to make the documents backward compatible is likely to
    not work as expected in XML-based user agents."

[^523]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(g))
    provide that

    "Row and column headers shall be identified for data tables". A
    virtually identical standard is set out in [Checkpoint 5.1
    \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-table-headers) *Web
    Content Accessibility Guidelines 1.0*.

[^524]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(h))
    provide that

    > Markup shall be used to associate data cells and header cells for
    > data tables that have two or more logical levels of row or column
    > headers.

    A virtually identical standard is set out in [Checkpoint 5.2
    \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-table-structure) *Web
    Content Accessibility Guidelines 1.0*.

[^525]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that an accessible
    website should "\[u\]se style sheets to control layout and
    presentation." Likewise, [Checkpoint
    5.3](http://www.w3.org/TR/WCAG10/#tech-avoid-table-for-layout)
    \[priority 2\] provides that "[*[Once user
    agents]{.underline}*](http://www.w3.org/TR/WCAG10/#until-user-agents%23until-user-agents)
    support style sheet positioning, tables should not be used for
    layout."

    One approach to replacing layout tables with style sheets is to use
    \<div\> tags with "class" attributes to invoke style sheets such as:

    > .nav {float: left; width: 32%;}
    >
    > .maincontent {float: left; width: 32%; margin: 0 1%;}
    >
    > .supnav {float: right; width: 32%;}

    In the example (for a 3-column layout), text in the "nav" class will
    appear in the left column, text in the "maincontent" class will
    appear in the middle column, and text in the "supnav" class will
    appear in the right column.

    **Note:** The total width is deliberately slightly less than 100% in
    order to make the layout compatible with various browsers that do
    not properly implement the CSS box model. This approach is suggested
    in Jeffrey Zeldman's, *Designing With Web Standards* (2^nd^ edition,
    \[2006\]), p. 297.

    **Additional Note:** Many of the Gecko-based browsers (including
    Firefox and Netscape 7) are unable to print more than one page of
    floated text. A solution to this bug suggested by Eric Meyer is
    basically to set up a **print** style sheet with "float:none". (See
    Eric Meyer's "[CSS Design: Going to
    Print,](http://alistapart.com/stories/goingtoprint/)" published in A
    List Apart, May 10, 2002.) Keep in mind that the standard set out in
    [checkpoint 3.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-relative-units) *Web
    Content Accessibility Guidelines 1.0* that accessible websites
    should "\[u\]se relative rather than absolute units in markup
    language attribute values and style sheet property values." does not
    apply to printed output from a Web page -- so it is permissible for
    a print style sheet to use fixed widths and fixed character sizes.

    For a strategy (and code) for setting up a 3-column layout with
    fixed-width columns on the left and right, a liquid center, and a
    full-screen width footer, see Matthew Levine's "[In Search of the
    Holy Grail](http://www.alistapart.com/articles/holygrail/)," A List
    Apart (January 30, 2006). **Note**, however, that the strategy in
    Levine's article does not work in Internet Explorer 5.5 -- a WSB
    analysis of www.house.gov usage for July 9 to 15, 2008, indicates
    that IE 5.x constitutes 1.39% of the identifiable, non-robot access
    to the site. Additionally, Levine's approach uses the IE "star
    hack", which is [no longer supported by IE starting with IE
    7](http://blogs.msdn.com/ie/archive/2005/10/12/480242.aspx) (which
    constituted 46.32% of [www.house.gov](http://www.house.gov/) usage).

[^526]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies
    ([Section 11.2.6 of the
    W3C](http://www.w3.org/TR/html4/struct/tables.html#h-11.2.6) *HTML
    4.01 Specification* designates the "height" and "width" attributes
    of the \<td\> and \<th\> tags as deprecated attributes).

[^527]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies
    ([Section 11.2.6 of the
    W3C](http://www.w3.org/TR/html4/struct/tables.html#h-11.2.6) *HTML
    4.01 Specification* designates the "nowrap" attribute as a
    deprecated attribute).

[^528]: Instructions for implementing a sort function in a Web table can
    be found at Neil Crosby's "[Standardista Table Sorting (A
    client-side JavaScript Table
    Sort)](http://www.workingwith.me.uk/articles/scripting/standardista_table_sorting),"
    Working With Me UK (February 26, 2006) and at Stuart Langridge's
    "[Sortable: Male All Your Tables
    Sortable](http://www.kryogenix.org/code/browser/sorttable/)," As
    Days Pass By (April 2007). An implementation of the sort function
    can be found at the [homepage of the Immigration Reform
    Caucus](http://www.house.gov/bilbray/irc/) and at the [videos page
    of Rep. Mike Rogers of
    Alabama](http://www.house.gov/mike-rogers/video.shtml).

[^529]: [Section 4.6 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.6)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that "Empty
    elements must either have an end tag or the start tag must end with
    /\>. For instance, \<br/\> or \<hr\>\</hr\>." [Checkpoint 11.1
    \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^530]: [Section 4.3 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.3)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that

    > All elements other than those declared in the DTD as EMPTY must
    > have an end tag. . . .
    >
    > ***CORRECT: terminated elements***
    >
    > \<p\>here is a paragraph.\</p\>\<p\>here is another
    > paragraph.\</p\>
    >
    > ***INCORRECT: unterminated elements***
    >
    > \<p\>here is a paragraph.\<p\>here is another paragraph.

    [Section 4.6 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.6) *XHTML
    1.0 (2^nd^ edition) Specification* provides that "Empty elements
    must either have an end tag or the start tag must end with /\>. For
    instance, \<br/\> or \<hr\>\</hr\>."

    [Checkpoint 11.1 \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^531]: [Section 4.1 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.1)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that:

    > all the elements must nest properly.
    >
    > Although overlapping is illegal in SGML, it is widely tolerated in
    > existing browsers.
    >
    > ***CORRECT: nested elements.***
    >
    > \<p\>here is an emphasized \<em\>paragraph\</em\>.\</p\>
    >
    > ***INCORRECT: overlapping elements***
    >
    > \<p\>here is an emphasized \<em\>paragraph.\</p\>\</em\>

    [Checkpoint 11.1 \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^532]: [Section 4.2 of the W3C](http://www.w3.org/TR/xhtml1/#h-4.2)
    *XHTML 1.0 (2^nd^ edition) Specification* provides that "XHTML
    documents must use lower case for all HTML element and attribute
    names." [Checkpoint 11.1 \[priority 2\] of
    the](http://www.w3.org/TR/WCAG10/#tech-latest-w3c-specs) *Web
    Content Accessibility Guidelines* provides that accessible websites
    should "\[u\]se W3C technologies when they are available and
    appropriate for a task and use the latest versions when supported."

[^533]: The regulations under § 508 of the Rehabilitation Act of 1973
    ([36 C.F.R. §
    1194.22](http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web)(k))
    provide that

    > A text-only page, with equivalent information or functionality,
    > shall be provided to make a web site comply with the provisions of
    > this part, when compliance cannot be accomplished in any other
    > way. The content of the text-only page shall be updated whenever
    > the primary page changes.

    [Checkpoint 11.4 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WCAG10/#tech-alt-pages) *Web Content
    Accessibility Guidelines 1.0* provides that

    > If, [after best
    > efforts](http://www.w3.org/TR/WCAG10/wai-pageauth.html#alt-page-note),
    > you cannot create an
    > [*[accessible]{.underline}*](http://www.w3.org/TR/WCAG10/wai-pageauth.html#accessible)
    > page, provide a link to an alternative page that uses W3C
    > technologies, is accessible, has
    > [*[equivalent]{.underline}*](http://www.w3.org/TR/WCAG10/wai-pageauth.html#equivalent)
    > information (or functionality), and is updated as often as the
    > inaccessible (original) page.
    > [.](http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-alt-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.

[^534]: [Section 7.4.2 of the
    W3C](http://www.w3.org/TR/REC-html40/struct/links.html#h-7.4.2)
    *HTML 4.01 Specification* provides that "Every HTML document
    **must** have a
    [[TITLE]{.underline}](http://www.w3.org/TR/REC-html40/struct/global.html#edef-TITLE)
    element in the
    [[HEAD]{.underline}](http://www.w3.org/TR/REC-html40/struct/global.html#edef-HEAD)
    section." [Checkpoint 3.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-grammar)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "validate to published formal grammars."

[^535]: [*Research-Based Web Design & Usability
    Guidelines*](http://www.usability.gov/pdfs/chapter9.pdf#page=3),
    2^nd^ edition, page 78, (compiled by the U.S. Department of Health
    and Human Services) notes that:

    > Titles are used by search engines to identify pages. If two or
    > more pages have the same title, they cannot be differentiated by
    > users or the Favorites capability of the browser. If users
    > bookmark a page, they should not have to edit the title to meet
    > the characteristics mentioned above.
    >
    > Remember that some search engines only list the titles in their
    > search results page.

[^536]: [Checkpoint 13.8 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-front-loading) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[p\]lace distinguishing information at the
    beginning of headings, paragraphs, lists, etc."

    Jakob Nielsen and Hoa Loranger in their *Prioritizing Web
    Usability*, 2006 (page 276) note that:

    > The main page title is especially important because it serves as
    > the link to the page in search engine listings. Users speed
    > through those listings, so your page title must convey your
    > purpose in just a few words. Our eye-tracking studies show that
    > users often read only the first words of the search listings, so
    > it's no good to save your information carrying keywords for the
    > end of the title.

[^537]: [Checkpoint 3.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-grammar)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "validate to published formal grammars."

[^538]: Other W3C validators are available at
    <http://www.w3.org/QA/Tools/#validators>.

[^539]: [Checkpoint 3.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-grammar)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "validate to published formal grammars."

[^540]: The default setting for the W3C Link Checker will test one page.
    To test an entire site, check the "Check linked documents
    recursively" box.

    A downloadable version of the W3C Link Cheker is available at
    <http://validator.w3.org/docs/checklink.html#install>.

[^541]: The default setting tests according to the luminosity contrast
    ratio referenced in [guideline 1.4.3 \[level AA\] of the World Wide
    Web Consortium's Web Content Accessibility Guidelines 2.0 (May 17,
    2007 working
    draft)](http://www.w3.org/TR/WCAG20/#visual-audio-contrast-contrast).

    The contrast standard set out in [checkpoint 2.2 of the
    W3C](http://www.w3.org/TR/AERT#color-contrast) *Techniques for
    Accessibility Evaluation and Repair Tools* (April 26, 2000 working
    draft) can be tested for by choosing "Options", "Algorithm", and
    "Colour brightness/difference".

[^542]: One option that Cynthia Says provides is to perform an analysis
    of the quality of "alt" attributes. The standards used by Cynthia
    Says to analyze "alt" attributes are set out at
    <http://www.hisoftware.com/cc/altquality.htm>. Cynthia Says also
    detects some deprecated attributes (e.g., "bgcolor" and "nowrap") as
    part of its WCAG priority 2 analysis.

[^543]: Section 5.1 of the W3C's [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#writing-style),
    recommends that webmasters "consider using the Gunning-Fog reading
    measure" to implement [WCAG 1.0 checkpoint
    14.1](http://www.w3.org/TR/WCAG10/#tech-simple-and-straightforward)
    \[priority 1\], that accessible websites should "\[u\]se the
    clearest and simplest language appropriate for a site\'s content."
    Microsoft Word. Without specifying a particular test, Jakob Nielsen
    and Hoa Loranger's *Prioritizing Web Usability*, 2006, p.34,
    recommends that websites written for adult audiences should be
    written at an 8^th^ grade reading level.

[^544]: *Prioritizing Web Usability*, by Jakob Nielsen and Hoa Loranger,
    2006 (p. 59) recommends:

    > The main guideline for under-construction signs is to avoid them
    > and not advertise features until you have them. If this is not
    > possible, at least provide an estimate of when the information
    > will be available. Even better, . . ., offer users the option of
    > receiving an email announcement when the page goes live.

    For a "history" of the use of "Under Construction" on the Web, see
    "[The Construction Sign
    Museum](http://boulter.com/construction/one.html)" by Jeff Boulter.

[^545]: Use the "text-decoration: underline" style sheets property.

[^546]: [Checkpoint 3.3 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-style-sheets) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[u\]se style sheets to control layout and
    presentation." Additionally, [checkpoint 11.2 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-avoid-deprecated)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[a\]void deprecated features of W3C technologies
    ([Section A.3.1 of the
    W3C](http://www.w3.org/TR/html4/appendix/changes.html#h-A.3.1.2)
    *HTML 4.01 Specification* designates the \<u\> tag as a deprecated
    element).

[^547]: Jakob Nielsen, in "[Guidelines for Visualizing
    Links](http://www.useit.com/alertbox/20040510.html)" (May 10, 2004)
    recommends:

    > Don\'t underline any text that\'s not a link, even if your links
    > aren\'t underlined. **Reserve underlining for links**. Because
    > underlines provide a strong perceived affordance of clickability,
    > users will be confused and disappointed if underlined text
    > doesn\'t have an actual affordance to match this perception.

[^548]: One potentially legitimate exception to this standard (and even
    then, one to be used with care) is when you are reproducing text
    that originally existed as non-World Wide Web printed text. As Paul
    Ford notes in "[Processing
    Processing](http://www.ftrain.com/ProcessingProcessing.html#3-anchor)"
    (September 2, 2003) (cited in Jeffrey Zeldman's, *Designing With Web
    Standards* (2^nd^ edition, \[2006\], p. 175):

    > When I\'m publishing content from 1901 and it\'s in italics, it\'s
    > in *italics,* not emphasized. Typography has a semantics that is
    > subtle, changing, and deeply informed by history.

[^549]: The U.S. Code is the official, subject-matter order, compilation
    of the Federal statutes (currently in force), of a general and
    permanent nature, The U.S. Code is compiled by the Office of the Law
    Revision Counsel of the U.S. House of Representatives. For more
    information, see <http://uscode.house.gov/about/info.shtml>.

[^550]: [*Research-Based Web Design & Usability
    Guidelines*](http://www.usability.gov/pdfs/chapter2.pdf#page=2),
    2^nd^ edition, page 10, (compiled by the U.S. Department of Health
    and Human Services), identifies providing "citatons and references"
    as one of the elements that project credibility in a website.

[^551]: U.S. Code title numbers run from 1 to 50. For a list of the
    subjects covered by each of the 50 titles, see
    <http://uscode.house.gov/download/ascii.shtml>.

[^552]: U.S. Code section numbers can include numerals, lower case
    letters, upper case letters, and up to one dash, e.g.,
    "123456aaaa-2b". For these purposes, section numbers do not include
    material in parentheses, e.g., "(c)(3)" in "501(c)(3)" -- in this
    instance the "(c)(3)" indicates that this is subsection "(c)(3)" of
    section 501.

[^553]: The [*Members' Congressional
    Handbook*](http://cha.house.gov/official_and_representational_expenses_continued.aspx#WebSites)
    (Web Sites, § 2), issued by the Committee on House Administration,
    provides that "Member\'s Web sites must be located in the HOUSE.GOV
    host-domain . . ." The
    [*Handbook*](http://cha.house.gov/official_and_representational_expenses_continued.aspx#NameURL)
    (Web Sites, Name (URL)) further provides that:

    > The URL name for an official Web site located in the HOUSE.GOV
    > domain must be recognizably derivative or representative of the
    > name of the Member or the name of the office sponsoring the Web
    > site.
    >
    > The URL name for an official Web site located in the HOUSE.GOV
    > domain may not:\
    > 1. Be a slogan.\
    > 2. Imply in any manner that the House endorses or favors any
    > specific commercial product, commodity, or service.

    The [*Committees' Congressional
    Handbook*](http://cha.house.gov/committee_handbook.aspx#general5)
    (Web Site Regulations, General, § 3) likewise provides that "Web
    sites must be located in the HOUSE.GOV host-domain . . ." and (in
    [Web Site Regulations, Name
    (URL)](http://cha.house.gov/committee_handbook.aspx#nameURL)) that:

    > 1\. The URL name for an official Web site located in the HOUSE.GOV
    > domain must be recognizably derivative or representative of the
    > name of the committee.\
    > 2. The URL name may not be a slogan or imply in any manner that
    > the House endorses or favors any specific commercial product,
    > commodity, or service.

[^554]: In July of 2006, the House Administration Committee rejected a
    request from the Clerk to establish a lobbying.house.gov domain, but
    did approve lobbyingdisclosure.house.gov.

[^555]: The [Congressional Management
    Foundation's](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=54)
    *Congress Online 2003: Turning the Corner on the Information Age*
    (p. 46) notes that "Committees and leadership offices with natural
    constituencies can also provide service information online. The
    *House Committee on Veterans' Affairs* website provides information
    on veterans' benefits for its key audience."

[^556]: The [Congressional Management
    Foundation's](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=50)
    *Congress Online 2003: Turning the Corner on the Information Age*
    (p. 42) sites the [veterans section of Rep. Mike Honda's
    website](http://www.honda.house.gov/veteransinformation.shtml) as a
    good example of using a website to build relations with veterans.
    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=49)
    (page 39) also praises the [veterans page on Rep. Dennis Moore's
    website](http://www.moore.house.gov/group.asp?group_id=1).

[^557]: Websites that are hosted on the HIR UNIX server (and do not use
    a virtual URL) are encouraged to use the server-side include along
    the lines of:

    > \<ul\>\<!\--#include
    > virtual=\"/house/subpage_content/Veterans_content.htm\"
    > \--\>\</ul\>

    All other sites can use code along the lines of:

    > \<ul\>\<iframe
    > src=\"http://www.house.gov/house/subpage_content/Veterans_content.htm\"
    > frameborder=\"0\" scrolling=\"auto\"
    > style=\"width:35em;height:15em;\" title=\"Veterans benefits
    > frequently asked questions\" \>\<li\>\<a
    > href=\"http://www.house.gov/house/subpage_content/Veterans_content.htm\"\>Veterans
    > benefits frequently asked questions\</a\>\</li\>\</iframe\>\</ul\>

    Using the \<include\> or \<iframe\> is preferable to just linking to
    <http://www.house.gov/house/subpage_content/Veterans_content.htm>.
    Using \<include\> or \<iframe\> retains the consistent look and feel
    of the rest of the office's website. A consistent look and feel
    assists with compliance with [Checkpoint 13.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* which provides that an
    accessible website should "\[u\]se navigation mechanisms in a
    consistent manner."

    [Section 4 of the
    W3C](http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation) *Core
    Techniques for Web Content Accessibility Guidelines 1.0* further
    provides that:

    > A consistent style of presentation on each page allows users to
    > locate navigation mechanisms more easily but also to skip
    > navigation mechanisms more easily to find important content. This
    > helps people with learning and reading disabilities but also makes
    > navigation easier for all users. Predictability will increase the
    > likelihood that people will find information at your site, or
    > avoid it when they so desire.
    >
    > Examples of structures that may appear at the same place between
    > pages:

    navigation bars

    the primary content of a page

    > . . .
    >
    > A navigation mechanism creates a set of paths a user may take
    > through your site. Providing navigation bars, site maps, and
    > search features all increase the likelihood that a user will reach
    > the information they seek at your site. If your site is highly
    > visual in nature, the structure might be harder to navigate if the
    > user can\'t form a mental map of where they are going or where
    > they have been. To help them, content developers should describe
    > any navigation mechanisms. It is crucial that the descriptions and
    > site guides be accessible since people who are lost at your site
    > will rely heavily on them.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site:** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. ***Sen. John Cornyn***'s Web site is a
    > model of clearly and consistently organized information. The menu
    > headers and options are clear, and they stay the same throughout
    > the site.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^558]: Created by [Pub. L.
    106-380](http://frwebgate.access.gpo.gov/cgi-bin/useftp.cgi?IPaddress=162.140.64.88&filename=publ380.pdf&directory=/disk3/wais/data/106_cong_public_laws).

[^559]: The [Congressional Management
    Foundation's](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=54)
    *Congress Online 2003: Turning the Corner on the Information Age*
    (p. 46) notes that "Committees and leadership offices with natural
    constituencies can also provide service information online. The
    *House Committee on Veterans' Affairs* website provides information
    on veterans' benefits for its key audience."

[^560]: <http://www.loc.gov/vets/>

[^561]: The [Congressional Management
    Foundation's](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=54)
    *Congress Online 2003: Turning the Corner on the Information Age*
    (p. 46) notes that "Committees and leadership offices with natural
    constituencies can also provide service information online. The
    *House Committee on Veterans' Affairs* website provides information
    on veterans' benefits for its key audience."

[^562]: <http://gravelocator.cem.va.gov/j2ee/servlet/NGL_v1>

[^563]: A list of state offices of veterans affairs (with links to their
    websites) is available from the National Association of State
    Directors of Veterans Affairs. Go to <http://www.nasdva.com/> and
    follow the "State VA Departments" link.

    Note: the Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=57)
    (pages 45 and 95) identifies providing information about state and
    local resources as an element of a successful Congressional website.

[^564]: Rep. Mike Honda's website includes some pages in Vietnamese.
    See, e.g., <http://honda.house.gov/biography_viet.shtml>,
    <http://honda.house.gov/welcomemessage-viet.shtml>, and
    <http://honda.house.gov/helpwithfederalagencies-viet.shtml>.

[^565]: Instructions for using CAO-Web Solutions Branch's form_proc
    software to create tour request forms are available on HouseNet at
    Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance) →
    Features and Scripts → Create a Congressional Tour Form.
    Instructions for making this form secure are set out on HouseNet at
    Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance) →
    Features and Scripts → Online Forms -- Secure Forms.

    Form_proc is the software suggested in Congressional Management
    Foundation's [*Congress Online 2003: Turning the Corner on the
    Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=65),
    (p. 57): "House offices can also simplify their e-mail management by
    utilizing the customized Web-based forms available from House
    Information Resources (i.e. for tour requests, scheduling requests,
    casework, feedback, etc.)."

    The importance of Congressional offices keeping personal information
    about constituents secure was highlighted in Baltimore radio station
    WBAL's November 14, 2007, investigative report "[White House Tours
    Could Lead to Identity
    Theft](http://www.wbaltv.com/11investigates/14597512/detail.html)".

[^566]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (pages 40, 45, and 95) identifies providing tour information and
    request forms as an element of a successful Congressional website;
    and notes ([page
    50](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=62))
    that "On the best sites on Capitol Hill, all of the content is
    synthesized, overlapped, and cross-referenced. Constituent services
    sections contain communications tools for users to start the process
    of casework, or request a tour." The report ([page
    21](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=33))
    also notes that 51% of House websites provide search capabilities.
    The report ([pages 67 to
    82](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=79))
    singles out the tour request pages on the websites of Reps. [Mike
    Ferguson](http://ferguson.house.gov/index.cfm?FuseAction=ConstituentServices.VisitingDC)
    and [Dave
    Weldon](http://weldon.house.gov/ConstituentServices/WhiteHouse.htm).

    The Congressional Management Foundation's [*Congress Online 2003:
    Turning the Corner on the Information
    Age*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/congressonline2003.pdf#page=65)
    (page 57) observes that:

    > Many offices use their Web sites to direct constituents to contact
    > them offline for the information and services they are seeking.
    > Yet, people who choose the Web as their method of contacting a
    > congressional office are doing so precisely because they prefer to
    > have their needs met online. Respond to their needs accordingly,
    > and you will find you have more satisfied "customers," at less
    > effort and expense to the office than you ever thought possible.

[^567]: To capture the text of the Tourist Information page, websites
    that are hosted on the HIR UNIX server (and do not use a virtual
    URL) can use the server-side include:

    > \<!\--#include
    > virtual=\"/house/subpage_content/Tour_dc_content.htm\" \--\>

    All other sites can use code along the lines of:

    > \<iframe
    > src=\"http://www.house.gov/house/subpage_content/Tour_dc_content.htm\"
    > scrolling=\"auto\" style=\"width:35em; height:250em;\"
    > title=\"Washington DC tourist information\"\>\<ul\>\<li\>\<a
    > href=\"http://www.house.gov/house/tour_dc.shtml\"\>Washington, DC
    > tourist information\</a\>\</li\>\</ul\>\</iframe\>

    To capture the text of the Visiting DC page, websites that are
    hosted on the HIR UNIX server (and do not use a virtual URL) can use
    the server-side include:

    > \<!\--#include
    > virtual=\"/house/subpage_content/Visitor_content.htm\" \--\>

    All other sites can use code along the lines of:

    > \<iframe
    > src=\"http://www.house.gov/house/subpage_content/Visitor_content.htm
    > \" scrolling=\"auto\" style=\"width:35em; height:50em;\"
    > title=\"Visiting Washington DC\"\>\<ul\>\<li\>\<a
    > href=\"http://www.house.gov/house/Visitor.shtml\"\>Visiting
    > Washington,, DC\</a\>\</li\>\</ul\>\</iframe\>

    Using the \<include\> or \<iframe\> is preferable to just linking to
    the House's "Washington DC Tourist Information" or "Visiting
    Washington, DC" pages. Using \<include\> or \<iframe\> retains the
    consistent look and feel of the rest of the office's website. A
    consistent look and feel assists with compliance with [Checkpoint
    13.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* which provides that an
    accessible website should "\[u\]se navigation mechanisms in a
    consistent manner."

    [Section 4 of the
    W3C](http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation) *Core
    Techniques for Web Content Accessibility Guidelines 1.0* further
    provides that:

    > A consistent style of presentation on each page allows users to
    > locate navigation mechanisms more easily but also to skip
    > navigation mechanisms more easily to find important content. This
    > helps people with learning and reading disabilities but also makes
    > navigation easier for all users. Predictability will increase the
    > likelihood that people will find information at your site, or
    > avoid it when they so desire.
    >
    > Examples of structures that may appear at the same place between
    > pages:

    navigation bars

    the primary content of a page

    > . . .
    >
    > A navigation mechanism creates a set of paths a user may take
    > through your site. Providing navigation bars, site maps, and
    > search features all increase the likelihood that a user will reach
    > the information they seek at your site. If your site is highly
    > visual in nature, the structure might be harder to navigate if the
    > user can\'t form a mental map of where they are going or where
    > they have been. To help them, content developers should describe
    > any navigation mechanisms. It is crucial that the descriptions and
    > site guides be accessible since people who are lost at your site
    > will rely heavily on them.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site:** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. ***Sen. John Cornyn***'s Web site is a
    > model of clearly and consistently organized information. The menu
    > headers and options are clear, and they stay the same throughout
    > the site.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^568]: For more information on WIDA's "issues" feature, see [at](../at)
    HouseNet → Technology → [Web
    Solutions](http://housenet.house.gov/keywords/webassistance) → Tools
    → WIDA → WIDA Issues Feature.

[^569]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=70)
    (page 60) notes that "Most of our award-winning sites keep their
    press releases up-to-date and organized chronologically and by topic
    as well." The report ([page
    17](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=27))
    also notes that, at the time it was compiled, only 28.1% of House
    Member, committee, and leadership websites provided press releases
    organized by topic.

[^570]: Instructions for WIDAinc can be found at HouseNet → Technology →
    [Web Solutions](http://housenet.house.gov/keywords/webassistance) →
    Tools → WIDA → WIDA Include (WIDAinc).

[^571]: The Congressional Management Foundation's [*2007 Gold Mouse
    Report: Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) recommends that "Links should be descriptive and clear
    enough that the user can tell where it leads."

    [Checkpoint 13.1 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-meaningful-links)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should:

    > Clearly identify the target of each link. \[Priority 2\]
    >
    > [*[Link
    > text]{.underline}*](http://www.w3.org/TR/WCAG10/#link-text%23link-text)
    > should be meaningful enough to make sense when read out of context
    > \-- either on its own or as part of a sequence of links. Link text
    > should also be terse.
    >
    > For example, in HTML, write \"Information about version 4.3\"
    > instead of \"click here\". In addition to clear link text, content
    > developers may further clarify the target of a link with an
    > informative link title (e.g., in HTML, the \"title\" attribute).

    Note that the Jaws screen reader can be configured so that it will
    read which ever is larger -- the text of the link or the value of
    the "title" attribute.

    An alternative technique to using the "title" attribute, that has
    been suggested is to put the additional information within \<span\>
    tags and give the tag a class (e.g. class=\"hidden\"), where the
    class places the text off screen and minimizes the size (e.g.,
    position:absolute;left:-999em; font-size:1%).

    A technique to avoid at the current time is adding the additional
    text to the link in a \<span\> with a class value that has a
    media=\"screen\" style sheet with a display:none property and a
    media=\"aural\" (or a media=\"speech\") style sheet without the
    display:none property. The Jaws screen reader (which currently has
    about 75% of the screen reader market) uses the screen style sheet
    (and not the aural (or speech) style sheet) to build its audio
    output. (See also, Gez Lemon's "Screen Readers and display:none,"
    Juicy Studio (October 12, 2007), for an apparent bug in how Jaws and
    Window-Eyes processes the "display:none" property.)

[^572]: Using \<a href=\"{HTMLFILE_LINK}\" title=\"**{TITLE}**\"\> is
    discouraged because the **{TITLE}** field may include a quotation
    mark that may be interpreted as the end of the "title" attribute of
    the \<a\> tag.

[^573]: [Checkpoint 13.4 \[priority 2\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-clear-nav-mechanism)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "Use navigation mechanisms in a consistent
    manner."

    [Section 4 of the
    W3C](http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation) *Core
    Techniques for Web Content Accessibility Guidelines 1.0* further
    provides that:

    > A consistent style of presentation on each page allows users to
    > locate navigation mechanisms more easily but also to skip
    > navigation mechanisms more easily to find important content. This
    > helps people with learning and reading disabilities but also makes
    > navigation easier for all users. Predictability will increase the
    > likelihood that people will find information at your site, or
    > avoid it when they so desire.
    >
    > Examples of structures that may appear at the same place between
    > pages:

    navigation bars

    the primary content of a page

    > . . .
    >
    > A navigation mechanism creates a set of paths a user may take
    > through your site. Providing navigation bars, site maps, and
    > search features all increase the likelihood that a user will reach
    > the information they seek at your site. If your site is highly
    > visual in nature, the structure might be harder to navigate if the
    > user can\'t form a mental map of where they are going or where
    > they have been. To help them, content developers should describe
    > any navigation mechanisms. It is crucial that the descriptions and
    > site guides be accessible since people who are lost at your site
    > will rely heavily on them.

    The Congressional Management Foundation's [*2006 Gold Mouse Report:
    Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=73)
    (page 63) recommends that Congressional websites should:

    > **Keep your format and navigation consistent on every page of your
    > site:** Don't force your audience to learn new formatting and
    > navigational rules on every page of your site. Each page should
    > follow the same pattern. ***Sen. John Cornyn***'s Web site is a
    > model of clearly and consistently organized information. The menu
    > headers and options are clear, and they stay the same throughout
    > the site.

    The Congressional Management Foundation's [*2007 Gold Mouse Report:
    Lessons from the Best Web Sites on Capitol
    Hill*](http://nposoapbox.s3.amazonaws.com/cmfweb/2007_GoldMouseReport.pdf#page=52)
    (page 40) also notes that "maintaining consistent design and
    navigation" is an important element in making websites "easy for all
    Americans to use, including constituents with disabilities".

[^574]: [Checkpoint 14.3 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-consistent-style)
    *Web Content Accessibility Guidelines 1.0* provides that an
    accessible website should "\[c\]reate a style of presentation that
    is consistent across pages".

[^575]: Section 7.14 of the *United States Government Printing Office
    Style Manual* (2000) recommends using "signup".

[^576]: [Checkpoint 13.8 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-front-loading) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "\[p\]lace distinguishing information at the
    beginning of headings, paragraphs, lists, etc."

    Section 5.1(2) of the W3C *[Core Techniques for Web Content
    Accessibility Guidelines
    1.0](http://www.w3.org/TR/WCAG10-CORE-TECHS/#writing-style)*
    recommends:

    > State the topic of the sentence or paragraph at the beginning of
    > the sentence or paragraph (this is called \"front-loading\"). This
    > will help both people who are skimming visually, but also people
    > who use speech synthesizers. \"Skimming\" with speech currently
    > means that the user jumps from heading to heading, or paragraph to
    > paragraph and listens to just enough words to determine whether
    > the current chunk of information (heading, paragraph, link, etc.)
    > interests them. If the main idea of the paragraph is in the middle
    > or at the end, speech users may have to listen to most of the
    > document before finding what they want. Depending on what the user
    > is looking for and how much they know about the topic, search
    > features may also help users locate content more quickly.

    Jakob Nielsen's article "[F-Shaped Pattern For Reading Web
    Content](http://www.useit.com/alertbox/reading_pattern.html)" (April
    17, 2006), based on a study of the eye movements of 232 website
    users, recommends that Web designers:

    > **Start subheads, paragraphs, and bullet points with
    > information-carrying words** that users will notice when scanning
    > down the left side of your content . . . . They\'ll read the third
    > word on a line much less often than the first two words.

[^577]: Section 5.1(3) of the W3C [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#writing-style)
    recommends "Limit each paragraph to one main idea."

[^578]: [Checkpoint 14.1 \[priority 1\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-simple-and-straightforward)
    *Web Content Accessibility Guidelines 1.0* provides that accessible
    websites should "Use the clearest and simplest language appropriate
    for a site\'s content."

    [Readability Test](http://juicystudio.com/services/readability.php)
    calculates the approximate grade level of the writing on a Web page
    using the Guuning-Fox Index and Flesch/Flesch--Kincaid Readability
    Tests (Flesch Reading Ease and Flesch--Kincaid Grade Level. Jakob
    Nielsen and Hoa Loranger's *Prioritizing Web Usability*, 2006, p.34,
    recommends that websites written for adult audiences should be
    written at an 8^th^ grade reading level.

[^579]: Section 5.1(5) of the W3C [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#writing-style)
    recommends "Favor words that are commonly used. For example, use
    'begin' rather than 'commence' or use 'try' rather than 'endeavor.'"

    *Prioritizing Web Usability*, by Jakob Nielsen and Hoa Loranger,
    2006 (p. 80) observes that:

    > One of the biggest problems on the Web is that companies don't
    > want to come clean and say what they are doing in plainspoken
    > language on their sites. This continues to be critical because Web
    > users are extremely impatient and allocate so little time to each
    > page. The more florid the descriptions, the more users tune them
    > out and go elsewhere. It's essential to quickly state what you are
    > offering users and what's in it for them.

    As William Strunk, Jr. and E. B. White's *The Elements of Style*
    (3^rd^ edition, p. 76) puts it:

    > Avoid the elaborate, the pretentious, the coy, and the cute. Do
    > not be tempted by a twenty-dollar word when there is a ten-center
    > handy, ready and able.

[^580]: Section 5.1(6) of the W3C [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#writing-style)
    recommends "Use active rather than passive verbs."

    As William Strunk, Jr. and E. B. White's *The Elements of Style*
    (3^rd^ edition, p. 18) puts it:

    > The active voice is usually more direct and vigorous than the
    > passive:
    >
    > I shall always remember my first visit to Boston.
    >
    > This is much better than
    >
    > My first visit to Boston will always be remembered by me.
    >
    > The latter sentence is less direct, less bold, and less concise.

[^581]: Section 5.1(7) of the W3C [*Core Techniques for Web Content
    Accessibility Guidelines
    1.0*](http://www.w3.org/TR/WCAG10-CORE-TECHS/#writing-style)
    recommends "Avoid complex sentence structures."

[^582]: A complete list of counties, by congressional district, is
    contained in the *Congressional Directory* at
    <http://www.gpoaccess.gov/cdirectory/browse.html>.

[^583]: For the list of caucuses registered with the House
    Administration Committee, see
    <http://cha.house.gov/index.php?option=com_content&task=view&id=45&Itemid=37>.

[^584]: The website of the Shipbuilding Caucus is in the process of
    being migrated from the website of the late Rep. Joanne Davis to the
    website of Rep. Gene Taylor.

[^585]: "Dublin Core" is the official implementation of ISO Standard
    15836-2003 and NISO Standard Z39.85-2001.

[^586]: Because these tags have values that are likely to remain
    consistent throughout the entire website, it is appropriate to have
    them contained in a server-side include, which could then be invoked
    on each HTML page.

    The "profile" attribute of the \<head\> tag should **not** be used
    as a substitute for the server-side include. [Section 7.4.4 of the
    W3C](http://www.w3.org/TR/html4/struct/global.html#profiles) *HTML
    4.01 Specification* (which defines the \<head\> tag "profile"
    attribute) reserves the profile file for definitions of the "name"
    attribute of each \<meta\> tag, rather than as a repository of the
    \<meta\> tags themselves. In the absence of a W3C standard for
    formatting profile files (§ 7.4.4 specifically provides that it
    "does not define formats for profiles"), the Global Multimedia
    Protocols Group has proposed that the profile file be a separate
    (X)HTML file that use the \<dl\>, \<dt\>, and \<dd\> tags to define
    the \<meta\> tag "name" attributes (see the GMPG's [*XMDP:
    Introduction and Format
    Description*](http://www.gmpg.org/xmdp/description)).

[^587]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=76)
    (page 66) recommends that "Every congressional Web site should
    prominently display basic contact information, including . . . their
    e-mail address or a link to their contact form".

[^588]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=76)
    (page 66) praises the website of Rep. John Larson for explaining why
    the office does not have a public e-mail address (see
    <http://www.house.gov/larson/emailaddress.htm>).

[^589]: See, e.g., Bert Bos' "[Character
    Encodings](http://www.w3.org/International/O-charset)".

    Use of UTF-8 (or UTF-16) is also consistent with the avoiding the
    problems associated with XML declarations (see footnote for
    \<!DOCTYPE\> declarations #(2)).

[^590]: UTF-8 is the successor to the series of standards that included
    ISO 8859-1.

[^591]: References to the website's designer (or the designer's
    employer) should not be visible on the Web page itself. The
    [*Members' Congressional
    Handbook*](http://cha.house.gov/official_and_representational_expenses_continued.aspx#Content)
    (Web Sites, Content, § 5), issued by the House Administration
    Committee, provides that:

    > The content of a Member's Web site: . . .
    >
    > 5\. May not include any advertisement for any private individual,
    > firm, or corporation, or imply in any manner that the government
    > endorses or favors any specific commercial product, commodity, or
    > service.

    An identical requirement is contained in the [*Committee's
    Congressional
    Handbook*](http://cha.house.gov/committee_handbook.aspx#content)
    (Web Site Regulations, Content, § e).

[^592]: Only use words that are relevant to what is on the page -- do
    not use words that are irrelevant even if you believe that doing so
    will attract people to your site through search engines. In addition
    to the ethical questions that such practices raise, also consider
    Jakob Nielsen's and Hoa Loranger's observation in *Prioritizing Web
    Usability*, 2006 (p. 18):

    > You might ask, "What's the harm in attracting users even if you
    > don't have the product they want? The worst they can do is leave."
    > But actually, they can do worse than leaving: They can never
    > return. Once users have been disappointed several times after
    > clicking your links in a search engine, they may well decide to
    > ignore your site in the future.

[^593]: The Congressional Management Foundation's [*2006 Gold Mouse
    Report: Recognizing the Best Web Sites on Capitol
    Hill*](http://www.cmfweb.org/storage/cmfweb/documents/CMF_Pubs/2006GoldMouseReport.pdf#page=79)
    (page 69) praises Rep. Shelley Berkley's website for indicating when
    each page was last updated.

[^594]: [Checkpoint 4.3 \[priority 3\] of the
    W3C](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-lang) *Web
    Content Accessibility Guidelines 1.0* provides that accessible
    websites should "Identify the primary natural language of a
    document." [Checkpoint
    4.1](http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-changes)
    \[priority 1\] provides that accessible websites should also
    "Clearly identify changes in the natural language of a document\'s
    text and any text equivalents (e.g., captions)."

    The standard for codes to identify individual languages is set out
    in [RFC 4646](http://www.rfc-editor.org/rfc/rfc4646.txt) (a
    simplified version is available at the W3C's "[Language tags in HTML
    and
    XML](http://www.w3.org/International/articles/language-tags/Overview.en.php)").

[^595]: Spanish is the primary language of over 10% of the population of
    49 of the 53 congressional districts of California; and is the
    primary language of over 50% of the population of California's
    29^th^, 32^nd^, 35^th^, 39^th^, 40^th^, and 48^th^ Congressional
    Districts, according to the Asian Pacific American Legal Center of
    Southern California's [*California Speaks: Language Diversity and
    English Proficiency by Legislative
    District*](http://apalc.org/demographics/wp-content/uploads/2006/09/apalc_californiaspeaks.pdf#page=139)
    (pp. 137-189).

    A collection of U.S. Government material in Spanish is available at

    http://www.usa.gov/gobiernousa/index.shtml

[^596]: A collection of U.S. Government material in Arabic is available
    at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Arabic>

[^597]: The Unicode 5.0 Standard for Arabic script is set out at
    <http://www.unicode.org/charts/PDF/U0600.pdf>; with supplemental
    material at <http://www.unicode.org/charts/PDF/U0750.pdf>,
    <http://www.unicode.org/charts/PDF/UFB50.pdf>, and
    <http://www.unicode.org/charts/PDF/UFE70.pdf>.

[^598]: Armenian is the primary language of over 10% of the population
    of California's 29^th^ Congressional District, according to the
    Asian Pacific American Legal Center of Southern California's
    [*California Speaks: Language Diversity and English Proficiency by
    Legislative
    District*](http://apalc.org/demographics/wp-content/uploads/2006/09/apalc_californiaspeaks.pdf#page=167)
    (p. 165).

    A collection of U.S. Government material in Armenian is available at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Armenian>

[^599]: The Unicode 5.0 Standard for Armenian script is set out at
    <http://www.unicode.org/charts/PDF/U0530.pdf>; with supplemental
    material at <http://www.unicode.org/charts/PDF/U0530.pdf>.

[^600]: Chinese is the primary language of over 10% of the population of
    California's 8^th^, 12^th^, and 29^th^ Congressional Districts,
    according to the Asian Pacific American Legal Center of Southern
    California's [*California Speaks: Language Diversity and English
    Proficiency by Legislative
    District*](http://apalc.org/demographics/wp-content/uploads/2006/09/apalc_californiaspeaks.pdf#page=146)
    (pp. 144, 148, and 165).

    A collection of U.S. Government material in Chinese is available at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Chinese>

[^601]: The Unicode 5.0 Standard for Unihan (the CJK Unified Ideographs)
    is set out at <http://www.unicode.org/charts/unihan.html>.

[^602]: A collection of U.S. Government material in Flemish is available
    at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Dutch>

[^603]: The 2000 U.S. Census indicates that 5.3% of households in Maine
    and 4.7% of households in Louisiana speak French.

    A collection of U.S. Government material in French is available at

    http://www.pueblo.gsa.gov/multilanguage/multilang.htm#French

[^604]: A collection of U.S. Government material in German is available
    at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#German>

[^605]: A collection of U.S. Government material in Greek is available
    at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Greek>

[^606]: The Unicode 5.0 Standard for modern Greek script is set out at
    <http://www.unicode.org/charts/PDF/U0370.pdf>; with supplemental
    material at <http://www.unicode.org/charts/PDF/U1F00.pdf>.

[^607]: A collection of U.S. Government material in Haitian Creole is
    available at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Haitian-Creole>

[^608]: A collection of U.S. Government material in Hebrew is available
    at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Hebrew>

[^609]: The Unicode 5.0 Standard for Hebrew script is set out at
    <http://www.unicode.org/charts/PDF/U0590.pdf>; with supplemental
    material at <http://www.unicode.org/charts/PDF/UFB00.pdf>.

[^610]: A collection of U.S. Government material in Hindi is available
    at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Hindi>

[^611]: The Unicode 5.0 Standard for Devanagari script is set out at
    <http://www.unicode.org/charts/PDF/U0900.pdf>.

[^612]: A collection of U.S. Government material in Hmong is available
    at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Hmong>

[^613]: For information on Pahawh Hmong script, see
    <http://www.omniglot.com/writing/hmong.htm>.

[^614]: A collection of U.S. Government material in Italian is available
    at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Italian>

[^615]: A collection of U.S. Government material in Japanese is
    available at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Japanese>

[^616]: The Unicode 5.0 Standard for Hiragana script is set out at
    <http://www.unicode.org/charts/PDF/U3040.pdf>.

[^617]: The Unicode 5.0 Standard for Katakana script is set out at
    <http://www.unicode.org/charts/PDF/U30A0.pdf>; with supplemental
    material at <http://www.unicode.org/charts/PDF/U31F0.pdf> and
    <http://www.unicode.org/charts/PDF/UFF00.pdf>.

[^618]: Korean is the primary language of over 5% of the population of
    California's 33^rd^ Congressional District, according to the Asian
    Pacific American Legal Center of Southern California's [*California
    Speaks: Language Diversity and English Proficiency by Legislative
    District*](http://apalc.org/demographics/wp-content/uploads/2006/09/apalc_californiaspeaks.pdf#page=171)
    (p. 169).

    A collection of U.S. Government material in Korean is available at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Korean>

[^619]: For information on the scripts associated with Korean, see
    <http://www.omniglot.com/writing/korean.htm>.

[^620]: The Unicode 5.0 Standard for Hangeul script is set out at
    <http://www.unicode.org/charts/PDF/UAC00.pdf>.

[^621]: A collection of U.S. Government material in Lao is available at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Laotian>

[^622]: The Unicode 5.0 Standard for Lao script is set out at
    <http://www.unicode.org/charts/PDF/U0E80.pdf>.

[^623]: Persian is the primary language of over 5% of the population of
    California's 30^th^ Congressional District, according to the Asian
    Pacific American Legal Center of Southern California's [*California
    Speaks: Language Diversity and English Proficiency by Legislative
    District*](http://apalc.org/demographics/wp-content/uploads/2006/09/apalc_californiaspeaks.pdf#page=168)
    (p. 166).

    A collection of U.S. Government material in Persian is available at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Farsi>

[^624]: For information on representing Persian text on the Web, see
    Behdad Esfahbad's [*Persian Computing with
    Unicode*](http://behdad.org/download/Publications/persiancomputing/a007.pdf),
    April 2004.

[^625]: A collection of U.S. Government material in Polish is available
    at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Polish>

[^626]: A collection of U.S. Government material in Portuguese is
    available at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Portuguese>

[^627]: a collection of U.S. Government material in Punjabi is available
    at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Punjabi>

[^628]: The Unicode 5.0 Standard for Gurmukhi script is set out at
    <http://www.unicode.org/charts/PDF/U0A00.pdf>.

[^629]: A collection of U.S. Government material in Russian is available
    at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Russian>

[^630]: The Unicode 5.0 Standard for Cyrillic script is set out at
    <http://www.unicode.org/charts/PDF/U0400.pdf>; with supplemental
    material at <http://www.unicode.org/charts/PDF/U0500.pdf>.

[^631]: A collection of U.S. Government material in Samoan is available
    at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Samoan>

[^632]: Tagalog is the primary language of over 5% of the population of
    California's 7^th^, 12^th^, 13^th^, and 51^st^ Congressional
    Districts, according to the Asian Pacific American Legal Center of
    Southern California's [*California Speaks: Language Diversity and
    English Proficiency by Legislative
    District*](http://apalc.org/demographics/wp-content/uploads/2006/09/apalc_californiaspeaks.pdf#page=145)
    (pp. 143, 148, 149, and 187).

    A collection of U.S. Government material in Tagalog is available at

    http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Tagalog

[^633]: The Unicode 5.0 Standard for Tagalog script is set out at
    <http://www.unicode.org/charts/PDF/U1700.pdf>.

[^634]: A collection of U.S. Government material in Thai is available at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Thai>

[^635]: The Unicode 5.0 Standard for Thai script is set out at
    <http://www.unicode.org/charts/PDF/U0E00.pdf>.

[^636]: A collection of U.S. Government material in Ukrainian is
    available at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Ukrainian>

[^637]: Vietnamese is the primary language of over 5% of the population
    of California's 15^th^, 16^th^, 46^th^, and 47th Congressional
    Districts, according to the Asian Pacific American Legal Center of
    Southern California's [*California Speaks: Language Diversity and
    English Proficiency by Legislative
    District*](http://apalc.org/demographics/wp-content/uploads/2006/09/apalc_californiaspeaks.pdf#page=153)
    (pp. 151, 152, 182, and 183).

    A collection of U.S. Government material in Vietnamese is available
    at

    <http://www.pueblo.gsa.gov/multilanguage/multilang.htm#Vietnamese>

[^638]: This model privacy policy is intended to be consistent with the
    privacy notice content regulations issued pursuant to the:

    Children's Online Privacy Protection Act - regulations set out at
    [16 C.F.R. §
    312.4](http://a257.g.akamaitech.net/7/257/2422/11feb20051500/edocket.access.gpo.gov/cfr_2005/janqtr/pdf/16cfr312.4.pdf)(b)(2);

    Privacy Act - regulations set out at [OMB Memorandum M-99-18,
    attachment (Guidance and Model Language for Federal Web Site Privacy
    Policies)](http://www.whitehouse.gov/omb/memoranda/m99-18attach.html);

    E-Government Act -- regulations are set out at [OMB Memorandum
    M-03-22,](http://www.whitehouse.gov/omb/memoranda/m03-22.html#a)
    [attachment
    A](http://www.whitehouse.gov/omb/memoranda/m03-22.html#a) , § III.

[^639]: For HIR hosted websites, use
    "http://www.house.gov/house/privacy.shtml".

[^640]: For HIR hosted websites, use "House Information Resources".

[^641]: This model privacy policy is intended to be consistent with the
    E-Government Act regulations set out at [OMB Memorandum
    M-03-22,](http://www.whitehouse.gov/omb/memoranda/m03-22.html#a)
    [attachment
    A](http://www.whitehouse.gov/omb/memoranda/m03-22.html#a) , § IV;
    and with [§ 2 of the W3C](http://www.w3.org/TR/P3P/#Referencing)
    *Platform for Privacy Preferences 1.0 (P3P1.0) Specification*.

[^642]: This model privacy policy is intended to be consistent with the
    E-Government Act regulations set out at [OMB Memorandum
    M-03-22,](http://www.whitehouse.gov/omb/memoranda/m03-22.html#a)
    [attachment
    A](http://www.whitehouse.gov/omb/memoranda/m03-22.html#a) , § IV;
    and with [§ 3 of the W3C](http://www.w3.org/TR/P3P/#P3P_markup)
    *Platform for Privacy Preferences 1.0 (P3P1.0) Specification*.

[^643]: These P3P \<link\> instructions are intended to be consistent
    with the E-Government Act regulations set out at [OMB Memorandum
    M-03-22,](http://www.whitehouse.gov/omb/memoranda/m03-22.html#a)
    [attachment
    A](http://www.whitehouse.gov/omb/memoranda/m03-22.html#a) , § IV;
    and with [§ 2.2.3 of the W3C](http://www.w3.org/TR/P3P/#syntax_link)
    *Platform for Privacy Preferences 1.0 (P3P1.0) Specification*.

[^644]: These P3P Compact Policy instructions are intended to be
    consistent with the E-Government Act regulations set out at [OMB
    Memorandum
    M-03-22,](http://www.whitehouse.gov/omb/memoranda/m03-22.html#a)
    [attachment
    A](http://www.whitehouse.gov/omb/memoranda/m03-22.html#a) , § IV;
    and with [§ 4 of the
    W3C](http://www.w3.org/TR/P3P/#compact_policies) *Platform for
    Privacy Preferences 1.0 (P3P1.0) Specification*.