-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Initial messaging for wide review publication before 1.0
- Loading branch information
1 parent
f2e90be
commit 03d1f48
Showing
4 changed files
with
155 additions
and
0 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 |
---|---|---|
@@ -0,0 +1,21 @@ | ||
replace "XYZ2" with a short name of your document | ||
* Expected date: 00 Month 202N | ||
* Contact(s) for Shawn to get info: Name e-mail phone | ||
* Draft document: link to staging | ||
* Related pages that need updating: (such as Overview page) | ||
|
||
Any notes for us working on the announcements, such as important points to get across: (see | ||
https://www.w3.org/wiki/WAI/announcements#Help_craft_messaging ) | ||
|
||
Status of announcements below: draft not ready for review | ||
|
||
Review of announcements below: | ||
* @@ OKed by [name] on [date] | ||
|
||
NOTE: For further guidance on creating messaging consult | ||
https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts#.5BTemplate.5D_Spec_XYZ_Announcements | ||
|
||
|
||
When announcements are ready for Shawn's review or drafting, please e-mail | ||
shawn@w3.org subject: [announcements] | ||
|
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 |
---|---|---|
@@ -0,0 +1,68 @@ | ||
Dear WAI Interest Group, | ||
|
||
W3C WAI invites you to comment on a version 1.0 APA Group Note: | ||
Accessibility Maturity Model | ||
|
||
Work will continue on the Maturity Model after the 1.0 note is released. | ||
Therefore, we continue to invite comments as W3C members and the public | ||
explore implementation in more detail. | ||
|
||
Overview: | ||
|
||
The Accessibility Maturity Model (AMM) describes an overall framework | ||
for establishing a robust ICT accessibility program and identifying | ||
areas for improvement. The Accessibility Maturity Model is a tool that: | ||
|
||
- Assesses the current effectiveness and capabilities of an entire | ||
organization or subunits within the organization | ||
|
||
- Supports identification of gaps between the current capabilities and | ||
the next level of accessibility maturity | ||
|
||
- Supports plans for next steps to improve the organization\'s | ||
accessibility performance over time | ||
|
||
The approaches identified in this document are intended to influence | ||
organizational accessibility programs to advance the accessibility focus | ||
from getting a product or website accessible to creating an environment | ||
where the entire product experience can be kept accessible over time. | ||
This evolution towards proactive accessibility is relevant to all parts | ||
of an organization that contribute either directly or indirectly to | ||
developing a product experience. | ||
|
||
Seeking input: | ||
|
||
We continue to encourage broad review from a cross-disability | ||
perspective. This 1.0 note incorporates substantial revisions made in | ||
response to various stakeholders\' comments on the previous Working | ||
Drafts. These comments led to adding additional details and definitions | ||
as well as clarifying the document\'s scope. | ||
|
||
Comments: | ||
|
||
Please open a new issue in the [document\'s GitHub | ||
repository](https://github.com/w3c/maturity-model/issues/new) to comment | ||
|
||
Please create separate GitHub issues for each comment, rather than | ||
commenting on multiple topics in a single issue. | ||
|
||
If it\'s not feasible to use GitHub, you may send comments via e-mail | ||
to: <public-maturity@w3.org> | ||
|
||
Please: | ||
|
||
\* put your comments in the body of the message, not as an attachment | ||
|
||
\* start your e-mail subject line with: \[Maturity\] | ||
|
||
Please do not include any proprietary data in your Github ticket or | ||
email as these are both archived publicly. | ||
|
||
Regards, | ||
|
||
Sheri Byrne-Haber and David Fazio for | ||
|
||
Janina Sajka and Matthew Atkinson, Accessible Platform Architectures | ||
(APA) Working Group Co-Chairs | ||
|
||
Roy Ran, W3C Staff Contact for APA Working Group |
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 |
---|---|---|
@@ -0,0 +1,32 @@ | ||
1.0 APA Note: Accessibility Maturity Model | ||
|
||
The Accessible Platform Architectures | ||
([APA](https://www.w3.org/groups/wg/apa/)) Maturity Model Task Force | ||
([MMTF](https://www.w3.org/groups/tf/maturity/)) welcomes feedback on | ||
the updated 1.0 version of the W3C Group Note: Accessibility Maturity | ||
Model. The Accessibility Maturity Model (AMM) describes an overall | ||
framework for establishing a robust ICT accessibility program and | ||
identifying areas for improvement. The Accessibility Maturity Model is a | ||
tool that: | ||
|
||
- Assesses the current effectiveness and capabilities of an entire | ||
organization or subunits within the organization | ||
|
||
- Supports identification of gaps between the current capabilities and | ||
the next level of accessibility maturity | ||
|
||
- Supports plans for next steps to improve the organization\'s | ||
accessibility performance over time | ||
|
||
The approaches identified in this note are intended to influence | ||
organizational programs and advance accessibility focus from making a | ||
product or website accessible to creating an environment where the | ||
entire product experience can be kept accessible over time. This | ||
evolution towards proactive accessibility is relevant to all parts of an | ||
organization that contributes directly or indirectly to developing a | ||
product experience. | ||
|
||
The MMTF will continue to develop and refine this note. | ||
[Comments](https://github.com/w3c/maturity-model/issues/new) are welcome | ||
at any time. We especially encourage comments by organizations | ||
implementing the model. |
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 |
---|---|---|
@@ -0,0 +1,34 @@ | ||
For Wide Review: APA Group Note Accessibility Maturity Model 1.0 | ||
|
||
**Date:** 20 November 2024 | ||
|
||
The Accessible Platform Architectures | ||
([APA](https://www.w3.org/groups/wg/apa/)) Maturity Model Task Force | ||
([MMTF](https://www.w3.org/groups/tf/maturity/)) welcomes feedback on | ||
the updated 1.0 version of the W3C Group Note: Accessibility Maturity | ||
Model. The Accessibility Maturity Model (AMM) describes an overall | ||
framework for establishing a robust ICT accessibility program and | ||
identifying areas for improvement. The Accessibility Maturity Model is a | ||
tool that: | ||
|
||
- Assesses the current effectiveness and capabilities of an entire | ||
organization or subunits within the organization | ||
|
||
- Supports identification of gaps between the current capabilities and | ||
the next level of accessibility maturity | ||
|
||
- Supports plans for next steps to improve the organization\'s | ||
accessibility performance over time | ||
|
||
The approaches identified in this note are intended to influence | ||
organizational programs and advance accessibility focus from making a | ||
product or website accessible to creating an environment where the | ||
entire product experience can be kept accessible over time. This | ||
evolution towards proactive accessibility is relevant to all parts of an | ||
organization that contributes directly or indirectly to developing a | ||
product experience. | ||
|
||
The MMTF will continue to develop and refine this note. | ||
[Comments](https://github.com/w3c/maturity-model/issues/new) are welcome | ||
at any time. We especially encourage comments by organizations | ||
implementing the model. |