Skip to content

Update to Mobile TF work statement #1110

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

Open
iadawn wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update to Mobile TF work statement #1110

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion pages/about/groups/task-forces/matf.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ The objectives of the Mobile A11y Task Force are to produce resources for how to

## Work statement

The Mobile A11y Task Force has regrouped in 2024 and a new Work Statement will be published soon.
To learn about the focus, scope and deliverables of the task force, see the [Mobile Accessibility Task Force Work Statement](/about/groups/task-forces/matf/work-statement/).

## Current work

Expand Down
75 changes: 55 additions & 20 deletions pages/about/groups/task-forces/matf/work-statement.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,34 +68,69 @@ Actual timelines and project management will be handled outside of this work sta
* Figure out efficient way of collaborating;
* List existing resources for applying WCAG to Mobile Applications.

**Phase 2: April - June 2024**
**Phase 2: April - September 2024**

* Develop an initial draft, focusing on Success Criteria at Level A;
* Publish Level A draft on Github;
* Discuss all Success Criteria at level A+AA during our weekly meetings; mark them as “Small”, “Medium”, or “Large” variation.
* Setup processes and tooling on Github;
* Request feedback from stakeholders, participants and AG WG.

**Phase 3: July - September 2024**
**Phase 3: October - December 2024**

* Develop second draft, process feedback, add Success Criteria at Level AA;
* Publish Level AA draft on Github;
* Request and process feedback from stakeholders, participants and AG WG.
* Develop an initial draft, focusing on Success Criteria marked as Small Variation;
* Publish Small Variation draft on Github;
* Request feedback from stakeholders, participants and AG WG.

**Phase 4: January - March 2025**

**Phase 4: October - December 2024**
* Process feedback from stakeholders, participants and AG WG.
* Publish First Public Working Draft.
* Request feedback from the public, stakeholders, participants and AG WG;

* Publish an First Public Working Draft through W3C, taking all feedback into account;
* Process feedback from the public, stakeholders, participants and AG WG;
* Publish new W3C Group Note.
**Phase 6: April - June 2025**

**Phase 5: January - March 2025**
* Process feedback from public, stakeholders, participants and AG WG.
* Work on Second Draft, focusing on Success Criteria marked as Medium Variation;
* Publish Second Public Working Draft, including Success Criteria marked as Medium Variation.
* Request feedback from the public, stakeholders, participants and AG WG;

* Expand Working Group Note with guidance for Level AAA criteria;
* Publish Level AAA draft on Github;
* Request and process feedback from stakeholders, participants and AG WG.
**Phase 6: July - September 2025**

**Phase 6: April - June 2025**
* Process feedback from public, stakeholders, participants and AG WG.
* Work on Third Draft, focusing on Success Criteria marked as Large Variation;
* Publish Third Public Working Draft, including Success Criteria marked as Large Variation.
* Request feedback from the public, stakeholders, participants and AG WG;

**Phase 6: October - December 2025**

* Process feedback from public, stakeholders, participants and AG WG.
* **Publish W3C Group Note**.

**Phase 8: January - February 2026**

* Discuss all Success Criteria at level AAA during our weekly meetings; mark them as “Small”, “Medium”, or “Large” variation.
* Work on Updated Group Note with guidance for Level AAA criteria;
* Request feedback from stakeholders, participants and AG WG.

**Phase 9: March - April 2026**
* Process feedback from stakeholders, participants and AG WG;
* Publish First Public Working Draft of Updated Group Note, including Success Criteria at level AAA marked as Small Variation.
* Request feedback from the public, stakeholders, participants and AG WG;

**Phase 10: May - June 2026**

* Process feedback from public, stakeholders, participants and AG WG;
* Publish Second Public Working Draft of Updated Group Note, including Success Criteria at level AAA marked as Medium Variation.
* Request feedback from the public, stakeholders, participants and AG WG;

**Phase 11: July - September 2026**

* Process feedback from public, stakeholders, participants and AG WG;
* Publish Second Public Working Draft of Updated Group Note, including Success Criteria at level AAA marked as Large Variation.
* Request feedback from the public, stakeholders, participants and AG WG;

**Phase 12: October - December 2026**

* Publish a Group Note through W3C, taking all feedback into account;
* Process feedback from the public, stakeholders, participants and AG WG;
* Process feedback from public, stakeholders, participants and AG WG.
* Publish updated W3C Group Note.

## Dependencies
Expand Down Expand Up @@ -136,8 +171,8 @@ Contact [Kevin White](mailto:[email protected]) to become a participant of the WCAG 2

Staff contacts from the Accessibility Guidelines Working Group oversee attention to W3C Process with respect to the chartered requirements of the Working Group. The facilitators set agenda, lead meetings, determine consensus, and are the primary liaison to the Working Group.

* [Chair](https://www.w3.org/groups/tf/wcag2x-backlog/mobile-a11y-tf/#chairs)
* [Staff Contact](https://www.w3.org/groups/tf/wcag2x-backlog/mobile-a11y-tf/#staff)
* [Chair](https://www.w3.org/groups/tf/mobile-a11y-tf/participants/#chairs)
* [Staff Contact](https://www.w3.org/groups/tf/mobile-a11y-tf/participants/#staff)

## Patent Policy

Expand Down