Content and Interface Accessibility for your CMS
The W3C/Web Accessibility Initiative would like to propose a tutorial
for OSCOM titled "Content and Interface Accessibility for your CMS".
Content management systems are an important target for the W3C Authoring
Tool Accessibility Guidelines, which has guidance specifically relevant
to CMS environments. Below is an outline.
About the Authoring Tool Accessibility Guidelines
Why ATAG is important
- Conformance requirements within EU
- Allows people with disabilities to create Web content
- Facilitates the creation of accessible Web content
- Helps create a more usable interface for all users
Conforming to ATAG
- conformance levels
- relationship to Web Content Accessibility Guidelines
Accessible CMS Interface
- alt text on images
- functional with JavaScript disabled (using events instead of javascript: URIs, etc.)
- marked-up labels on form elements
- metadata needs
- page refresh and redirect issues
- keyboard shortcuts
- font size, contrast, and configurability
- integrating accessibility-related features naturally within the interface
- giving priority to accessible processes over inaccessible processes
- alternatives for rich editing interfaces (ActiveX controls, Java applets, contentEditable, etc.)
Creating Accessible Content
- correcting and storing valid content
- capturing accessibility-related metadata (alt text, titles, long descriptions)
- managing collateral (images, objects, templates, etc.)
Checking for Accessibility Problems
- parsing new content as it is updated
- checking templates
- checking legacy content
- automated and semi-automated repair techniques
- alerting authors on missing attributes
- integrating Open Accessibility Checks
Documenting for Accessibility
- producing accessible bundled templates
- giving accessible example code
Future: ATAG 2.0 and WCAG 2.0
Presenter:
Matt May, W3C/WAI
Editor with Jan Richards of Authoring Tool Accessibility Guidelines 2.0
About the Authoring Tool Accessibility Guidelines
Why ATAG is important
- Conformance requirements within EU
- Allows people with disabilities to create Web content
- Facilitates the creation of accessible Web content
- Helps create a more usable interface for all users
Conforming to ATAG
- conformance levels
- relationship to Web Content Accessibility Guidelines
Accessible CMS Interface
- alt text on images
- functional with JavaScript disabled (using events instead of javascript: URIs, etc.)
- marked-up labels on form elements
- metadata needs
- page refresh and redirect issues
- keyboard shortcuts
- font size, contrast, and configurability
- integrating accessibility-related features naturally within the interface
- giving priority to accessible processes over inaccessible processes
- alternatives for rich editing interfaces (ActiveX controls, Java applets, contentEditable, etc.)
Creating Accessible Content
- correcting and storing valid content
- capturing accessibility-related metadata (alt text, titles, long descriptions)
- managing collateral (images, objects, templates, etc.)
Checking for Accessibility Problems
- parsing new content as it is updated
- checking templates
- checking legacy content
- automated and semi-automated repair techniques
- alerting authors on missing attributes
- integrating Open Accessibility Checks
Documenting for Accessibility
- producing accessible bundled templates
- giving accessible example code
Future: ATAG 2.0 and WCAG 2.0
Presenter:
Matt May, W3C/WAI
Editor with Jan Richards of Authoring Tool Accessibility Guidelines 2.0