To view graphic version of this page, refresh this page (F5)

Skip to page body

Web Accessibility Standards and Guidelines

Text:Text Only
Text Size: Increase Font Size Decrease Font Size

The City and County of San Francisco has adopted enhanced Web Development guidelines based upon the Federal Access Board’s Section 508 Guidelines (a)-(p). Enhancements to these guidelines have been made to address new technologies and to provide more robust detail for developers. References to Web Content Accessibility Guidelines have been included as well as custom checkpoints.

  1. Provide “Alternate Text” Equivalent for Non-Text Content
    1. All meaningful non-text elements are required to contain a text equivalent, for example, by providing an ALT attribute, or in element content. Non-text elements include, but are not limited to, images, image map regions, applets and programmatic objects, frames, scripts, stand-alone audio files, audio tracks of video, and video.
      1. An ALT attribute will not exceed 150 characters.
      2. A LONGDESC attribute is required within an element if alt text exceeds 150 characters.
      3. Elements which are strictly for decoration, such as bullets, will have an ALT attribute defined with no value (e.g., alt="").
    2. All OBJECT and APPLET elements are required to contain element content. These elements typically use technologies that are not available to all users. The element content or the ALT attribute shall be used to describe the purpose of the applet element. The element content shall be used to describe the purpose of the object element.
    3. When EMBED elements are used, the NOEMBED element is required in the page. EMBED elements present functionality not available to all users. The NOEMBED element can be used to provide a description.

Additional Requirements:

Page Content:

  • Contact information should be easily identified for each site. Contact information should include email, telephone, and if available, text telephone (TTY).
  • Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). [Ref: WCAG 4.1, P1]
  • Ensure that equivalents for dynamic content are updated when the dynamic content changes. [Ref: WCAG 6.2, P1]
  • Use the clearest and simplest language appropriate for a site's content. [Ref: WCAG 14.1, P1]
  • Clarify the first appearance of acronyms on each page by providing the full wording of the acronym followed by the acronym in parenthesis.
Last updated: 5/12/2009 5:13:08 PM