The primary purpose of these HTML/XHTML Best Practices is to improve the accessibility of web resources at the University of Illinois at Urbana/Champaign for students, faculty, staff, and the general public.
The typical approach to web accessibility is a "repair" approach which focuses on meeting the technical requirements of either the Section 508 or W3C WCAG 1.0 accessibility standards. This accessibility repair usually results in the resources becoming more "technically accessible" but still remaining functionally unusable by many people with
In a sense, nobody is in charge of the web. The web is an open standard, with no restrictions on who can post content, or what that content should be about. The web belongs to everybody, and so it belongs to nobody. The openness and decentralization of the web is one of its greatest strengths. But it wouldn't work at all without some sort of standard way of encoding the information. That's where the World Wide Web consortium (W3C) comes in.
The W3C is an international, vendor-neutral group that determines the protocols and standards for the web. They
The Web Accessibility Initiative (WAI) is a branch of the World Wide Web Consortium (W3C) which aims to improve the accessibility of the World Wide Web for those using all kinds of user agents as well as web browsers, such as screen readers, mobile phones and braille browsers. The WAI has developed a series of guidelines to this end, particularly with physically disabled internet users in mind.
Compliance with these guidelines is wise, not only because excluding any group of people is inadvisable and unethical, but also because WAI compliant sites
When developing web sites, making them as accessible as possible is crucial, both to people with different kinds of disabilities as well as to all kinds of different devices, web browsers and screen readers etc.
Why? Out of respect for the user, while making the web site available to as many users as possible.
You need to be aware of the fact that the web site will not look the same to all visitors, not all UAs handle CSS and other things. The solution isn’t to code in HTML 3.2 and avoid using CSS and JavaScript, since that’s just plain dumb.