Skip to main content - Skip to contact information

Accessibility Guidelines

Content editor guidelines - Contribute Users

  1. Write for the web. Write in short, clear, straightforward sentences. Use bulleted lists. Put the main point at the beginning of a paragraph. Write links that start with keywords. 
  2. Write "home page" as two words, but avoid it where possible.
  3. Do not make up unusual names for products, services, or elements of a Web site. Do not combine two or more words into one name.
  4. To make screen readers read an acronym or abbreviation as letters rather than attempting to read it as a word, use the <ACRONYM> and <ABBR> tags. Do not create new acronyms because they can cause confusion.
  5. Make links descriptive. Be sure that the link will be useful by itself, with no surrounding text. Do not use "click here," "more," "answer," or other repetitive words or phrases as links.
  6. Start links with relevant keywords.
  7. Try not to have many links that start with the same word or phrase.
  8. Start question headings with a keyword followed by the question.
    • Instead of "What is Literacy?" use "Literacy – What is it?"
  9. Make sure that the keywords are not in images.
  10. Do not create subtle differences between the text on the page and the ALT text that can trip users up when they search for words on the page.
  11. Use anchor links when a page has several topics. Keep pages from refreshing when users select an anchor link.
  12. Use many headings in content and be sure that those headings are clear, meaningful, and parallel. This guideline is critical for both sighted users and screen-reader users.
  13. Put the keyword at the beginning of the heading. If many headings are about the same thing, differentiate them in meaningful ways.
  14. Be sure that the headings are used appropriately. Do not use headings to increase text size. Headings should only be used to help users find different sections of content that vary by theme or idea.
  15. Do not use tables as design elements. Instead, minimize the use of tables to tabular data. All tables must include table header tags <th> for each column.

Web developer guidelines - Dreamweaver Users

  1. Web developers should adhere to the content editor guidelines.
  2. For designers and developers of websites: Make the site structure clear and obvious. The more obvious the structure of the site, the easier it will be for screen-reader users (as well as for sighted users) to understand and use the site.
  3. Include a "skip" link at the top of every Web page. Name it "Skip to main content." Screen readers will mispronounce content if the link is "Skip to content."
  4. Pay attention to the wording on pages and be sure that keywords that users would look up are actually on the page. (This is useful for sighted users, too.)
  5. Be sure that the headings are coded properly in HTML, for example, as <H1> <H2>, etc.
  6. Do not put a lot of text on the same page as a form.
  7. Do not put a form far down on the page or far to the right.
  8. Make sure that all fields are coded so that users do not have to switch to and from Edit mode. Use the HTML label element. To add more information than is in the label, use the title attribute.
  9. Do not put information between fields on a form.
  10. If the user has an option of filling out either of two fields, and they are mutually exclusive, inform the user with the label of the first field.
  11. Do not exclude labels from fields.