Skip to content

Commit

Permalink
About Section: Add a page about contributing and APG TF membership (p…
Browse files Browse the repository at this point in the history 
…ull #2734)

Resolves #2706 by adding a new page providing instructions for contributing to the APG. It describes each of the contribution channels and describes how to utilize each of them.

---------

Co-authored-by: Jon Gunderson <[email protected]>
Co-authored-by: Daniel Montalvo <[email protected]>
Co-authored-by: JaEun Jemma Ku <[email protected]>
  • Loading branch information
@mcking65 @jongund
@daniel-montalvo @a11ydoer
4 people authored Oct 2, 2023
1 parent f97050b commit 7fb7c8e
Show file tree
Hide file tree
Showing 2 changed files with 139 additions and 0 deletions.
7 changes: 7 additions & 0 deletions content/about/about.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,13 @@ <h2><a href="aria-basics/aria-basics.html">ARIA Basics</a></h2>
<a href="aria-basics/aria-basics.html">ARIA Basics</a>.
</p>
</li>
<li>
<h2><a href="contributing/contributing.html">Contributing to the APG</a></h2>
<p>
The APG Task Force relies on broad community representation and participation to continuously improve the usefulness and quality of the APG.
<a href="contributing/contributing.html">Learn how you can contribute and help promote development of accessible experiences</a>.
</p>
</li>
<li>
<h2><a href="acknowledgements/acknowledgements.html">Acknowledgements</a></h2>
<p>
Expand Down
132 changes: 132 additions & 0 deletions content/about/contributing/contributing.html
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,132 @@
<!DOCTYPE html>
<html lang="en">

<head>
<meta charset="UTF-8">
<meta content="width=device-width, initial-scale=1.0" name="viewport">
<title>Contributing to the APG</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>Contributing to the APG</h1>

<section id="introduction">
<h2>Introduction </h2>
<p>
Continuous improvement to the utility and quality of the ARIA Authoring Practices Guide (APG) depends on broad community input and participation.
Anyone may contribute feedback, suggestions, or code via the channels described below.
However, if you would like to contribute regularly, please consider
<a href="#joining-the-authoring-practices-task-force">joining the Authoring Practices Task Force</a>.
As a task force participant, you and your organization have greater influence over APG development, and are listed as contributors where appropriate.
</p>
</section>

<section id="providing-feedback">
<h2>Providing feedback</h2>
<p>
The APG provides two public feedback channels -- GitHub and email.
Links to both are provided at the bottom of every page in the APG.
</p>
<p>
GitHub issues are the best way to ask a question, make a suggestion, or report a problem.
Before creating a new issue, it is helpful if you first review existing issues to determine whether there is an issue addressing the same concern.
If so, please comment on that issue rather than raising another.
If the concern you would like addressed is related to an example implementation of an APG pattern, at the bottom of the page, next to the revision date, there is a link named "Related Issues".
That link opens a GitHub project containing all issues associated with the relevant pattern and its examples.
</p>
<p>
<a href="https://github.com/w3c/aria-practices/issues">View and create APG issues on GitHub.</a>
</p>
<p>
The task force also uses the aria-practices public mailing list for email discussion.
Meeting announcements, agendas, and links to minutes are sent to the mailing list.
While GitHub issues are the preferred place to discuss APG content, the mailing list is available to anyone who would prefer to communicate by
<a href="mailto:[email protected]">sending email to the ARIA Authoring Practices public mailing list</a>.
</p>
<p>
<a href="https://lists.w3.org/Archives/Public/public-aria-practices/">View the aria-practices mailing list archive</a>.
</p>
</section>

<section id="Making-improvements-to-documentation-or-code">
<h2>Making improvements to documentation or code</h2>
<p>
If you would like to help improve the APG with enhancements or fixes to documentation or code, please adhere to the following procedure.
</p>
<ol>
<li>Get your development environment ready:
<ul>
<li>
Install and configure linters as described in the
<a href="https://github.com/w3c/aria-practices#code-conformance">code conformance section of the repository readme</a>.
</li>
<li>
Read our wiki page about
<a href="https://github.com/w3c/aria-practices/wiki/Submitting-Pull-Requests">preparing and submitting pull requests</a>.
</li>
</ul>
</li>
<li>Comment in an existing issue or raise a new issue, expressing your willingness to help and briefly summarizing the nature of your proposed resolution.</li>
<li>An editor will confirm there are no conflicting plans and, if needed, provide guidance.</li>
<li>Do some fabulous work and submit a pull request.</li>
<li>Watch your GitHub notifications and respond to feedback during the pull request review process.</li>
</ol>
<p>
If you run into any difficulties, please feel free to ask questions either via a GitHub issue or by
<a href="mailto:[email protected]">sending email to the ARIA Authoring Practices public mailing list</a>.
</p>
</section>

<section id="joining-the-authoring-practices-task-force">
<h2>Joining The Authoring Practices Task Force</h2>
<p>
The APG is developed by the
<a target="_blank" href="https://www.w3.org/WAI/ARIA/task-forces/practices/">ARIA Authoring Practices Task Force</a>,
which is a sub-group of the
<a target="_blank" href="https://www.w3.org/WAI/ARIA/">ARIA Working Group</a>.
The task force meets weekly to coordinate work on development of the APG.
Task force participants are expected to regularly attend meetings and to actively contribute.
Examples of contributions include:
</p>
<ul>
<li>Testing the functionality and accessibility of example implementations of the APG patterns</li>
<li>Fixing bugs and implementing enhancements in example implementations of the APG patterns</li>
<li>Helping write responses to community feedback</li>
<li>Reviewing and editing documentation</li>
<li>Designing or engineering pattern implementation examples</li>
<li>Creating and editing patterns and practices for ARIA usage</li>
</ul>
<p>
To participate in the Authoring Practices Task Force, you first need to
<a href="https://www.w3.org/WAI/ARIA/participation">become a participant in the ARIA Working Group</a>.
If you are already a participant in the ARIA Working Group, contact
<a href="https://www.w3.org/staff/#dmontalvo">Daniel Montalvo</a>
and request membership in the Authoring Practices Task Force.
</p>
</section>

<section id="Helping-provide-assistive-technology-support-data">
<h2>Helping provide assistive technology support data</h2>
<p>
The assistive technology support tables included on APG example pages, e.g.,
<a href="../../patterns/radio/examples/radio-activedescendant.html#at-support">Assistive Technology Support for Radio Group Example Using aria-activedescendant</a>,
are provided by the
<a href="https://www.w3.org/groups/cg/aria-at/">ARIA and Assistive Technologies (ARIA-AT) Community Group</a>.
The ARIA-AT community group aims to ensure APG patterns have consistent and interoperable accessibility support.
If you would like to contribute to this aspect of the APG, you can learn more about the ARIA-AT project and how to contribute at
<a href="https://aria-at.w3.org/">ARIA and Assistive Technologies Home</a>.
</p>
</section>

</main>
</body>

</html>

0 comments on commit 7fb7c8e

Please sign in to comment.