Web Accessibility Evaluation and the use of Web Standards
Accessing Higher Ground November: Accessible Media, Web and Technology Conference
November 15th, 2017
Slides
- Overview
- Introductions
- Part 1: The Basics
- Web Content Accessibility Guidelines 2.0
- WCAG 2.0 Success Criteria
- Scope of Success Criteria for Level A and AA Success Criteria
- Accessible Rich Internet Applications (ARIA) 1.0
- HTML 5
- HTML5: main element
- Accessible Rich Internet Application API Mappings
- HTML API Mappings
- ARIA Authoring Practices
- Manual Testing: Keyboard Accessibility
- Focus Styling for Links and Form Controls
- A keyboard focus and mouse hover styling strategy
- Link menu focus and hover styling example
- Pizza Order Form: Focus Styling
- Keyboard focus should always be visible
- High Contrast Testing
- Part 2: Automated Tools
- Browser Based Accessibility Evaluation and Inspection
- Demonstration of Tools for Basic Accessibility Features
- OpenAjax Evaluation Library
- Rulesets
- Rule Features
- Rule Results
- Rule Categories
- Ruleset and Rule Details
- Functional Accessibility Evaluator (FAE) 2.0
- Part 3: ARIA Landmarks and Widgets
- Landmarks and HTML5 Section Elements
- ARIA 1.1 Landmarks
- General Principles of Landmark Design
- MAIN Landmark
- NAVIGATION Landmark
- BANNER Landmark
- CONTENTINFO Landmark
- COMPLEMENTARY Landmark
- REGION Landmark
- Landmark Coding Patterns
- Bookmarklets for Visualizing Landmarks and Headings
- The Problem of Custom Wigets
- Purpose of ARIA to Describe Behavior and Features
- ARIA Contract with Browsers and Assistive Technologies
- Important Concepts: Role, Accessible Name and Accessible Description
- ARIA Example: Checkbox
- Part 4: ARIA Authoring Practices
- Section 3: Landmark Regions
- Landmarks Example
- Section 2: Design Patterns and Widgets
- Section 2.15: Menu Button
- Menu Button Example
- Section 4: Developing a Keyboard Inteface
- Section 4.1: Fundamental Keyboard Navigation Conventions
- Section 4.2: Discernable and Predictable Keyboard Focus
- Section 4.3: Focus vs. Selection and the Perception of Dual Focus
- Section 4.4: Deciding When to Make Selection Automatically Follow Focus
- Section 4.5: Keyboard Navigation Between Components (The Tab Sequence)
- Section 4.6: Keyboard Navigation Inside Components
- Section 4.7: Focusability of Disabled Controls
- Section 4.8: Keyboard Shortcuts
- Section 6: Intentionally Hiding Semantics with the Presentation Role
- Section 7. Roles That Automatically Hide Semantics by Making Their Descendants Presentational
- Design Example: Drop Down Navigation Links
- Drop Down Navigation Links: Tab Key Operation
- Drop Down Navigation Links: ARIA Menu Button Pattern
- Drop Down Navigation Links: ARIA Menubar Pattern
- Jon Gunderson's Evaluation Priorities
- Training Resources