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
This is a Canadian standard, but it is also a key aspect of being able to meet targets for EN 301 549. Authors should be able to expect an accessible authoring interface and be given support to produce accessible content. We know that providing training for authors hasn't been sufficient.
Canadian tools like https://sa11y.netlify.app/ are simple open source implementations that can help authors, as can simply installing Microsoft's Accessibility Insights https://accessibilityinsights.io/ by default (because it is open source, accessible & works well in Edge), by default in government implementations of Edge.
Authors need access to these tools so that they don't need to be an accessibility expert to find basic accessibility barriers. Browser extensions like this are like training wheels for accessibility standards.
This discussion was converted from issue #211 on November 24, 2022 16:43.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
2.3 Standards are as follows:
https://a11y.canada.ca/en/standards/standard/#2.3.3.1
We really need to include Authoring Tool Accessibility Guidelines (ATAG) 2.0 https://www.w3.org/TR/ATAG20/
This is a Canadian standard, but it is also a key aspect of being able to meet targets for EN 301 549. Authors should be able to expect an accessible authoring interface and be given support to produce accessible content. We know that providing training for authors hasn't been sufficient.
Another great example came from the work of Funka in their work for the EC which can be found https://accessibilitycluster.com/
Authors cannot be left as an afterthought.
Canadian tools like https://sa11y.netlify.app/ are simple open source implementations that can help authors, as can simply installing Microsoft's Accessibility Insights https://accessibilityinsights.io/ by default (because it is open source, accessible & works well in Edge), by default in government implementations of Edge.
Authors need access to these tools so that they don't need to be an accessibility expert to find basic accessibility barriers. Browser extensions like this are like training wheels for accessibility standards.
Beta Was this translation helpful? Give feedback.
All reactions