accessibility in rapid iterative development
TRANSCRIPT
Accessibility in Rapid Iterative Development
AIDAN TIERNEY ! @AIDANA11Y
"
Iterative & AgileIncremental instead of all at once.
# $ %
Requirements Analysis
Design
Development
Testing
Iteration Complete
Start Release
& ' ( %
Waterfall
Requirements Analysis
Design
Development
Testing
Release
Maintenance
Waterfall vs. Iterative
Requirements Analysis
Design
Development
Testing
WaterfallOne-off activities
AgileContinuous activities
Requirements Analysis
Design
Development
Testing
agilenutshell.com
Agile terms
Persona User Story Sprint
Features Acceptance Criteria
Backlog Release
Grooming Continuous Integration
Epic Scrum
Accessibility in an iterative workflow
"
Planning) ○
Defining high-level requirements (e.g. standards, support baseline)
Define Accessibility team involvement Dev and QA planning
Exception management
Communications and customer support
Personas
+ , + +
- 0
Nature of limitation (for example, blind, unable to use mouse, operating in noisy environment)
Special tools or assistive technology used (for example, uses a magnifying glass to read text smaller than 16 point, uses screen reader software, stops machinery to hear mobile phone)
Experience and skills with the relevant tools or assistive technologies
Frequency of use of relevant tools or assistive technologies
See: http://www.uiaccess.com/accessucd/personas.html
User Stories & Epics
2
As an <actor phrase> I want <action phrase> so that <outcome phrase>
As an Administrator, I want to be able to create User Accounts so that I can grant users access to the system.
As a user who is colourblind, I want to have access to information conveyed in colour so that I do not miss anything and I understand the content.
As keyboard-only user, I want to know where I am on the screen at all times so that I know what I can do and how to do it.
See:interactiveaccessibility.com/blog/how-write-user-stories-accessibility-requirements
“Accessibility is not a feature”
Acceptance criteria
3
“Pre-established standards or requirements a product or
project must meet.”
Accessibility within sprints
"
Grooming sessions
‘Wireframe’ reviews (may be very informal)
Design reviews
Content reviews (especially offscreen text)
Developer and QA support
Defect triage
Challenges4
Speed Work happening in parallel
Resources must be committed to project longer
Some job roles don’t seem to ‘get’ Agile
Some work not as well suited to iterative decisions
Solutions & Approaches5
Culture
Detailed accessibility standards with examples
Pattern library
Front-end development style guide for accessibility
Automated testing
Front-end Development Style Guide for Accessibility
67"
Detailed requirements for components & patternsExpected keyboard interactions
WAI-ARIA patterns
Create testable requirements for items that often get left to chance
Beneficial to QA. Expected behaviours documented
Example: https://accessibility.temple.edu/sites/accessibility/files/documents/Web%20Accessibility%20Standards%20and%20Guidelines%20v4.pdf
Testing
8
8
Testing tools
Test driven development (extreme accessibility) Test automation
Unit testing, regression, continuous integration
Define manual tools (including support baseline)
“So, what’s your experience?”
9
:
Accessibility in Rapid Iterative Development
AIDAN TIERNEY ! @AIDANA11Y
"