|
The following City of Shreveport standards were developed using the U.S. Access
Board's Section 508 standards, supplemented by The Web Content Accessibility
Guidelines developed by World Wide Web Consortium (W3C) as a benchmark for
access to web based information and services. Resources to assist designers in
understanding and meeting these standards are detailed in the City of Shreveport
Web Designer Guide; the
Section 508 standards and links to tools and resources can be found at
http://www.section508.gov and the WCAG
Guidelines and associated resources are available at:
http://www.w3.org/tr/wai-webcontent.
Equivalent facilitation
Nothing in these standards are
intended to prevent the use of designs or technologies as alternatives to those
prescribed in these standards provided they result in substantially equivalent
or greater access to and use of a web site for people with disabilities. |
Standards
|
|
|
Examples:
- Non-text elements (images, java applets, flash files, video files, audio
files, plug-ins, etc.) have alt tag descriptions that convey the purpose or
intended meaning of the object (e.g. Alt Tags for images used as links
describe the link destination).
- Complex graphics that summarize information (graphs, charts, tables,
etc.) are accompanied by text conveying the information providing a
meaningful narrative of the information.
- Decorative graphics with no other function have empty alt descriptions
(alt= "") not missing alt descriptions.
When descriptions are lengthy or
refer to other resources or sites, a longer description will be made
available using a link or supported "longdesc".
|
|
|
Examples:
- Multimedia files on a web page has
synchronized captions.
- Video and multimedia content may include a transscript.
|
|
|
Example:
- If color is used to convey information, use graphic symbols such as
underling, asterisks or borders to identify special content.
|
|
|
Example:
- Blue on Blue, using different saturations of the same color for
background and foreground
|
|
|
Examples:
- When a document is rendered without associated style sheet, it must
still be possible to read the document.
- Provide a text equivalent for any important image or text generated by
style sheets (e.g., via the 'background-image', 'list-style', or 'content'
properties).
|
|
|
Example:
- Use standard HTML client-side image maps with appropriate alt tags for
the image and hot spots.
|
|
|
Example:
- Separate text links are provided outside of the server-side image map
that provide the same to the content that image map hot spots access.
|
|
|
Examples:
- Tables used only for layout do not have header rows or columns.
- In data tables, column and row headers are identified using the <th>
tag.
|
|
|
Example:
- Table cells are associated with the appropriate headers (e.g.
ID,
HEADERS and/or SCOPE HTML attributes).
|
|
|
Example:
- Each frame has a title that describes its purpose or the type of
information contained within the frame.
|
|
|
Example:
- When moving content images are necessary to interpreting content, the
user can pause or stop the movement.
|
|
|
Examples:
- Within scripts information is text-based or a text alternative is
provided.
- All scripts (Javascript, pop-up menus, etc.) work with
keyboard-accessible alternatives (either within or outside of the script)
that provide equivalent functionality.
|
|
|
Examples:
- When applets, plug-ins or applications (Java applets, Java scripts,
Acrobat PDF files or PowerPoint files) are not accessible to assistive
technologies you must provide an alternative means of accessing the content
within the applications (e.g., a mirror HTML file for a PDF file)
- When an applet, plug-in or application is utilized you must provide a
link to a an accessible page where the plug-in can be downloaded
|
|
|
Examples:
- Form controls have text labels adjacent to them and keyboard access to
control functionality.
- Form elements have explicitly associated labels in the markup (i.e. the
ID and FOR, HTML elements).
Dynamic HTML scripting of the form does not
interfere with assistive technologies.
|
|
|
Example:
- A link is provided to skip over lengthy lists of links (e.g.
navigational menus).
|
|
|
Example:
- Do not automatically forward, refresh, or otherwise alter pages, unless you
provide the user with a method to adjust the timing of these content changes.
|
|
|
Example:
- Identify any links that open in a new window using a referenced symbol
or plain text.
|
|
|
Example:
- Choose link text that make sense out of context and describes where the
link leads (e.g. "Get more information about us" or Get more
information about us").
|
|
|
Examples:
- A mirror page is acceptable when there is no other way to make the
content accessible, or when it offers significant advantages for ease of
navigation.
- The content for primary and mirror pages should be updated
simultaneously.
- Mirror pages must be
the functionality equivalent to primary pages (e.g. provides alternatives
for applets, scripts, plug-ns and similar applications that are not directly
accessible).
- "Text-only" and "accessible" are not synonymous; designers must
incorporate all of the above standards when designing mirror pages.
|
