Skip to content

Add PHL as co-editor #240

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 14, 2020
Merged

Add PHL as co-editor #240

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e598908
Add PHL as co-editor
patrickhlauke Aug 13, 2020
48a6e27
Merge branch 'gh-pages' into patrickhlauke-add-editor
scottaohara Aug 14, 2020
e19a413
Update index.html
scottaohara Aug 14, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 24 additions & 13 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,14 +12,20 @@
url: "https://www.paciellogroup.com",
company: "The Paciello Group",
companyURL: "https://www.paciellogroup.com",
w3cid: "35007",
w3cid: "35007"
},
{
name: "Scott O'Hara",
url: "https://www.paciellogroup.com",
company: "The Paciello Group",
companyURL: "https://www.paciellogroup.com",
w3cid: "103856",
w3cid: "103856"
},
{ name: "Patrick H. Lauke",
url: "https://tetralogical.com",
company: "TetraLogical",
companyURL: "https://tetralogical.com/",
w3cid: '35129'
},
],
previousMaturity: "WD",
Expand Down Expand Up @@ -63,11 +69,11 @@ <h2 id="rules-wd">
Web developers MAY use the ARIA `role` and `aria-*` attributes on
<a data-cite="html/dom.html#elements">HTML elements</a>, in accordance
with the requirements described in [[wai-aria-1.1]], except where these
conflict with the <dfn><a data-cite=
"wai-aria-1.1#host_general_conflict">strong native semantics</a></dfn>
or are equal to the <dfn><a data-cite=
"wai-aria-1.1#implicit_semantics">implicit ARIA semantics</a></dfn> of
a given HTML element. These constraints are intended to prevent
conflict with the
<dfn><a data-cite="wai-aria-1.1#host_general_conflict">strong native semantics</a></dfn>
or are equal to the
<dfn><a data-cite="wai-aria-1.1#implicit_semantics">implicit ARIA semantics</a></dfn>
of a given HTML element. These constraints are intended to prevent
developers from making assistive technology products report nonsensical
user interface (UI) information that does not represent the actual UI
of the document.
Expand All @@ -92,7 +98,8 @@ <h2 id="rules-wd">
<aside class="example">
The following uses a `role=button` on a `button` element. This is unnecessary, as "button"
is already exposed as the implicit role for the element. In practice this redundancy will
likely not have any unforeseen side effects, other than unnecessarily making the markup more verbose, and incorrectly signaling to other developers that this practice is useful.
likely not have any unforeseen side effects, other than unnecessarily making the markup
more verbose, and incorrectly signaling to other developers that this practice is useful.
<pre class="HTML">
&lt;button role="button"&gt;...&lt;/button&gt;
</pre>
Expand All @@ -109,7 +116,10 @@ <h2 id="rules-wd">

<aside class="example">
The following uses a `role=list` on an `ul` element. This is generally unnecessary,
because the `ul` element is implicitly exposed as a `role=list`. However, some user agents suppress a list's implicit ARIA semantics if list markers are removed. Authors can use `role=list` to reinstate the role if necessary, though this practice would generally not be recommended, otherwise.
because the `ul` element is implicitly exposed as a `role=list`. However, some
user agents suppress a list's implicit ARIA semantics if list markers are removed.
Authors can use `role=list` to reinstate the role if necessary, though this practice
would generally not be recommended, otherwise.
<pre class="HTML">
&lt;ul role="list"&gt;...&lt;/ul&gt;
</pre>
Expand All @@ -136,9 +146,9 @@ <h2 id="docconformance">
<p>
The following table provides normative per-element document-conformance
requirements for the use of ARIA markup in HTML documents and describes
the <a>implicit ARIA semantics</a> that apply to <a data-cite=
"html/dom.html#elements">HTML elements</a> as defined in the [[html-aam-1.0|HTML
Accessibility API Mappings 1.0]] specification.
the <a>implicit ARIA semantics</a> that apply to
<a data-cite="html/dom.html#elements">HTML elements</a> as defined in
the [[html-aam-1.0|HTML Accessibility API Mappings 1.0]] specification.
</p>
<p>
Each language feature (element or attribute) in a cell in the first column implies the
Expand All @@ -153,7 +163,8 @@ <h2 id="docconformance">

<p class="note" id="aria-usage-note">
While setting an ARIA `role` and/or `aria-*` attribute that matches the
<span>implicit ARIA semantics</span> is NOT RECOMMENDED, in some situations explicitly setting these attributes can be helpful. For instance, in user agents which lack specific implicit semantics.
<span>implicit ARIA semantics</span> is NOT RECOMMENDED, in some situations explicitly setting
these attributes can be helpful. For instance, in user agents which lack specific implicit semantics.
</p>

<table class="simple">
Expand Down