VIP Model Call Girls Hadapsar ( Pune ) Call ON 9905417584 Starting High Prof...
ย
Rethinking Accessibility: Role-Based Analysis of WCAG 2.0 - CSUN 2017
1. CSUN 2017, San Diego
Bill Tyler
March 2, 2017
Rethinking Accessibility:
Role-Based Analysis of
WCAG 2.0
2. My Experience
30+ yrs. of UI/UX Design & Development
12+ yrs. in medical devices
15+ yrs. in plans & providers
2X dot-com survivor
Started Web 1996
Started Accessibility 2002
Materials Presented
3+ yrs. of ongoing accessibility research & analysis at Optum Technology
Background
2
4. No one thinks about accessibility
โฆ EXCEPT the accessibility expert
Accessibility testing comes at END of development
โฆand LONG after other design decisions are made
All issues found are directed to DEVELOPERS to fix
โฆwith help from accessibility expert
Final Result: โSort ofโ Accessible Result
The Problem: The Usual Approach to Accessibility
4
5. 5
Typical Development Sequence (by Role)
Add
A11y
Here QA / A11y Testing
Developers
Content Author
Visual (Vx) Designer
Interaction (IX) Designer
Business Owner
6. 6
Thereโs something very wrong with this picture
Add
A11y
Here QA / A11y Testing
Developers
Content Author
Visual (Vx) Designer
Interaction (IX) Designer
Business Owner
13. Decision Making Roles
โข Standard
agile role
โข Project
initiator
โข Requirements
definer
โข Result
approver
โข Business
liaison
โข Requirement
author
โข Wireframe
creator
โข UX / Usability
expert
โข Presentation
owner
โข Style expert
โข Layout
creator
โข Design
enforcer
โข Style guide
author
โข Design comp
artist
โข Image file
producer
โข Author of All
Text โLarge &
Smallโ
Large: sections
Small: words
โข Content
proofreader
โข Includes time-
based media
โข Script writer
โข Audio & video
file creator
โข Front-End
Programmer
โข Last stop
before testing
โข Primary target
for all defects
13
14. Of a like mindโฆ
14
Accessibility Responsibility Breakdown
โข Denis Boudreau / W3C / WAI-Engage Community, April 2012
Source: http://www.w3.org/community/wai-engage/wiki/Accessibility_Responsibility_Breakdown
โ 12 Roles
Interactive WCAG 2.0
โข Jeremy Fields / Viget, January 2015
Source: http://code.viget.com/interactive-wcag/
โ 5 Roles
Accessibility is Everyoneโs Job: A Role-Based Model for
Teams
โข Mark Palmer / Simply Accessible, June 2016
Source: http://simplyaccessible.com/article/role-based-a11y
โ 6 Roles
15. Differences in our approach
15
Decision Ownership
โข Roles not just identified as part of process
RACI Model Levels
โข Levels of ownership based on impact to deliverable
Additional Analysis
โข Examined (much) more than just ownership (or phases)
Actionable
โข Apply to enterprise distribution of work and responsibility
16. RACI (RASCI) Modeling
Responsible โ Owns the issueR
Accountable โ to Responsible โownerโA
Supportive โ but not accountableS
Consulted โ to address issueC
Informed โ of results, but not consultedI
16
Source: http://www.valuebasedmanagement.net/methods_raci.html
17. Role Ownership Model
Primary โ Individual role with โfinal approvalโP
Secondary โ actively involved in decisionS
Contributor โ affect, but not deeply involvedC
17
18. Example: SC1.4.1 Use of Color
Visual Designer Interaction Designer Business Owner
18
21. 21
Primary Success Criteria Ownership
IX Designer: 37% (14)
Content Author: 24% (9)
Developer: 21% (8)
Vx Designer: 16% (6)
Business Owner: 3% (1)
Observations
Developers only own 1 in 5 criteria
Developers are third in ownership
Need to work with other roles
23. Software Design Lifecycle Entry Points
Code (front-end development: HTML, CSS, JavaScript)
Content (text, terminology, and includes video & audio)
Design Comps (page or feature final presentation)
Style Guides (site presentation, branding, colors, logos)
Wireframes (structure of page, interface, interactions)
User Story / Standard Requirements
23
24. Of a like mindโฆ
24
Accessibility Responsibility Breakdown
โข Government of Canada, April 2014
Source: https://wet-boew.github.io/themes-dist/GCWeb/demos/arb-rra/arb-rra-en.html
โ 7 โProduction Phasesโ
As with roles, we went further and added levels
โข Levels based upon expected frequency
25. Entry Point Level Model
Primary โ single, most significant (typical) entry pointP
Secondary โ other significant entry pointsS
Impact โ other minor sources of design inputI
25
28. 28
Primary Success Criteria Entry Points
Wireframes: 50% (19)
User Story/Std. Req.: 24% (9)
Style Guides: 18% (7)
Code: 5% (2)
Content: 2% (1)
Design Comps: โ0%โ
Observations
95% of decisions come before code
Half are defined in wireframes
A quarter are in user stories
Nearly a fifth in style guide
33. 33
Success Criteria Types
Best Practices: 53% (20)
Primarily A11y: 39% (15)
User Stories: 8% (3)
Observations
โข Over half of decisions are
best practices roles should
already know
โข Accessibility training could
focus on topics they donโt
35. Example (of what NOT to do): โPress the green button on the right.โ
Notes:
โข Rare instance of single owner, no secondary owner or contributor
โข Example of a โNeverโ event
SC1.3.3 Sensory Characteristics
35
36. Example: โSession times out in 5 minutes. Continue? Yes / Noโ
Notes:
โข Business Ownerโs only primary ownership criterion
โข Rare Standard Requirement case
SC2.2.1 Timing Adjustable
36
37. Example: Search, Site Map, Breadcrumbs, Top-nav, In-page links
Notes:
โข One of several Interaction Designer-only primary criteria
SC2.4.5 Multiple Ways
37
38. (Questionable) Example: โBlue on โlightโ blueโ
Notes:
โข One of several Visual Designer primary ownership crits
โข Visual Designer has no secondary ownership
SC1.4.3 Color Contrast (Minimum)
38
39. (Bad) Example: โMissing alt attribute in <img>โ
Notes:
โข Code reviews should already include code validation
SC4.1.1 Parsing
39
41. Opportunities to improve efficiency and quality for both new
and existing sites
Involvement should be early in the design process
โข Includes project intake
โข For more:
Success Criteria Dependencies & Prioritization: Implication & Use
Sean Kelly, Bill Tyler
3:20PM Old Town AB
Distribute and assign ownership (resolution) to other roles
All roles should have training tailored to their role
Checklists for reviewing all design deliverables before sign-off
Changes: General
41
42. Distribute most common issue remediation to roles
โข Agile teams become more self-sufficient
โข Design roles make better decisions preventing issues at the start
โข Trained team members can identify and return issues at earlier steps
โข Train QA to do basic a11y testing
Accessibility SME can focus on difficult issues that require
their expertise
Net Result: Reduce the total number of accessibility
SMEs across the enterprise
โข Important for organizations with hundreds of sites
Changes: Accessibility Role
42
43. Integrate accessibility early in the design process
Distribute accessibility ownership to key decision makers
Targeted, role-based training
โข Refresher on existing best practices
โข Accessibility training only on topics they own or impact
Changes: New Projects
43
44. 44
New Approach for New Projects
QA / A11y Testing
Developers
Content Author
Visual (Vx) Designer
Interaction (IX) Designer
Business Owner
ADD
A11Y
HERE
45. As with new projects, all roles should have targeted role-
based training
As issues are found they should be directed to the correct role
owner, not simply the developer
โข Issues directed to specific roles will demonstrate how previous
decisions impacted accessibility
Changes: Triage of Existing Sites
45
46. 46
New Approach for Triage Projects
QA / A11y Testing
Developers
Content Author
Visual (Vx) Designer
Interaction (IX) Designer
Business Owner
ADDRESS
A11Y HERE