Skip to content
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

Section 3.1 (communication) should be clarified. #42

Closed
jasonjgw opened this issue Nov 29, 2021 · 4 comments
Closed

Section 3.1 (communication) should be clarified. #42

jasonjgw opened this issue Nov 29, 2021 · 4 comments

Comments

@jasonjgw
Copy link
Contributor

There are two topics in this section: (1) communication about accessibility, and (2) the accessibility of communications themselves - whether or not they are about accessibility.

I think the two issues should be clarified and better distinguished in a revision of the text.

The headings of subsections under 3.1.1 don't clearly describe the content of the subsections. The proof points are only briefly stated, and it isn't clear what is required to satisfy them (e.g., what a "statement of commitment" or an "accessibility statement" is, and what either of them should contain).

"Voluntary Product Accessibility Template" should include a bibliography reference that cites the official documentation. The same holds for "model accessibility statement".

In section 3.1.2, it isn't clear that the items listed under the "Optimize" level relate to communications - they appear to be more about organizational governance.

The relationship between "proof points" and "ratings for evaluation" could be clarified in general (e.g., the "proof points" describe what evidence to acquire, and the ratings describe what the evidence needs to show to achieve different levels of maturity along the dimension).

@jake-abma
Copy link
Contributor

Thank you for bringing this issue to our attention. We will review and edit accordingly.

@Helixopp
Copy link
Contributor

We are reviewing this section to address your concerns. We will close this issue once we have updated the section.

@Helixopp
Copy link
Contributor

There are multiple issues here, some of which we can agree to, others that require more discussion.Please break this issue up into individual components

@Helixopp
Copy link
Contributor

This topic has been discussed at length. We are currently discussing it with organizations that are experimenting with the model. We will respond

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants