You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2022. It is now read-only.
Worth specifically mentioning ATAG 2.0 in "For authoring tools such as content management systems (CMS), blog software, and WYSIWYG editors, follow Authoring Tool Accessibility Guidelines (ATAG)."
ATAG 2.0 is in 2 parts. It should be clear that you want both parts addressed. Most stumble over Part A and barely look at Part B.
Worth specifically mentioning ATAG 2.0 in "For authoring tools such as content management systems (CMS), blog software, and WYSIWYG editors, follow Authoring Tool Accessibility Guidelines (ATAG)."
ATAG 2.0 is in 2 parts. It should be clear that you want both parts addressed. Most stumble over Part A and barely look at Part B.
Also useful to highlight those systems that have already started addressing this such as Drupal.
https://www.drupal.org/project/issues/search?issue_tags=atag
This should also be held up as a great example of a standard that is Built in Canada:
https://www.w3.org/TR/ATAG20/
Jutta Treviranus & Jan Richards of the Inclusive Design Institute at OCAD University really lead this.
This should also be seen as a cost savings issue for both accommodation & post-publishing remediation is the most expensive way to address the system.
The text was updated successfully, but these errors were encountered: