Skip to content

Update Participate in WAI#1322

Open
tamsinewing555 wants to merge 2 commits intomainfrom
Update-Participate-in-WAI
Open

Update Participate in WAI#1322
tamsinewing555 wants to merge 2 commits intomainfrom
Update-Participate-in-WAI

Conversation

@tamsinewing555
Copy link
Copy Markdown
Contributor

@netlify /about/participating/

@netlify
Copy link
Copy Markdown

netlify bot commented Jun 23, 2025

Deploy Preview for wai-website ready!

Name Link
🔨 Latest commit e0ac765
🔍 Latest deploy log https://app.netlify.com/projects/wai-website/deploys/6859a4b4772b52000864da4a
😎 Deploy Preview https://deploy-preview-1322--wai-website.netlify.app/about/participating/
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 76 (🔴 down 19 from production)
Accessibility: 100 (no change from production)
Best Practices: 92 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.


Details for joining are on the respective community group pages.

## Join a working group
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This and 'Join a TF' I find a bit difficult. This relates to the discussion on IEs but also covers how membership works.

I am slightly conflicted about linking through to Membership information though.

@shawna-slh Would welcome your thoughts - or a chat about this one.

@shawna-slh
Copy link
Copy Markdown
Collaborator

Thank you for the draft. I skimmed it and I like lots and I have comments. I'll have to schedule a time for full review.

@shawna-slh shawna-slh self-assigned this Jun 23, 2025
@shawna-slh
Copy link
Copy Markdown
Collaborator

shawna-slh commented Jun 23, 2025

related: W3C page which is titled "Get involved" (which is the wording we have in the WAI site header)

@tamsinewing555 tamsinewing555 self-assigned this Jul 3, 2025
@tamsinewing555
Copy link
Copy Markdown
Contributor Author

@shawna-slh - please can you review this PR, thank you.

@netlify
Copy link
Copy Markdown

netlify bot commented Jan 31, 2026

Deploy Preview for wai-website ready!

Name Link
🔨 Latest commit 2658232
🔍 Latest deploy log https://app.netlify.com/projects/wai-website/deploys/697e7f6a2a18370008bff1a2
😎 Deploy Preview https://deploy-preview-1322--wai-website.netlify.app/about/participating/
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 87
Accessibility: 100
Best Practices: 83
SEO: 100
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@shawna-slh
Copy link
Copy Markdown
Collaborator

When I looked at this initially, I disagreed with much of it and it would take a lot of time for me to review and comment. I haven't been able to make that a priority. I'll say just a little here now.

Fundamentally, I think this is the wrong approach. I agree with Kevin's concern, though I'll be more blunt. :) We don't want to present Joining WGs (and TFs) outside of Membership.

These are the main options to get involved/participate/contribute:

  • Contribute through GitHub or email. Anyone can do that without meetings or other commitments. (minor: we want to strongly encourage comments on in-progress drafts, rather than "after they are published". "specifications" -> "standards")
  • WAI IG Discussion List.
  • Community Groups.
  • W3C Membership, which allows you to join groups. (WG and TF not separate categories for participation)

Possibly we mention option to join groups without Membership, though we would want to word that carefully given parameters and issues with Invited Experts.

When this becomes a priority, please see Get Involved | W3C and let's think about how we want to align with that approach.

@tamsinewing555
Copy link
Copy Markdown
Contributor Author

Thanks @shawna-slh - I have 5 questions below.

We don't want to present Joining WGs (and TFs) outside of Membership

  1. If I understand correctly, it would fix your main concern if we remove the following two sections entirely from the document:
  • Join a working group
  • Join a task force

Note: 'Participating in working groups' is currently a topic on this page, which is why it was included in the proposed updates. I understand you'd like not to encourage this here, and am happy to remove all such content.

  1. Would you like me to create a short new section about encouraging people to become a W3C Member, linking to 'How to join W3C'?

Possibly we mention option to join groups without Membership, though we would want to word that carefully given parameters and issues with Invited Experts.

  1. I can create wording around options for joining WAI groups without being a member — can you clarify if this would be a new section on the page about how to become an Invited Expert, linking to Invited Experts?

'Thank you for the draft. I skimmed it and I like lots'
versus
'When I looked at this initially, I disagreed with much of it'

  1. I'm unclear about what you like and do not like. For example, do you also want the following sections to be removed from this page?
  • Translate WAI documents
  • Sponsor WAI
  • Promote accessibility
  • Implement accessibility
  • Advocate for accessibility
  1. see Get Involved | W3C and let's think about how we want to align with that approach

To align with W3C's wording, I propose we change the heading 'Review and comment on WAI documents' to 'Public review'. Does that work for you?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants