guidelines | design principals | maintaining accessibility | priorities
The State of Kansas guidelines are based in part on the work of the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C) and their Web Content Accessibility Guidelines 1.0 (WCAG 1.0). This revision also encompasses the rules for Web-based intranet and Internet information and applications required of Federal departments and agencies (and others as applicable) by section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d) and takes into account the draft of the W3C’s Web Content Accessibility Guidelines 2.0 (WCAG 2.0). Where relevant, the number of the corresponding WCAG 1.0 guideline and Section 508 standard is listed. (When available, there are links to the corresponding guidelines in the hypertext version of this document).
The following items, more general than the prioritized guidelines below, are considered "best practices". They apply broadly to all Web pages.
In order to satisfy many of the accessibility guidelines, it is necessary to use version 4.0+ of HTML in combination with Cascading Style Sheets (CSS) version 1.0+ For example, do not use proprietary or browser-dependent HTML tags such as <blink> or <marquee>.
Whenever possible, avoid deprecated features of W3C technologies. Deprecated features are considered obsolete and will be replaced in future versions. For example, the HTML <font> tag will be replaced by CSS.
Tables should be used to mark up truly tabular information rather than using them to control page layout. Once user agents better support style sheet positioning, tables should not be used for layout.
Avoid creating pages that periodically auto-refresh.
Use the clearest and simplest language appropriate for a site's content.
Divide large blocks of information into more manageable groups where natural and appropriate.
Create alternative, accessible pages only when other solutions fail because alternative pages are typically updated less often than "primary" pages. An out-of-date page may be as frustrating as an inaccessible one since, in both cases, the information on the original page is unavailable. Before resorting to an alternative page, reconsider the design of the original page; making it accessible is likely to improve it for all users. (See also Priority 1, #19.)
Once your site has met the State of Kansas Web Content Accessibility Guidelines it is imperative that the site continue to remain in compliance with the guidelines on an ongoing basis. Web authors and administrators must assure that all new pages and changes to site design (e.g., changes in navigation or color scheme) maintain full accessibility compliance.
Each item on the following list has a priority level assigned based on the item's impact on accessibility.
Web developers must satisfy this item. All Section 508 Standards are included in Priority 1. These guidelines represent the most fundamental accessibility features.
Web developers must satisfy this item. These guidelines represent more complex accessibility feature. Generally, these items would be addressed after satisfying Priority 1 items.
Web developers may satisfy this item. These guidelines represent accessibility features that offer the broadest level of accessibility to web pages.
Kansas.gov - a service of the Information Network of Kansas, Inc. |
created: 1.10.2002 |
modified: 9.29.2005 |