« Web design | Home | Accessibility and cross-browsing testing in web design (II part) »
By nyx | October 4, 2008
One of our main concerns here at None Interaction is to make our websites accessible for as much people as possible. There are two important problems to be tackled in this subject, one is accessibility design and the other is cross browsing testing.
Designing websites for accessibility means using the solutions available to create websites that are accessible for people with disabilities. The World Wide Web Consortium (W3C) is the entity that regulate, produce and promote the guidelines that most web designer and developers follow to create their work. Among these guidelines the W3C has established what it’s called the “Web Content Accessibility Guidelines 1.0“. It this guidelines is clearly explained how to make websites more accessible but also how to make them easier to find in the web:
Following these guidelines will also help people find information on the Web more quickly. These guidelines do not discourage content developers from using images, video, etc., but rather explain how to make multimedia content more accessible to a wide audience.
For those unfamiliar with accessibility issues pertaining to Web page design, consider that many users may be operating in contexts very different from your own:
They may not be able to see, hear, move, or may not be able to process some types of information easily or at all.
- They may have difficulty reading or comprehending text.
- They may not have or be able to use a keyboard or mouse.
- They may have a text-only screen, a small screen, or a slow Internet connection.
- They may not speak or understand fluently the language in which the document is written.
- They may be in a situation where their eyes, ears, or hands are busy or interfered with (e.g., driving to work, working in a loud environment, etc.).
- They may have an early version of a browser, a different browser entirely, a voice browser, or a different operating system.
[1st part] [2nd part]
Tags: Projects |
Comments
You must be logged in to post a comment.