Skip to content
This repository has been archived by the owner on Nov 7, 2022. It is now read-only.

ATAG & Accessibility #212

Open
mgifford opened this issue Jun 20, 2018 · 2 comments
Open

ATAG & Accessibility #212

mgifford opened this issue Jun 20, 2018 · 2 comments
Assignees

Comments

@mgifford
Copy link

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.

@pjackson28
Copy link
Collaborator

@Jeromefb Please see the suggestion regarding ATAG 2.0 (for Standard 2).

@JuliannaR
Copy link

WCAG, ATAG and UAAG should all be considered when looking at standard requirements for accessibility.

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

No branches or pull requests

4 participants