-
Notifications
You must be signed in to change notification settings - Fork 11
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
Link to Success Criteria in submit a tool form and in tool list itself #53
Comments
Agreed. Adding this to my to do list… |
For now I added to the listing page:
And in the submission form:
|
+1. Came here to create this issue. I've found the reference to criteria useful to look it up but a link would be handy. Unless the following approach was ruled out early in the form design, I'd like to suggest considering to reuse guideline text in the form, e.g.: A.1.1. (For the authoring tool user interface) Ensure that web-based functionality is accessible
Perhaps also taking changes of context into account somewhere "(opens in new tab/window)" after the guideline text so that the user doesn't loose the (filled out) form at some point. Alternatively, the guideline text can be used as the content of the |
Thanks much for the input, @csarven !
+1 (we just haven't gotten to adding that yet, given other priorities)
As I recall, the form creator thought paraphrase would be easier to understand. +1 to revisiting that. Perhaps we provide both?
Noting here for when we come back to this issue: in the report tools, we have both: "Show full description [+]" and links to Understanding in new window. Having said all that, I will note that we have limited resources for this project, and others have had higher priority. We will address the most important issues, and not sure if/when we will get to non-essential enhancements. |
Related issue is that we are getting feedback about confusion over the wording in the list page as well. The paraphrasing make it unclear how it relates to ATAG. So for the list page, we should also consider:
|
When adding a tool the Accessibility features section includes a reference to the ATAG success criteria, for example 'See also: A. 1.1'.
This should link to the ATAG Success Criteria.
The text was updated successfully, but these errors were encountered: