A brief overview on how to establish an environment for creating a workflow for developing accessible technology

1. An Environment for Access

2. Team Members Project stakeholders Content creators User interface designers Graphic designers (Visual identity) Software developers

3. Project Stakeholder Stakeholders are those who are behind the project vision or those will be affected by the project’s outcome. In the case of educators, the project stakeholders are often students. Accessibility Responsibilities: Listen Support Mediate Monitor

4. Content Creators Responsibilities Creating content for the project Accessibility Responsibilities Ensure that content is created for all assets (images, animations, video, etc.) within the project

5. User Interface Designers Responsibilities Creating content layouts that ensure consistency and reliability Accessibility Responsibilities Ensure that standardized styles are consistently used Ensure that the “behind the scenes” coding represents the message of both the graphic designer and the content creator.

6. Graphic Designers Responsibilities: To enhance the content with flexible visual layouts Accessibility Responsibilities: Address visual identity in an accessible manner Create appropriate styles for the content Be aware of color decisions

7. Infrastructure Developers Responsibilities Programming and building frameworks to deliver the content Communicate effectively with other members to understand their expectations Accessibility Responsibilities Ensure functionality for all users, regardless of their technological devices

8. + + + = YOU! When there are not enough people to make up an entire team, then the team is sometime you alone.

9. Be Positive Try to be positive in the way you present accessibility. Using the danger of a lawsuit will onlyinspire defensiveness.

10. Documentation Document the team’s progress and project details with a project wiki or a project style guide containing detailed information. Media specification sheet: outlines project content, images, videos and other media along with their associated text descriptions, metadata and other needs.

11. Plan for Access Do it right the first time to avoid retrofitting inaccessible websites! By planning for accessibility in the beginning, project costs can be reduced.

12. WET Dilemma WET = Writing everything twice If you choose to create alternate versions to accommodate accessibility, then you will be in a WET dilemma. 1. Non-Accessible Version 2. Accessible Version

13. DRY Principle DRY = Don’t repeat yourself! Present content only once if possible. Avoid creating an alternate version to accommodate accessibility. 1. Accessible Version Only

14. Templates Templates allow us to formalize our thoughts and eliminate repetition.