Short description: Technical specification for web accessibility
WAI-ARIA
Web Accessibility Initiative - Accessible Rich Internet Applications
Status
W3C Recommendation
Year started
2006; 18 years ago (2006)
First published
September 26, 2006; 17 years ago (2006-09-26)
Latest version
WAI-ARIA 1.2: W3C Recommendation June 6, 2023; 13 months ago (2023-06-06)
Organization
W3C
Adobe
Apple
IBM
Igalia
Knowbility
Spec-Ops
Committee
ARIA WG
Editors
Joanmarie Diggs
James Nurthen
Michael Cooper
Carolyn MacLeod
Former editors
Shane McCarron (until 2018 (2018))
Richard Schwerdtfeger (until October 2017 (2017-10))
James Craig (Editor until May 2016 (2016-05))
Domain
Assistive technology
Progressive web applications
Semantic HTML
Web accessibility
Abbreviation
WAI-ARIA
Website
www.w3.org/WAI/standards-guidelines/aria/
Web Accessibility Initiative – Accessible Rich Internet Applications (WAI-ARIA) is a technical specification published by the World Wide Web Consortium (W3C) that specifies how to increase the accessibility of web pages, in particular, dynamic content, and user interface components developed with Ajax, HTML, JavaScript, and related technologies.
In the 15 September 2008 working draft, SVG 1.2 Tiny added support for WAI-ARIA.[1] On 20 March 2014, WAI-ARIA 1.0 became a completed W3C Recommendation.[2] 14 December 2017 saw the release of WAI-ARIA 1.1.[3]
Contents
1The 5 Rules of ARIA
2Scope
3Documents
4See also
5References
6External links
The 5 Rules of ARIA
Don’t use ARIA if you can achieve the same semantics with a native HTML element or attribute[4]
Do not change the semantics of native HTML (unless you really have to)[5]
All interactive ARIA controls must be usable with the keyboard.[6]
Do not remove semantics or hide focusable elements (using role="presentation" or aria-hidden="true" on a focusable element)[7]
Ensure all interactive elements have an accessible name (Accessibility API accessible name).[8]
Scope
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 applications rather than as static documents, by adding role, property, and state information to dynamic web applications. ARIA is intended for use by developers of web applications, web browsers, assistive technologies, and accessibility evaluation tools.[9]
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).[10][11]
Documents
The Web Accessibility Initiative has published an overview of WAI-ARIA that introduces the subject and guides readers to the WAI-ARIA Suite documents:[9]
Accessible Rich Internet Applications (WAI-ARIA) Version 1.0
This is primarily aimed at developers of Web browsers, assistive technologies, and other user agents, in addition to developers of other technical specifications, and developers of accessibility evaluation tools. The WAI-ARIA has been marked as completed on 20 March 2014 and is therefore a W3C recommendation.[12]
WAI-ARIA Overview
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.[9]
WAI-ARIA Authoring Practices
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, alert and dialog boxes, reusable component libraries, and testing.[13]
Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap)
Much of the content of this document has been moved into other documents.[14]
The ARIA specifications editors have included Lisa Seeman, Rich Schwerdtfeger, James Craig, Michael Cooper, and Lisa Pappas.[12]
↑SVG Working Group (2008-12-22). "Document Structure – SVG Tiny 1.2 § 5.10.1 Attributes common to all elements". https://www.w3.org/TR/SVGMobile12/struct.html#RoleAttribute.
↑SVG Working Group (2008-12-22). "Document Structure – SVG Tiny 1.2 § 18.3 Extensible metadata attributes". https://www.w3.org/TR/SVGMobile12/metadata.html#MetadataAttributes..
↑ 12.012.1"Accessible Rich Internet Applications (WAI-ARIA) 1.0". W3.org. https://www.w3.org/TR/wai-aria/.
↑"WAI-ARIA Authoring Practices 1.1". Accessible Rich Internet Applications Working Group. 2019-08-14. http://www.w3.org/TR/wai-aria-practices/.
↑"Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap)". Protocols & Formats Working Group. 2008-02-04. http://www.w3.org/TR/wai-aria-roadmap/.
External links
Introduction to WAI ARIA by Gez Lemon
ARIA developer portal documentation, videos, and articles relating to ARIA (materials under Creative Commons Attribution-Share Alike license)
Henny Swan (Opera): Setting up a screen reader test environment for WAI-ARIA
v
t
e
World Wide Web Consortium (W3C)
Products and standards
Recommendations
ActivityPub
ARIA
Canonical XML
CDF
CSS
DOM
Geolocation API
HTML (HTML5)
ITS
JSON-LD
Linked Data Notifications
MathML
Micropub
OWL
PLS
RDF
RDF Schema
SISR
SKOS
SMIL
SOAP
SRGS
SRI
SSML
SVG
SCXML
SHACL
SPARQL
Timed text
VoiceXML
Web storage
WSDL
Webmention
WebSub
XForms
XHTML
XHTML+RDFa
XInclude
XLink
XML
XML Base
XML Encryption
XML Events
XML Information Set
XML namespace
XML Schema
XML Signature
XOP
XPath
XPath 2.0
XPointer
XProc
XQuery
XSL
XSL-FO
XSLT (elements)
Notes
IndieAuth
JF2
Post Type Discovery
XAdES
XHTML+SMIL
XUP
Working drafts
CCXML
CURIE
EME
InkML
MSE
RIF
SMIL Timesheets
sXBL
XFDL
XFrames
XBL
XMLHttpRequest
Guidelines
Web Content Accessibility Guidelines
Initiative
Multimodal Interaction Activity (MMI)
Markup Validation Service
Web Accessibility Initiative
WebPlatform
Deprecated
C-HTML
HDML
JSSS
PGML
VML
XHTML+MathML+SVG
Obsoleted
P3P
Organizations
Advisory Committee (AC)
World Wide Web Foundation
Elected groups
Advisory Board (AB)
Working groups
CSS
Geolocation
Social Web
SVG
Web Hypertext Application Technology (WHATWG)
Web Platform
Community groups
Web Incubator Community Group (WICG)
Closed groups
Device Description (DDWG)
HTML
Software
CERN httpd
Libwww
Browsers
Line Mode (1990–)
Arena (1993–98)
Agora (1994–97)
Argo (1994–97)
Amaya (browser/editor, 1996–2012)
Conferences
International World Wide Web Conference (IW3C)
Steering Committee (IW3C2)
First conference ("WWW1", 1994)
0.00
(0 votes)
Original source: https://en.wikipedia.org/wiki/WAI-ARIA. Read more