WAI-ARIA (Web Accessibility Initiative - Accessible Rich Internet Applications) is a technical specification published by the World Wide Web Consortium that specifies how to increase the accessibility of web pages, in particular, dynamic content and user interface components developed with AjaxHTMLJavaScript and related technologies. As of March 2014, it was a Recommendation.[1]

Web developers increasingly use client-side scripts to create user interface controls that cannot be created with HTML alone. They also use client-side scripts to update sections of a page without requesting a completely new page from a web server. Such techniques on websites are called rich Internet applications. 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 allows web pages (or portions of pages) to declare themselves as applicationsrather than as static documents, by adding role, property, and state information to dynamic web applications. ARIA is intended for use by developers of web applicationsweb browsersassistive technologies, and accessibility evaluation tools.[2]

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.[3]

The Web Accessibility Initiative has published an overview of WAI-ARIA[2] that introduces the subject and guides readers to the WAI-ARIA Suite documents:

Accessible Rich Internet Applications (WAI-ARIA) Version 1.0 (Draft)
[1] This is primarily aimed at developers of Web browsersassistive technologies, and other user agents, in addition to developers of other technical specifications, and developers of accessibility evaluation tools.
WAI-ARIA Primer
[4] 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
[5] This document describes best practices for delivering rich Internet applications with WAI-ARIA: it discusses subjects such as general steps for building accessible widgetskeyboard navigation, relationships, form properties, drag-and-drop support, alert and dialog boxesreusable component libraries, and testing.
Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap)
[6] Much of the content of this document has been moved into other documents.

The ARIA specifications editors have included Lisa Seeman, Rich Schwerdtfeger, James Craig, Michael Cooper and Lisa Pappas.

See also[edit]

References[edit]



source - http://en.wikipedia.org/wiki/WAI-ARIA






리치 인터넷 어플리케이션 접근성 (ARIAAccessible Rich Internet Applications)는 (특히 AJAX와 JavaScript를 사용하여 개발하는)웹 콘텐츠와 웹 어플리케이션을 제작할 때 장애인을 위한 접근성 향상 방법을 정의하고 있습니다. 예를 들어, ARIA는 접근가능한 네비게이션에 표시를 한다거나, JavaScript 위젯 사용이나, form 힌트 및 에러 메시지 그리고 실시간 콘텐츠 업데이트 등을 사용할 수 있도록 합니다.

ARIA는 어떤 마크업 요소에도 추가 가능한 접근성 속성의 집합이지만, 특히 HTML에 최적화되어 있습니다. role속성은 객체(article, alert, slider와 같은 것들)의 제너럴 타입을 정의할 수 있습니다. 추가로 ARIA 속성들은 form을 위한 설명이나 progressbar의 현재 값을 나타내어 주는 것과 같은 다른 유용한 프로퍼티들을 제공합니다.

ARIA는 대부분의 유명 브라우저들과 스크린리더에서 지원합니다. 그러나, 구현방식이 가지각색이며 오래된 기술들이 그를 잘 지원하지 않거나 전체를 지원하지 않습니다. "안전한" ARIA를 우아하게 낮추거나, 유저들에게 새로운 기술로 업그레이드 할 것을 요구하는 것 중 하나를 사용하십시요.


출처 - https://developer.mozilla.org/ko/docs/Web/Accessibility/ARIA





'Web > Common' 카테고리의 다른 글

web - woff, eot  (0) 2014.04.21
웹 페이지 속도 개선  (0) 2014.03.18
web - tomcat gzip config  (0) 2014.02.07
web - HATEOAS  (0) 2014.01.12
web - SPDY  (0) 2014.01.09
Posted by linuxism
,