Skip to content

Commit c891215

Browse files
daniel-montalvodaniel-montalvo
authored
Includes relevant changes from #2102 (#2120)
1 parent f5d2c81 commit c891215

File tree

1 file changed

+21
-20
lines changed

1 file changed

+21
-20
lines changed

‎index.html‎

Lines changed: 21 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,10 @@
1515
specStatus: "ED",
1616
//crEnd: "2012-04-30",
1717
//perEnd: "2013-07-23",
18-
//publishDate: "2013-08-22",
18+
//publishDate: "2024-01-23",
1919

2020
// the specifications short name, as in https://www.w3.org/TR/short-name/
21-
shortName: "wai-aria-1.2",
21+
shortName: "wai-aria-1.3",
2222

2323
// if you wish the publication date to be other than today, set this
2424
//publishDate: "2014-12-11",
@@ -28,7 +28,7 @@
2828
// and its maturity status
2929
//previousPublishDate: "2014-06-12",
3030
//previousMaturity: "WD",
31-
prevRecURI: "https://www.w3.org/TR/wai-aria-1.2/",
31+
prevRecURI: "https://www.w3.org/TR/wai-aria/",
3232
//previousDiffURI: "https://www.w3.org/TR/2014/REC-wai-aria-20140320/",
3333

3434
// if there a publicly available Editors Draft, this is the link
@@ -57,7 +57,7 @@
5757
{
5858
name: "Michael Cooper",
5959
company: "W3C",
60-
companyURL: "http://www.w3.org",
60+
companyURL: "https://www.w3.org",
6161
w3cid: 34017,
6262
note: "Editor until 2023"
6363
},
@@ -71,14 +71,14 @@
7171
{
7272
name: "Shane McCarron",
7373
company: "Spec-Ops",
74-
companyURL: "https://www.spec-ops.io",
74+
// companyURL: "https://www.spec-ops.io",
7575
w3cid: 89030,
7676
note: "Editor until 2018"
7777
},
7878
{
7979
name: "Richard Schwerdtfeger",
8080
company: "Knowbility",
81-
companyURL: "https://www.knowbility.org/",
81+
companyURL: "https://knowbility.org/",
8282
w3cid: 2460,
8383
note: "Editor until October 2017"
8484
},
@@ -116,10 +116,11 @@
116116

117117
// Spec URLs
118118
ariaSpecURLs: {
119-
"ED": "",
120-
"WD" : "",
121-
"CR": "",
122-
"REC": ""
119+
"ED": "https://w3c.github.io/aria/",
120+
"FPWD": "https://www.w3.org/TR/wai-aria-1.3/",
121+
"WD": "https://www.w3.org/TR/wai-aria-1.3/",
122+
"CR": "https://www.w3.org/TR/wai-aria-1.3/",
123+
"REC": "https://www.w3.org/TR/wai-aria-1.3/",
123124
},
124125
accNameURLs: {
125126
"ED": "https://w3c.github.io/accname/",
@@ -136,11 +137,11 @@
136137
"REC": "https://www.w3.org/TR/core-aam-1.2/"
137138
},
138139
practicesURLs: {
139-
"ED": "https://w3c.github.io/aria-practices/",
140-
"WD" : "https://www.w3.org/TR/wai-aria-practices-1.2/",
141-
"FPWD": "https://www.w3.org/TR/wai-aria-practices-1.2/",
142-
"CR": "https://www.w3.org/TR/wai-aria-practices-1.2/",
143-
"REC": "https://www.w3.org/TR/wai-aria-practices-1.2/"
140+
"ED": "https://www.w3.org/WAI/ARIA/apg/",
141+
"WD" : "https://www.w3.org/WAI/ARIA/apg/",
142+
"FPWD": "https://www.w3.org/WAI/ARIA/apg/",
143+
"CR": "https://www.w3.org/WAI/ARIA/apg/",
144+
"REC": "https://www.w3.org/WAI/ARIA/apg/"
144145
},
145146

146147
preProcess: [ linkCrossReferences ],
@@ -163,10 +164,10 @@
163164
<body>
164165
<section id="abstract">
165166
<p>Accessibility of web content requires semantic information about widgets, structures, and behaviors, in order to allow assistive technologies to convey appropriate information to persons with disabilities. This specification provides an ontology of roles, states, and properties that define accessible user interface elements and can be used to improve the accessibility and interoperability of web content and applications. These semantics are designed to allow an author to properly convey user interface behaviors and structural information to assistive technologies in document-level markup. This version adds features new since WAI-ARIA 1.1 [[wai-aria-1.1]] to improve interoperability with assistive technologies to form a more consistent accessibility model for [[HTML]] and [[SVG2]]. This specification complements both [[HTML]] and [[SVG2]].</p>
166-
<p>This document is part of the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> suite described in the <a href="http://www.w3.org/WAI/intro/aria.php"><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Overview</a>.</p>
167+
<p>This document is part of the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> suite described in the <a href="https://www.w3.org/WAI/standards-guidelines/aria/"><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Overview</a>.</p>
167168
</section>
168169
<section id="sotd">
169-
<p>The Accessible Rich Internet Applications Working Group seeks feedback on any aspect of the specification. When submitting feedback, please consider issues in the context of the companion documents. To comment, <a href="https://github.com/w3c/aria/issues/new">file an issue in the <abbr title="World Wide Web Consortium">W3C</abbr> ARIA GitHub repository</a>. If this is not feasible, send email to <a href="mailto:[email protected]?subject=Comment%20on%20WAI-ARIA%201.2">[email protected]</a> (<a href="http://lists.w3.org/Archives/Public/public-aria/">comment archive</a>). In-progress updates to the document can be viewed in the <a href="http://w3c.github.io/aria/">publicly visible editors' draft</a>.</p>
170+
<p>The Accessible Rich Internet Applications Working Group seeks feedback on any aspect of the specification. When submitting feedback, please consider issues in the context of the companion documents. To comment, <a href="https://github.com/w3c/aria/issues/new">file an issue in the <abbr title="World Wide Web Consortium">W3C</abbr> ARIA GitHub repository</a>. If this is not feasible, send email to <a href="mailto:[email protected]?subject=Comment%20on%20WAI-ARIA%201.2">[email protected]</a> (<a href="http://lists.w3.org/Archives/Public/public-aria/">comment archive</a>). In-progress updates to the document can be viewed in the <a href="https://w3c.github.io/aria/">publicly visible editors' draft</a>.</p>
170171
</section>
171172
<section class="informative" id="introduction">
172173
<h1>Introduction</h1>
@@ -267,8 +268,8 @@ <h1>Important Terms</h1>
267268
<dl class="termlist">
268269
<dt><dfn data-export="">Accessibility <abbr title="Application Programming Interface">API</abbr></dfn></dt>
269270
<dd>
270-
<p>Operating systems and other platforms provide a set of interfaces that expose information about <a class="termref">objects</a> and <a class="termref">events</a> to <a>assistive technologies</a>. Assistive technologies use these interfaces to get information about and interact with those <a class="termref">widgets</a>. Examples of accessibility APIs are <a href="https://docs.microsoft.com/en-us/windows/win32/winauto/microsoft-active-accessibility">Microsoft Active Accessibility</a> [[MSAA]], <a href="https://docs.microsoft.com/en-us/windows/win32/winauto/entry-uiauto-win32">Microsoft User Interface Automation</a> [[UI-AUTOMATION]], <abbr title="Microsoft Active Accessibility">MSAA</abbr> with <cite><a href="https://docs.microsoft.com/en-us/windows/win32/winauto/iaccessibleex"><abbr title="User Interface Automation">UIA</abbr> Express</a></cite> [[UIA-EXPRESS]], the
271-
<a href="https://developer.apple.com/documentation/appkit/nsaccessibility">Mac <abbr title="OS Ten">OS X</abbr> Accessibility Protocol</a> [[AXAPI]], the <cite><a href="https://developer.gnome.org/atk/unstable/">Linux/Unix Accessibility Toolkit</a></cite> [[ATK]] and <cite><a href="https://developer.gnome.org/libatspi/stable/">Assistive Technology Service Provider Interface</a></cite> [[AT-SPI]], and <a href="https://wiki.linuxfoundation.org/accessibility/iaccessible2/start">IAccessible2</a> [[IAccessible2]].</p>
271+
<p>Operating systems and other platforms provide a set of interfaces that expose information about <a class="termref">objects</a> and <a class="termref">events</a> to <a>assistive technologies</a>. Assistive technologies use these interfaces to get information about and interact with those <a class="termref">widgets</a>. Examples of accessibility APIs are <a href="https://docs.microsoft.com/en-us/windows/win32/winauto/microsoft-active-accessibility">Microsoft Active Accessibility</a> [[MSAA]], <a href="https://learn.microsoft.com/en-us/windows/win32/winauto/entry-uiauto-win32">Microsoft User Interface Automation</a> [[UI-AUTOMATION]], <abbr title="Microsoft Active Accessibility">MSAA</abbr> with <cite><a href="https://learn.microsoft.com/en-us/windows/win32/winauto/iaccessibleex"><abbr title="User Interface Automation">UIA</abbr> Express</a></cite> [[UIA-EXPRESS]], the
272+
<a href="https://developer.apple.com/documentation/appkit/nsaccessibility">Mac <abbr title="OS Ten">OS X</abbr> Accessibility Protocol</a> [[AXAPI]], the <cite><a href="https://gnome.pages.gitlab.gnome.org/atk/">Linux/Unix Accessibility Toolkit</a></cite> [[ATK]] and <cite><a href="https://gnome.pages.gitlab.gnome.org/at-spi2-core/libatspi/">Assistive Technology Service Provider Interface</a></cite> [[AT-SPI]], and <a href="https://wiki.linuxfoundation.org/accessibility/iaccessible2/start">IAccessible2</a> [[IAccessible2]].</p>
272273
</dd>
273274
<dt><dfn data-export="">Accessible object</dfn></dt>
274275
<dd>
@@ -505,7 +506,7 @@ <h3>Information for Authors</h3>
505506
This is often a more convenient way of providing keyboard navigation within widgets, such as a <rref>listbox</rref>, where the widget occupies only one stop in the page <kbd>Tab</kbd> sequence and other keys, typically arrow keys, are used to focus elements inside the widget.
506507
</p>
507508
<p>Typically, the author will use host language <a>semantics</a> to put the widget in the <kbd>Tab</kbd> sequence (e.g., <code>tabindex="0"</code> in HTML) and <code>aria-activedescendant</code> to point to the ID of the currently active descendant. The author, not the user agent, is responsible for styling the currently active descendant to show it has keyboard focus. The author cannot use <code>:<span class="css-selector">focus</span></code> to style the currently active descendant since the actual focus is on the container.</p>
508-
<p>More information on managing focus can be found in the <a href="#keyboard" class="practices">Developing a Keyboard Interface</a> section of the <cite><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Authoring Practices</cite>.</p>
509+
<p>More information on managing focus can be found in the <a href="practices/keyboard-interface" class="practices">Developing a Keyboard Interface</a> section of the <cite><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Authoring Practices</cite>.</p>
509510
</section>
510511
<section id="managingfocus_useragents">
511512
<h3>Information for User Agents</h3>

0 commit comments

Comments
 (0)