Skip to content

Commit

Permalink
About Page: Convert to an About section overview that links to severa…
Browse files Browse the repository at this point in the history 
…l new pages within the about APG section (pull #2558)

Resolves #2423 by:
* Moving content on About page to new subpages for Introduction, ARIA Basics, Acknowledgements, Change History, and References
* Making the About page a landing page that provides links to the new subpages

---------

Co-authored-by: JaEun Jemma Ku <a11ydoer@gmail.com>
Co-authored-by: alflennik <alflennik@users.noreply.github.com>
Co-authored-by: Nick Schonning <nschonni@gmail.com>
Co-authored-by: Sarah Higley <smhigley@users.noreply.github.com>
Co-authored-by: Jon Gunderson <jongund@illinois.edu>
Co-authored-by: Andrea N. Cardona <cardona.n.andrea@gmail.com>
  • Loading branch information
@mcking65 @a11ydoer
@alflennik @nschonni @smhigley @jongund @andreancardona
7 people committed Apr 11, 2023
1 parent 9a729ec commit edc6ab7
Show file tree
Hide file tree
Showing 7 changed files with 597 additions and 282 deletions.
316 changes: 41 additions & 275 deletions content/about/about.html
View file

Large diffs are not rendered by default.

153 changes: 153 additions & 0 deletions content/about/acknowledgements/acknowledgements.html
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,153 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta content="width=device-width, initial-scale=1.0" name="viewport">
<title>Acknowledgements</title>

<!-- Core JS and CSS shared by about content-->
<link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2016/base.css">
<link rel="stylesheet" href="../../shared/css/core.css">
<script src="../../shared/js/highlight.pack.js"></script>
<script src="../../shared/js/app.js"></script>
<script src="../../shared/js/skipto.js"></script>
</head>
<body>
<main>
<h1>Acknowledgements</h1>

<section id="editors">
<h2>Editors</h2>
<dl>
<dt>Current editors:</dt>
<dd class="editor p-author h-card vcard" data-editor-id="44582">
<a class="ed_mailto u-email email p-name" href="mailto:mck@meta.com">Matt King</a>
(<span class="p-org org h-org">Meta</span>)
</dd>
<dd class="editor p-author h-card vcard" data-editor-id="74097">
<a class="ed_mailto u-email email p-name" href="mailto:jku@uic.edu">JaEun Jemma Ku</a>
(<span class="p-org org h-org">University of Illinois</span>)
</dd>
<dd class="editor p-author h-card vcard" data-editor-id="37155">
<a class="ed_mailto u-email email p-name" href="mailto:nurthen@adobe.com">James Nurthen</a>
(<span class="p-org org h-org">Adobe</span>)
</dd>
<dd class="editor p-author h-card vcard" data-editor-id="74040">
<span class="p-name fn">Zoë Bijl</span> (<span class="p-org org h-org">Invited Expert</span>)
</dd>
<dd class="editor p-author h-card vcard" data-editor-id="34017">
<a class="u-url url p-name fn" href="https://www.w3.org/People/cooper/">Michael Cooper</a>
(<span class="p-org org h-org">W3C</span>)
</dd>
<dt>Former editors:</dt>
<dd class="editor p-author h-card vcard" data-editor-id="42279">
<span class="p-name fn">Joseph Scheuhammer</span> (<span class="p-org org h-org">Inclusive Design
Research Centre, OCAD University</span>) - Until
<time datetime="2014-10-01">01 October 2014</time>
</dd>
<dd class="editor p-author h-card vcard" data-editor-id="41725">
<span class="p-name fn">Lisa Pappas</span> (<span class="p-org org h-org">SAS</span>) - Until
<time datetime="2009-10-01">01 October 2009</time>
</dd>
<dd class="editor p-author h-card vcard" data-editor-id="2460">
<span class="p-name fn">Rich Schwerdtfeger</span> (<span class="p-org org h-org">IBM Corporation</span>) - Until
<time datetime="2014-10-01">01 October 2014</time>
</dd>
</dl>
</section>

<section id="honorary-editor">
<h2>Honorary Editor</h2>
<p>
This version of the ARIA Authoring Practices Guide is dedicated to the memory of Carolyn MacLeod whose contributions are visible throughout the entire guide.
She was dedicated to all aspects of the work of the APG Task Force from writing code and suggesting editorial revisions to testing examples with assistive technologies.
</p>
<ul>
<li>Carolyn MacLeod (IBM Canada)</li>
</ul>
</section>

<section id="major-contributors-to-version-1-1">
<h2>Major Contributors to Version 1.1</h2>
<p>
While <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Authoring Practices 1.1 is the work of
the entire Authoring Practices Task Force and also benefits from many people throughout the open source
community who both contribute significant work and provide valuable feedback, special thanks goes to the
following people who provided distinctly large portions of the content and code in version 1.1.
</p>
<ul>
<li>Jon Gunderson and Nicholas Hoyt of the Division of Disability Resources and Education Services at the
University of Illinois Urbana/Champaign and the students Max Foltz, Sulaiman Sanaullah, Mark McCarthy, and
Jinyuan Zhou for their contributions to the development of many of the design pattern examples.</li>
<li>Valerie Young of Bocoup and her sponsor, Facebook, for development of the example test framework and
regressions tests for more than 50 examples.</li>
<li>Simon Pieters of Bocoup and his sponsor, Facebook, for authoring of significant guidance sections,
including comprehensive treatment of the topic of accessible names and descriptions.</li>
</ul>
</section>

<section id="active-participants">
<h2>Participants active in the ARIA Authoring Practices Task Force</h2>
<ul>
<li>Ann Abbott (Invited Expert)</li>
<li>Shirisha Balusani (Microsoft Corporation)</li>
<li>Dorothy Bass (Wells Fargo Bank N.A.)</li>
<li>Curt Bellew (Oracle)</li>
<li>Zoë Bijl (Invited Expert)</li>
<li>
Michael Cooper (<abbr title="World Wide Web Consortium">W3C</abbr>)
</li>
<li>Bryan Garaventa (Level Access)</li>
<li>Jon Gunderson (University of Illinois at Urbana-Champaign)</li>
<li>Jesse Hausler(Salesforce)</li>
<li>Sarah Higley (Microsoft Corporation)</li>
<li>Hans Hillen (The Paciello Group, LLC)</li>
<li>Matt King (Facebook)</li>
<li>Jaeun Ku (University of Illinois at Urbana-Champaign)</li>
<li>Aaron Leventhal (Google)</li>
<li>Carolyn MacLeod (IBM Corporation)</li>
<li>Mark McCarthy (University of Illinois at Urbana-Champaign)</li>
<li>James Nurthen (Adobe)</li>
<li>Scott O'Hara (The Paciello Group, LLC)</li>
<li>Simon Pieters (Bocoup)</li>
<li>Scott Vinkle (Shopify)</li>
<li>Evan Yamanishi (W. W. Norton)</li>
<li>Valerie Young (Bocoup)</li>
</ul>
</section>

<section id="commenters-and-contributors">
<h2>Other commenters and contributors to Version 1.1</h2>
<ul>
<li>Vyacheslav Aristov</li>
<li>J. Renée Beach</li>
<li>Kasper Christensen</li>
<li>Gerard K. Cohen</li>
<li>Anne-Gaelle Colom</li>
<li>Kevin Coughlin</li>
<li>Cameron Cundiff</li>
<li>Manish Dahamiwal</li>
<li>Gilmore Davidson</li>
<li>Boris Dušek</li>
<li>Michael Fairchild</li>
<li>Jeremy Felt</li>
<li>Rob Fentress</li>
<li>Geppy</li>
<li>Tatiana Iskandar</li>
<li>Patrick Lauke</li>
<li>Marek Lewandowski</li>
<li>Dan Matthew</li>
<li>Shane McCarron</li>
<li>Victor Meyer</li>
<li>Jonathan Neal</li>
<li>Philipp Rudloff</li>
<li>Joseph Scheuhammer</li>
<li>Nick Schonning</li>
<li>Thomas Corthals</li>
<li>Christopher Tryens</li>
</ul>
</section>

</main>
</body>
</html>
59 changes: 59 additions & 0 deletions content/about/aria-basics/aria-basics.html
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,59 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta content="width=device-width, initial-scale=1.0" name="viewport">
<title>ARIA Basics</title>

<!-- Core JS and CSS shared by all About content -->
<link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2016/base.css">
<link rel="stylesheet" href="../../shared/css/core.css">
<script src="../../shared/js/highlight.pack.js"></script>
<script src="../../shared/js/app.js"></script>
<script src="../../shared/js/skipto.js"></script>
</head>
<body>
<main>
<h1>ARIA Basics</h1>
<p>
A solid understanding of what ARIA is, what accessibility semantics are, and their purpose and limitations can facilitate success when applying guidance provided by the APG.
</p>
<section id="what-is-aria">
<h2>What is ARIA?</h2>
<p>
ARIA, which stands for Accessible Rich Internet Applications, refers to a set of more than 150 declarations that can be added into web page code so assistive technologies, such as screen readers, can understand how to present the page.
For example, the text "Home" might be visually presented as a heading, an interactive link or button, or as the label for a phone number.
If the web code does not declare what the element containing that text represents, a screen reader cannot present it to a blind user in an accessible way.
</p>
<p>
The declarations that can be made with ARIA are defined by the <a href="https://www.w3.org/TR/wai-aria/">WAI-ARIA Specification</a>.
These attributes and other features required to make sites usable by people who rely on assistive technologies or keyboard navigation are not natively included in the languages used to create web sites, such as HTML, JavaScript, CSS, and SVG.
The W3C Web Accessibility Initiative's (WAI) Accessible Rich Internet Applications working group (ARIA WG) is addressing these deficiencies through several W3C standards efforts.
The <a href="https://www.w3.org/WAI/intro/aria.php">WAI-ARIA Overview</a>
provides additional background on WAI-ARIA, summarizes those efforts, and lists the other documents included in the WAI-ARIA suite.
</p>
</section>
<section id="semantics">
<h2>What Are Accessibility Semantics?</h2>
<p>
Accessibility semantics refer to the meaning of user interface elements that need to be conveyed to assistive technology users in order for those users to understand and use the elements.
For example, people who can visually perceive a search icon button understand the element can be activated to perform a search by the way it is styled and positioned.
To make that icon accessible to a screen reader user, one of the semantics that needs to be communicated is that the element represents an interactive button.
This is accomplished by encoding the element in a way that enables browsers to determine that the accessibility role of the element is <q>button</q>.
Similarly, another accessibility semantic browsers must be able to convey for the search icon is its accessible name, which inturn enables screen reader users to know the purpose of the button.
</p>
<p>
The types of accessibility semantics that may be required to make an element accessible include:
</p>
<ul>
<li>
Role: The type of element, e.g., <q>button</q> or <q>list</q>.
ARIA includes more than 80 roles that can be declared in content.
</li>
<li>Properties: Attributes that provide information about the nature of an element, such as its name, orientation, or position in a set.</li>
<li>State: A dynamic property, such as selected, checked, or disabled, whose value may be changed by users or application events.</li>
</ul>
</section>
</main>
</body>
</html>
66 changes: 66 additions & 0 deletions content/about/change-history/change-history.html
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta content="width=device-width, initial-scale=1.0" name="viewport">
<title>Change History</title>

<!-- Core JS and CSS shared by about content-->
<link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2016/base.css">
<link rel="stylesheet" href="../../shared/css/core.css">
<script src="../../shared/js/highlight.pack.js"></script>
<script src="../../shared/js/app.js"></script>
<script src="../../shared/js/skipto.js"></script>
</head>
<body>
<main>
<h1>Change History</h1>
<p>
APG 1.1 supported ARIA 1.1, and this version, APG 1.2, includes changes to support version 1.2 of the ARIA specification.
It also includes nearly 200 significant updates to improve the quality and breadth of content.
A <a href="https://github.com/w3c/aria-practices/wiki/Change-Log-for-November-2021-APG-1.2-Note-Release-1">detailed log of all changes</a> is available on the wiki of the w3c/aria-practices GitHub repository.
Highlights of major changes to support ARIA 1.2 as well as some of the improvements include the following.
</p>
<ul>
<li>Added section to provide guidance related to 38 document structure roles, 18 of which are new in ARIA 1.2.</li>
<li>Revised guidance for roles where naming requirements changed in ARIA 1.2. ARIA 1.2 prohibits names on some roles. ARIA 1.2 removed naming requirements from some other roles.</li>
<li>Added naming guidance for 18 roles that are new in ARIA 1.2.</li>
<li>Revised the combobox pattern and 4 combobox examples to reflect the ARIA 1.2 revisions to combobox.</li>
<li>Added example illustrating changes in ARIA 1.2 that enable creation of custom select-only comboboxes, which are similar to HTML select elements. This replaces the Collapsible Listbox example, which is now deprecated.</li>
<li>Revised the listbox pattern to specify how to utilize the new ARIA 1.2 support for named groups of options and Added a new listbox example to demonstrate the named option group feature.</li>
<li>Revised the editor menubar example to illustrate new ARIA 1.2 support for named groups of items in a menu.</li>
<li>Updated the listbox and tree patterns to reflect current browser processing of aria-selected and provided guidance regarding the use of aria-checked to communicate selection.</li>
<li>Added section providing guidance about properties used with range widgets, such as aria-valuemin and aria-valuemax.</li>
<li>Added a design pattern and example implementation of the meter role, which is new in ARIA 1.2</li>
<li>Added two examples that demonstrate how to create rating inputs, one based on slider and one based on radio group.</li>
<li>Added two other slider examples: a vertical temperature slider and a media seek slider.</li>
<li>Added a switch design pattern and three example implementations: one made from a div element, one based on HTML button, and one that uses HTML checkbox input.</li>
<li>Added a button example that illustrates use of the new ARIA 1.2 IDL interface.</li>
<li>Added a date picker example that illustrates choosing a date with a combobox.</li>
<li>Added another example of a disclosure navigation menu that demonstrates how to include top-level links.</li>
<li>Added example of a sortable table.</li>
<li>Changed all example pages to include a <q>Jump to</q> menu, a button to open the example in CodePen, and added a prominently placed warning with guidance about testing before re-using example code.</li>
<li>Improved support for high contrast settings and added detailed documentation of high contrast support in many examples.</li>
<li>Improved support for touch-based screen readers in several examples, most notably in sliders.</li>
<li>Due to change in ARIA 1.2, removed Math role from list of roles that have presentational children.</li>
<li>Developed a <a href="https://github.com/w3c/aria-practices/wiki/Code-Guide#apg-coding-standards">comprehensive set of coding standards for HTML, CSS, and Javascript</a> for the APG and updated a significant portion of content to conform with the standards.</li>
<li>In response to feedback, fixed many documentation errors and functional bugs in examples.</li>
</ul>
<p>Comprehensive lists of closed issues included in APG 1.2 release 1 are tracked in the following GitHub milestones.</p>
<ul>
<li>
<a href="https://github.com/w3c/aria-practices/milestone/2?closed=1">APG 1.2 Release 1 Milestone</a>:
Github issues closed in the first publication of APG 1.2 as a W3C Note in November 2021.
</li>
<li>
<a href="https://github.com/w3c/aria-practices/milestone/10">APG 1.2 Working Draft 3 Milestone</a>:
Github issues closed in the third working draft of APG 1.2 published in November 2019.
</li>
<li>
<a href="https://github.com/w3c/aria-practices/milestone/7">APG 1.2 Working Draft 1 milestone</a>:
GitHub issues closed in the first working draft of APG 1.2 published on July 17, 2018.
</li>
</ul>
</main>
</body>
</html>
Loading

0 comments on commit edc6ab7

Please sign in to comment.