Skip to content
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

Jump to bottom

[Wg/ARIA] Update to fit template requirements #601

Merged
merged 1 commit into from
Oct 3, 2024
Merged

[Wg/ARIA] Update to fit template requirements #601

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
17 changes: 12 additions & 5 deletions 2024/aria-charter.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -398,11 +398,11 @@ <h2>Success Criteria</h2>
them. For specifications which are not split apart in this fashion, no platform will be dropped out of the
specification without prior consultation with that platform's owners.</li>
</ul>
<p> Modules that reach <a href="https://www.w3.org/policies/process/#transition-rec">W3C Recommendation</a> are
<p> Specifications that reach <a href="https://www.w3.org/policies/process/#transition-rec">W3C Recommendation</a> are
considered successful when all of the following are present:</p>
<ul>
<li>Production of stable documents addressing the work items listed in the Deliverables section</li>
<li>Test suites for each module with conformance criteria</li>
<li>Test suites for each specification with conformance criteria</li>
<li>Availability of multiple, independent, interoperable implementations of each feature with conformance criteria
in each deliverable; as demonstrated by an implementation report (summarizing implementation status against the
relevant test suite) for each testable class of product, including user agents</li>
Expand All @@ -416,8 +416,15 @@ <h2>Success Criteria</h2>
<p>Each specification should contain separate sections detailing all known security and privacy implications for
implementers, Web authors, and end users.</p>
<p>There should be testing plans for each specification, starting from the earliest drafts.</p>
<p> To promote interoperability, all changes made to specifications should have <a
href="https://www.w3.org/2019/02/testing-policy.html">tests</a>.</p>
<p>To promote interoperability, all changes made to specifications
in Candidate Recommendation
or to features that have deployed implementations
should have <a href='https://www.w3.org/2019/02/testing-policy.html'>tests</a>.
Testing efforts should be declared in the <a href="https://github.com/web-platform-tests/wpt">Web Platform Tests</a> project.</p>
<p>This Working Group expects to follow the
TAG <a href="https://www.w3.org/TR/design-principles/">Web Platform Design Principles</a>.
</p>
<p>All new features should have expressions of interest from at least two potential implementors before being incorporated in the specification.</p>
</section>
<section id="coordination">
<h2>Coordination</h2>
Expand Down Expand Up @@ -517,7 +524,7 @@ <h2>
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and
meetings) will be available from the <a href="https://www.w3.org/WAI/about/groups/ariawg/">Accessible Rich Internet Applications
meetings) will be available from the <a href="https://www.w3.org/groups/wg/aria">Accessible Rich Internet Applications
Working Group home page.</a>
</p>
<p>
Expand Down