The document outlines roles and responsibilities in a project focused on accessibility, highlighting the contributions of access team members, project stakeholders, content creators, user interface designers, graphic designers, and infrastructure developers. It emphasizes the importance of planning for accessibility from the outset to avoid costly retrofitting and presents principles like 'wet dilemma' versus 'dry principle' to discourage redundant content versions. Additionally, it suggests documenting progress and using templates to streamline processes and enhance collaboration.

1. An Environment for Access

2. Team MembersProject stakeholdersContent creatorsUser interface designersGraphic designers (Visual identity)Software developers

3. Project StakeholderStakeholders 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:ListenSupportMediateMonitor

4. Content CreatorsResponsibilitiesCreating content for the projectAccessibility ResponsibilitiesEnsure that content is created for all assets (images, animations, video, etc.) within the project

5. User Interface DesignersResponsibilitiesCreating content layouts that ensure consistency and reliabilityAccessibility ResponsibilitiesEnsure that standardized styles are consistently usedEnsure that the “behind the scenes” coding represents the message of both the graphic designer and the content creator.

6. Graphic DesignersResponsibilities:To enhance the content with flexible visual layoutsAccessibility Responsibilities:Address visual identity in an accessible mannerCreate appropriate styles for the contentBe aware of color decisions

7. Infrastructure DevelopersResponsibilitiesProgramming and building frameworks to deliver the contentCommunicate effectively with other members to understand their expectationsAccessibility ResponsibilitiesEnsure 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 PositiveTry to be positive in the way you present accessibility.Using the danger of a lawsuit will onlyinspire defensiveness.

10. DocumentationDocument 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 AccessDo it right the first time to avoid retrofitting inaccessible websites!By planning for accessibility in the beginning, project costs can be reduced.

12. WET DilemmaWET = Writing everything twiceIf you choose to create alternate versions to accommodate accessibility, then you will be in a WET dilemma.1.Non-AccessibleVersion2.AccessibleVersion

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

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