Creating Accessible Web Content

Creating Accessible Web Content

Rick HillWeb CMS AdministratorOffice of Strategic Communications

Strategic Communications

Cascade Environment Matters

Decentralized

Centralized

CONTENTCONTRO

L

• Number of sites, pages, users• Static or dynamic content• Server side or client-side

Strategic Communications

Why WCAG 2 AA and not 508?

• 508 based on WGAG 1• 508 update: WCAG 2 AA • WCAG 2 is technology agnostic• International standard• Can validate against both

Strategic Communications

What is WCAG 2 AA?

• W3C Web Accessibility Initiative• WCAG 2.0 principles

• Perceivable• Operable• Understandable• Robust

• Conformance levels - A, AA, AAA

Strategic Communications

Basic Design Considerations

• User-centric • Logical information architecture• Standard (X)HTML • Use CSS and JavaScript appropriately• Use fonts approriately• Write for the Web• Optimize content

Strategic CommunicationsStrategic Communications

Cascade Design Tips

• Minimize WYSIWYG editor need• Data definitions use good practices• Provide appropriate overides• Style for hover and focus

Strategic CommunicationsStrategic Communications

Basic Compliance Testing

• Validate• No mouse• Disable CSS• Disable images• Zoom text• Check contrast

• Data tables• Forms• Multimedia• Flicker• Cross browser• Cross device

Strategic Communications

Robust Compliance Testing

• No tool tests completely• Free and commercial tools• Scheduled scans• AT browsers• User testing• Other Web content• Cascade integrated testing?

Strategic Communications

Training

• Training is important!• What can a user do:

• Alt for images• Tables for data only• Links don’t open new windows/tabs• iframes• Writing for the Web

Strategic Communications

Tim Berners-LeeW3C DirectorInventor of the World Wide Web

The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.