The World Wide Web Consortium (W3C) has launched its Web Accessibility Initiative (WAI), which aims to make the Web universally accessible. The WAI ensures that web technologies such as HTML and CSS support accessibility and promotes education and research to see that the standards are understood and followed.
In addition to overseeing the development of web technologies, the WAI has created recommendation documents that address three key audiences. First, the Web ContentAccessibility Guidelines recommendation provides rules and techniques for web designers and authors on how to create content that is as accessible as possible. The Authoring Tool Accessibility Guidelines speaks to software developers making web authoring tools. Tools should make it easy to create standards-compliant content, as well as being accessible themselves. And third, the User Agent Accessibility Guidelines are for developers of browsing devices, from standard desktop graphical browsers to specialized assistive technologies.
Web Content Accessibility Guidelines
In general, to make web content accessible to everyone, there is a greater reliance on text and document structure. That is not to say that sites need to be text-only and media-free in order to be accessible to everyone. The goal is to create sites that (as the WAI puts it) "transform gracefully" when accessed via alternative methods. Some simple examples include providing alternative text for images that can be read if the image can't be viewed, or providing a text transcript of an audio track if it can't be heard. It also requires the proper use of HTML markup for document structure and Cascading Style Sheets for presentation.
The Web Content Accessibility Guidelines 1.0 document is a recommendation by the WAI for web designers and web content developers. It outlines the general principles of accessible design in the form of 14 guidelines. Each guideline is supported by a number of "checkpoints" that describe how the guideline applies. In addition, each point is given a priority rating: Priority 1 means the guideline must be followed in all cases, Priority 2 items should be addressed in order to make the material more accessible, and Priority 3 means that the point may be addressed for the most thorough compliance with standards.
Web Content Accessibility Guidelines 1.0 is a thorough and highly detailed document. What follows here is a summary of the guidelines to point you in the right direction.
Guideline 1: Provide equivalent alternatives to auditory and visual
When providing text alternatives to images, video, and audio, be sure that the text has the same function and purpose as the media it is replacing. For example, if there is a graphic of an arrow that is used as a link to the top of the page, the alternative text should read "go to the top of the page," not "arrow." In addition, consider providing an auditory track (like a narrative explanation) for video media whose meaning is lost if it can't be seen.
Guideline 2: Don't rely on color alone.
Make sure your site is usable in black and white and colors contrast sufficiently.
Guideline 3: Use markup and style sheets and do so properly.
Great strides have been made in HTML and CSS technology to aid in accessibility, but they are only successful if they are used consistently to separate style from content.
Guideline 4: Clarify natural language usage.
Identify the language of the document and mark up exceptions such as foreign words, abbreviations, and acronyms. This makes it easier for speech devices and other assistive technologies to interpret the content.
Guideline 5: Create tables that transform gracefully.
The WAI recommends that tables be used for tabular data only. In addition, taking advantage of the more descriptive HTML 4 table markup can help users with disabilities navigate through complex tables. It is also useful to provide a summary of the table's contents in the <table> tag.
Guideline 6: Ensure that pages featuring new technologies transform
Guideline 7: Ensure user control of time-sensitive changes.
Any scrolling, blinking, or otherwise moving object should be able to be paused or stopped. Audio should be able to be paused or turned off as well.
Guideline 8: Ensure direct accessibility of embedded user interfaces.
This means that if you create your own site interface using a Java applet or Flash, the interface should follow basic accessibility guidelines.
Guideline 9: Design for device-independence.
Keep in mind that users may be using a variety of input devices, such as a mouse, keyboard, voice, head wand, or other device. Take advantage of technologies that allow shortcuts to links and elements on the page.
Guideline 10: Use interim solutions.
The W3C is developing technologies that will be useful just while older browsers are catching up to the current HTML 4.0/CSS2 way of doing things. These interim solutions ensure that older browsers operate correctly.
Guideline 11: Use W3C technologies and guidelines.
This one seems like a given, but be sure to use the current technologies since they have been developed and reviewed thoughtfully to support accessibility.
Guideline 12: Provide context and orientation information.
Provide clear labels for frames, sections of the page, and any complex page structure that requires extra explanation. Keep in mind what it would be like to use your site if you couldn't see it.
Guideline 13: Provide clear navigation mechanisms.
Take measures to ensure your site is easy to navigate, including clearly identified links, a site map or index, and consistent navigation.
Guideline 14: Ensure documents are clear and simple.
Everyone benefits from web pages that are laid out clearly and use simple language.
WAI has also compiled a list of very practical applications of each of these principles in a document called Techniques for Web Content Accessibility Guidelines 1.0. It provides specific techniques that address each of the checkpoints outlined in the general guidelines document. It also acts as a gateway to a number of other resources that describe the specifics on how HTML, CSS, and other core technologies address accessibility.
The WAI Techniques document is too vast to summarize here, but the following list presents a few simple measures you can take to make your pages more accessible:
If you would like to check how accessible your web page is, try running it through a validator, such as Bobby, that will scan your page and point out accessibility issues.
Web Designing Related Interview Questions
|HTML Interview Questions||HTML 5 Interview Questions|
|Flash Interview Questions||Graphic Design Interview Questions|
|Illustrator Interview Questions||Dreamweaver Interview Questions|
|UI Developer Interview Questions||Dreamweaver CS3 Interview Questions|
|CSS Advanced Interview Questions||Web Developer Guide Interview Questions|
|Log Shipping Interview Questions||Spring Boot Interview Questions|
|UI Designer Interview Questions||Bootstrap 4 Interview Questions|
Web Designing Related Practice Tests
|HTML Practice Tests||HTML 5 Practice Tests|
|Flash Practice Tests||Graphic Design Practice Tests|
|Illustrator Practice Tests||Dreamweaver Practice Tests|
|UI Developer Practice Tests||Dreamweaver CS3 Practice Tests|
|Web Developer Guide Practice Tests||Advanced jQuery Practice Tests|
Web Designing Tutorial
Designing For A Variety Of Browsers
Designing For A Variety Of Displays
Web Design Principles For Print Designers
A Beginners Guide To The Server
Printing From The Web
Structural Html Tags
Adding Images And Other Page Elements
Specifying Color In Html
Cascading Style Sheets
Server Side Includes
Designing Graphics With The Web Palette
Audio On The Web
Video On The Web
Flash And Shockwave
Introduction To Smil
Introduction To Dhtml
Introduction To Xml
Wap And Wml
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.