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

Link to Success Criteria in submit a tool form and in tool list itself #53

Open
iadawn opened this issue Oct 18, 2019 · 5 comments
Open
Labels
enhancement New feature or request

Comments

@iadawn
Copy link
Contributor

iadawn commented Oct 18, 2019

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.

@hidde hidde added the enhancement New feature or request label Oct 18, 2019
@hidde
Copy link
Member

hidde commented Oct 18, 2019

Agreed. Adding this to my to do list… 

@hidde hidde added this to the Submit a tool milestone Oct 22, 2019
@shawna-slh
Copy link
Contributor

shawna-slh commented Dec 10, 2022

For now I added to the listing page:

The Details section under the Tools listing has information on how the tool meets the web standard: Authoring Tool Accessibility Guidelines (ATAG). For a brief summary of ATAG, see ATAG at a Glance.

And in the submission form:

The 'See also's below refer to the section of ATAG.

@shawna-slh shawna-slh modified the milestones: Submit a tool, MVP + 2 Dec 10, 2022
@csarven
Copy link
Member

csarven commented Dec 28, 2022

+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

  • Yes
  • No
  • Partially
  • Not applicable
  • Not sure

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 summary element in details, and the opened content showing more information.

@shawna-slh
Copy link
Contributor

Thanks much for the input, @csarven !

... a link would be handy

+1 (we just haven't gotten to adding that yet, given other priorities)

I'd like to suggest considering to reuse guideline text in the form

As I recall, the form creator thought paraphrase would be easier to understand.

+1 to revisiting that. Perhaps we provide both?

... 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 summary element in details, and the opened content showing more information.

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.

@shawna-slh
Copy link
Contributor

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:

  • add link to ATAG SC [fairly easy]
  • provide a way to see both the paraphrase and the actual SC text [more time to figure out UI and program it]
  • other ways to meet the needs of users who are familiar with ATAG and users who are not

@shawna-slh shawna-slh changed the title Link to Success Criteria in submit a tool form Link to Success Criteria in submit a tool form and in tool list itself Jan 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants