Accessibility Team of Zero
•Transferir como PPTX, PDF•
4 gostaram•241 visualizações
Slides from the session of the same name at the 2019 CSUN Assistive Technology Conference
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Accessibility Team of Zero
Semelhante a Accessibility Team of Zero (20)
Último
Último (16)
Accessibility Team of Zero
- 1. Accessibility Team of Zero Accessible Products Without a Dedicated Team Melissa Brooks – CollegeSource, Inc.
- 2. About CollegeSource • Higher Education software company • Transfer Credit, Degree Audit and Degree Planning and Scheduling • Clients throughout the United States, Canada and Hong Kong
- 3. About CollegeSource • About 90 employees across two offices • Development team of 15
- 4. About Me • User Experience Manager at CollegeSource • Responsible for: • User interface design • Product Testing • Product documentation • Accessibility • Other duties as assigned*
- 5. Small companies/teams are held to the same standards as their larger counterparts.
- 6. Larger companies likely have dedicated accessibility resources.
- 7. So how do those of us at small companies make accessible products?
- 8. 7 Tips to get started
- 9. 1. What can you as an individual control?
- 10. What you can control • Identify the changes you can make within your organization to push accessibility forward
- 11. In the beginning • VPATs on demand • Accessibility testing only occurred when a client asked for a VPAT • This was problematic since we had to drop everything to focus on accessibility
- 12. In the beginning • Accessibility bugs and enhancements were only prioritized when a client insisted • This was problematic since we had to drop everything to focus on accessibility
- 13. What I could control • User Experience Manager at CollegeSource • Responsible for: • User interface design • Product Testing • Product documentation • Accessibility • Other duties as assigned*
- 14. What I could control • Design with accessibility in mind • VPATs every release. Period. • Updates of accessibility documentation • Accessibility Roadmaps • Testing documents
- 15. What I could control • Ask questions in meetings with developers • Talk to them about accessibility
- 16. 2. Standards you MUST support
- 17. Standards you MUST support • Section 508? • WCAG? • Something else?
- 18. Standards you MUST support • At CollegeSource it was Section 508 • Not because WE specifically had to, but because our customers do
- 19. Standards you MUST support • Learn the requirements • Supporting documentation • Training/documentation/resources
- 20. Standards you MUST WANT TO support • If you aren’t required to follow any specific standard, learn about the one you most want to follow.
- 21. 3. TEST. TEST. TEST.
- 22. TEST. TEST. TEST. • Take stock of the current state of accessibility of your product.
- 23. TEST. TEST. TEST. • Take stock of the current state of accessibility of your product. • Utilize any of the free automated tools • WAVE • Axe • AInspector • Accessibility Insights for Web
- 24. TEST. TEST. TEST. • Take stock of the current state of accessibility of your product. • Utilize any of the free automated tools • WAVE • Axe • AInspector • Accessibility Insights for Web • Organize an all-hands testing session
- 25. TEST. TEST. TEST. • Pick a few areas of accessibility and focus your testing on those • Color contrast? • Tab order?
- 26. TEST. TEST. TEST. • Don’t worry about fixing things right now • Do document any issues you find • VPAT/Conformance Report • Create bug/enhancement issues
- 27. 4. Organize your issues
- 28. Organize your issues • Group similar issues • Tags within your issue tracking software • Spreadsheet • Word document
- 29. Organize your issues • Patterns will emerge
- 30. Organize your issues • Patterns will emerge • What may look like hundreds of bugs may actually only be 5 or 6 problems that are repeated throughout your application.
- 32. Identify Roadblocks • Identify MAJOR roadblocks • User can’t log in? • Major functionality completely inaccessible?
- 33. Identify Roadblocks • Fix those first
- 35. Schedule Fixes • Fix all issues of a specific type in one release • Fix all issues of another type the next release
- 36. Schedule Fixes • Carve out time EVERY release • Even if it’s just a few issues
- 37. 7. Spread the word
- 38. Spread the word • Leverage the advantages you have as a member of small team or company.
- 39. Spread the word • Talk with team members • Do an in-service
- 40. Spread the word • Offer to provide training to other departments
- 41. Spread the word • Offer to provide training to other departments • Encourage them to also make accessible choices in the things they can control
- 42. Spread the word • Do a presentation on what you’ve learned here at CSUN.
- 43. Wrapping Up 1. What can you control? 2. Standards you MUST support 3. TEST. TEST. TEST. 4. Organize your issues 5. Identify Roadblocks 6. Schedule Fixes 7. Spread the word
- 44. Questions? Melissa Brooks – CollegeSource, Inc.
Notas do Editor
- I also do some coding, support, training, and occasional sales demos. I am also in charge of accessibility. My team and I are responsible for all of the accessibility testing and documentation that is relevant to our products (including VPATs and Accessibility Roadmaps). I serve as the main point of contact when our users have questions or concerns about the accessibility of our products. I wear many different hats, with accessibility being only one.
- Designers and developers will tend to make the same mistakes over and over
- Designers and developers will tend to make the same mistakes over and over