Website Accessibility Policy
The Government Information Technology Agency (GITA) shall develop, implement and maintain a coordinated statewide plan for information technology (IT) (A.R.S. § 41-3504(A (1))) including the adoption of statewide technical, coordination, and IT Policy and Standards (A.R.S. § 41-3504(A (1(a)))).
The purpose is to establish a statewide policy that provides an accessibility model for the development and implementation of Arizona State government web sites that minimizes technical barriers to accessibility for individuals with disabilities.
⇧ top of page
This applies to all budget units. Budget unit is defined as a department, commission, board, institution or other agency of the state organization receiving, expending or disbursing state funds or incurring obligations of the state including the Arizona Board of Regents but excluding the universities under the jurisdiction of the Arizona Board of Regents and the community college districts and the legislative or judicial branches. A.R.S. § 41-3501(2).
The Budget Unit Chief Executive Officer (CEO), working in conjunction with the Budget Unit Chief Information Officer (CIO), shall be responsible for ensuring the effective implementation of Statewide Information Technology Policies, Standards, and Procedures (PSPs) within each budget unit.
⇧ top of page
To provide an accessibility model in which web content authors, format designers, and software developers within budget units understand their roles in providing persons with disabilities, access to existing and developing State web sites. This model is designed for the general public with disabilities who are able to handle general-purpose web content under ordinary operating conditions, see Attachment A (PDF), Web Site Accessibility Technical Suggestions and Examples, for further specifics.
The information presented in Attachment A (PDF) is designed to assist and aid budget unit webmasters in developing accessible web pages. Because of vast changes and improvements in information technologies, budget unit webmasters are encouraged to use other available technical methods that will promote equivalent or greater access to and use of websites in being compliance with Section 508. This accessibility model is not intended to cover other accessibility issues related to Section 508.
The accessibility model consists of the following web page features that are to be addressed for all State web sites:
- GRAPHICS Simple images; linked images; content images; graphical text; ASCII Art; list bullets; spacer images; animated graphics-text equivalent; animated graphics-frame rate.
- INFORMATION IN COLOR Information in color; color contrast.
- MOVING CONTENT Static background color; moving text.
- DOWNLOADABLE FILES Graphics in downloadable files; PDF files.
- REPETITIVE CONTENT Skipping navigation links.
- DATA TABLES Identifying row and column headers; using SCOPE to group table cells.
- MULTIMEDIA Sounds 10; speech-short clips (up to 60 seconds); speech-long clips; video-short clips (up to 10 seconds); video-long clips.
- IMAGE MAPS Image map graphics-text equivalent; client-side image map regions; server-side image map regions.
- STYLE SHEETS Style sheets.
- FORMS Forms-label placement; forms-associating labels and controls; forms-time responses.
- SCRIPTS Scripts-text equivalents; scripts-keyboard accessibility.
- APPLETS and PLUG-INS Applets and plug-ins-links; applets and plug-ins-text equivalent information or functionality.
- FRAMES Frames-labeling; frames-NOFRAMES elements.
- KEYBOARD CONTROL Keyboard control.
- TEXT-ONLY PAGES Text-only versions.
- BIOMETRIC IDENTIFICATION Alternative identification.
- EQUIVALENT FACILITATION Equivalent access.
It is the responsibility of each budget unit to remain current with the development of accessible information technology through their ADA/508 Coordinators.
- Known Limitations of this Policy
Individuals with (or without) disabilities access the Web with widely varying sets of capabilities, software, and hardware. While this policy does provide the ability for individuals with disabilities to access Web based information, this policy does not include requirements for the production of every known accessibility need, due to known limitations on existing technology. The limitations of this policy are as follows:
- Braille - this policy does not address Braille production.
- Synthesized Speech production - not covered by this policy.
- Input Modalities - no voice input, only keyboard and pointing devices.
- A.R.S. § 41-621 et seq., "Purchase of Insurance; coverage; limitations, exclusions; definitions."
- A.R.S. § 41-1335 ((A (6 & 7))), "State Agency Information."
- A.R.S. § 41-1339 (A), "Depository of State Archives."
- A.R.S. § 41-1461, "Definitions."
- A.R.S. § 41-1463, "Discrimination; unlawful practices; definition."
- A.R.S. § 41-1492 et seq., "Prohibition of Discrimination by Public Entities."
- A.R.S. § 41-2501 et seq., "Arizona Procurement Codes, Applicability."
- A.R.S. § 41-3501, "Definitions."
- A.R.S. § 41-3504, "Powers and Duties of the Agency."
- A.R.S. § 41-3521, "Information Technology Authorization Committee; members; terms; duties; compensation; definition."
- A.R.S. § 44-7041, "Governmental Electronic Records."
- Arizona Administrative Code, Title 2, Chapter 7, "Department of Administration Finance Division, Purchasing Office."
- Arizona Administrative Code, Title 2, Chapter 10, "Department of Administration Risk Management Section."
- Arizona Administrative Code, Title 2, Chapter 18, "Government Information Technology Agency."
- Statewide Information Technology Policy P100.
- Digital Millennium Copyright Act (1998).
- Title 17 United States Code.
- Title 18 United States Code § 2319 & 2320.
- Federal Rehabilitation Act, Section 508.
- Telecommunications Act of 1996, Section 255
- State of Arizona Technology Related Assistance for Individuals with Disabilities Act, Section 103.
Attachment A (PDF). Web Site Accessibility Technical Suggestions and Examples
(Attachment A, provides technical suggestions that are cited as possible good software designs and practices and does not profess to be a complete and final document. This is due to a variety of other technical methods and solutions that webmasters may want to pursue to implement the accessibility model).