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

Make Benefits a bulleted list 3.3.3: Error Suggestion #1798

Closed
jake-abma opened this issue May 11, 2021 · 1 comment · Fixed by #1804
Closed

Make Benefits a bulleted list 3.3.3: Error Suggestion #1798

jake-abma opened this issue May 11, 2021 · 1 comment · Fixed by #1804

Comments

@jake-abma
Copy link
Contributor

jake-abma commented May 11, 2021

https://www.w3.org/WAI/WCAG22/Understanding/error-suggestion

The Benefits are concatenated and should better be different list items, as we do in all other SCs.

Change:

Benefits

  • Providing information about how to correct input errors allows users who have learning disabilities to fill in a form successfully. Users who are blind or have impaired vision understand more easily the nature of the input error and how to correct it. People with motion impairment can reduce the number of times they need to change an input value.

to:

Benefits

  • Providing information about how to correct input errors allows users who have learning disabilities to fill in a form successfully.
  • Users who are blind or have impaired vision understand more easily the nature of the input error and how to correct it.
  • People with motion impairment can reduce the number of times they need to change an input value.
@jake-abma jake-abma changed the title Make Benefits a bulleted list Make Benefits a bulleted list 3.3.3: Error Suggestion May 11, 2021
patrickhlauke added a commit that referenced this issue May 11, 2021
* remove the unnecessary reference to the "definition in WCAG 2.0"
* make "Benefits" a proper list
* remove G83, ARIA2, SL35, PDF5 as sufficient techniques / remove entire first "situation" / reorder the sufficient and advisory techniques (currently some of the techniques are listed as both)

Closes #1796 #1798 #1799 #1800 #1801
@patrickhlauke
Copy link
Member

#1804

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

Successfully merging a pull request may close this issue.

3 participants