-
Notifications
You must be signed in to change notification settings - Fork 467
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.
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
Wg tf updates 2 #1107
base: main
Are you sure you want to change the base?
Wg tf updates 2 #1107
Conversation
✅ Deploy Preview for wai-website ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
pages/about/groups/agwg.md
Outdated
* [WCAG 2 Overview](https://www.w3.org/WAI/standards-guidelines/wcag/) | ||
* [WCAG 3 Introduction](https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for getting started with this Tamsin!
These are not publications of the Working Group. Let's check in if we want to include them on this page up where we cover WCAG 2 and WCAG 3 to help folks get to these key first pages (or, if that's too much of a distraction for most users of these pages).
And there are others for ARIA, mobile, COGA, WCAG2ICT, ...
|
||
### Contribute without joining the task force | ||
|
||
You can contribute to the work without being a member of the task force in the [Mobile A11y GitHub repository](https://github.com/w3c/Mobile-A11y-TF-Note/issues): | ||
You can contribute to the work without being a member of the task force in the [Mobile Accessibility GitHub repository](https://github.com/w3c/Mobile-A11y-TF-Note/issues): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change https://github.com/w3c/Mobile-A11y-TF-Note/issues
to https://github.com/w3c/matf/issues
|
||
## Work statement | ||
|
||
The Mobile A11y Task Force has regrouped in 2024 and a new Work Statement will be published soon. | ||
The Mobile Accessibility Task Force has regrouped in 2024 and a new Work Statement will be published soon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the other PR, the link is: https://deploy-preview-1110--wai-website.netlify.app/about/groups/task-forces/matf/work-statement/
Can we change this line to:
The Mobile Accessibility Task Force has regrouped in 2024, a [new Work Statement has been published](/about/groups/task-forces/matf/work-statement/).
The acronyms should match how the groups are referred to — even if they don't follow the same pattern. Reality is better than consistency here. When we don't use acronyms to refer to a group, acronyms shouldn't be included. from quick skim:
maybe @iadawn spots more? |
I've fixed this and created a PR in the wg-tf-updates-2 branch, thanks! |
Post publication of the refreshed WG and TF section changes.
@netlify /about/groups/