-
Notifications
You must be signed in to change notification settings - Fork 7
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
Should "proof points" and "ratings for evaluation" sections be combined for clarity? #43
Comments
Thank you for bringing this issue to our attention. We will review and edit accordingly. |
@jasonjgw I'm taking a look at this issue and would love to test out a couple of ideas with you through here with a Google Doc link. Would you be open to taking a look and letting me know if the ideas start to offer better clarity and usability? (If you're using a screen reader and the Google doc isn't working correctly, please let me know.) If yes, please check out this idea: [https://docs.google.com/document/d/1Wrhomdc2gJWIkDPOveiH3_ig1bddTMonEhIDZIzohrc/edit?usp=sharing] Using 3.1 Communications as the example.
Thanks! |
Moving the ratings so that they appear before the proof points seems reasonable. I apologise for the slow response; I missed the notification of the update to this issue. |
No worries! I also miss the notifications. I'll share this with the task force to get their feedback on this approach as well. |
This issue should be addressed in the most recent publication update. We hope you’ll review the updated information and continue providing feedback by filing Github issues. |
The "proof points" and "ratings for evaluation" are currently in different subsections of each section. it isn't clear, for instance, which proof points relate to which level of maturity. The reader also has to move back and forth between the subsections to understand what evidence establishes which outcomes.
Can this material be reorganized and, perhaps, combined to make it clearer?
The text was updated successfully, but these errors were encountered: