Editing Web Accessibility Initiative

From Wikipedia, the free encyclopedia

You are not currently logged in. Editing this way will cause your IP address to be recorded publicly in this page's edit history. If you create an account, you can conceal your IP address and be provided with many other benefits. Messages sent to your IP can be viewed on your talk page.

Please do not save test edits. If you want to experiment, please use the sandbox.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

If you are undoing an edit that is not vandalism, explain the reason in the edit summary rather than using only the default message.

Current revision Your text

Line 26: Line 26:

* Planning Web Accessibility Training <ref>[http://www.w3.org/WAI/training/ Planning Web Accessibility Training]</ref>

* Developing a Web Accessibility Business Case for Your Organization <ref>[http://www.w3.org/WAI/bcase/ Developing a Web Accessibility Business Case for Your Organization: Overview]</ref>

* How People with Disabilities Use the Web, a document that describes various fictitious characters with disabilities and how they use the Web in different scenarios <ref name="pwduseweb">[http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/Overview.html How People with Disabilities Use the Web]</ref>

* many introduction pages on the WAI website.

Anti-spam check. Do NOT fill this in!

The [[World Wide Web Consortium]] (W3C)'s '''Web Accessibility Initiative''' ('''WAI''') is an effort to improve the [[Web accessibility|accessibility]] of the [[World Wide Web]] (WWW or Web) for people with [[Disability|disabilities]]. People with disabilities may encounter difficulties when using computers generally, but also on the Web.
Since people with disabilities often require non-standard devices and [[user agent|browsers]], making websites more [[Accessibility|accessible]] also benefits a wide range of user agents and devices, including mobile devices, which have limited resources.

The W3C launched the Web Accessibility in 1997 with endorsement by The White House and W3C members.<ref>[http://www.w3.org/Press/WAI-Launch.html World Wide Web Consortium (W3C) Launches International Web Accessibility Initiative] Press release, 7 April 1997.</ref> 
It has several working groups and interest groups that work on guidelines, technical reports, educational materials and other documents that relate to the several different components of web accessibility.
These components include web content, web browsers and media players, authoring tools, and evaluation tools.

== Organization ==

WAI develops guidelines and other technical reports through the same process as other parts of the W3C.<ref>[http://www.w3.org/WAI/intro/w3c-process How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute]</ref> Like other W3C initiatives, the WAI consists of several working groups and interest groups, each with its own focus. Only working groups can produce technical reports that become W3C recommendations. A working group can sometimes delegate specific work to a task force, which then presents its results back to the working group for approval. Interest groups may produce reports (for example, as W3C Notes), but not recommendations.
Each of these types of groups (working group, task force, interest group) can have one or more mailing lists. They meet through conference calls at regular intervals (typically every week or every other week) and sometimes use web-based surveys to collect input or comments from participants. They can also meet face to face (one to four times per year).

=== Authoring Tool Accessibility Guidelines Working Group (AUWG) ===

The Authoring Tool Accessibility Guidelines Working Group develops guidelines, techniques and supporting resources for tools that create web content, ranging from desktop [[HTML editor|HTML editors]] to [[Content management system|content management systems]].
The accessibility requirements apply to two types of things: the user interface on the one hand, and the content produced by the tool on the other.
The working group consists of representatives from organizations that produce authoring tools, researchers, and other accessibility experts.
The working group produced the Authoring Tool Accessibility Guidelines 1.0 in 2000 and is currently working on Authoring Tool Accessibility Guidelines 2.0. It also published a document on Selecting and Using Authoring Tools for Web Accessibility.<ref>[http://www.w3.org/WAI/impl/software.html Selecting and Using Authoring Tools for Web Accessibility]</ref>

=== Education and Outreach Working Group (EOWG) ===

The Education and Outreach Working Group develops materials for training and education on Web accessibility. This working group has produced documents on a wide range of subjects, including:
* Accessibility Features of CSS <ref>[http://www.w3.org/TR/CSS-access Accessibility Features of CSS - W3C NOTE 4 August 1999]</ref>
* Curriculum for Web Content Accessibility Guidelines 1.0 <ref>[http://www.w3.org/WAI/wcag-curric/ Curriculum for Web Content Accessibility Guidelines 1.0]</ref>
* Evaluating Web Sites for Accessibility, a suite of documents about subjects such as conformance evaluation, evaluation approaches for specific contexts, involving users in web accessibility evaluation, and selecting web accessibility evaluation tools <ref>[http://www.w3.org/WAI/eval/ Evaluating Web Sites for Accessibility]</ref>
* Planning Web Accessibility Training <ref>[http://www.w3.org/WAI/training/ Planning Web Accessibility Training]</ref>
* Developing a Web Accessibility Business Case for Your Organization <ref>[http://www.w3.org/WAI/bcase/ Developing a Web Accessibility Business Case for Your Organization: Overview]</ref>
* many introduction pages on the WAI website.

Currently, the working group has a task force to support the work done in the WAI-AGE project. This project published a document that reviews literature about the needs of older users and compares these needs with those of people with disabilties as already addressed in WAI guidelines.<ref>[http://www.w3.org/WAI/WAI-AGE/ WAI-AGE Project (IST 035015)]</ref><ref>[http://www.w3.org/TR/wai-age-literature/ Web Accessibility for Older Users: A Literature Review - W3C Working Draft 14 May 2008 ]</ref>

The Education and Outreach Working Group can also review working drafts produced by other WAI working groups.

=== Evaluation and Repair Tools Working Group (ERT WG) ===

The Evaluation and Repair Tools Working Group develops technical specifications that support the accessibility evaluation and repair of Web sites. It also maintains a database of tools for evaluating Web sites and for making them more accessible (â€œrepairâ€, â€œretrofittingâ€).
The working group consists mainly of developers of such tools and researchers.
Current work focuses on
* '''Evaluation and Report Language (EARL)''': a language for expressing evaluation reports in a machine-readable way <ref>[http://www.w3.org/TR/EARL10-Schema/ Evaluation and Report Language 1.0 Schema]</ref> <ref>Evaluation and Report Language 1.0 Guide</ref>
* '''HTTP Vocabulary in RDF''', which specifies how [[Hypertext Transfer Protocol|HTTP]] requests and responses can be expressed in [[Resource Description Framework|RDF]] <ref>[http://www.w3.org/TR/HTTP-in-RDF/ HTTP Vocabulary in RDF]</ref>
* '''Representing Content in RDF''', which specifies how content (retrieved from the Web or a local storage device) can be represented in RDF <ref>[http://www.w3.org/TR/Content-in-RDF/ Representing Content in RDF]</ref>
* '''Pointer Methods in RDF''', early work on how locations in and parts of online documents can be expressed in RDF.<ref>[http://www.w3.org/WAI/ER/Pointers/WD-Pointers-20080623 Pointer Methods in RDF]</ref>

=== Protocols & Formats Working Group (PFWG) ===

The Protocols & Formats Working Group reviews all W3C technologies for accessibility before they are published as a recommendation. It has also published a note on accessibility issues of [[CAPTCHA]]<ref>[http://www.w3.org/TR/turingtest/ Inaccessibility of CAPTCHA: Alternatives to Visual Turing Tests on the Web - W3C Working Group Note 23 November 2005]</ref>, 
a paper on natural language usage for people with cognitive disabilities<ref>[http://www.w3.org/WAI/PF/natural-lang-20030326.html Natural Language Usage -- Issues and Strategies for Universal Access to Information]</ref>,
and initial work on accessibility requirements for XML-based markup languages (XML Accessibility Guidelines).

In 2006, the working group started development of a set of document and specifications for accessible [[Rich Internet application|rich internet applications]]: [[WAI-ARIA]].
<ref name="ariaroadmap2006">[http://www.w3.org/TR/2006/WD-aria-roadmap-20060926/ Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap) - W3C Working Draft 26 September 2006]. This is the first public working draft; the most recent version can always be found at [http://www.w3.org/TR/wai-aria-roadmap/ www.w3.org/TR/wai-aria-roadmap/].</ref>
<ref name="waiaria1">[http://www.w3.org/TR/wai-aria/ Accessible Rich Internet Applications (WAI-ARIA) Version 1.0 - W3C Working Draft 6 August 2008]</ref>
<ref name="waiariabp">[http://www.w3.org/TR/wai-aria-practices/ WAI-ARIA Best Practices - W3C Working Draft 4 February 2008]</ref>

=== Research and Development Interest Group (RDIG) ===

The goal of the Research and Development Interest Group is 
* to increase the incorporation of accessibility considerations into research on Web technologies, and
* to identify projects researching Web accessibility and suggest research questions that may contribute to new projects.<ref name="rdigcharter2005">[http://www.w3.org/WAI/RD/charter2 Research and Development Interest Group (RDIG) Charter]</ref>

This interest group has seen very little activity since 2004. Its current charter expired at the end of 2006. <ref name="rdigcharter2005" />

=== User Agent Accessibility Guidelines Working Group (UAWG) ===

The User Agent Accessibility Guideline Working Group develops guidelines, techniques and other documents to promote the accessibility of [[user agent|user agents]]: [[Web browser|browsers]] and [[Plug-in (computing)| plug-ins]].
The working group consists mainly of organizations that develop user agents, researchers, and other accessibility experts.
The working group published User Agent Accessibility Guidelines 1.0 (UAAG 1.0) as a W3C Recommendation in 2002, and is currently working on the second version of this specification.

=== WAI Interest Group (WAI IG) ===

The WAI Interest Group is an open group with a mailing list to which anyone can subscribe. W3C staff post announcements of new WAI documents to this mailing list to invite reviews and comments. Members of the list also post announcements of relevant events and publications, and ask advice on issues related to web accessibility.
The language of the mailing list is English; there are no parallel mailing lists in other languages.

=== Web Content Accessibility Guidelines Working Group (WCAG WG) ===

The Web Content Accessibility Guidelines Working Group produces guidelines, techniques and other supporting documents relating to the accessibility of Web content. Web content refers to any information you may find on a Web site: text, images, forms, sound, video, etcetera, regardless whether these were produced on the server side or on the client side (with a [[Client-side scripting| client-side scripting language]] such as [[JavaScript]]). Thus, the guidelines also apply to [[Rich Internet application|rich internet applications]].

The working group consists of representatives from industry, accessibility consultancies, universities, organizations that represent end users, and other accessibility experts.

The working group published the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) as W3C Recommendation in 1999, followed by techniques documents in 2000.
In 2001, the working group started work on WCAG 2.0.

The Web Content Accessibility Guidelines Working Group is probably the most well-known working group in WAI; the Web Content Accessibility Guidelines 1.0 are often simply referred to as â€œthe WAI guidelines,â€ even though WAI also produces other guidelines and specifications.

=== WAI Coordination Group ===

The WAI Coordination Group co-ordinates that activities of the WAI working groups (and interest groups). Its activities are not public.

==Guidelines and technical reports==
===Web Content Accessibility Guidelines (WCAG)===
{{seesubarticle|Web Content Accessibility Guidelines}}

The Web Content Accessibility Guidelines 1.0 (known as WCAG) were published as a W3C Recommendation on 5 May 1999. A supporting document, Techniques for Web Content Accessibility Guidelines 1.0<ref>[http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/ Techniques for Web Content Accessibility Guidelines 1.0 - W3C Note 6 November 2000]</ref> was published as a W3C Note on 6 November 2000.
WCAG 1.0 is a set of guidelines for making web content more accessible to persons with disabilities. They also help make web content more usable for other devices, including mobile devices (PDAs and cell phones).
The Web Content Accessibility Guidelines 1.0 are recognized as a de facto standard and have served as a basis for legislation and evaluation methodologies in many countries.

The WCAG working group is currently working on a new version of the guidelines. The development of WCAG 2.0 is based on very different requirements from WCAG 1.0:
* the guidelines needed to be technology-neutral, whereas WCAG 1.0 was strongly based on HTML and CSS;
* the guidelnes needed to be worded as testable statements instead of instructions to authors.
The combination of more general applicability and higher precision proved very challenging. Currently, WCAG 2.0 is in the Candicate Recommendation phase, which means that the working group needs to find evidence that the guidelines can be implemented in real websites.

===Authoring Tools Accessibility Guidelines (ATAG)===

Developed by the Authoring Tool Accessibility Guidelines Working Group, the ATAG 1.0 became a W3C Recommendation on 3 February 3 2000. 
The ATAG is a set of guidelines for developers of any kind of authoring tool for Web content: simple [[HTML editor|HTML editors]], tools that export content for use on the Web (for example, word processors that can save as HTML), tools that produce multimedia, [[Content management system|content management systems]], etcetera.

The goal is for developers to create tools that:
* are accessible to authors regardless of disability,
* produce accessible content by default,
* support and encourage authors to create accessible content.

The ATAG working group is currently working on a second version of the guidelines. A Last Call Working Draft was published in November 2004
<ref>[http://www.w3.org/TR/2004/WD-ATAG20-20041122/ Authoring Tool Accessibility Guidelines 2.0 - W3C Working Draft 22 November 2004]</ref>
<ref>[http://www.w3.org/WAI/AU/2005/11_2004_comment_responses.html Response to Last Call Comments] on ATAG 2.0, November 2004</ref>
but subsequent versions were published as normal working drafts.
Implementation Techniques for ATAG 2.0<ref>[http://www.w3.org/TR/2008/WD-ATAG20-TECHS-20080310/ Implementation Techniques for Authoring Tool Accessibility Guidelines 2.0 - W3C Working Draft 10 March 2008]</ref> are also available as a working draft.

===User Agent Accessibility Guidelines (UAAG)===
Developed by the User Agent Accessibility Guidelines Working Group, the UAAG 1.0 became a W3C Recommendation on 17 December 2002. The UAAG is a set of guidelines for user agent developers (such as [[web browser]]s and [[media player (application software)|media player]]s) aimed at making the user agent accessible to users with disabilities. Techniques for User Agent Accessibility Guidelines 1.0<ref>[http://www.w3.org/TR/2002/NOTE-UAAG10-TECHS-20021217/ Techniques for User Agent Accessibility Guidelines 1.0 - W3C Note 17 December 2002]</ref> was published as a W3C Note on the same day; it provides techniques for satisfying the checkpoints defined in UAAG 1.0.
Working group members also produced other supporting documents, including initial notes on How to evaluate a user agent for conformance to UAAG 1.0<ref>[http://www.w3.org/WAI/UA/2001/10/eval How to evaluate a user agent for conformance to UAAG 1.0]</ref>; this document was not formally approved by the working group.
No user agents have been reported as fully conforming to UAAG 1.0.

The working group is currently working on a new version of the guidelines. The first public draft of User Agent Accessibility Guidelines 2.0 was published on 12 March 2008.<ref>[http://www.w3.org/TR/2008/WD-UAAG20-20080312/ User Agent Accessibility Guidelines 2.0: W3C Working Draft 12 March 2008].</ref>

===XML Accessibility Guidelines (XAG)===
The XAG explains how to include features in XML applications (i.e. markup languages conforming to the XML specification) that promote accessibility. Work on these guidelines stopped in 2002; the guidelines are still a working draft.

===Accessible Rich Internet Applications (WAI-ARIA)===
{{seesubarticle|WAI-ARIA}}
WAI-ARIA is a set of documents that specify how to increase the accessibility of dynamic content and user interface components developed with Ajax, HTML, JavaScript and related technologies. Hypertext Markup Language (HTML) does not provide features to create dynamic content or advanced user interface controls, but allows the inclusion of applets (Flash, Java) and client-side scripts (typically JavaScript). Web developers increasingly use client-side script to create user interface controls that cannot be created with HTML alone. They also use client-side script to update sections of a page without requesting a completely new page from a web server. These user interface controls and content updates are often not accessible to users with disabilities, especially screen reader users and users who cannot use a mouse or other pointing device.

WAI-ARIA describes how to add semantics and other metadata to HTML content in order to make user interface controls and dynamic content more accessible. For example, with WAI-ARIA it is possible to identify a list of links as a navigation menu and to state whether it is expanded or collapsed. Although originally developed to address accessibility issues in HTML, the use of WAI-ARIA is not limited to HTML: in principle, it can also be used in other markup languages such as [[Scalable Vector Graphics]] (SVG). SVG 1.2 Tiny added support for WAI-ARIA in the 15 September 2008 working draft.<ref name="ariasvg2008">See [http://www.w3.org/TR/2008/WD-SVGMobile12-20080915/struct.html#RoleAttribute SVG 1.2 Tiny: role attribute] and [http://www.w3.org/TR/2008/WD-SVGMobile12-20080915/metadata.html#MetadataAttributes SVG 1.2 Tiny: Extensible metadata attributes].</ref>

The Web Accessibility Initiative has published an overview of WAI-ARIA<ref name="waiariaoverview">[http://www.w3.org/WAI/intro/aria.php WAI-ARIA Overview]</ref> that introduces the subject and guides readers to the WAI-ARIA Suite documents:
* '''Accessible Rich Internet Applications (WAI-ARIA) Version 1.0'''. This is primarily aimed at developers of Web browsers assistive technologies and other user agents, developers of other technical specifications, and developers of accessibility evaluation tools.<ref name="waiaria1" />
* '''WAI-ARIA Primer'''<ref name="waiariaprimer">[http://www.w3.org/TR/wai-aria-primer/ WAI-ARIA Primer]</ref>. This is a technical introduction to WAI-ARIA. It describes the problems WAI-ARIA tries to address, the underlying concepts, the technical approach and business reasons for adopting WAI-ARIA.
* '''WAI-ARIA Best Practices'''<ref name="waiariabp" />. This document describes best practices for delivering rich internet applications with WAI-ARIA: it discusses subjects such as general steps for building accessible widgets, keyboard navigation, relationships, form properties, drag-and-drop support, alerts and dialogs, reusable component libraries, and testing.
* '''Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap)'''<ref name="ariaroadmap">[http://www.w3.org/TR/wai-aria-roadmap/ Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap)]</ref>. Much of the content of this document has been moved into other documents.

==See also==
* [[Web accessibility]]
* [[Section 508 Amendment to the Rehabilitation Act of 1973]] - a US government accessibility standard

==External links==

*[http://www.w3.org/WAI/ Official website]
** [http://www.w3.org/TR/WAI-WEBCONTENT/ Web Content Accessibility Guidelines 1.0]
** [http://www.w3.org/TR/WCAG20/ Web Content Accessibility Guidelines 2.0 (W3C Proposed Recommendation 03 November 2008)]
** [http://www.w3.org/TR/WAI-AUTOOLS Authoring Tool Accessibility Guidelines 1.0]
** [http://www.w3.org/TR/WAI-USERAGENT User Agent Accessibility Guidelines 1.0]
** [http://www.w3.org/TR/xag XML Accessibility Guidelines Working Draft]
** [http://www.w3.org/WAI/EO/ Education & Outreach Working Group]
** [http://www.w3.org/WAI/RD/ Research and Development Interest Group]
** [http://www.w3.org/WAI/gettingstarted/ Getting Started]

==References==
{{Reflist}}

[[Category:Web accessibility]]
[[Category:World Wide Web Consortium standards]]

[[de:Web Accessibility Initiative]]
[[es:Web Accessibility Initiative]]
[[eu:Web Accessibility Initiative]]
[[fr:Web Accessibility Initiative]]
[[ja:Web Accessibility Initiative]]
[[nl:Web Accessibility Initiative]]
[[pl:Web Accessibility Initiative]]
[[it:WAI]]
[[sv:WAI]]

Content that violates any copyright will be deleted. Encyclopedic content must be verifiable. You irrevocably agree to release your contributions under the terms of the GFDL^*.

Edit summary (Briefly describe the changes you have made):

Cancel | Editing help (opens in new window)

Do not copy text from other websites without a GFDL-compatible license. It will be deleted.

Copy and paste: â€“ â€” â€¦ â€˜ â€œ â€™ â€ Â° â€³ â€² â‰ˆ â‰ â‰¤ â‰¥ Â± âˆ’ Ã— Ã· â† â†’ Â· Â§ Sign your posts on talk pages: ~~~~

{{}} {{{}}} | [] [[]] [[Category:]] #REDIRECT [[]]   <s></s> <code></code> <blockquote></blockquote> <ref></ref> {{Reflist}} <references/> <includeonly></includeonly> <noinclude></noinclude> {{DEFAULTSORT:}} <nowiki></nowiki>

Symbols: ~ | Â¡ Â¿ â€ â€¡ â†” â†‘ â†“ â€¢ Â¶ # Â½ â…“ â…” Â¼ Â¾ â…› â…œ â… â…ž âˆž â€˜ â€œ â€™ â€ Â«Â» Â¤ â‚³ à¸¿ â‚µ Â¢ â‚¡ â‚¢ $ â‚« â‚¯ â‚¬ â‚ â‚£ Æ’ â‚´ â‚ â‚¤ â„³ â‚¥ â‚¦ â„– â‚§ â‚° Â£ áŸ› â‚¨ â‚ª à§³ â‚® â‚© Â¥ â™ â™£ â™¥ â™¦ mÂ² mÂ³
Characters: Ã Ã¡ Ä† Ä‡ Ã‰ Ã© Ã Ã Ä¹ Äº Åƒ Å„ Ã“ Ã³ Å” Å• Åš Å› Ãš Ãº Ã Ã½ Å¹ Åº Ã€ Ã Ãˆ Ã¨ ÃŒ Ã¬ Ã’ Ã² Ã™ Ã¹ Ã‚ Ã¢ Äˆ Ä‰ ÃŠ Ãª Äœ Ä Ä¤ Ä¥ ÃŽ Ã® Ä´ Äµ Ã” Ã´ Åœ Å Ã› Ã» Å´ Åµ Å¶ Å· Ã„ Ã¤ Ã‹ Ã« Ã Ã¯ Ã– Ã¶ Ãœ Ã¼ Å¸ Ã¿ ÃŸ Ãƒ Ã£ áº¼ áº½ Ä¨ Ä© Ã‘ Ã± Ã• Ãµ Å¨ Å© á»¸ á»¹ Ã‡ Ã§ Ä¢ Ä£ Ä¶ Ä· Ä» Ä¼ Å… Å† Å– Å— Åž ÅŸ Å¢ Å£ Ä Ä‘ Å® Å¯ Ç ÇŽ ÄŒ Ä ÄŽ Ä Äš Ä› Ç Ç Ä½ Ä¾ Å‡ Åˆ Ç‘ Ç’ Å˜ Å™ Å Å¡ Å¤ Å¥ Ç“ Ç” Å½ Å¾ Ä€ Ä Ä’ Ä“ Äª Ä« ÅŒ Å Åª Å« È² È³ Ç¢ Ç£ Ç– Ç˜ Çš Çœ Ä‚ Äƒ Ä” Ä• Äž ÄŸ Ä¬ Ä ÅŽ Å Å¬ Å ÄŠ Ä‹ Ä– Ä— Ä Ä¡ Ä° Ä± Å» Å¼ Ä„ Ä… Ä˜ Ä™ Ä® Ä¯ Çª Ç« Å² Å³ á¸Œ á¸ á¸¤ á¸¥ á¸¶ á¸· á¸¸ á¸¹ á¹‚ á¹ƒ á¹† á¹‡ á¹š á¹› á¹œ á¹ á¹¢ á¹£ á¹¬ á¹ Å Å‚ Å Å‘ Å° Å± Ä¿ Å€ Ä¦ Ä§ Ã Ã° Ãž Ã¾ Å’ Å“ Ã† Ã¦ Ã˜ Ã¸ Ã… Ã¥ Æ É™ {{Unicode|}}
Greek: Î† Î¬ Îˆ Î Î‰ Î® ÎŠ Î¯ ÎŒ ÏŒ ÎŽ Ï Î ÏŽ Î‘ Î± Î’ Î² Î“ Î³ Î” Î´ Î• Îµ Î– Î¶ Î— Î· Î˜ Î¸ Î™ Î¹ Îš Îº Î› Î» Îœ Î¼ Î Î½ Îž Î¾ ÎŸ Î¿ Î Ï€ Î¡ Ï Î£ Ïƒ Ï‚ Î¤ Ï„ Î¥ Ï… Î¦ Ï† Î§ Ï‡ Î¨ Ïˆ Î© Ï‰ {{Polytonic|}}
Cyrillic: Ð Ð° Ð‘ Ð± Ð’ Ð² Ð“ Ð³ Ò Ò‘ Ðƒ Ñ“ Ð” Ð´ Ð‚ Ñ’ Ð• Ðµ Ð Ñ‘ Ð„ Ñ” Ð– Ð¶ Ð— Ð· Ð… Ñ• Ð˜ Ð¸ Ð† Ñ– Ð‡ Ñ— Ð™ Ð¹ Ðˆ Ñ˜ Ðš Ðº ÐŒ Ñœ Ð› Ð» Ð‰ Ñ™ Ðœ Ð¼ Ð Ð½ ÐŠ Ñš Ðž Ð¾ ÐŸ Ð¿ Ð Ñ€ Ð¡ Ñ Ð¢ Ñ‚ Ð‹ Ñ› Ð£ Ñƒ ÐŽ Ñž Ð¤ Ñ„ Ð¥ Ñ… Ð¦ Ñ† Ð§ Ñ‡ Ð ÑŸ Ð¨ Ñˆ Ð© Ñ‰ Ðª ÑŠ Ð« Ñ‹ Ð¬ ÑŒ Ð Ñ Ð® ÑŽ Ð¯ Ñ
IPA: tÌª dÌª Êˆ É– ÉŸ É¡ É¢ Ê¡ Ê” É¸ Êƒ Ê’ É• Ê‘ Ê‚ Ê Ê É£ Ê Ê• Êœ Ê¢ É¦ É± É³ É² Å‹ É´ Ê‹ É¹ É» É° Ê™ Ê€ É¾ É½ É« É¬ É® Éº É ÊŽ ÊŸ É¥ Ê É§ É“ É— Ê„ É Ê› Ê˜ Ç€ Çƒ Ç‚ Ç É¨ Ê‰ É¯ Éª Ê ÊŠ É˜ Éµ É¤ É™ Éš É› Éœ É Éž ÊŒ É” É É¶ É‘ É’ Ê° Ê· Ê² Ë Ë¤ â¿ Ë¡ Ëˆ ËŒ Ë Ë‘ Ìª {{IPA|}}

Once you click the Save button, your changes will be visible immediately.

For testing, please use the sandbox instead.

Please note:

If you don't want your writing to be edited mercilessly or redistributed for profit by others, do not submit it. Only public domain resources can be copied without permission—this does not include most web pages or images. See our policies and guidelines for more information on editing.

^ GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts.

Pages transcluded onto the current version of this page:

Template:Details (view source) (protected) Template:Reflist (view source) (protected) Template:Seesubarticle (view source) (protected)

Retrieved from "http://en.wikipedia.org/wiki/Web_Accessibility_Initiative"

Editing Web Accessibility Initiative

From Wikipedia, the free encyclopedia

Views

Personal tools

Navigation

Search

Interaction

Toolbox