EIR Accessibility Framework Template V1.1

1. EIR Accessibility Framework Template V1.1 Agency Name

2. Approaching EIR accessibility holistically • Set agency expectation levels • Define agency EIR accessibility objectives • Prioritize your EIR accessibility work • Develop strategy and plans using the EIR Accessibility Framework Template • Identify EIR accessibility skill gaps and develop training plans • Develop short / long term goals and measure to them

3. Set agency expectations through a proper set of program assumptions • Prioritized, multi-year initiative • Work items assigned at various levels • Individual • Departmental team(s) • Interdepartmental team(s) • Interagency team(s) • Work efforts and schedules will be realistically balanced as to complement or not significantly impact contributors primary duties/assignments • Dynamic, with course and trajectory adjustments as needed

4. Define the overall objective(s) Example • Ensure that all Electronic Information Resources (EIR) delivered or used by <Agency Name> are accessible, usable and compliant to Texas accessibility requirements: • Texas Government Code 2054, Subchapter M • Texas Administrative Code Chapter 206 • Texas Administrative Code Chapter 213 • Includes but not limited to: • Intranet and internet content • Public information • Business applications • Media services • Telecommunications • Contracted information resources projects • Purchased goods or services that are covered under the definition of electronic information technology 4

5. Prioritize the work effort Priority classification hierarchy* example • Externally facing, mission critical, high number of external users (includes all Internet pages) • Externally facing, non-mission critical, high number of external users • Externally facing, mission critical, low number of external users • Externally facing, non-mission critical, low number of external users • Internal use, mission critical, high number of users • Internal use, non-mission critical, high number of users • Internal use, mission critical, low number of users • Internal use, non-mission critical, low number of users *Priority classification assumptions 1. New applications/application enhancements entering pilot (user acceptance) test phase (Internet or intranet) should receive priority within the priority class (1–6) 2. New applications/application enhancements under development (Internet or intranet) will receive priority within the priority class (1–6) 3. Priority for individual applications may change based upon business needs PrioritizedApplicationsTemplate

6. Develop strategy and plans usingthe EIR Accessibility Framework Template Agency Work Plan 6

7. Identify skill gaps and build“Role Based” Accessibility Training Plans * As needed based on assignment. 7

8. Develop short and long term accessibility goals: Example 8