This was my fifth session at the CSUN conference on Thursday, March 5. Interested in this session because of my home institution’s use of Oracle/PeopleSoft, and I expect this session may provide an interesting counterpoint to that platform.
How Agile Fails Accessibility
- Decentralized product ownership
- Teams control their own backlog
- Balance: bugs/accessibility
- Balance: feature enhancement / Enhancements
- Separate accessibility features; mountain of accessibility debt
- Unless a proper system is put in place, accessibility – under agile – will always take a back seat to the creation of new features
- “The email” is not the solution. It can’t do the work that needs to be done.
- Executives remove blockers and help us build an environment in which accessibility can thrive
Building the Environment – Culture
- Gain allies and raise awareness.
- Build the base of passionate people.
- Spread knowledge about accessibility
- Build empathy through examples
- Frame accessibility through your company’s core mission
- Make it contagious (get other people talking about it)
- Embed on a scrum team: teach how to ship accessible features, learn at a micro level how agile works at your company.
- Knowledge of your company’s brand of agile
- Success building an accessible feature
- Prove to the team that it’s not a big hurdle
- Allies in UX, scrum leadership, development, and quality
- Path to embed on another, larger, more influential team
- Create an award that recognizes excellence; publicize winners, generate incentive to build accessible
- Create reusable components: use your contacts to join the appropriate scrum team, guide them toward the development of accessible components
- 3rd party components: know which ones are used, gauge level of accessibility, catalogue functionally equivalent alternatives for inaccessible ones, work with stakeholders to enlist accessible alternatives
- Grassroots marketing campaign: dropdown / throwdown poster was a classic (lots of great comics in this preso)
- Take advantage of redesigns: product redesigns are common, be prepared with a set of accessible, reusable components, beware of redesigns (they could pull out good stuff)
- Testing Framework
- Quality Engineering does not normally include accessibility as a traditional part of quality testing.
- Automation is key to accessibility; build test automation that is specific to your environment. Opt everyone in, automatically issue test failures where possible, test for patterns that indicate accessibility bugs, perform manual spot checks, track everything.
- DOM test the simple things (WAVE-testable stuff)
- How does your company implement a new process?
- Develop a plan: problem statement, teams/groups impacted, proposal detail, tracking / success metrics, exception policy, release sign-off process, communication plan
- Get an executive sponsor: their main job is to believe in your idea.
- Example meta process: define problem > ID impacted parties > engage forum (present proposal, gather feedback) > go/no-go > re-socialize revised proposal, get alignment, final buy-in > go/no-go > visibility to executives > communication and rollout
- Cultivate Support
- Provide Good components
- Leverage your test framework
- Institute process change
- Keep it going