You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>In order to advance to <ahref="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each normative specification is expected to have <ahref="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent interoperable implementations</a> of every feature defined in the specification, where interoperability can be verified by passing open test suites and two or more implementations interoperating with each other. In order to advance to Proposed Recommendation, each normative specification must have an open test suite of every feature defined in the specification.</p>
307
-
<p>There should be testing plans for each specification, starting from the earliest drafts. To promote interoperability, all changes made to specifications in Candidate Recommendation or to features that have deployed implementations should have <ahref="https://www.w3.org/2019/02/testing-policy.html">tests</a>.</p>
308
-
<p>Each specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and end users. Each specification should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them and recommendations for maximising accessibility in implementations.</p>
309
-
<p>This Working Group expects to follow the <abbrtitle="Technical Architecture Group">TAG</abbr><ahref="https://www.w3.org/TR/design-principles/">Web Platform Design Principles</a>. </p>
should have expressions of interest from at least two potential implementors before being incorporated in the
335
+
specification.</p>
310
336
<p>Additional success criteria:</p>
311
337
<ul>
312
338
<li>Advancement of WAI-Adapt support on the web via specifications published by this group and features incorporated into other work;</li>
@@ -319,8 +345,20 @@ <h2>Success Criteria</h2>
319
345
320
346
<sectionid="coordination">
321
347
<h2>Coordination</h2>
322
-
<p>For all specifications, this Working Group will seek <ahref="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">horizontal review</a> for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the <ahref="https://www.w3.org/2001/tag/"><abbrtitle="Technical Architecture Group">TAG</abbr></a>. Invitation for review must be issued during each major standards-track document transition, including <ahref="https://www.w3.org/Consortium/Process/#RecsWD"><abbrtitle="First Public Working Draft">FPWD</abbr></a>. The Working Group is encouraged to engage collaboratively with the horizontal review groups throughout development of each specification. The Working Group is advised to seek a review at least 3 months before first entering <ahref="https://www.w3.org/Consortium/Process/#RecsCR"><abbrtitle="Candidate Recommendation">CR</abbr></a> and is encouraged to proactively notify the horizontal review groups when major changes
323
-
occur in a specification following a review.</p>
348
+
<p>For all specifications, this Working Group will seek <a
349
+
href="https://www.w3.org/guide/documentreview/#how-to-get-horizontal-review">horizontal review</a> for
350
+
accessibility, internationalization, privacy, and security with the relevant Working and
351
+
Interest Groups, and with the <ahref="https://www.w3.org/groups/other/tag/"
352
+
title="Technical Architecture Group">TAG</a>.
353
+
Invitation for review must be issued during each major standards-track document transition, including
354
+
<ahref="https://www.w3.org/policies/process/#RecsWD" title="First Public Working Draft">FPWD</a>. The
355
+
Working Group is encouraged to engage collaboratively with the horizontal review groups
356
+
throughout development of
357
+
each specification. The Working Group is advised to seek a review at least 3 months
358
+
before first entering
359
+
<ahref="https://www.w3.org/policies/process/#RecsCR" title="Candidate Recommendation">CR</a> and is encouraged
360
+
to proactively notify the horizontal review groups when major changes occur in a specification following a review.
361
+
</p>
324
362
325
363
<p>Additional technical coordination with the following Groups will be made, per the <ahref="https://www.w3.org/Consortium/Process/#WGCharter">W3C Process Document</a>:</p>
326
364
@@ -382,13 +420,21 @@ <h2 id="participation">
382
420
</h2>
383
421
<p> To be successful, this Working Group is expected to have 6 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a working day per week towards the Working Group. There is no minimum requirement for other Participants. </p>
384
422
<p>
385
-
The group encourages questions, comments, and issues on its public mailing lists and document repositories, as described in <ahref='#communication'>Communication</a>.
423
+
The group encourages questions, comments and issues on its public mailing lists and document repositories, as
424
+
described in <ahref="#communication">Communication</a>. The group also welcomes non-Members to make technical
425
+
contributions for ongoing work, provided they agree to the terms of the <a
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <ahref="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a>.
429
+
The Chairs should periodically look through the non-Members who have contributed to the Working Group and consider whether each one should be
430
+
invited to participate as an <ahref="https://www.w3.org/invited-experts/">Invited Expert</a>. If a non-Member
431
+
contributor would like to participate in meetings, they are encouraged to <a
432
+
href="https://www.w3.org/groups/wg/apa/instructions/">apply to be an Invited Expert</a></i>.
389
433
</p>
390
-
<p>Participants in the group are required (by the <ahref="https://www.w3.org/Consortium/Process/#ParticipationCriteria">W3C Process</a>) to follow the
391
-
W3C <ahref="https://www.w3.org/Consortium/cepc/">Code of Ethics and Professional Conduct</a>.</p>
434
+
435
+
<p>Participants in the group are required (by the <a
436
+
href="https://www.w3.org/policies/process/#ParticipationCriteria">W3C Process</a>) to follow the
437
+
W3C <ahref="https://www.w3.org/policies/code-of-conduct/">Code of Conduct</a>.</p>
392
438
</section>
393
439
394
440
@@ -397,13 +443,31 @@ <h2 id="participation">
397
443
<h2>
398
444
Communication
399
445
</h2>
400
-
<pid="public"> Technical discussions for this Working Group are conducted in <ahref="https://www.w3.org/Consortium/Process/#confidentiality-levels">public</a>: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests. The meetings themselves are not open to public participation, however, except by explicit one-time invitation from the chair(s). </p>
446
+
<pid="public">
447
+
Technical discussions for this Working Group are conducted in <a
448
+
href="https://www.w3.org/policies/process/#confidentiality-levels">public</a>: the meeting minutes from
449
+
teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue
450
+
tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and
451
+
Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution
452
+
requests.
453
+
The meetings themselves are not open to public participation, however.
454
+
</p>
455
+
401
456
<p> Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <ahref="https://www.w3.org/WAI/APA/">Accessible Platform Architectures Working Group home page.</a>
402
457
</p>
403
-
<p> This group primarily conducts its technical work at <ahref="mailto:[email protected]" id="public-name">[email protected]</a> (<ahref="https://lists.w3.org/Archives/Public/public-apa/">archive</a>) and on <ahref="https://github.com/w3c/apa/" id="public-github">GitHub</a>. <ahref="https://www.w3.org/WAI/APA/communication">Additional communication channels</a> are also used. The public is invited to review, discuss, and contribute to this work. </p>
404
-
<p>
405
-
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
406
-
</p>
458
+
459
+
<p>
460
+
Most Working Group teleconferences will focus on discussion
461
+
of particular specifications, and will be conducted on an as-needed basis.
462
+
</p>
463
+
<p> This group primarily conducts its technical work at <ahref="mailto:[email protected]"
464
+
id="public-name">[email protected]</a> (<ahref="https://lists.w3.org/Archives/Public/public-apa/">archive</a>) and
465
+
on <ahref="https://github.com/w3c/apa/" id="public-github">GitHub</a>. <a
466
+
href="https://www.w3.org/WAI/APA/communication">Additional communication channels</a> are also used. The public is
467
+
invited to review, discuss, and contribute to this work. </p>
468
+
<p>
469
+
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs
470
+
and members of the group, for member-only discussions in special cases when a participant requests such a discussion. </p>
407
471
</section>
408
472
409
473
@@ -412,13 +476,35 @@ <h2>
412
476
<h2>
413
477
Decision Policy
414
478
</h2>
415
-
<p> This group will seek to make decisions through consensus and due process, per the <ahref="https://www.w3.org/Consortium/Process/#Consensus">W3C Process Document (section 5.2.1, Consensus)</a>. Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required. </p>
416
-
<p> However, if a decision necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections. </p>
417
-
<p> To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional. A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue, or web-based survey), with a response period from 2 to 7 working days, depending on the chair's evaluation of the group consensus on the issue. If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group. </p>
418
-
<p> All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs or the Director. </p>
479
+
<p>
480
+
This group will seek to make decisions through consensus and due process, per the <a
481
+
href="https://www.w3.org/policies/process/#Consensus">W3C Process Document (section 5.2.1, Consensus)</a>.
482
+
Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members
483
+
of the group and other reviewers, and consensus emerges with little formal voting being required.</p>
484
+
<p>
485
+
However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of
486
+
the range of views presented, the Chairs may call for a group vote and record a decision along with any objections.
487
+
</p>
488
+
489
+
<p>
490
+
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions)
491
+
taken in a face-to-face meeting or teleconference will be considered provisional.
492
+
493
+
A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based
494
+
survey), with a response period from 2 to 7 working days, depending on the chair's evaluation of the group consensus on the issue.
495
+
496
+
If no objections are raised by the end of the response period, the resolution will be considered to have consensus as
497
+
a resolution of the Working Group.
498
+
</p>
499
+
<p>
500
+
All decisions made by the group should be considered resolved unless and until new information becomes available or
501
+
unless reopened at the discretion of the Chairs.
502
+
</p>
419
503
<p>The Working Group maintains specific procedures to establish and measure consensus and address objections in the <ahref="https://www.w3.org/WAI/APA/decision-policy">Accessible Platform Architectures Working Group Decision Policy</a>. All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs or the Director. </p>
420
504
<p>
421
-
This charter is written in accordance with the <ahref="https://www.w3.org/Consortium/Process/#Votes">W3C Process Document (Section 3.4, Votes)</a> and includes no voting procedures beyond what the Process Document requires.
505
+
This charter is written in accordance with the <ahref="https://www.w3.org/policies/process/#Votes">W3C Process
506
+
Document (Section 5.2.3, Deciding by Vote)</a> and includes no voting procedures beyond what the Process Document
0 commit comments