Content deleted Content added
Tag: references removed |
m Reverted edits by 118.116.99.231 to last revision by Falcon8765 (HG) |
||
Line 30:
With growing specialization within [[communication design]] and [[information technology]] fields, there is a strong tendency to draw a clear line between ''web design'' specifically for web pages and ''[[web development]]'' for the overall logistics of all web-based services.
== Accessible Web design ==
{{Main|Web accessibility}}
To be accessible, web pages and sites must conform to certain accessibility principles. These accessibility principles are known as the [[WCAG]] when talking about content. These can be grouped into the following main areas.<ref>{{cite journal|date=December 11, 2008|title=Web Content Accessibility Guidelines (WCAG) 2.0|issue=2|url=http://www.w3.org/TR/WCAG20/}}</ref>
* Use [[semantic markup]] that provides a meaningful structure to the document (i.e. web page)
* Semantic markup also refers to semantically organizing the web page structure and publishing web services description accordingly so that they can be recognized by other web services on different web pages. Standards for semantic web are set by [[IEEE]]
* Use a valid [[markup language]] that conforms to a published [[Document Type Definition|DTD]] or [[XML schema|Schema]]
* Provide text equivalents for any non-text components (e.g. images, multimedia)
* Use [[hyperlinks]] that make sense when read out of context. (e.g. avoid "Click Here")
* Don't use [[Framing (World Wide Web)|frames]]
* Use [[Cascading Style Sheets|CSS]] rather than [[Tableless web design|HTML tables for layout]]
* Author the page so that when the source code is read line-by-line by [[user agents]] (such as [[screen reader]]s) it remains intelligible. (Using tables for design will often result in information that is not.)
However, W3C permits an exception where tables for layout either make sense when linearized or an alternate version (perhaps linearized) is made available.
Website accessibility is also changing as it is impacted by Content Management Systems that allow changes to be made to webpages without the need of obtaining programming language knowledge.
It is very important that several different components of Web development and interaction can work together in order for the Web to be accessible to people with disabilities. These components include:
* content - the information in a Web page or Web application, including:
** natural information such as text, images, and sounds
** code or markup that defines structure, presentation, etc.
* Web browsers, media players, and other "user agents"
* assistive technology, in some cases - screen readers, alternative keyboards, switches, scanning software, etc.
* users' knowledge, experiences, and in some cases, adaptive strategies using the Web
* developers - designers, coders, authors, etc., including developers with disabilities and users who contribute content
* authoring tools - software that creates Web sites
* evaluation tools - Web accessibility evaluation tools, HTML validators, CSS validators, etc.
== History ==
| |||