Terms of Use

This is the official accessibility statement for the Virginia First People Web site, which details the features that have been implemented to improve the accessibility of its contents for all users and, in particular, for users with sensory or physical impairments.

If you have any questions or comments about the accessibility features of this site, e-mail them to info@pwnet.org

Standards Compliance

• Every page on this site is designed to comply with all Priority 1 guidelines of the W3C Web Content Accessibility Guidelines and conforms to all standards in Section 508 (29 U.S.C. ' 794d) of the Rehabilitation Act. We will continue to review and seek to extend compliance with these and other accessibility guidelines.
• Every page on this site is designed to be written in well-formed, valid XHTML with the visual layout and design controlled by valid Cascading Style Sheets.
• Every page on this site uses structured semantic markup. H1 tags are used for section titles, H2 tags for main page sub-headings. Certain specialist browsers, such as screen readers like JAWS, allow users to navigate through pages by headings and sub-headings when they are properly marked-up in this way. (For example, on this page, JAWS users can skip to the next section within the accessibility statement by pressing ALT+INSERT+2.)

Links

• Many links have title attributes that describe the link in greater detail, unless the text of the link already fully describes the target (such as the title of a page or section).
• Links are written to make sense out of context.

Visual Design

1. This site uses cascading style sheets for its visual layout and text formatting.
2. If your browser or browsing device does not support stylesheets at all, the content of each page is still readable.

Tables and Forms

All of the input elements in the forms on this site are marked up with label tags. These provide several benefits:

• Users who have difficulty navigating through a form with a mouse can, for example, click on the text beside the form elements, such as text input boxes, in order to enter those elements.
• The use of label tags allows screen readers to intelligently announce what a particular input element is, by reading the label.

Accessibility References

1. W3C accessibility guidelines, which explains the reasons behind each of the guidelines.
2. W3C accessibility techniques, which explains in detail how to implement theguideline.
3. W3C accessibility checklist, a very useful web developer's accessibility checklist.