-
Notifications
You must be signed in to change notification settings - Fork 400
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #955 from w3c/contacting-Nov-2024
clearer WAI IG list info in contacting.md
- Loading branch information
Showing
1 changed file
with
27 additions
and
42 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,7 +13,7 @@ feedbackmail: [email protected] | |
class: tight-page | ||
--- | ||
|
||
{::options toc_levels="2" /} | ||
{::options toc_levels="2,3" /} | ||
|
||
{::nomarkdown} | ||
{% include_cached toc.html type="start" title="Page Contents" %} | ||
|
@@ -26,66 +26,51 @@ class: tight-page | |
{% include_cached toc.html type="end" %} | ||
{:/} | ||
|
||
## Press Inquiries | ||
## Press inquiries | ||
|
||
For press inquiries regarding WAI or web accessibility, please send e-mail to [[email protected], [email protected], [email protected]](mailto:[email protected],[email protected],[email protected]?subject=press%20request-accessibility) | ||
For press inquiries regarding **accessibility or the Web Accessibility Initiative (WAI)**, email [[email protected], [email protected], [email protected]](mailto:[email protected],[email protected],[email protected]?subject=press%20request-accessibility) | ||
|
||
For general W3C press inquires, see [How to contact W3C, Press](/Consortium/Contact#press). | ||
For press inquiries regarding other areas of W3C, see [How to contact W3C, Press](/Consortium/Contact#press). | ||
|
||
## Technical, Implementation, and other Support Questions | ||
## Technical, implementation, and other support questions | ||
|
||
Many questions are addressed in documents on the WAI site. For example, | ||
[Understanding WCAG 2.0](/TR/UNDERSTANDING-WCAG20/) provides extensive | ||
guidance on making Web sites accessible, including the intent of | ||
guidelines and success criteria; how they help people with different | ||
disabilities, browser and assistive technology support notes, examples, | ||
and resources. The [WAI site map](/sitemap/) lists all documents and | ||
[search](/search/) is available to look for specific information. | ||
### WAI website | ||
|
||
Current Web accessibility issues are discussed through the WAI mailing | ||
lists, which are archived and visible to the public. The [WAI Interest | ||
Group](/WAI/IG/) is a public forum for discussion of issues relating to | ||
Web accessibility. If you have a question that might be relevant to the | ||
WAI IG list, you can: | ||
Many questions are addressed in documents on the WAI website. | ||
* A good starting place to find relevant resources is the [Accessibility Fundamentals Overview listing page](/fundamentals/) and [Introduction to Web Accessibility](/fundamentals/accessibility-intro/). | ||
* For information on Web Content Accessibility Guidelines (WCAG), see the [WCAG 2 Overview](/standards-guidelines/wcag/). | ||
* For an annotated list of all WAI educational and technical support documents covering a wide range of topics, see **[[WAI Resources]](/resources/)**. | ||
|
||
- Search the [WAI IG list archives](http://lists.w3.org/Archives/Public/w3c-wai-ig/) to see if it has already been addressed sufficiently | ||
- Read the [Mailing Lists](/WAI/about/groups/waiig/#mailinglist) section of the WAI IG page | ||
- [Subscribe to the Discussion List](/WAI/about/groups/waiig/#subscribing-and-unsubscribing-to-the-discussion-list) and | ||
post appropriate questions | ||
### Mailing list for accessibility questions | ||
|
||
## Feedback on Specific Documents | ||
WAI hosts a WAI Interest Group (IG) mailing list for discussion of digital accessibility issues and questions. The list is open for anyone to read, submit, and respond to it. If you have a question that might be relevant to the WAI IG list, you can: | ||
|
||
To submit comments on a specific document: | ||
- Search the [WAI IG mailing list archives](http://lists.w3.org/Archives/Public/w3c-wai-ig/) to see the topic has already been addressed sufficiently | ||
- Read the [Mailing Lists](/about/groups/waiig/#mailinglist) section of the WAI IG page for guidance on contributing to a comfortable, constructive exchange of ideas; <br>then [Subscribe to the Discussion List](/about/groups/waiig/#subscribing-and-unsubscribing-to-the-discussion-list) and post appropriate questions | ||
|
||
- Many WAI resources are on GitHub and you can create issues and | ||
submit pull requests. Look for the GitHub links near the bottom of | ||
the page. | ||
- WAI resource documents have a specific e-mail address for submitting | ||
comments, which is usually **at the bottom of the document**. This | ||
is usually: <[email protected]> (a public list) | ||
- W3C Recommendations and W3C Working Drafts have **in the Status | ||
section** an e-mail address to send comments. | ||
## Feedback on specific documents | ||
|
||
If you cannot determine where to send comments, send an e-mail with the | ||
document name in the subject line to: <[email protected]> and we will forward | ||
your message to the appropriate place. Please include permission to send | ||
it to a publicly-archived e-mail list. | ||
To submit comments on a specific document: | ||
|
||
## Feedback on the WAI Web Site | ||
- For WAI web pages under <code>w3.org/WAI/</code> — in the 'Help improve this page' box near the bottom of the page, there are links for you to submit comments, edit requests, and issues through GitHub or by email. | ||
- For WCAG, other standards, and technical reports under <code>w3.org/TR/</code> — in the 'Status of This Document' section, there are links for you to submit comments through GitHub and/or email. | ||
|
||
You can submit comments on the overall WAI Web site (www.w3.org/WAI/) either to a W3C WAI staff list or to a public list: | ||
If you cannot determine where to send comments on a specific document, email <a href="mailto:[email protected]?body=%5Binclude%20a%20relevant%20email%20Subject%5D%0A%0A%5Bput%20comment%20here...%5D%0A%0AI%20give%20permission%20to%20share%20this%20to%20a%20publicly-archived%20email%20list.">wai@w3.org</a> with the document name in the subject line and the permission to send your email to a publicly-archived email list. We will forward your message to the appropriate place. | ||
|
||
- <[email protected]> (for WAI staff, not public) | ||
- <[email protected]> (can be seen by the public) | ||
## Feedback on the WAI website design | ||
|
||
Comments on other parts of the W3C Web site (www.w3.org) go to: <[email protected]> | ||
You can submit comments on the overall WAI website (www.w3.org/) either to a W3C WAI staff list or to a public list: | ||
- <[email protected]> (seen by WAI staff only, not public) | ||
- <[email protected]> (seen by WAI staff and the public) | ||
|
||
## WAI Staff | ||
## WAI staff | ||
* [Shawn Lawton Henry](https://www.w3.org/staff/#shawn) is Web Accessibility Initiative (WAI) Program Lead; Accessibility Education and Communications Lead. | ||
* [Kevin White](https://www.w3.org/staff/#kevin) is Accessibility Technical Lead and supports the Accessibility Guidelines Working Group that develops Web Content Accessibility Guidelines (WCAG). | ||
* [Roy Ruoxi Ran (冉若曦)](https://www.w3.org/staff/#ran) supports accessibility Working Groups and accessibility in China. | ||
* [Daniel Montalvo](https://www.w3.org/staff/#dmontalvo) supports accessibility Working Groups and standards harmonization. | ||
* [Ken Franqueiro](https://www.w3.org/staff/#kfranqueiro) develops the new technical architecture for WCAG 2, WCAG 3, and the WAI website. | ||
* [Tamsin Ewing](https://www.w3.org/staff/#tamsin) supports accessibility communications, educational resources, and Working Group deliverables. | ||
|
||
If you don't know who to contact, or to reach all WAI staff, you can e-mail <[email protected]> | ||
If you don't know who to contact or you want to reach all WAI staff, you can email <[email protected]>. | ||
|
||
Note that WAI is not resourced to answer specific support questions. We will usually direct those to the [WAI IG mailing list, per above](/about/contacting/#mailing-list-for-questions). |