For publication / deploy on Wednesday April 12 or Thursday April 13 (see comments for date determination)

ARIA/apg/about/acknowledgements/acknowledgements.md

@@ -0,0 +1,200 @@
+---
+# This file was generated by scripts/pre-build/library/formatForJekyll.js
+title: "Acknowledgements"
+ref: /ARIA/apg/about/acknowledgements/
+
+github:
+  repository: w3c/aria-practices
+  branch: main
+  path: content/about/acknowledgements/acknowledgements.html
+feedbackmail: public-aria-practices@w3.org
+permalink: /ARIA/apg/about/acknowledgements/
+
+sidebar: true
+
+
+
+# Context here: https://github.com/w3c/wai-aria-practices/issues/31
+type_of_guidance: APG
+
+lang: en
+---
+<meta charset="UTF-8" />
+<meta content="width=device-width, initial-scale=1.0" name="viewport" />
+<title>Acknowledgements</title>
+
+<script src="../../../../content-assets/wai-aria-practices/shared/js/highlight.pack.js"></script>
+<script src="../../../../content-assets/wai-aria-practices/shared/js/app.js"></script>
+<script src="../../../../content-assets/wai-aria-practices/shared/js/skipto.js"></script>
+
+
+<link 
+  rel="stylesheet"
+  href="{{ '/content-assets/wai-aria-practices/styles.css' | relative_url }}"
+>
+<!-- Code highlighting styles -->
+<link 
+  rel="stylesheet"
+  href="{{ '/content-assets/wai-aria-practices/shared/css/github.css' | relative_url }}"
+>
+
+<script>
+const addBodyClass = undefined;
+const enableSidebar = true;
+if (addBodyClass) document.body.classList.add(addBodyClass);
+if (enableSidebar) document.body.classList.add('has-sidebar');
+</script>
+
+
+<script>
+    const parentPage = window.location.pathname.match(
+      /\/(patterns|practices|about)\//
+    )?.[1];
+    if (parentPage) {
+      const parentHref = 'a[href*="' + parentPage + '"]';
+      document.querySelector(parentHref).classList.add('active');
+    }
+  </script>
+<div>
+
+    <div>
+
+
+      <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>
+
+    </div>
+
+</div>
+<script 
+  src="{{ '/content-assets/wai-aria-practices/shared/js/skipto.js' | relative_url }}"
+></script>

ARIA/apg/about/aria-basics/aria-basics.md

@@ -0,0 +1,106 @@
+---
+# This file was generated by scripts/pre-build/library/formatForJekyll.js
+title: "ARIA Basics"
+ref: /ARIA/apg/about/aria-basics/
+
+github:
+  repository: w3c/aria-practices
+  branch: main
+  path: content/about/aria-basics/aria-basics.html
+feedbackmail: public-aria-practices@w3.org
+permalink: /ARIA/apg/about/aria-basics/
+
+sidebar: true
+
+
+
+# Context here: https://github.com/w3c/wai-aria-practices/issues/31
+type_of_guidance: APG
+
+lang: en
+---
+<meta charset="UTF-8" />
+<meta content="width=device-width, initial-scale=1.0" name="viewport" />
+<title>ARIA Basics</title>
+
+<script src="../../../../content-assets/wai-aria-practices/shared/js/highlight.pack.js"></script>
+<script src="../../../../content-assets/wai-aria-practices/shared/js/app.js"></script>
+<script src="../../../../content-assets/wai-aria-practices/shared/js/skipto.js"></script>
+
+
+<link 
+  rel="stylesheet"
+  href="{{ '/content-assets/wai-aria-practices/styles.css' | relative_url }}"
+>
+<!-- Code highlighting styles -->
+<link 
+  rel="stylesheet"
+  href="{{ '/content-assets/wai-aria-practices/shared/css/github.css' | relative_url }}"
+>
+
+<script>
+const addBodyClass = undefined;
+const enableSidebar = true;
+if (addBodyClass) document.body.classList.add(addBodyClass);
+if (enableSidebar) document.body.classList.add('has-sidebar');
+</script>
+
+
+<script>
+    const parentPage = window.location.pathname.match(
+      /\/(patterns|practices|about)\//
+    )?.[1];
+    if (parentPage) {
+      const parentHref = 'a[href*="' + parentPage + '"]';
+      document.querySelector(parentHref).classList.add('active');
+    }
+  </script>
+<div>
+
+    <div>
+
+      <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>
+    </div>
+
+</div>
+<script 
+  src="{{ '/content-assets/wai-aria-practices/shared/js/skipto.js' | relative_url }}"
+></script>