Skip to content

Commit

Permalink
Merge pull request w3c#117 from w3c/update-editor-list
Browse files Browse the repository at this point in the history 
Updated editors list
  • Loading branch information
@MelSumner
MelSumner committed Mar 24, 2021
2 parents 5b60cb2 + 1694ee4 commit 6e63219
Showing 1 changed file with 17 additions and 16 deletions.
33 changes: 17 additions & 16 deletions accname/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
github: "w3c/accname",
doJsonLd: true,
lint: true,

// specification status (e.g., WD, LC, NOTE, etc.). If in doubt use ED.
specStatus: "ED",
//crEnd: "2012-04-30",
Expand All @@ -23,7 +23,7 @@

// the specifications short name, as in https://www.w3.org/TR/short-name/
shortName: "accname-1.2",

// if you wish the publication date to be other than today, set this
//publishDate: "2014-12-11",
copyrightStart: "2014",
Expand Down Expand Up @@ -55,18 +55,19 @@
companyURL: "https://www.linkedin.com/",
w3cid: 125865
},
{ name: "Joanmarie Diggs",
company: "Igalia, S.L.",
companyURL: "https://www.igalia.com/",
w3cid: 68182
},
{ name: "Michael Cooper",
company: "W3C",
companyURL: "https://www.w3.org/",
w3cid: 34017
}
],
formerEditors: [
{ name: "Joanmarie Diggs",
company: "Igalia, S.L.",
companyURL: "https://www.igalia.com/",
w3cid: 68182,
note: "Editor until March 2021"
},
{ name: "Richard Schwerdtfeger",
company: "Knowbility",
companyURL: "https://knowbility.org/",
Expand Down Expand Up @@ -98,7 +99,7 @@
note: "Editor until January 2009"
},
],
// authors, add as many as you like.
// authors, add as many as you like.
// This is optional, uncomment if you have authors as well as editors.
// only "name" is required. Same format as editors.

Expand All @@ -117,7 +118,7 @@
label: "PDF version" }
],
*/

// Working group info
wg: "Accessible Rich Internet Applications Working Group",
wgURI: "https://www.w3.org/WAI/ARIA/",
Expand All @@ -129,10 +130,10 @@
// document unless you know what you're doing. If in doubt ask your friendly neighbourhood
// Team Contact.
wgPatentURI: "https://www.w3.org/2004/01/pp-impl/83726/status",

tocIntroductory: true,
//maxTocLevel: 4,

// Spec URLs
ariaSpecURLs: {
"ED": "https://w3c.github.io/aria/",
Expand All @@ -146,7 +147,7 @@
"FPWD": "https://www.w3.org/TR/core-aam-1.2/",
"REC": "https://www.w3.org/TR/core-aam-1.2/"
},

preProcess: [ linkCrossReferences ]
}
</script>
Expand All @@ -164,7 +165,7 @@ <h2>Introduction</h2>
<p><a class="termref">User agents</a> acquire information from the <abbr title="Document Object Model">DOM</abbr> [[DOM]] and create a parallel structure called the <a class="termref">accessibility tree</a>, made up of <a class="termref">accessible objects</a>. An accessible object provides information about its <a class="termref">role</a>, <a class="termref">states</a>, and <a class="termref">properties</a>. An example is an accessible object whose role is <code>menuitem</code>, is currently in an <code>enabled</code> state, with a <code>haspopup</code> property, indicating that it leads to a sub-menu. </p>
<p>The two properties of accessible objects described in this document are its <a class="termref">accessible name</a> and <a class="termref">accessible description</a>. The name is a short label that provides information about the purpose of the object. An example of an accessible name for a menu item is <code>New</code>, signifying that the menu item provides for the creation of new documents, windows, and so on. </p>
<p>The description is a short explanation that further clarifies the nature of the accessible object. It is not always necessary to provide a description if the name is sufficient, but it can help a user better understand the use of the object.</p>
<p><a class="termref">Accessibility <abbr title="Application Programming Interfaces">APIs</abbr></a> currently support flat, unstructured strings for accessible names and descriptions. The result of the name/description computation is thus a flat string. </p>
<p><a class="termref">Accessibility <abbr title="Application Programming Interfaces">APIs</abbr></a> currently support flat, unstructured strings for accessible names and descriptions. The result of the name/description computation is thus a flat string. </p>
<p>The terms "accessible name" and "accessible description" are used to emphasize that they are properties of <a class="termref">accessible objects</a> as exposed by <a class="termref">Accessibility <abbr title="Application Programming Interfaces">APIs</abbr></a>. However, they are frequently referred to hereafter as simply "name" and "description".</p>
</section>
<section id="conformance">
Expand Down Expand Up @@ -213,7 +214,7 @@ <h4>Terminology</h4>
<dt>Current node</dt>
<dd>The <abbr title="Document Object Model">DOM</abbr> <a class="termref">node</a> currently traversed to compute the <code>root node</code>'s text equivalent. Initially, the <code>current node</code> is the <code>root node</code>, but at later stages is either some descendant of the <code>root node</code>, or another referenced node.</dd>
<dt>Flat string</dt>
<dd>A string of characters where all carriage returns, newlines, tabs, and form-feeds are replaced with a single space, and multiple spaces are reduced to a single space. The string contains only character data; it does not contain any markup. </dd>
<dd>A string of characters where all carriage returns, newlines, tabs, and form-feeds are replaced with a single space, and multiple spaces are reduced to a single space. The string contains only character data; it does not contain any markup. </dd>
<dt>Total accumulated text</dt>
<dd>The text equivalent computed up to, but not including the <code>current node</code>.</dd>
<dt>Accumulated text</dt>
Expand Down Expand Up @@ -266,7 +267,7 @@ <h4>Computation steps</h4>
<li id="step2B">Otherwise:
<ul>
<li>if computing a <a class="termref" data-lt="accessible name">name</a>, and the <code>current node</code> has an <code>aria-labelledby</code> <a class="termref">attribute</a> that contains at least one valid IDREF, and the <code>current node</code> is not already part of an <code>aria-labelledby</code> traversal, process its IDREFs in the order they occur: </li>
<li>or, if computing a <a class="termref" data-lt="accessible description">description</a>, and the <code>current node</code> has an <code>aria-describedby</code> <a class="termref">attribute</a> that contains at least one valid IDREF, and the <code>current node</code> is not already part of an <code>aria-describedby</code> traversal, process its IDREFs in the order they occur:
<li>or, if computing a <a class="termref" data-lt="accessible description">description</a>, and the <code>current node</code> has an <code>aria-describedby</code> <a class="termref">attribute</a> that contains at least one valid IDREF, and the <code>current node</code> is not already part of an <code>aria-describedby</code> traversal, process its IDREFs in the order they occur:
<ol>
<li id="step2B.i">Set the <code>accumulated text</code> to the empty string.</li>
<li id="step2B.ii">For each IDREF:
Expand Down Expand Up @@ -365,7 +366,7 @@ <h4>Computation steps</h4>
</li>
<li id="step2G">Otherwise, if the <code>current node</code> is a <a class="termref">Text node</a>, return its textual contents.</li>
<li id="step2H">Otherwise, if the <code>current node</code> is a descendant of an element whose <a class="termref">Accessible Name</a> or <a class="termref">Accessible Description</a> is being computed, and contains descendants, proceed to 2F.i.</li>
<li id="step2I">Otherwise, if the <code>current node</code> has a <a class="termref">Tooltip attribute</a>, return its value.
<li id="step2I">Otherwise, if the <code>current node</code> has a <a class="termref">Tooltip attribute</a>, return its value.
<div><details>
<summary>Comment:</summary>
<p>Tooltip attributes are used only if nothing else, including subtree content, has provided results. </p>
Expand Down

0 comments on commit 6e63219

Please sign in to comment.