participating in groups [was: For Review: WCAG 3 Working Draft Outcomes]

Hello Adam,

Most groups facilitate "asynchronized" work, such as through GitHub, Google docs, or other.

Some have meetings that work better in different time zones.

For the group work that you are interested in contributing to, there should be information about how to participate in that specific group and a contact for more information.

Best regards,
~Shawn

www.w3.org/People/Shawn




On 15-May-24 11:36 PM, Adam Cooper wrote:
>
> Hello Shawn,
>
> Will there be community/working group meetings in the future that are at times more suitable for people who live in the southern hemisphere?
>
> I’d very much like to participate in any public fora, but they’re typically in the very early hours of the morning.
>
> Regards,
>
> Adam Cooper
>
> *From:*Shawn Henry <shawn@w3.org>
> *Sent:* Thursday, May 16, 2024 2:05 PM
> *To:* public-wai-announce@w3.org
> *Cc:* w3c-wai-gl@w3.org
> *Subject:* For Review: WCAG 3 Working Draft Outcomes
>
> Dear WAI Interest Group,
>
> For background and up-to-date information on W3C Accessibility Guidelines (WCAG) 3, please see:
>     WCAG 3 Introduction
> https://www.w3.org/WAI/wcag3
>
> The Accessibility Guidelines Working Group (AG WG) published an updated WCAG 3 Working Draft at:
> https://www.w3.org/TR/wcag-3.0/
>
> This draft includes *potential *outcomes that we are exploring. The final set of outcomes in WCAG 3 will be different from this draft. Outcomes will be edited, added, combined, and removed.
>
> The purpose of this draft is to:
>
>   * better understand the scope of user needs and how they could be addressed in an accessibility standard,
>   * request assistance in identifying gaps, and
>   * request assistance locating and conducting research to validate or invalidate the drafted outcomes.
>
> Some of the outcomes are marked as needing research. We are particularly interested in assistance identifying or conducting research to support or refute them.
>
> *For your review:*
>
> When reviewing this update, please focus on the Guidelines section. We did not make changes to conformance related sections.
>
> Please consider the following questions when reviewing the outcomes in this draft:
>
>   * What outcomes needed to make web content accessible are missing?
>   * What research supports or refutes these outcomes?
>   * Are any of these outcomes out of scope for accessibility standards? If so, please explain why.
>
> To provide input, please file GitHub issues at:
> https://raw.githack.com/w3c/wcag3/30-april-meeting/guidelines/index.html
> Or, if you are unable to use GitHub, send email to public-agwg-comments@w3.org
>
> Please create separate GitHub issues or email messages for each topic (rather than putting multiple topics in a single issue or email).
>
> Thank you in advance for your contributions to WCAG 3. This draft reflects ongoing work on WCAG 3. If you have questions or concerns, please contact the AG Chairs via email to: group-ag-chairs@w3.org
>
> Regards,
> Shawn Lawton Henry, as Accessibility Communications Lead, for:
> Rachael Bradley Montgomery, Alastair Campbell, Chuck Adams – AG WG Co-Chairs
> Kevin White – W3C Staff Contact for AG WG
>
> -- 
> Shawn Lawton Henry
> W3C Web Accessibility Initiative (WAI) Program Lead
> W3C Accessibility Education and Communications Lead
> www.w3.org/People/Shawn  <http://www.w3.org/People/Shawn>