-
Notifications
You must be signed in to change notification settings - Fork 11
What can AT do?
Hidde de Vries edited this page Jul 17, 2019
·
2 revisions
Some ways Authoring Tools can provide better accessibility in their own interface (ATAG-A) and in the websites they produce (ATAG-B):
- follow WCAG
- check structure (WordPress' Gutenberg has document outline panel)
- check markup validity
- make creating alt text easy
- for accessibility related fields, use CMS field names that make sense to content people (corporate CMS can have a lot of fields built for specific features, sometimes the names for those fields are invented by back-end developers and mimic what stuff is called in Java/.NET; could help to have very useful labels for fields)
- ensure consistency
- check spelling (in Mike Gifford's presentation: misspelled words don't work well in screenreaders, hard to click with Dragon Naturallyspeaking, bad for SEO)
- automated checks for readability (like Grammarly)
- for content editing avoid WYSWIYG (some AT use Markdown or something else, some called this What You See Is What You Mean)
- for template selection, identify which templates comply with WCAG