The Web is for everybody! | |
What is Web Accessibility Compliance? | |
Web Accessibility Compliance works to ensure equal opportunity for all, as defined by the W3C Web Accessibility Initiative & Section 508. The Tiki Team firmly believes in providing equal opportunity, access, and availability to all.
|
Table of contents | |
WAI, Section 508 and Related Legislation | |
Introduction | |
Disability rights laws are intended to remove barriers, and provide equal opportunity & access for all. The Americans with Disabilities Act (ADA) required removal of physical barriers – wheelchair ramps, curb cuts, Braille elevator buttons, etc.
The World Wide Web presents a new set of challenges to help make another aspect of life accessible for all. Access to electronic and information technology for people with disabilities is a significant law and policy issue.
|
Statistics | |
So what if users with disabilities cannot access a website?
|
Inaccessibility = Barriers to Information | |
Inaccessible technology interferes with an individual's ability to obtain and use information quickly and easily. Accessible web design removes barriers so that as many people as possible can access & have equal opportunity to work interactively online.
|
Rehabilitation Act | |
|
Section 508: What’s Covered | |
|
Section 508: What’s not Covered | |
|
Accessibility Initiatives | |
|
Related Legislation | |
|
Why Accessibility Matters | |
Introduction | |
|
Usability vs. Accessibility | |
Many people confuse usability and accessibility. In fact, they’re two very similar concepts, but each is also very distinct. Often times people think that a usable site is accessible (and vice versa). While the two are not exclusive, it is important to understand the difference.
|
Types of Disabilities | |
The following are the most common disabilities identified in Section 508.
Mobility disabilities, either permanent or short-term, limit ability to use a mouse. Since manipulating a mouse cursor can be laborious, providing a feature such as the option to skip repetitive navigation links can help these users get to the content of a page more directly. |
Assistive Technology (AT) | |
Assistive technology devices are designed to allow a person with a particular disability to interact with his environment.
|
Benefits of Accessible Design | |
Many people may not use a graphical browser or may turn graphics off. This may be due to hardware limitations such as:
Some users may prefer to read content rather than display a complex presentation format. By creating accessible websites, a greater audience is being reached, thereby extending the range of communication. |
Developing Accessible Websites | |
Introduction | |
The focus of this presentation is on designing Web pages that are compliant with section 508. However, there are additional recommendations beyond section 508 that concern accessibility. Where applicable, these additional techniques are placed at the end of the appropriate section. |
Keep it Separated | |
To design accessible websites one must separate the key elements of a page.
• Content is what you say
|
Section-508 Guidelines & Applying it to Tiki | |
Color | |
Although colorful elements can richly enhance a Web page for a sight-dependent user, the content must still be accessible to those who cannot interpret colors.
|
CSS | |
All of the design and formatting issues discussed previously apply to the design of style sheets.
|
Flash | |
|
Forms | |
Typically, web-based forms are not easy for a person with a disability to complete. Complicated navigation and ambiguous instructions can create a frustrating experience.
(...more to follow...) |
Frames | |
|
Java | |
''To develop accessible code, only use the Java Foundation Classes/Swing Set (version 1.8 or newer) and:
|
JavaScript | |
While very handy & powerful, JavaScript does have limitations, particularly when it comes to accessibility. The following details common event handlers & commonly accepted practices when using JavaScript, with accessibility in mind.
|
Multimedia | |
|
Navigation | |
Image maps are ok to use as a navigational tool provided developers incorporate a few simple coding techniques to make navigation fully accessible.
Guideline (f): Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. Guideline (o): A method shall be provided that permits users to skip repetitive navigation links.
Intuitive navigation is essential to keep users oriented. Provide cues as to where the user is, where they should go, how to get there, and how to get back.
|
Non-text Elements | |
Guideline (a): A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
|
Adobe PDF files preserve the formatting and text layout perfectly for sight-dependent users. Users can download a utility from http://access.adobe.com to convert the file to make it accessible to screen readers. As of April 18, 2000, Adobe partnered with Microsoft, GW Micro and Henter-Joyce to support the Microsoft Active Accessibility (MSAA) Application Programming Interface (API).
Note: Avoid creating PDF files as graphical images |
Plug-ins | |
|
Scripts | |
Guideline (j): Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
Guideline (p): When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
|
Tables | |
It is very important to separate the structure of a page's content (information flow) from the presentation (layout). HTML was not designed to handle complex layouts and older assistive technology devices may have difficulty interpreting it. Until CSS is better supported, developers will still need to use tables for complex formatting.
Guideline (h): Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.
This technique is much more cumbersome than SCOPE.
If you use a table for layout:
|
Development Tools | |
Editors | |
|
WYSIWYG | |
Visual (WYSIWYG) HTML editors offer conveniences unavailable in text editors. Typically, WYSIWYG software is used for formatting (layout) rather than structure (content).
|
Validation | |
Testing Tiki | |
Colors | |
Colors can have a tremendous impact on not only how we perceive information, but it can also impact our ability to access information. The following are recommendations for how to experience Tikiwiki from the perspective of a person that has difficulty with colors & certain color combinations.
|
Format | |
Test the format by changing the following browser options:
|
Media | |
How do you process information most effectively? Visually, auditorily, kinesthetically, or some other way? What if you have trouble hearing, or are completely deaf? It's important to ensure people aren't left unable to use Tikiwiki because of hearing loss. Below are some suggestions for what to consider in trying to simulate experiencing Tikiwiki as if hard of hearing, or deaf.
|
Navigation | |
|
Additional Tests | |
|
Resources | |
Toolkit | |
A-Prompt Toolkit for HTML Editors
|
References | |
Validators | |
Layout Analyzers | |
Filters | |
|
Tips for Coders | |
|
Who works here? | |
|
Discussion/participation | |