ADA/504 Accessibility Program FY Transition Plan Progress Report Juanita Webber, Civil Rights Division

Transcription

1 ADA/504 Accessibility Program FY 2018 Transition Plan Progress Report Juanita Webber, Civil Rights Division

2 Table of Contents 1. INTRODUCTION BACKGROUND DEPARTMENT ADA/504 PROGRAM ACCESSIBILITY TO BUILDING FACILITIES... 3 Safety Rest Areas PEDESTRIAN ACCESS IN THE PUBLIC RIGHT-OF-WAY... 5 Design Standards... 5 Bridges PROGRAM ACCESSIBILITY ON-GOING PROGRAM ACTIVITIES:... 8 TxDOT ADA Program Plan... 8 Nondiscrimination Assurances... 8 Training... 9 Public Involvement Citizen Comments/Complaints Web-based Accessibility DEPARTMENT KEY DOCUMENTS TRANSITION PLAN ACTIVITIES: SUMMARY OF FY 2017 ACCOMPLISHMENTS AND FY 2018 GOALS ATTACHMENTS ii FY 2018 ADA/504 Transition Plan Progress Report

3 INTRODUCTION This document describes the actions of the Texas Department of Transportation (TxDOT, Department) to provide accessibility to its programs, services and activities for those with disabilities, in compliance with 23 CFR 200.7, 28 CFR 35, 49 CFR 27 and 49 CFR 37, and other applicable regulations and authorities. It is intended to be a living document to reflect the current state of the Department s Americans with Disabilities Act (ADA) and Section 504 (504) Accessibility Program, and provide a progress report of the development of a revised Transition Plan, due August, The Department welcomes comments, suggestions and questions from the public, particularly those with disabilities or service groups representing communities with disabilities. For more information, please visit the Department s ADA Webpage ( or contact the Department s State-wide ADA/505 Coordinator or ADA Compliance Program Administrator: ADA Coordinator Name: Michael D. Bryant Phone: (512) Michael.D.Bryant@txdot.gov Mail: Texas Department of Transportation 125 E. 11 th Street Austin, Texas ADA Compliance Program Administrator Name: Juanita Webber Phone: (512) Juanita.Webber@txdot.gov Mail: Texas Department of Transportation 125 E. 11 th Street Austin, Texas BACKGROUND Adopted on July 26, 1990, the ADA is a federal civil rights law that provides protection for persons with disabilities against discrimination by public and private entities. The ADA extends similar, earlier protections provided by the Section 504 of the Rehabilitation Act of 1973 (Section 504). Section 504 requires entities that receive federal financial assistance to ensure they do not discriminate against persons with disabilities when providing their services, programs and activities. The ADA prohibits discrimination on the basis of disability for operations conducted by State and local governments and for facilities owned by private businesses, even if they do not receive federal financial assistance. Title II of the ADA requires State and local governments to ensure their services, programs and activities are accessible to and usable by persons with disabilities. 1 FY 2018 ADA/504 Transition Plan Progress Report

4 Title III requires public accommodations and commercial facilities to ensure their buildings and sites are designed, constructed and altered in compliance with accessibility standards. As a State government agency, the operations of the Department are subject to both the requirements of Section 504 and Title II of the ADA. In addition, the Department provides oversight of, information and resources to, and coordinates transportation-related activities with other Title II agencies in Texas, including city and county governments; metropolitan planning organizations (MPOs) and public transit providers. As an employer within Texas State Government, and a provider and user of public and private services, the Texas Department of Transportation is also subject to requirements of ADA Title I (employment), Title III (contracts with private consultants and contractors) and Title IV (telecommunications services). Under a Governor s Executive Order, the Department s Websites are designed to meet the web content criteria under Section 508 of the Rehabilitation Act of 1973 Standards for Electronic and Information Technology. DEPARTMENT ADA/504 PROGRAM In July 1990, the Office of General Counsel advised all State Transportation Agencies (STA) of the adoption of the ADA. Around that time TxDOT began to consider the impact of this law on building facilities owned and operated by the Department. When the ADA Standards were published in July 1991, the Department began to include accessible elements into the Department s programs, services, activities and facilities. The ADA became effective on January 26, Consistent with this law, in 1993 TxDOT began using the ADA Accessibility Guidelines as its accessibility standards. A state-wide ADA Coordinator was appointed and assigned the task of implementing and administering Department compliance activities under ADA Title II(A) State and Local Government Services, and coordinating activities under Title III Public Accommodations and Commercial Facilities. TxDOT developed its initial Transition Plan in That plan was later revised in 2004 and is currently under another revision. The current state-wide ADA Coordinator has oversight of the grievance process and investigating complaints; training; providing technical assistance; customer service and other program services and activities. In October, 2016 the Department hired an ADA Compliance Program Administrator with specialized knowledge and skill to provide guidance to transform the ADA/504 Accessibility Program. During this initiative, an ADA mission, values and goals have been developed to establish the Department s policies and procedures for accessibility that are instrumental in directing training and outreach activities related to accessible transportation services and facilities. In addition, a data collection process has been instituted to guide the Department s self-evaluation of its policies, procedures, and practices in all services, programs, activities and facilities to identify and eliminate barriers to accessibility and revise the 2004 Transition Plan. 2 FY 2018 ADA/504 Transition Plan Progress Report

5 The Department is comprised of twenty-five districts and thirty-four divisions. In addition to the statewide ADA Coordinator and ADA Compliance Program Administrator, an ADA Liaison has been assigned to each district and division respectively, who is responsible for program implementation. Each ADA Liaison coordinates compliance activities with the Compliance Program Administrator and submits required compliance reports and other goals and accomplishments updates which are encompassed in this report. (See Attachment A for a list of ADA Liaisons with contact information). The list is updated regularly. ACCESSIBILITY TO BUILDING FACILITIES TxDOT currently owns 2,641 facilities at 375 locations throughout the state of Texas. There are three classes of buildings: (a) 657 Class A which are occupied with people; (b) 950 Class B which houses equipment, shops and some people; and (c) 921 Class C which are salt sheds, canopies used for equipment or material storage. A Facility Condition Assessment (FCA) was performed to evaluate the overall health and condition of each TxDOT facility. The assessment focused on the core structure and the supporting systems (such as electrical, mechanical, plumbing, ingress, egress, roofing, accessibility, fire safety and protection, exterior envelop, etc.) As a result, the FCA created a baseline for each facility; thereby, creating a rudimentary baseline for accessibility compliance of each occupied facility. A contract was executed with architectural consultants, Lockwood, Andrews & Newnam, Inc. in September, 2017 to conduct a comprehensive evaluation of all TxDOT occupied facilities to identify ADA accessibility deficiencies. The Statewide ADA Facilities Assessments began July 2017 once contract negotiations were completed. The program began with a pilot assessment of the Austin Headquarters and Austin District facilities. A statewide assessment program was initiated in early To date, the assessments have been performed for twenty-three (23) of the twenty-five (25) districts. The assessment is scheduled to be completed July 15, The deliverables and Project Schedule Summary can be found in Attachment B. The project deliverables were broken into five separate Work Authorizations in order to add quality control to each phase of statewide assessments. An executive summary of the findings and recommended solutions to meet ADA standards will be submitted on or before July 15, These findings and recommendations will be included in the final revised Transition Plan, August All new and altered buildings include accessible features that meet the ADA accessibility requirements, as well as Texas Accessibility Standards for staff and visitors with disabilities. These findings will be integrated in the interactive Geographic Information System (GIS) and coded in a similar method as in the attached maps Attachment C. 3 FY 2018 ADA/504 Transition Plan Progress Report

6 Safety Rest Areas TxDOT maintains 78 Safety Rest Areas across the state. In addition to the multiple repairs completed every year at various Safety Rest Areas, TxDOT builds 1-2 new safety rest areas per year. Each new Safety Rest Area is subject to inspection through an accessibility specialist to comply with Texas Accessibility Requirements. TxDOT employs a 24 hour maintenance company to run the safety rest areas. This company is responsible for repairs needed at each rest area. TxDOT performs inspections of each Safety Rest Area 4 times per year. At these inspections, any potential safety hazards are investigated and reported, whether they are small or large in scale. TxDOT uses two important sources to determine where to put safety rest areas. The first source is the Crash Reporting for Safer Highways (CRASH) which is a data base where law enforcement officers can input reports of accidents. The second is the TxDOT state-wide planning map This map indicates traffic counts for cars and trucks on highways in Texas. Since the land is usually in rural areas it is usually at a minimum cost and the Maintenance Division works with the Districts to acquire the land. Once funding is available and the land is acquired, the project is sent to an architect for design although TxDOT completes some of the safety rest area plans in house. While the architect does the building design work, the District completes the roadway design. At the completion of plans, specifications and estimates, the two drawing sets combined are sent out to bid. There is a sign located at each safety rest area that states where to call if someone has a maintenance concern. The onsite maintenance staff also takes comments and complaints. The maintenance company then schedules the necessary repairs. If the complaint goes beyond their scope, it comes directly to the Safety Rest Area Section where it is addressed. Since some of the safety rest areas are years of age and are in need of repair and upgrading. TxDOT has recently implemented a program where they are demolishing these older safety rest areas and building new, ground up buildings. These are mostly our open air concept buildings (no air conditioning). At the current time, there are three demo and replace safety rest areas that are in the design process, one large set of rest areas that have just opened, one large set that will open in September, and one large set that is in the design phase. For new safety rest areas, plans are handed over to a registered accessibility specialist to review for Texas Accessibility Standards compliance. Once the safety rest area is built, the accessibility specialist inspects the project for compliance. For older safety rest areas, an assessment was completed on our facilities preceding the adoption of the Texas Accessibility Standards and changes were implemented. We also continue to monitor each safety rest area to see if there is a need to incorporate more safety features, some pertaining to ADA. Our Safety Rest Area team currently consists of 3 architects and 4 engineers (one engineer being the section head) as well as 2 inspectors and 1 supervisor to the inspectors. 4 FY 2018 ADA/504 Transition Plan Progress Report

7 PEDESTRIAN ACCESS IN THE PUBLIC RIGHT-OF-WAY Design Standards TxDOT maintains 80,483 centerline miles of roadway, of which an estimated 9755 centerline miles are within urbanized areas. There is also an estimated 26,859 miles of sidewalk within the State right of way. All projects within urbanized areas must consider the addition of pedestrian and bicycle facilities as an integral part of the design. To this end, the Design Division supports TxDOT district staff as well as consultant engineering staff to ensure that all new and altered facilities meet the requirements of the ADA. The division maintains the Roadway Design Manual as well as the Pedestrian Facility Standards to serve to provide guidance for accessible design compliance. TxDOT has developed internal design standards to be consistent with the information contained in the latest draft of the Public Right of Way Accessibility Guidelines (PROWAG) issued by the U.S. Access Board. These guidelines represent the most current approach to accessible design in the public rights of way. The Design Division has also developed a Departmental Material Specification for detectable warning materials to be used on curb ramps constructed by the department. The division also maintains a list of approved detectable warning materials and suppliers known as the Material Producer List. The Design Division has also been in the process of developing a plan of action to refresh TxDOT s self-evaluation and ADA Transition Plan discussed later in this document. Bridges Texas has 54,180 publically owned vehicular bridges. This number includes 35,564 bridges on the state system and maintained by TxDOT and 18,616 bridges off the state system, such as city streets and county roads, which are maintained by local governments. Texas also has 27 international bridges open to vehicular traffic between Mexico and Texas. The average age of Texas on-system bridges is 46 years and 33 years for off-system bridges. TxDOT inspects all publically owned vehicular bridges every two years and some more frequently. This ensures all bridges open to vehicular traffic in Texas are safe. TxDOT utilizes the following terms to identify the conditions of its bridges which are eligible for rehabilitation or replacement: structurally deficient (SD); functionally obsolete (FO); or substandard-for-load-only bridge. 5 FY 2018 ADA/504 Transition Plan Progress Report

8 Prior to 2012, the Federal Highway Administration (FHWA) used the bridge condition terms to designate bridges eligible for federal funding for its Highway Bridge Program (HBP). When the new Moving Ahead for Progress in the 21st Century (MAP 21) bill was signed into law in July, 2012, FHWA no longer managed a federal highway bridge program and began allocating federal funds to the State Transportation Agencies (STAs) to manage. TxDOT chose to continue its Highway Bridge Program (HBP) at the state level and continues to use the terms above to identify bridges that are eligible for rehabilitation or replacement. Bridge projects are selected and programmed in five-year cycles that run continuously. This means that each year, a new five-year program is established, made up of the previous four years of already programmed bridges, plus additional bridges eligible to be programmed in the fifth year. Bridges in the HBP must be SD or FO and have an inspection Sufficiently Ratings (SR) of 80 or below to be eligible for HBP funding. Bridges with the lowest SR are given the highest priority for programming in the HBP. The HBP Eligibility List is distributed to all TxDOT districts, who work with local officials to determine which bridges to consider for programming. This collaboration results in a proposed project list of both on- and off-system bridges. This proposed list is submitted to the Bridge Division for prioritization, which results in a state wide list of on-system and off-system programmed bridge projects. Project development of on-system bridge projects can begin as soon as they are programmed, while project development for off-system bridge projects begins upon the execution of necessary funding agreements. The HBP is monitored monthly by the Bridge Division to review changes to project schedules. The Bridge Division, in consultation with the districts, modifies project letting schedules when necessary to insure all fiscal year allocations of HBP funding are expended. The Bridge Division provides guidance to the 25 districts regarding the construction of the bridges, facilitates programming, and assists with funding the projects. The respective districts are responsible for ensuring all bridges are constructed in compliance with the American Association of State Highway and Transportation Officials (AASHTO) specifications, which includes all of the necessary requirements to meet ADA accessibility according to the Americans with Disabilities Act and other accessibility laws and regulations. Additionally, TxDOT submits reports to FHWA annually and compiles the Report on Texas Bridges biennially. The most recent Report on Texas Bridges was prepared from data as of September The 2018 report, using data as of September 2018, will be published in time for the 86th Texas Legislative Session. 6 FY 2018 ADA/504 Transition Plan Progress Report

9 PROGRAM ACCESSIBILITY Title II of the Americans with Disabilities Act (ADA) requires State and local governments to make their programs and services accessible to persons with disabilities. This requirement extends not only to physical access at government facilities, programs and events, but also to policy changes that government entities must make to ensure that all people with disabilities can take part in, and benefit from, the program services. A self-evaluation was conducted in all district and division programs through the use of the Self- Evaluation Update Program Accessibility Questionnaire to determine if the programs and activities are accessible to persons with disabilities. The questionnaire focused on thirteen (13) key areas: General Description of the District/Division; Policies and Practices that may limit the Participation of Individuals with Disabilities in the Organization s Programs and Activities; Information and Training for Staff; Use of Contractors; Transportation; Telephone Communication; Documents and Publications; Meetings; Audio Visual Presentations; Automated Electronic Equipment; Emergency Evacuation; Notification; and Service Animals. Each district and division was required to complete and submit supporting documentation of its practices and procedures with respect to all of its programs. The questionnaire was distributed in November 2017 and is currently being analysed by the Civil Rights Division (CIV) in an effort to determine deficiencies or barriers that may keep persons with disabilities from being fully engaged in the services offered by TxDOT. These thirteen (13) components were evaluated in alignment with the Americans with Disabilities Act and other Federal and State laws and regulations. The final report identifying deficiencies and recommended solutions can be found in Attachment D. Barriers that can be removed easily to improve TxDOT s ability to serve the needs of people with disabilities and their families will be addressed immediately and those requiring additional time will be included in the revised, August 2019 Transition Plan. 7 FY 2018 ADA/504 Transition Plan Progress Report

10 ON-GOING PROGRAM ACTIVITIES: TxDOT ADA Program Plan Each year on November 1 st, the Department submits to the Texas Division Office of the U. S. Department of Transportation Federal Highways Administration (FHWA) an updated ADA/504 Accessibility Program Fiscal Year Accomplishments and Goals Report. The report is composed of three areas: A description of the Department s project-level and program-level activities directed toward providing accessibility to its facilities and services. These include a description of the Program; participants involved in the program directly and indirectly; ADA training provided to the Department staff, consultants, contractors; outreach to local government agencies and other business partners; public involvement activities during program implementation and project delivery; and the grievance policy and procedures. A narrative from all twenty-five (25) districts and twenty-eight (28) divisions identifying changes, emerging issues or accomplishments in the program during the past fiscal year, along with prospective innovation and activities. A narrative of goals from all districts and divisions for the upcoming year and an outreach plan devised by each district describing their respective plan to reach out to persons with disabilities in the community to provide awareness, education or training regarding future projects. Future reports will include responses to customer complaints, including resolution of accessibility issues and accounting of transition plan activities, including features surveyed during the year, those identified as needing repair or upgrade and those actually programmed for work. Nondiscrimination Assurances As the head of the Department, the TxDOT Executive Director is ultimately responsible for ensuring equity and non-discrimination in all Department program services and activities. Every three years or commensurate with a change in Department executive leadership, the Executive Director executes a written commitment to non-discrimination as required by 23 CFR 200.9(a)(1) and 49 CFR 27.9(a). The Department is an equal opportunity employer and strives to make all of its services, programs, activities and facilities accessible with regard to disability in compliance with 28 CFR Toward this end, the Department has issued policies and procedures reflecting this intent: The Department s Equal Opportunity Policy may be found at: The Department s ADA Policy Notice is posted on the Department website at: 8 FY 2018 ADA/504 Transition Plan Progress Report

11 The Department s ADA Nondiscrimination Statement is posted on the Department website: The Department s Assurance is posted on the Department website at: All are available by hard copy and in alternative formats upon request. Training TxDOT established an ADA Training Program describing the requirements of ADA and its responsibility under it. The training program covers in detail, courses and topics that address the ADA Regulations and Standards and how they impact Department operations, the scoping of technical requirements of the ADA Standards for Accessible Design (ADAS), the Standards for Transportation Facilities (ADASTF) and the proposed Public Rights of Ways Accessibility Guidelines (PROWAG) and include examples of compliant and non-compliant facilities. Specifically, DES 122 a six-hour course, was developed to provide an update on accessible facility design with a focus on compliance with the Americans with Disabilities Act (ADA) and the Texas Accessibility Standards (TAS). The class was previously known as Designing for Pedestrian Access. DES 122 is made available to all TxDOT employees and external Subrecipients. The training was created to provide information and best practices for those involved in the design, construction and maintenance of pedestrian facilities and for those individuals who ensure compliance with applicable Federal and State laws. It is offered in multiple district office locations at various times and in some cases, upon request. TxDOT partnered with the Southwest ADA Center to provide ADA training to its employees. Topics ranged from Effective Communication to Title II-Disability Employee Awareness. Trainings were delivered in- person and via WebEx. Other training will soon be offered through TxDOT s Electronic Learning Management System (ELM). Multiple divisions currently provide ADA training to Subrecipients regarding assurances and obligations required in their contractual agreements with TxDOT. Additional training is being developed to provide training that covers the ADA Subrecipients Compliance and Monitoring Program which includes training to assist with transition plans and more. This past April, the Federal Highway Administration conducted the training for Designing Pedestrian Facilities for Accessibility course in the Houston and Austin districts. The targeted audience of the course was Local Agency Employees and TxDOT Design, Construction, Traffic and Safety Engineers. The six-hour course was designed to ensure that pedestrian facilities and access routes are properly construction and maintained for all individuals, including those with disabilities. This course also focuses on proper design and maintenance of pedestrian access routes in new construction or when existing facilities are altered. Participants were engaged through a power point presentation, small group discussion, and an outdoor exercise. 9 FY 2018 ADA/504 Transition Plan Progress Report

12 Audience Course Name Date Duration Location Presenter ADA Liaisons Disability Etiquette Nov. 9, hours (in person) 200 E. Riverside Dr. Rm 1A.1 Austin, Texas Effective Communication Feb. 15, min. WebEx Program Accessibility Apr. 19, min. WebEx The Top 10 ADA Transportation Related Questions & Answers Sept. 27, min. WebEx Southwest ADA Center Southwest ADA Center Southwest ADA Center Southwest ADA Center Nov. 2, Day Austin District Office Krause/Webber Nov. 7, Day Fort Worth District Office Krause Nov. 29, Day Houston District Office Krause TxDOT Technical Employees TxDOT Employees and Local Governments/ Subrecipients TxDOT Managers and Supervisory Staff* Non-supervisory TxDOT Employees TxDOT Subrecipients DES 122 FHWA: ADA & Subrecipients ADA Title II Disability Employment Awareness TxDOT s ADA Subrecipient Monitoring Program ** May 17, Day Dallas District Office Krause June 12, Day San Antonio District Office Krause Jan. 23, Day El Paso District Office Krause Apr. 25, Day Austin (RA 200 Divisions) Krause May 17, day Dallas District Office Krause Apr. 9-11, Days Houston District Office Apr , 2018 Complete w/in 60 days of notification 2 Days Ric Williamson Hearing Rm. 125 E. 11 th St. Austin, Texas Patrick Gomez (FWHA) Patrick Gomez (FWHA) 2 ½ hours ELM TxDOT TBD 1½ Days Dallas/Fort Worth CIV - ADA Aug , ½ Days Houston CIV - ADA TBD 1½ Days San Antonio CIV - ADA * Complete every two years as part of the EEO requirement. ** Computer-based training also available. TBD 1½ Days El Paso CIV - ADA Public Involvement The Department actively pursues public involvement opportunities. The Civil Rights Division (CIV) works closely with the Office of Public Involvement. TxDOT s Public Involvement Policy states: The Texas Department of Transportation (TxDOT) commits to purposefully involve the public in planning and project implementation by providing early, continuous, transparent and effective access to information and decision-making processes. TxDOT will regularly update public involvement and incorporate a range of strategies to encourage broad participation reflective of the needs of the state s population. The policy can be found at 10 FY 2018 ADA/504 Transition Plan Progress Report

13 Each district office has a Public Involvement Officer to assist with various outreach events. Regional Public Involvement Specialists are designated to assist districts with various stages of planning. Additionally, the Office of Public Involvement collaborates with CIV in sharing information about the ADA Accessibility Program through the Connection Our Communities newsletter. (Attachment E) A public involvement meeting specifically related to accessibility is hosted every November by TxDOT CIV, the Austin District, ADA Outreach Committee, and other Divisions. The most recent meeting was held November 16, Several stakeholders of the disability rights advocacy community participated in this outreach to provide feedback on safety, mobility and the Transition Plan. Projects specific to the Austin District Office were highlighted by the ADA Liaison. Other Department representatives from various divisions also presented information and encouraged feedback through questions and answers participation with the attendees. (See Attachment I) Each district office submits an Outreach Action Plan every year, along with their respective narratives for the Department s overall Accomplishments and Goals Report. (See example below). 11 FY 2018 ADA/504 Transition Plan Progress Report

14 Procedures were developed to assist districts and divisions when hosting public meetings. Several resources are provided on CIV s internal Crossroads webpage to help with planning successful meetings. The Office of Public Involvement partnered with CIV to provide Public Involvement training to introduce TxDOT Public Involvement Policy and offer meeting strategies. Specific attention was given to: (a) accessible locations; (b) effective communication; (c) special accommodations and appropriate language; and (d) auxiliary aids and service to help make meetings more accessible. All other Department divisions participate, support and collaborate with CIV to accomplish the TxDOT - Headquarters Outreach Plan. CIV also posts public involvement opportunities on the Department s website at 12 FY 2018 ADA/504 Transition Plan Progress Report

15 13 FY 2018 ADA/504 Transition Plan Progress Report

16 14 FY 2018 ADA/504 Transition Plan Progress Report

17 Citizen Comments/Complaints Through a positive interactive process, the Department is able to quickly respond to citizen comments, requests and complaints about the accessibility of Department operations and facilities. Contact information for statewide and District ADA liaisons is published on the Department s internal and external website. TxDOT s ADA Coordinator and ADA Compliance Program Administrator have the responsibility to reply to citizen comments. District and division ADA liaisons refer queries to the Civil Rights Division (CIV) and other offices within the Department. Ultimately, CIV is responsible for taking action; direct activities of others to quickly resolve accessibility problems, and submitting official Department responses to a grievance or complaint to the Federal Highway Administration (FHWA). Citizens who bring accessibility complaints to the Department s attention receive a courtesy call and acknowledgement of receipt of the complaint within fifteen days. In most cases, final resolution is reached within thirty (30) days. To ensure maximum opportunity for the public to identify potential issues, the Department broadly posts and distributes non-discrimination language: Texas Department of Transportation (TxDOT) does not discriminate on the basis of race, color, national origin, sex, age, disability or family status. Those with concerns or who require special accommodations under the ADA, should contact the organizer of a meeting, if applicable, or the ADA Coordinator or ADA Compliance Program Administrator if assistance is needed to address a complaint or grievance. Attachment F contains a list of the complaints or inquiries received by the Department during FY 2017/2018 along with a description of the resolution and date, if any. Web-based Accessibility Section 508 of the Rehabilitation Act of 1973 (Section 508) and the Americans with Disabilities Act (ADA) promise that no person can be discriminated against in a physical location or environment due to a disability. Digital accessibility is no exception to that rule. In recent months, the United States Access Board adopted fixed accessibility standards that will help guarantee digital inclusion for all. The Communications Division (CMD) is responsible for TxDOT s internal and external communications. CMD comprises the Executive & Employee Communications, Media Relations, Creative Services and Public Information sections. CMD oversees and coordinates TxDOT s internal and external websites; informs and responds to media outlets; manages social media efforts; conducts conversations with employees; produces photography, video and publishing and design services; plans conferences; and carries out customer service operations. 15 FY 2018 ADA/504 Transition Plan Progress Report

18 The Department websites are routinely reviewed to ensure continued compliance with Section 508. In an effort to constantly improve the user experience, was republished last summer to comply with software updates from Adobe as part of Phase I of the self-evaluation conducted on the websites. Some of the noticeable visual changes include: is no mobile-friendly; users can view and access pages on smartphones and tablets. The left-hand navigation buttons appear slightly larger so mobile users can touch them. The footer on the homepage is now organized into four columns so users can navigate the site better when using a mobile device. The search function is improved and yields more detailed information. The internal and external websites include a variety of program information and resources, including accessibility information, training and contacts. The ADA Notice, ADA Grievance Procedure, Department Design Standards and contact information for the Department s ADA Coordinator, ADA Compliance Program Administrator, and ADA Liaisons are also available. The sites include links to outside sources of information related to accessibility, to transportation services and facilities. Questions about the websites may be directed to Michael Sledge, Director of Creative Services at Michael.Sledge@txdot.gov or Joshua Hunter, Web Services Branch Manager at Joshua.Hunter@txdot.gov. Some district and division web coordinators attended training on the new CMS. District public information officers (PIOs) were trained July-August, 2017 regarding software features of the upgrade. Web Publishing Guidelines were updated to reflect changes in CMS. Additional information on the topic of accessibility was included to increase awareness of laws concerning TxDOT s role in ensuring our websites can be accessed by all users. Training is ongoing and is part of the website content rewrite plan now being developed by CMD. Phase II of the self-evaluation web accessibility process is now underway. In collaboration with the Information Management Division (IMD), a list identifying accessible applications and programs auxiliary to the static content on is being compiled. IMD or TxDOT s designee oversees the upgrade of applications and programs that can be updated, and the elimination of those that are obsolete and do not meet the Standards of Section 508. A plan has been developed to help provide accessibility to everyone who visits That plan is outlined in the IMD Project Charter for User Experience RITM (See Attachment G) 16 FY 2018 ADA/504 Transition Plan Progress Report

19 DEPARTMENT KEY DOCUMENTS Beginning in 1992, the Department started adding and revising procedures, handbooks, guidelines and manuals to include direction to provide accessible elements to pedestrian facilities during the planning and development of Department building, road and bridge projects. The following table lists accessibility pertinent information presented in documents published by the Department: Document ADA Accessibility Program Liaisons Booklet I ADA Accessibility Program Liaisons Booklet II ADA Subrecipients Technical Manual Bridge Inspection Manual Roadway Design Manual Human Resources Policy Manual Web Publishing Guidelines Project Development Process Manual ROW Utility Manual TDLR Construction Accessibility Requirements Traffic Signals Manual TxDOT 2014 Standard Specifications Book Description Provides guidance and the Department s intent and procedures for complying with the ADA and Section 504 of the Rehabilitation Act. This procedure was originally published in Fall Updated annually. Provides guidance and the Department s intent and procedures for complying with the ADA and Section 504 of the Rehabilitation Act. This procedure was originally published in Fall Updated annually. Provides technical assistance and guidance to Subrecipients regarding TxDOT s ADA Accessibility Program and the ADA Subrecipients Compliance and Monitoring Program. This manual provides guidance for bridge inspection personnel, provides a reference for consultants, and helps to ensure consistency in bridge inspection, rating, and evaluation. The Roadway Design Manual was developed by the Texas Department of Transportation to provide guidance in the geometric design of roadway facilities. It should be noted at the outset that this document is a guide containing geometric design recommendations and does not represent an absolute design requirement. The Roadway Design Manual represents a synthesis of current information and operating practices related to the geometric design of roadway facilities The Human Resources Policies are intended to provide a broad overview of the most commonly referenced rules relating to employment with the Department. The policies in this manual are based on federal and state law, and shall defer to those laws if any changes occur. This is not intended to be an exhaustive source of information, and other laws or policies may apply beyond this document. The Human Resources Policy Manual is an electronic publication and any amendments, deletions or additions, are effective on the day posted to the website unless otherwise noted. Updating content renders any physical copy to be out of date. The policies in the Human Resources Policy Manual shall supersede any operating or governing procedures that may be found elsewhere. These guidelines serve as a resource for TxDOT staff responsible for maintaining District or Division content on our external websites (web coordinators and PIOs), primarily TxDOT.gov. This manual release updates references to outdated department structure, policies, technology, and processes. The Project Development Process Manual provides task information for the transportation engineering practitioner to begin with a project concept and move forward to a complete PS&E project approved for work authorization. Describes the authority of TxDOT to permit the use of public rights of way by public and private utility entities. It includes acceptable minimum clearances around above-grade utilities when they are placed in or near pedestrian facilities. The ROW Utility Manual is developed by Rule in close coordination with utility companies in Texas. Describes how TxDOT projects must be constructed so that they are in compliance with various accessibility requirements. These requirements are contained in: 1. Texas Accessibility Standards (TAS) TAC, Part 4, Chapter 68, Elimination of Architectural Barriers (AB) 3. Texas Government Code, Title 4, Subtitle E., Chapter 469, Elimination of Architectural Barriers (TABA) This manual is a guide and reference for the handling of requests for traffic signals on the designated State Highway System, including installations financed by federal funds and installed off the numbered State Highway System. This manual describes the steps necessary for the installation of traffic signals, from project inception through construction and final disposition of records. Describes TxDOT s standards and specifications for the construction and maintenance of highways, streets and bridges. ftp://ftp.dot.state.tx.us/pub/txdot-info/des/spec-book-1114.pdf 17 FY 2018 ADA/504 Transition Plan Progress Report

20 TRANSITION PLAN ACTIVITIES: Through the implementation, development and maintenance of policies, procedures and practices, the Department has institutionalized the provision of accessible services, programs and facilities into Department operations. Since 1992, the Department has included accessible features in all projects. TxDOT completed a comprehensive self-evaluation (including its buildings and rest areas, programming policies, and employment) and published a transition plan in 1993 addressing those aspects of the ADA. An effort to update the original transition plan took place in extending to full inventory of curb ramps at all intersections on the state highway system. Existing curb ramps were assessed for compliance and assigned a static severity ranking by field collection staff with respect to the standards in effect at the time of collection and the proximity of each asset to nearby pedestrian activity generators. The inventory was used as the basis for TxDOT s 2004 Transition Plan. Over time, the 2003 inventory has become outdated due to uncaptured improvements made within the right of way changes in the makeup and location of pedestrian attractors since the initial inventory was completed. The technology used to maintain the 2003 inventory was limiting, as was universal knowledge of the system s existence amongst the various stakeholders. Legal precedent showed that an uncoordinated approach to documenting the construction of accessible pedestrian elements through the course of routine roadway projects, maintenance activities, and dedicated remediation programs could leave the Department vulnerable to legal challenges. Also, the USDOT adopted the 2006 standards for public transportation facilities and in 2010 updated the federal accessibility standards which contributed to the decline in usefulness of the 2003 inventory in selecting and prioritizing project components, thereby prompting the need for a new inventory. In an effort to revise the 2004 Transition Plan, a contractor was hired to develop procedures, program goals, and policy definitions to support the redevelopment of the Pedestrian Access Inventory (PAI) of infrastructure in the state right of way (ROW) and the collection effort associated with this inventory. An update of the Pedestrian Access Inventory and Self-Evaluation can be found in Attachment H. The information collected and policy recommendations will be used as the basis for the Department s Americans with Disabilities Act (ADA) Transition Plan and Curb Ramp Program Planning Document updates. 18 FY 2018 ADA/504 Transition Plan Progress Report

21 The development of the PAI began with a pilot study in Austin, San Marcos, New Braunfels, and San Antonio to trial data collection methods; prioritization models, cost estimating, and reporting mechanisms; program planning tools; and documentation procedures prior to statewide implementation of the final recommended policies. Once completed, the collected data was analysed and the information was customized for GIS compatibility. A final executive summary of the findings was issued in January of the following year. Two additional contractors were hired to assist with the statewide implementation. Currently, data is being collected in all twenty-five (25) districts. The self-evaluation is scheduled to conclude no later than May, The final report of the findings will form the basis of the PAI, and will be included in the newly revised Transition Plan, August TxDOT hired an ADA Compliance Program Administrator with specialized knowledge and technical skills to begin developing the ADA Accessibility Program in accordance with the October 2016 FHWA Risk Assessment and oversee the transition plan revision process. Other self- evaluations are underway to identify the inventory of facilities, web-based accessibility of all IT and Communications, and programs, activities and services. These evaluations are on schedule to be completed by the TxDOT target day of June, Upon completion, beginning June 2018 through January 2019, the planning, programming and design process will ensue to begin the removal of all identified barriers or deficiencies. The drafting of the new transition plan will take place the following six months, January 2018 through June TxDOT will allow a 30-day public comment period to generate feedback regarding the revised plan. The finalized Transition Plan will be available August FY 2018 ADA/504 Transition Plan Progress Report

22 SUMMARY OF FY 2017 ACCOMPLISHMENTS AND FY 2018 GOALS The Texas Department of Transportation understands its duty to provide accessibility for all users of its services and programs, including persons with disabilities. We are striving to provide accessible public services and facilities for persons using Texas state roadways and other transportation facilities. Significant progress in assuring compliance with the Americans with Disabilities Act and Section 504 of the Rehabilitation Act of 1973 has been made in the following areas: updating the 2004 Transition Plan; meeting FHWA reporting requirements; awareness; internal and external communications; outreach/public involvement; training; processing grievances; and developing and implementing a subrecipient monitoring program. FY 2017 Activities Number Date(s) Training courses provided to Department or Stakeholders 34 Multiple Dates ADA complaints or concerns received 3 Multiple Dates ADA Complaints resolved or closed 3 Multiple Dates Pedestrian features identified for accessibility repairs 21,371 Ongoing Pedestrian features for accessibility repairs corrected 3003 Multiple Dates Pedestrian facilities with accessibility repairs identified during daily operations Pedestrian facilities with accessibility repairs corrected during daily operations 70 Ongoing 38 Multiple Dates ADA committee meetings held 61 Multiple Dates ADA outreach events conducted 38 Multiple Dates Accommodations provided 33 Multiple Dates District and Local Agency Reviews 3 Multiple Dates ADA Subrecipients Survey sent to Local Agencies, Contractors and Consultants ADA Subrecipients Survey responses received from Local Agencies, Contractors and Consultants 6,000+ November, January, FY 2018 ADA/504 Transition Plan Progress Report

23 2018 FY 2017 Accomplishments Date 100% Districts and 98% Divisions identified an ADA Liaison January % of Districts and 98% of Divisions responded to the FHWA Dashboard Report Multiple Dates - Quarterly ADA reporting tool was designed and created for FHWA Reporting Portal November 2017 ADA Liaisons meetings and trainings offered Multiple Dates - Quarterly 25 district offices created an ADA Committee and host quarterly committee meetings Multiple Dates - Quarterly 25 district offices developed outreach plan and host quarterly outreach events Multiple Dates - Quarterly Developed ADA Training Program and multiple trainings delivered/offered Multiple Dates CIV, AHQ, AUS and many divisions hosted the annual Stakeholders outreach event November 15, 2017 Developed an electronic resource library of vendors for auxiliary aids to provide effective communication during public meetings and/or trainings June, 2017 Established the Subrecipients Compliance and Monitoring Program August September, 2017 Developed the ADA Subrecipients Compliance and Monitoring Technical Manual September, 2017 Created three different surveys to measure Subrecipients compliance August, 2017 Developed partnerships and new relationships with disability-related organizations, activists and other advocates Ongoing Conducted self-evaluations in all public rights of way, facilities, programs, activities and services Distributed ADA Notice posters to all districts and divisions New requirement was implemented regarding all public notices and flyers which must contain special accommodation statement Ongoing FY 2018 Goals Date Complete first draft of Transition Plan and June, 2019 Submit first draft of Transition Plan for public comment July, 2019 Make necessary revisions to the first draft and submit final copy of Transition Plan August, 2019 Complete data collection for public rights-of-way self-evaluation and submit report of findings May, 2019 Complete data collection for facilities self-evaluation and submit report of findings June, 2018 Analyse data collected for program accessibility self-evaluation and submit report of findings August, 2018 Complete data collection for web-based accessibility self-evaluation and submit report of findings Develop training for ADA Subrecipients Compliance and Monitoring Program August, 2018 CIV, AHQ, AUS and various divisions host the annual ADA Anniversary Celebration Outreach Event July 23, 2018 Re-send first Subrecipients surveys focusing on local governments only; analyse responses; and take the next steps in the process to further determine Strive for 100% reporting compliance from all districts and divisions Continue to foster inclusion and provide accessibility to all visitors and TxDOT employees June, 2018 Ongoing Ongoing 21 FY 2018 ADA/504 Transition Plan Progress Report

24 This page intentionally left blank. 22 FY 2018 ADA/504 Transition Plan Progress Report

25 ATTACHMENTS to follow in PDF format 23 FY 2018 ADA/504 Transition Plan Progress Report

26 ADA/504 Accessibility Program FY Attachments Transition Plan Progress Report Civil Rights Division

27

28 Attachment A ADA Liaisons TxDOT ADA Liaisons District or Division Name Title Phone Abilene Joe LeBlanc Business Services Supervisor (325) Joe.LeBlanc@txdot.gov Amarillo Justin Ford Business Services Supervisor Justin.Ford1@txdot.gov Atlanta Jason Overmyer Landscape Architect (903) Jason.Overmyer@txdot.gov Atlanta Sarah Heath ADA Liaison Sara.Heath@txdot.gov Atlanta Tommy Bruce Transportation Engr Supvr. (903) Tommy.Bruce@txdot.gov Audit and Compliance Nicole Lawson DE/DD Executive Assistant (512) Nicole.Lawson@txdot.gov Audit and Compliance Richard Wright Internal Audit Section Mgr (512) Richard.Wright1@txdot.gov Austin Amro Gaber Transportation Engineer (512) Amro.Gaber@txdot.gov Austin Mahendran Thivakaran Transportation Engineer (512) Mahendran.Thivakaran@txdot.gov Aviation Kari Campbell Aviation Grants Section Dir (512) Kari.Campbell@txdot.gov Aviation ROSE PANKHURST AVN Grant ADM ROSE.PANKHURST@txdot.gov Beaumont Deidre Williams HR Specialist (409) Deidre.Williams@txdot.gov Bridge Steven Smith Business Operations Admin. (512) Steven.Smith@txdot.gov Brownwood Eric Lykins Director of Construction (325) Eric.Lykins@txdot.gov Bryan Maury Jacob Landscape Architect (979) Maury.Jacob@txdot.gov Childress Chris Reed Director of Construction (940) Chris.Reed@txdot.gov Communications Tim Harriman Business Operations Manager (512) Tim.Harriman@txdot.gov Compliance Christpher Whitton Compliance Specialist (512) Christopher.Whitton@txdot.gov Compliance Parsons Townsend Compliance Section Director (512) Parsons.Townsend@txdot.gov Contract Services KAREN FITZPATRICK CONTRACT ADMIN. MGR KAREN.FITZPATRICK@TXDOT.GOV Contract Services RON STUCKEY CONTRACT ADMIN. MGR RON.STUCKEY@TXDOT.GOV Corpus Christi Aurora Guajardo Engineering Assistant (361) Aurora.Guajardo@txdot.gov Corpus Christi Michael Alvarez Transportation Engineer (361) Michael.Alvarez@txdot.gov Dallas Maher Ghanayem Transportation Engineer (214) Maher.Ghanayem@txdot.gov Dallas Tommy Johns Architect (214) Tommy.Johns@txdot.gov Design Harry Dawson Landscape Architect (512) Harry.Dawson@txdot.gov Design Pete Krause Landscape Arch Section Dir. (512) Pete.Krause@txdot.gov El Paso Sandra Sierra Special Projects Coord. (915) Sandra.Sierra@txdot.gov Environmental Affairs Billie Long HR Specialist (512) Billie.Long@txdot.gov Environmental Affairs Linda Pendergras Office Technician Linda.Pendergras@txdot.gov Financial Management Cynthia Ochoa DE/DD Executive Assistant (512) Cynthia.Ochoa@txdot.gov Financial Management Kurt Ahlhorn Special Projects Coord (512) Kurt.Ahlhorn@txdot.gov Fleet Operations Darah Walrip Info. Spec Darah.Waldrip@txdot.gov Fleet Operations Edwin Baez Spec. Proj. Coord Edwin.Baez@txdot.gov Fort Worth Chris Houghton Transportation Specialist (817) Chris.Houghton@txdot.gov TxDOT ADA Liaisons 6/25/ of 3

29 Fort Worth Faisal Abdel-Qader Transportation Engr Supvr (817) Houston Jannie Blackmon Construction Records Auditor (713) Houston Pablo Pinales Human Resources Officer (713) Human Resources Billie Long HR Specialist (512) Human Resources Denise Landry HR Specialist (512) Information Management Angie Burford Executive Assistant (512) Information Management James Pennington IMD Operations Section Director (512) Laredo Omar Costilla Transportation Specialist (956) Lubbock Kylan Francis Dir of Trans Plan & Devlpmt (806) Lubbock Rusty Smith Special Projets Coord Lufkin Ana Mijares Transportation Engr Supvr (936) Lufkin Jimmy Thompson Transportation Engr Supvr (936) Lufkin Kelly Morris Director of Transportation Planning and Development (936) Maintenance Stephen Binder Architect Assistant (512) Maritime Travis Milner Bus. Ops. Proj. Mgr Occupational Safety Monica Spiller Office Technician (512) Odessa Lennerd Byrd Business Services Supervisor (432) Paris Darius Samuels Transportation Engr Supvr. (903) Pharr Abel Marroquin Engineering Asst Pharr Evan Roberts Transportation Engr Supvr. (956) Pharr Joseph Leal, Jr. Transportation Engineer (956) Procurement Cynthia Goodson PRO Contract Specialist Procurement Jo Woten Purchasing Branch Manager (512) Professional Engineering Roy Gonzales PEPS Operations Manager (512) Professional Engineering Procurement Services Roy Gonzalez PEPS Operations Mgr Public Transportation Rebecca (Becky) Ligon Transport Funding Spec. (512) Rail Robert Travis Rail / Hwy Safety Branch Manager Robert.Travis@txdot.gov Research and Technology Implementation Crystal Stark-Nelson Contract Specialist, RTI (512) Crystal.StarkNelson@txdot.gov Right of Way Elizabeth Osgood Division Admin Manager (512) Elizabeth.Osgood@txdot.gov Right of Way Matthew Jimenez Right of Way Agent (512) Matthew.Jimenez@txdot.gov San Angelo Mario Ybarra Business Services Coord (325) Mario.Ybarra@txdot.gov San Antonio Darcie Schipull Planner (210) Darcie.Schipull@txdot.gov San Antonio Elizabeth Hogeda-Romo Business Services Supervisor (210) Elizabeth.HogedaRomo@txdot.gov San Antonio Gregg Granato Transportation Engr Supvr (210) Gregg.Granato@txdot.gov Support Services Byron Hicks Architect Byron.Hicks@txdot.gov Toll Operations Ralph O'Neal Field Oprs Facilities Coord (512) Ralph.ONeal@txdot.gov Traffic Operations Ann Hatchitt Management Analyst (512) Ann.Hatchitt@txdot.gov TxDOT ADA Liaisons 6/25/ of 3

30 Traffic Operations Shelli Belser Business Operations Administrator (512) Transportation Planning and Programming Jessica Smith Safety Officer (512) Travel Information Erin Lashlee Transportation Funding Spec (512) Travel Information Kristi Urkuski DE/DD Executive Assistant (512) Tyler Eric Fisher Transportation Engr Supvr Tyler Janice Allen HR Specialist (903) Tyler Jeff Kuechle Facilities Coordinator (903) Tyler Jeffrey Harmon Director of Construction (903) Tyler Juanita Daniels-West Transportation Engineer Waco Katelyn Kasberg Spec. Proj. Coordinator Wichita Falls Allan Moore Director of Construction (940) Yoakum Camille Marek, P.E. Transportation Engineer (361) TxDOT ADA Liaisons 6/25/ of 3

31 Attachment B - Project Schedule Summary

32 DocuSign Client : TxDOT Envelope ID: 6B681FDB-D8D C-DA50064A8A70 ID Task Name Duration Start Finish 1 ADA Facility Accessibility Assessment - Pilot Project 83 days Mon 7/3/17 Wed 10/25/17 2 Contract Negotiations 10 days Mon 7/3/17 Fri 7/14/17 3 Notice To Proceed 0 days Fri 7/14/17 Fri 7/14/17 4 Team Mobilization 10 days Mon 7/17/17 Fri 7/28/17 5 Austin East (MO) - LAN 7 days Mon 7/31/17 Tue 8/8/17 9 Austin North (AEM) - RDLR 7 days Mon 7/31/17 Tue 8/8/17 13 CTECC - LAN 10 days Mon 8/14/17 Fri 8/25/17 17 State HQ - Greer Building - LAN 10 days Mon 8/14/17 Fri 8/25/17 21 Austin Northwest (MO) - RDLR 10 days Mon 8/14/17 Fri 8/25/17 25 Burnett (AEM) - RDLR 8 days Wed 8/16/17 Fri 8/25/17 29 Llano (MO) - RDLR 10 days Mon 8/14/17 Fri 8/25/17 33 Mason (MO) - RDLR 8 days Wed 8/16/17 Fri 8/25/17 37 Interim Draft Report Submittal 5 days Mon 8/28/17 Fri 9/1/17 40 Interim Draft Review & 1 Day Review Meeting 5 days Mon 9/4/17 Fri 9/8/17 41 Austin District HQ & MO - LAN 10 days Mon 9/11/17 Fri 9/22/17 45 Austin Maintenance Special Crews - LAN 7 days Mon 9/11/17 Tue 9/19/17 49 Austin South (AEM) - RDLR 10 days Mon 9/11/17 Fri 9/22/17 53 San Marcos (MO) - RDLR 8 days Wed 9/13/17 Fri 9/22/17 57 Austin West / SW (MO) - LAN 10 days Mon 9/11/17 Fri 9/22/17 61 Austin Toll Rd. Customer Service - LAN 8 days Wed 9/13/17 Fri 9/22/17 65 Lockhart (MO) - RDLR 10 days Mon 9/11/17 Fri 9/22/17 69 Bastrop (AEM) - RDLR 8 days Wed 9/13/17 Fri 9/22/17 73 Pre-Final Report Submittal 5 days Mon 9/25/17 Fri 9/29/17 76 Pre-Final Review & 1 Day Meeting 5 days Mon 10/2/17 Fri 10/6/17 77 Taylor (MO) - LAN 7 days Mon 10/9/17 Tue 10/17/17 81 Georgetown (AEM) - LAN 7 days Mon 10/9/17 Tue 10/17/17 85 Fredericksburg (MO) - RDLR 7 days Mon 10/9/17 Tue 10/17/17 Statewide Facilities ADA Accessibility Assessment - Pilot Project Project Schedule 2017 June July August September October November 6/4 6/11 6/18 6/25 7/2 7/9 7/16 7/23 7/30 8/6 8/13 8/20 8/27 9/3 9/10 9/17 9/24 10/1 10/8 10/15 10/22 10/29 11/5 11/12 11/19 11/26 12/3 ADA Facility Accessibility Assessment - Pilot Project 83 days 10/25 Contract Negotiations 7/14 7/14 Notice To Proceed Team Mobilization 7/28 7 days 8/8 Austin East (MO) - LAN 7 days 8/8 Austin North (AEM) - RDLR 10 days 8/25 CTECC - LAN 10 days 8/25 State HQ - Greer Building - LAN 10 days 8/25 Austin Northwest (MO) - RDLR 8 days 8/25 Burnett (AEM) - RDLR 10 days 8/25 Llano (MO) - RDLR 8 days 8/25 Mason (MO) - RDLR 5 days 9/1 Interim Draft Report Submittal 5 days 9/8 Interim Draft Review & 1 Day Review Meeting 10 days 9/22 Austin District HQ & MO - LAN 7 days 9/19 Austin Maintenance Special Crews - LAN 10 days 9/22 Austin South (AEM) - RDLR 8 days 9/22 San Marcos (MO) - RDLR 10 days 9/22 Austin West / SW (MO) - LAN 8 days 9/22 Austin Toll Rd. Customer Service - LAN 10 days 9/22 Lockhart (MO) - RDLR 8 days 9/22 Bastrop (AEM) - RDLR 5 days 9/29 Pre-Final Report Submittal 5 days 10/6 Pre-Final Review & 1 Day Meeting 7 days 10/17 Taylor (MO) - LAN 7 days 10/17 Georgetown (AEM) - LAN Contract No DPS070 ERP No days 10/17 Fredericksburg (MO) - RDLR Task Rolled Up Progress Inactive Task Duration-only External Tasks Items in Blue - LAN Field Work Items in Green - Client Review / Meetings Items in Red - Critical Milestone Dates Items In Black - LAN Report & Submittal Production Milestone Summary Rolled Up Task Split External Tasks Project Summary Inactive Milestone Inactive Milestone Inactive Summary Manual Summary Rollup Manual Summary Start-only External Milestone Progress Deadline Rolled Up Milestone Group By Summary Manual Task Finish-only LAN Facilities Page 1 Sat 7/1/17

33 DocuSign Envelope ID: ABE8C385-37B E3-4BA981805FF0 Contract No. 38-7IDP8075 Work Authorization No. 2 ID Task Name Duration Start 1 Statewide ADA Facility Accessibility Assessment 67 days Fri 1/26/18 Mon 4/30/18 2 Notice To Proceed 1 day Fri 1/26/18 Fri 1/26/18 3 Team Mobilization 1 day Mon 1/29/18 Mon 1/29/ Laredo District 19 days Tue 1/30/18 Fri 2/23/18 24 Pharr District 19 days Tue 1/30/18 Fri 2/23/18 Exhibit C Statewide Facilities ADA Accessibility Assessment 2018 November December January February March April May June July A B M E B M E B M E B M E B M E B M E B M E B M E B M E B 67 days 1/26 Statewide ADA Facility Accessibility Assessment 1/26 Notice To Proceed Team Mobilization 1/29 19 days 1/30 Laredo District 19 days 1/30 Pharr District PS Contract No PS PO No % Draft Report Submittal 5 days Mon 2/26/18 Fri 3/2/ % Draft Report Review 5 days Mon 3/5/18 Fri 3/9/18 54 Corpus Christi District 20 days Mon 3/5/18 Fri 3/30/18 75 San Antonio District 30 days Mon 2/26/18 Fri 4/6/ Houston District (RDLR) 44 days Tue 1/30/18 Fri 3/30/ Pre-Final Report Submittal 5 days Mon 4/9/18 Fri 4/13/ Pre-Final Report Review 5 days Mon 4/16/18 Fri 4/20/ Final Report Submittal 6 days Mon 4/23/18 Mon 4/30/18 5 days 2/26 60% Draft Report Submittal 5 days 3/5 60% Draft Report Review 20 days 3/5 Corpus Christi District 30 days 2/26 San Antonio District 44 days 1/30 Houston District (RDLR) 5 days 4/9 Pre-Final Report Submittal 5 days 4/16 Pre-Final Report Review Task Rolled Up Progress Inactive Task Duration-only External Tasks Items in Blue - LAN Field Work Items in Green - Client Review / Meetings Items in Red - Critical Milestone Dates Milestone Summary Rolled Up Task Split External Tasks Project Summary Inactive Milestone Inactive Milestone Inactive Summary Manual Summary Rollup Manual Summary Start-only External Milestone Progress Deadline Rolled Up Milestone Group By Summary Manual Task Finish-only Engineering Engineering_IndefDelWA.doc Page 1 of 8 Exhibit C

34 DocuSign Envelope ID: A79659A5-A46B-4095-A2DA-31EA05B2EDF4 69D D1C-4B09-BD41-3A868D8B9FF4 Contract No. 38-7IDP8075 Work Authorization No. 3 ID Task Name Duration Start Finish Predecessors Resource Names 1 Statewide ADA Facility Accessibility Assessment 99 days WA Executed Tue 7/31/18 2 Notice To Proceed 1 day WA Executed WA Executed 3 Team Mobilization 1 day Fri 3/16/18 Fri 3/16/ Yoakum District 20 days Mon 3/19/18 Fri 4/13/18 29 Dallas District 20 days Mon 3/19/18 Fri 4/13/18 49 Lufkin District (RDLR) 15 days Mon 3/19/18 Fri 4/6/18 67 Tyler District 15 days Mon 4/16/18 Fri 5/4/ % Draft Report Submittal 5 days Mon 4/16/18 Fri 4/20/ % Draft Report Review 5 days Mon 4/23/18 Fri 4/27/18 90 Atlanta District 15 days Mon 4/23/18 Fri 5/11/ Beaumont District (RDLR) 15 days Mon 4/9/18 Fri 4/27/ Paris District 10 days Mon 4/30/18 Fri 5/11/ Pre-Final Report Submittal 3 days Thu 5/10/18 Mon 5/14/ Pre-Final Report Review 3 days Tue 5/15/18 Thu 5/17/ Final Report Submittal 2 days Fri 5/18/18 Mon 5/21/ Closeout and Final Invoice 9 days Tue 5/22/18 Fri 6/1/ Termination of Work Authorization and TxDOT Coordination with CIV 1 day Tue 7/31/18 Tue 7/31/18 Statewide Facilities ADA Accessibility Assessment PS Contract No PS PO No ber January February March April May June July A E B M E B M E B M E B M E B M E B M E B M E B 99 days? WA Executed Stat WA Executed Team Mobilization 3/16 Notice To Proceed 20 days 3/19 Yoakum District 20 days 3/19 Dallas District 15 days 4/6 Lufkin District (RDLR) 15 days 4/16 Tyler District 5 days 4/16 60% Draft Report Submittal 5 days 4/23 60% Draft Report Review 15 days 4/23 Atlanta District 15 days 4/9 Beaumont District (RDLR) 10 days 5/11 Paris District 3 days 5/10 Pre-Final Report Submittal 3 days 5/15 Pre-Final Report Review 2 days 5/18 Final Report Submittal 9 days 5/22 Closeout and Final Invoice Termination of Work Authorization and TxDOT Coordination with CIV 7/31 Task Rolled Up Progress Inactive Task Duration-only External Tasks Items in Blue - LAN Field Work Items in Green - Client Review / Meetings Items in Red - Critical Milestone Dates Milestone Summary Rolled Up Task Split External Tasks Project Summary Inactive Milestone Inactive Milestone Inactive Summary Manual Summary Rollup Manual Summary Start-only External Milestone Progress Deadline Rolled Up Milestone Group By Summary Manual Task Finish-only Architectural-Architectural _WA_ID Page 1 of 1 Exhibit C

35 DocuSign Envelope ID: BC5896D1-709A-4065-A80A-08D59F80A6CC 8D455F09-600A-400A-A6F3-313D3928C90F Contract No. 38-7IDP8075 PS Contract No Work Authorization No. 4 PS PO No Statewide Facilities ADA Accessibility Assessment ID Task Name Duration Start Finish Predecessors Resource Names 1 Statewide ADA Facility Accessibility Assessment 79 days WA Executed Tue 7/31/18 2 Notice To Proceed 1 day WA Executed WA Executed 3 Team Mobilization 1 day Fri 4/13/18 Fri 4/13/ Brownwood District 10 days Mon 4/16/18 Fri 4/27/18 17 Waco District 15 days Mon 4/16/18 Fri 5/4/18 36 Bryan District (RDLR) 15 days Mon 4/16/18 Fri 5/4/18 53 Fort Worth District 20 days Mon 4/30/18 Fri 5/25/ % Draft Report Submittal 5 days Mon 5/28/18 Fri 6/1/ % Draft Report Review 5 days Mon 6/4/18 Fri 6/8/18 81 Wichita Falls District 20 days Mon 5/7/18 Fri 6/1/ Childress District 15 days Mon 5/7/18 Fri 5/25/ Pre-Final Report Submittal 3 days Mon 6/4/18 Wed 6/6/ Pre-Final Report Review 3 days Thu 6/7/18 Mon 6/11/ Final Report Submittal 2 days Tue 6/12/18 Wed 6/13/ Closeout and Final Invoice 12 days Thu 6/14/18 Fri 6/29/ Termination of Work Authorization and TxDOT Coordination with CIV 1 day Tue 7/31/18 Tue 7/31/ January February March April May June July A B M E B M E B M E B M E B M E B M E B M E B 79 days? WA Executed Stat WA Executed Team Mobilization 4/13 Notice To Proceed 10 days 4/16 Brownwood District 15 days 4/16 Waco District 15 days 4/16 Bryan District (RDLR) 20 days 4/30 Fort Worth District 5 days 5/28 60% Draft Report Submittal 5 days 6/4 60% Draft Report Review 20 days 5/7 Wichita Falls District 15 days 5/7 Childress District 3 days 6/4 Pre-Final Report Submittal 3 days 6/7 Pre-Final Report Review 2 days 6/12 Final Report Submittal 12 days 6/14 Closeout and Final Inv Termination of Work Authorization and TxDOT Coordination with CIV 7/31 Task Rolled Up Progress Inactive Task Duration-only External Tasks Items in Blue - LAN Field Work Items in Green - Client Review / Meetings Items in Red - Critical Milestone Dates Milestone Summary Rolled Up Task Split External Tasks Project Summary Inactive Milestone Inactive Milestone Inactive Summary Manual Summary Rollup Manual Summary Start-only External Milestone Progress Deadline Rolled Up Milestone Group By Summary Manual Task Finish-only LAN Facilities Architectural-Architectural_WA_ID Page 1 of 1 Exhibit C

36 DocuSign Envelope ID: CC C6B-4C98-B6FD-342C6B12168D 0C0B25DB BD34-B F655 Contract No. 38-7IDP8075 Work Authorization No. 5 ID Task Name Duration Start Finish Predecessors Resource Names 1 Statewide ADA Facility Accessibility Assessment 64 days WA Executed Tue 7/31/18 2 Notice To Proceed 1 day WA Executed WA Executed 3 Team Mobilization 1 day Fri 5/4/18 Fri 5/4/ Amarillo District 20 days Mon 5/7/18 Fri 6/1/18 30 Lubbock District 25 days Mon 5/7/18 Fri 6/8/18 57 Abilene District 20 days Mon 5/14/18 Fri 6/8/18 81 San Angelo District 14 days Mon 6/4/18 Thu 6/21/ % Draft Report Submittal 5 days Fri 6/22/18 Thu 6/28/ % Draft Report Review 5 days Fri 6/29/18 Thu 7/5/ Odessa District 15 days Mon 6/11/18 Fri 6/29/ El Paso District 19 days Mon 6/11/18 Thu 7/5/ Pre-Final Report Submittal 3 days Fri 7/6/18 Tue 7/10/ Pre-Final Report Review 3 days Wed 7/11/18 Fri 7/13/ Final Report Submittal 2 days Mon 7/16/18 Tue 7/17/ Closeout and Final Invoice 10 days Wed 7/18/18 Tue 7/31/ Termination of Work Authorization and TxDOT Coordination with CIV 1 day Tue 7/31/18 Tue 7/31/18 Statewide Facilities ADA Accessibility Assessment PS Contract No PS PO No March April May June July B M E B M E B M E B M E B M E B 64 days? WA Executed Statew WA Executed Team Mobilization 5/4 Notice To Proceed 20 days 6/1 Amarillo District 25 days 5/7 Lubbock District 20 days 5/14 Abilene District 14 days 6/4 San Angelo District 5 days 6/22 60% Draft Report Submittal 5 days 6/29 60% Draft Report Review 15 days 6/11 Odessa District 19 days 6/11 El Paso District 3 days 7/6 Pre-Final Report Subm 3 days 7/11 Pre-Final Report Rev 2 days 7/16 Final Report Subm 7/31 Closeo Termination of Work Authorization and TxDOT Coordination with CIV 7/31 Task Rolled Up Progress Inactive Task Duration-only External Tasks Items in Blue - LAN Field Work Items in Green - Client Review / Meetings Items in Red - Critical Milestone Dates Milestone Summary Rolled Up Task Split External Tasks Project Summary Inactive Milestone Inactive Milestone Inactive Summary Manual Summary Rollup Manual Summary Start-only External Milestone Progress Deadline Rolled Up Milestone Group By Summary Manual Task Finish-only Architectural_Architectural_WA_ID Page 1 of 1 Exhibit C

37 Attachment C Interactive Geographic Information System (GIS)

38 Attachment D - Program Accessibility Self-Evaluation Analysis Introduction The Texas Department of Transportation (TxDOT) has a long history of being committed to providing for the safety, reliability and accessibility of the public the agency serves. The people of Texas have come to expect the best highway system in the United States from the agency and should be able to now expect the best transportation system for all of our citizens. TxDOT is proud to be a part of changes and progress that can unite, serve and further the safe and efficient movement of goods, services and people that ensure everyone is included. The Department is responsible for the operation and management of more than 195,000 lane miles of roadways on the State Highway System. This responsibility includes more than 53,000 bridges, miles of interstate, an estimated 26,000 miles of sidewalks and other pedestrian facilities and more than 2500 Department-owned buildings across the State. The American with Disabilities Act (ADA) is a civil rights law that mandates an equal opportunity for individuals with disabilities. The ADA prohibits accessibility discrimination to jobs, public accomodations, government services, public transportation, and telecommunications. The Texas Department of Transportation (TxDOT) is required to conduct a comprehensive re-evaluation of its policies, programs, and facilities to determine the extent to which individuals with disabilities may be restricted in their access to services and activities. Access to civic life by people with disabilities is a fundamental goal of the Americans with Americans with Disabilities Act (ADA). To ensure that this goal is met, Title II of the ADA requires state and local governments to make their programs and services accessible to persons with disabilities (28 CFR ). This requirement extends not only to physical access at government facilities, programs, and events, but also to pedestrian facilities in public rights-of-way. The Texas Department of Transportation developed an ADA Transition Plan in 2004 as required by law, and is currently in the process of updating that document. The Texas Department of Transportation is obligated to observe all requirements of Title I employment practices; Title II in its policies, programs, and services; parts of Title IV that apply to TxDot's programs, services, or facilities; and all requirements specified in the Acessibility Guidelines (ADAAG) that apply to facilities and other physical holdings. Title II has the broadest impact on the State. Included in Title II are administrative requirements for all government entities employing more than 50 people. These administrative requirements include completion of a self-evaluation; development of an ADA complaint procedure; designation of a person who is responsible for overseeing Title II compliance; and development of a transition plan if the self-evaluation identifies any structural modifications necessary for compliance. The transition plan must be updated every three to four years and maintained as an official record until superseded by a revised plan. Pursuant to the Rehabilitation Act of 1973, Section 504, no otherwise individual in the United States, as defined in section 705 (20) of this title, shall, solely be of his or her disability, be excluded from the participation in, be denied the benefits of, or be 1

39 subjected to discrimination under any program or activity receiving Federal financial assistance or under any program or activity conducted by an Executive agency or by the United States Postal Service. For the purposes of this section, the term "program or activity" means all of the operations (1)(a) a department, agency, special purpose district, or other instrumentality of a State or local government; or (2) the entity of such State or local government that distributes such assistance and such department or agency (and each other State or local government entity) to which assistance is extended, in the case of assistance to a State or local government. Policies & Practices Standards Title II prohibits all public entities, regardless of size of workforce, from discriminating in their employment practices against qualified individuals with disabilities. All public entities must ensure that their employment practices and policies do not discriminate on the basis of disability against qualified individuals in every aspect of employment, including recruitment, hiring, promotion, demotion, layoff, return from layoff, compensation, job assignments, job classifications, paid or unpaid leave, fringe benefits, training, and employer-sponsored activities, including recreational or social programs. No covered entity shall discriminate against a qualified individual on the basis of disability in regard to job application procedures, the hiring, advancement, or discharge of employees, employee compensation, job training, and other terms, conditions, and privileges of employment. TxDOT Standards will not discriminate against qualified individuals with disabilities on the basis of disability in its services, programs or activities. Persons with disabilities, in accordance with federal and state law may request reasonable accommodation throughout the hiring and selection process. Directors, managers, supervisors and employees are prohibited from taking retaliatory action against any person making allegations of violations. Information & Staff Training TxDOT established an ADA Training Program describing the requirements for ADA and its responsibility under it. The training program covers in detail, courses and topics that address the ADA Regulations and Standards; how they impact Department operations; the scoping of technical requirements of the ADA Standards for Accessible Design (ADAS); the Standards for Transportation Facilities (ADASTF); and the proposed Public Rights of Ways Accessibility Guidelines (PROWAG), including examples of compliant and non-compliant facilities. Specifically, DES a six hour course, was developed to provide an update on accessible facility design with a focus on compliance with the Americans with Disabilities Act (ADA) and the Texas Accessibility Standards (TAS). The training was created to provide information and best practices for 2

40 those involved in the design, construction, and maintenance of pedestrian facilities and for those individuals who ensure compliance with applicable Federal and State laws. Multiple divisions currently provide ADA training to Subrecipients regarding assurances and obligations required in their contractual agreements with TxDOT. Additional training is being developed to provide training that covers the ADA Subrecipients Compliance and Monitoring Program which includes training to assist with transition plans and more. Use of Contractors A public entity may not discriminate on the basis of disability in contracting for the purchase of goods and services. The Department prohibits discrimination against any person because of race, color religion, sex, national origin, genetic information, citizenship or immigration status, disability, military status, or age. This applies to contractors employment decisions as well as conduct. Transportation Under the ADA, the Department of Transportation (DOT) issues and enforces accessibility standards for transportation. These requirements apply to new or remanufactured vehicles covered by the ADA, including: buses and vans, rail cars, automated guideway vehicles, trams and similar vehicles. All vehicles shall provide a level-change mechanism or boarding device. The Americans with Disabilities Act (ADA) applies to both public and private ground transportation. The ADA rules that apply to transportation are regulated by the U.S. Department of Transportation. Both public and private organizations must meet ADA requirements. A public transportation system must provide adequate information on services in accessible formats for persons with different types of disabilities. Equipment and facilities such as lifts, ramps, securement devices signage, and communication devices must be in good operating condition. If a feature is out of order, it must be repaired promptly. In the interim, an alternative accessible vehicle or option must be available. Public transit operators must allow adequate time for people with disabilities to board and exit from vehicles. Service animals may accompany people with disabilities in vehicles and facilities. The DOT ADA regulations define a service animal as any guide dog, signal dog; and other animal individually trained to provide assistance to an individual with a disability, regardless of whether the animal has been licensed or certified by a state or local government. Fixed-route systems must have signs designating seating for passengers with disabilities. At least one set of forward-facing seats must be marked as priority (for people with disabilities). Each public and private transportation operator must ensure that personnel are trained to operate vehicles and equipment safely; properly assist individuals with disabilities in a respectful, courteous way; and recognize that individuals with disabilities have different abilities and needs requiring different types of assistance. 3

41 Telephone Communication Public entities that communicate by telephone must provide equally effective communication to individuals with disabilities, including hearing and speech impairments. If telephone relay services are available, these services generally may be used to meet this requirement. Auxiliary aids and services include a wide range of services and devices that promote effective communication. Examples of auxiliary aids and services for individuals who are deaf or hard of hearing include telephone handset amplifiers, assistive listening systems, telephones compatible with hearing aids, closed caption decoders, open and closed captioning, and telecommunications devices for deaf persons (TDDs). TxDOT will generally apply appropriate aids and services leading to effective communication for qualified persons with disabilities so they can participate equally in TxDOT s programs, services, & activities, including qualified sign language interpreters, documents in Braille and other ways of making information and communications accessible to people who have speech, hearing or vision impairments. Documentation & Publications A public entity must ensure that its communications with individuals with disabilities are as effective as communications with others. This obligation, however, does not require a public entity to take any action that it can demonstrate would result in a fundamental alteration in the nature of its services, programs, or activities, or in undue financial and administrative burdens. In order to provide equal access, a public accommodation is required to make available appropriate auxiliary aids and services where necessary to ensure effective communication. Web pages and electronic documents should be designed to be accessible to people with disabilities. Pages should conform to Section 508 and Web Content Accessibility Guidelines. The Communications and Information Management Divisions can provide information regarding accessibility design, and accessibility reviews of TxDOT s websites. Meetings A public entity may not deny the benefits of its programs, activities, and services to individuals with disabilities because its facilities are inaccessible. A public entity s services, programs, or activities, when viewed in their entirety, must be readily accessible to and usable by individuals with disabilities. This standard, known as program accessibility, applies to all existing facilities of a public entity. Public entities may achieve program accessibility by a number of methods. In many situations, the entity may provide access to facilities through structural methods, such as alteration of existing facilities through structural methods. The public entity may also pursue alternatives to structural changes in order to achieve program accessibility. TxDOT ensures its programs will be conducted, and its facilities operated, in compliance with all nondiscriminatory practices and requirements imposed. TxDOT will make all reasonable modifications to policies & programs to ensure that people with disabilities have an equal opportunity to enjoy all of its programs, services, & activities. Anyone who requires auxiliary aids or services for effective 4

42 communication should request it as soon as possible but no later than 48 hours before the scheduled event. TxDOT will not place a fee on a particular individual s disability to cover the cost of provding auxiliary aids and services. Three components are key to presenting meetings that are accessible to people with disabilities: where the meeting is held, how the meeting room furniture is arranged, and how the meeting information is communicated. Divisions, Districts and other offices within the Texas Department of Transportation (TxDOT) should take steps in order to assure fair and equal access to TxDOT s facilities, services, programs and activities when hosting public meetings or events. Audio Visual Presentations An accessible meeting presentation ensures that all participants have equal access to the meeting s content. Guidelines for Accessible Materials during presentations should be followed. Auxiliary aids and services bridge communication between people who are deaf or have hearing loss and people who are hearing so that each can understand the other. Auxiliary aids for individuals with vision impairments included qualified readers, taped texts, audio recordings, Brailled materials, large print materials, and assistance in locating items. The type of auxiliary aid or service necessary to ensure effective communication will vary in accordance with the length and complexity of the communication involved. Automated Electronic Equipment ADAAG requires that areas used only by employees as work areas be designed and constructed so that individuals with disabilities can approach, enter, and exit the areas. For a parallel approach, the proper reach is up to 54 inches above the floor. Emergency Evacuation Areas of rescue assistance (safe areas in which to await help in an emergency are generally required on each floor, other than the ground floor, of a multistory building. An accessible egress route or an area of rescue assistance is required for each exit required by the local fire code. Specific requirements are provided for such features as location, size, stairway, width, and two-way communication. If emergency systems are provided, they should have both flashing lights and audible signals. Evacuation procedures, including procedures for persons with disabilities, should be posted and individuals should be on hand to provide appropriate assistance when needed. Notification A public entity must provide information on the requirements of Title II of the Americans with Disabilities Act to applicants, participants, beneficiaries, and other interested persons. The notice shall explain the requirements to applicants, participants, beneficiaries, and other interested persons. The notice shall explain the applicability to the public entity s services, programs, or 5

43 activities. A public entity shall provide such information as the head of the public entity determines to be necessary, to apprise individuals of the prohibition against discrimination. If an individual files an administrative complaint, the appropriate federal agency can and will investigate the allegations of discrimination. A public entity that employs more than 50 or more persons shall designate at least one employee to coordinate its efforts to comply with and fulfill its responsibilities under Title II of the Americans with Disabilities Act, including the investigation of complaints. In addition, the public entity must adopt and publish grievance procedures providing for prompt and equitable resolution of complaints alleging any action that would be prohibited by Title II. An accommodation statement must be included in publications (flyers, newsletters, s, websites, etc.) inviting participation in TxDOTsponsored events. Publicity for events should notify potential attendees how to request information or request accommodations. Service Animals Under the ADA, State and local governments, businesses, and nonprofit organizations that serve the public generally must allow service animals to accompany people with disabilities in all areas of the facility where the public is normally allowed to go. Under the ADA, service animals must be harnessed, leashed, or tethered, unless these devices interfere with the service animal s work or the individual s disability prevents using these devices. In that case, the individual must maintain control of the animal through voice, signal, or other effective controls. Service animals must be permitted in all areas except in unusual circumstances. There must be a designated area identified for service animals to relieve themselves. Individuals with service animals are welcomed in TxDOT offices, even where pets are generally prohibited. 6

44 Policies & Procedures Staff Training Use of Contractors Transportation Phone Communication Documentation & Publications Meetings Audio-Visual Presentations Electronic Equipment ADA Self Evaluation Program District Data (At A Glance) Section District Titles PAR FTW WFS AMA LBB ODA SJT ABL WAC TYL LFK HOU YKM AUS SAT CRP BRY DAL ATL BMT PHR LRD BWD ELP CHS C C C C C C C C C C C C C C C C C C C C C C C C C 2.3 C NA NA C C NA NA NA C C NA NA C C C NA C NA C NA C C NA C NA 2.4 C NA NA NA C NA NA NA C NA NA NA C C C NA C NA NA C C C NA C NA 3.1 C C C C C C C C C C C C C C C C C C C C C C C C C 3.2 C C C C C C C C C C C C C C C C C C C C C C C C C 4.1 C C NA C C NA NA NA C NA NA C C C C C C C C C C C NA C NA 4.2 C C NA C C NA NA NA C NA NA NA C C C C C C C C C C NA C NA 4.3 C C NA C C NA NA NA C NA NA NA C C C C C C C C C C NA C NA 5.1 NA NA NA NA C NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA 5.2 NA NA NA NA C NA NA NA NA NA NA C NA NA NA NA NA NA NA NA NA NA NA NA NA 6.1 NA C C C C C C C C C C C NC C C NC C C C C C C C C C NA C C NA C C C C NA NA NA NA NA C C NA NA C NA NA NA C C NA NA NA C NA NA C NA NA NA NA NA NA NA NA C C NA NA NA NA NA NA C NA NA NA NA C NA NA NA NA NA NA NA NA NA NA NA NA C NA NA NA NA NA NA C NA NA NA 6.2 NC C C NA C NC NC NC C NA C NA NA C C NC C NC NA NC NC NC NC NA NC 7.1 NA C C C C C C C C C C C NA C C C C C C C C C C C C 7.2 NC C C C C C C C C C C C NC C C NC C C NC C C C C C C 7.3 NC NC NC NC NC NC NC NC NC NC NC C NC NC C NC NC NC NC NC NC C NC NC NC 8.1 C C C C C C C C C C C C C C C C C C C C C C C C C 8.2 C C C C C C C C C C C C NA C C C C C NA C C C C C NA 8.3 C C C C C NA C C C C C C NA C C C C C NA C C C C C NA 9.1 NA NA NA NA NA NA NA NA NA NA NA C NA C NA NA NA NA NA C C NA NA NA NA 9.2 NC NC NC NC NC NC NC NC NC NC NC C NC C NC NC C NC NA NC C NC NC NC NC 10.1 NA C NA C NA NA NA NA C NA NA C C NA C C C NA NA C NA C NA NA NA 10.2 NA C NA C C C NA C C NA C C C C C C C NA NA C C C NA C NA Evacuation 11.1 C C C C C C C C C C C C C C C NC C C NA C C C C C C 12.1 C C C C C C C C C C C C C C C C C C C C C C C C C Notification 12.2 C C C C C C C C C C C C C C C C C C C C C C C C C 12.3 C C C C C C C C C C C C C C C NC C C C C C C C C C 12.4 C C C C C C C C C C NC C NC C C NC C C C C C C C C C 13.1 C C C C C C C C C C C C C C C C C C C C C C C C C Service Animals 13.2 NC C C C C NC C NC C C C NC C C C NC NC NC NC C C C NC C NC Legend: Compliant = C; Non-Compliant = NC; Non-Applicable= N/A; The highlighted rows are in need of the most attention.

45 Policies & Procedures Staff Training Use of Contractors Transportation Phone Communication Documentation & Publications Meetings Audio-Visual Presentations Electronic Equipment Section 2.1 ADA Self Evaluation Program Division Data (At A Glance) Division Titles AUD AVN BRG CIV CMD CMP CST CSD DES ENV FIN FOD HR IMD MNT MRD OCC PRO PEPS PTN Rail ROW RTI SSD Toll TRF TPP TRV 2.2 C C C C C C C C C C C C C C C C C C C C C C C C 2.3 C NA C NA NA C C C NA NA NA C NA NA NA NA NA NA NA NA NA C NA NA NA 2.4 C NA NA NA NA C C C NA NA NA C NA NA NA NA NA NA NA NA NA C NA NA C 3.1 C C C C C C C C C C C C NC C C C NA C C C C C NA C 3.2 C C C C C C NC C C C C C NC C C C NA C C C C C NA C 4.1 NA C C C C NA C C C C C C NA C C C NA C NA C C C C C C 4.2 NA C C C NA C C C C C C C NA NA NA C NA C NA C C C C C C 4.3 NA C NA C NA NA NA C C C C C NA NA NA C NA C NA C C C C NA C 5.1 NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA C NA NA NA 5.2 NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA C NA NA NA 6.1 C C C C C C NA C C C C NA C NA C C C C C C C C C C NA NA NA NA C NA NA NA C NA NA NA C NA NA NA NA NA NA NA C C C NA NA NA NA NA NA C NA NA NA C NA NA NA C NA NA NA NA NA NA NA NC C C NA NA NA NA NA NA C NA NA NA C NA A NA C NA NA NA NA NA NA NA C NA C NA NA NA 6.2 NA NA NC NC NA NC NA C NC NA NC NA C NC NC NC NC NA NA C C C NC NA NA 7.1 NA C C C C NA C C C C C C C NA C C NA C C C C C C C C 7.2 C C C C C NC C C NC C NA C C C C C C C NC NA C C C NA NC 7.3 C NC NA C NC NC NC C NC NC NA NC NC NC NC NC NC NC NC NC NC C NC NC NC 8.1 C C C C NA C C C C NA NA C C C C C C C C C C C C C C 8.2 NC C C C NA NC C C C NA NA C C C C NA C NA C C C C C C C 8.3 NC C C C NA NC C C C NA NA C C C C NA C NA C C C C NA C C 9.1 NA NA NA C NA C C C C NA NA NA NA C NA NA C NA NA NA NA C NA NA NA 9.2 NA NC NC C NC C C C NC NC NA C NA NC NC NC NC NA NC NC NC C NA NA NC 10.1 C C C C C C C C C C C NA NA C NA C C NA C C C C NA NA C 10.2 C C C C C C C C C C C NA NA C NA C C NA C C C C NA NA C Evacuation 11.1 C C C C C C C C C C C C C C C C C NA C C C C C NA C Notification 12.1 NA C C C C NA C C C C C C C C C C C C C C C C C C C 12.2 C C C C NA C C C C C NC C C C C C C C C C C C C NA C 12.3 C C C C NA C C C C C C C C C C C C C C C C C C NA NA 12.4 NA C C C NC NC C C C C C C C C C C C C C C C C C NC C 13.1 C C C C C C C C C C C C C C C C C C C C C C C NA C Service Animals 13.2 NC C C C NC NC C C C C C NC C C C NC NC C C NC C C C NA C Legend: Compliant = C; Non-Compliant = NC; Non-Applicable= N/A; The highlighted rows are in need of the most attention.

46 Observations Districts Policies and Practices - Compliant in the applicable areas and non-applicable in other areas. Information/Staff Training A few districts only have the ADA liason or upper management informed about obligations and policies that enable persons with disabilities to participate in TxDOT s programs or activities. Use of Contractors Compliant in the applicable areas and non-applicable in other areas. Transportation - Compliant in the applicable areas and non-applicable in other areas. Phone Communication - Across section 6, there seems to be a lack of knowledge or resources with regards to phone communication. Some districts have stressed that they need training in particular with 6.2. Thorough training should be given for effective communication because there is a high amount of non-compliance in this area. Documentation and Publications (7.2) Stress documents should be simple to understand for people with disabilities or provide training. (7.3) Provide training on how and when to portray individuals in documents. The majority of districts are non-compliant in displaying individuals with disabilities in their documents and publications. Meetings - Compliant in the applicable areas and non-applicable in other areas. Audio-Visual Presentations (9.2) Provide training on how and when to portray individuals in audiovisual presentations. The majority of districts are non-compliant in this area. Automated Electronic Equipment - Compliant in the applicable areas and non-applicable in other areas. Emergency Evacuation - Compliant in the applicable areas and non-applicable in others areas. Notification (12.4) Provide training on how to file a disability discrimination complaints. All other areas associated with this section can be improved through districts providing the accommodation statement throughout the building and on websites. Service Animals (13.2) Provide training on designated areas to relieve themselves. Divisions Policies and Practices Compliant in the applicable areas and non-applicable in other areas. Information/Staff Training - A few districts only have the ADA liason or upper management trained or obligations and policies that enable persons with disabilities to participate in TxDOT s programs or activities. 9

47 Use of Contractors - Compliant in the applicable areas and non-applicable in other areas. Transportation - Compliant in the applicable areas and non-applicable in other areas. Phone Communication - Across section 6, there seems to be a lack of knowledge or resources with regards to phone communication. Some districts have stressed that they need training in particular with 6.2. Thorough training should be given for effective communication because there is a high amount of non-compliance in this area. Documentation and Publications - (7.2) Stress documents should be simple to understand for people with disabilities or provide training. (7.3) Provide training on how and when to portray individuals in documents. The majority of districts are non-compliant in displaying individuals with disabilities in their documents and publications. Meetings - Compliant in the applicable areas and non-applicable in other areas. Audio-Visual Presentations - (9.2) Provide training on how and when to portray individuals in audiovisual presentations. The majority of districts are non-compliant in this area. Automated Electronic Equipment - Compliant in the applicable areas and non-applicable in other areas. Emergency Evacuation - Compliant in the applicable areas and non-applicable in other areas. Notification - (12.4) Provide training on how to file a disability discrimination complaints. All other areas associated with this section can be improved through districts providing the accommodation statement throughout the building and on websites. Service Animals - (13.2) Provide training on designated areas to relieve themselves. Recommendations Policies & Practices - No recommendations Information/Staff Training All Division and District staff should be trained on the obligations and policies under the Americans with Disabilities act that enable persons with disabilities to participate in TxDOT s programs or activities. Use of Contractors No recommendations Transportation No recommendations Phone Communications Divisions and Districts need training on effective communication using TDDs. Documentations & Publications Divisions and Districts need training on how and when to portray individuals with disabilities in their materials. Meetings No recommendations 10

48 Audio-Visual Presentations Divisions and Districts need training on how and when to portray individuals with disabilities in their presentations. Automated Electronic Equipment No recommendations Emergency Evacuation No recommendations Notification Divisions and Districts need training on the utility of the accommodation statement throughout their facilities and materials. Service Animals Divisions and Districts need training on the designated areas for service animals to relieve themselves. 11

49 Attachment E - Public Involvement Newsletters

50 CONNECTING OUR COMMUNITIES Director s Corner SUMMER 2018 Director s Corner... 1 TxDOT Project Pages... 1 I-10 at Exit PI Spotlight: Bryan... 2 Quote of the Quarter... 3 MetroQuest Webinar... 3 Online Engagement... 3 Upcoming Events... 3 Engagement Webinar... 3 PI Quick Hits... 4 Staff Contacts... 4 TxDOT s Public Involvement Policy: The Texas Department of Transportation (TxDOT) commits to purposefully involve the public in planning and project implementation by providing for early, continuous, transparent and effective access to information and decision-making processes. TxDOT will regularly update public involvement methods to include best practices in public involvement and incorporate a range of strategies to encourage broad participation reflective of the needs of the state s population. As adopted by the Texas Transportation Commission on January 27, Previous issues here! Just when we think things cannot get any busier here comes the summer construction season. Please keep in mind that outreach to the public during construction is absolutely critical to effective and successful implementation of our projects. Not only do we owe it to the public to ensure that they are aware of closures and lane changes, but we should recognize that the needs of stakeholders may require that we be creative in how we address their concerns. Establishing an open two-way dialogue with our customers prior to initiating construction is the key; and we here in PI can help. Several questions have recently arisen regarding the use of court reporters. Keep in mind that a court reporter is not required for an open house or a public meeting but can be procured to record comments if you wish. However, for a public hearing a professional court reporter must prepare and certify the hearing transcript. Occasionally, a court reporter will fail to attend a hearing for any number of reasons. Agency procedures allow for the recording of the hearing and then the later transcription of the hearing by a court reporter. If the hearing is to be recorded, then we should undertake a variety of methods to ensure the completeness of the recording such as having multiple recordings of the hearing. Finally, I wish to give kudos to the Procurement Division for their hard work on establishing Blanket Purchase Orders (BPOs) governing the procurement of translation and transcription services. Please know that we here in PI can continue to serve as the conduit for obtaining these services for you. However, do know that the BPOs are set up so that any division or district may use them to procure these services. Thank you all for working to establish a culture where we make decisions that are both transparent and consider the value of public input. Website Project Pages Can be Effective Communication Tool Project pages on the txdot.gov site are a dynamic way of presenting robust, deep information about a project to create an informed public. With 24/7 availability, the online pages address a key component of TxDOT s Public Involvement Policy: providing for early, continuous, transparent and effective access to information and decisionmaking processes. Districts/Divisions effectively link project pages and public meetings pages as they build a community of information for the public to access regarding a project. The project page is also a consistent host, where through various outreach methods, such as flyers and business cards with a QR code, and social media, as well as traditional media we can direct the public to access the information on a project all in one place. Districts/Divisions are using the project page venue for corridor studies, planning and environmental linkage (PEL) studies and construction updates, to name a few. The number of project pages on txdot.gov has more than doubled during the past two years as districts and divisions are realizing what an accessible and effective communications tool it can be.

51 San Angelo District - I-10 at Exit 365 At the May public hearing for the I-10 frontage road extension in Ozona, two people spoke on the record, both in favor of the project. This support is in contrast to a public meeting just two months prior, which drew 60 people, many in opposition to the project. Much of the project support can be attributed to diligence on the part of the San Angelo District, working in partnership with Crocket County officials, in informing and engaging the community. At the March public meeting, the proposed project was introduced by the Crockett County Judge. As a key stakeholder and ambassador for the project, the judge was able to articulate and validate the community s concerns. He then communicated the steps that TxDOT and Crockett County went through with local, regional and state officials to address these concerns. The project was presented as a plan that balances the need for access to the community west of Johnson Draw with improved and safe access to Ozona/ SH 163 in a manner that conforms with current TxDOT design standards and practices regarding interstate facilities. Safer exit and entry during flood conditions for the community south of I-10 and west of Johnson Draw was a top project goal, along with increasing the safety of I-10 eastbound exiting traffic. San Angelo District Engineer Mark Jones, and John DeWitt, Director of Transportation Planning and Development, along with the Crockett County judge and one of the Crockett County commissioners, answered questions and addressed concerns during the public meeting, reinforcing the environment established by the district that TxDOT was present to listen. DeWitt described to the community the unique approach of TxDOT funding and constructing a frontage road extension in exchange for Crockett County accepting operation and maintenance of RM/FM mileage representative of the anticipated construction cost. Extension of the existing frontage road would necessitate its conversion to one way. We have been working on this iteration of the project for four years, and we want to make sure we re getting it right, DeWitt told the community during the public meeting. Community members expressed concerns about the one-way frontage road conversion, and TxDOT staff and Crockett County officials answered the questions and noted the concerns. TxDOT continued to partner with Crockett County in answering questions and addressing concerns from the community, committing to mitigate construction impacts. A month following the meeting, Crockett County commissioners signed a resolution supporting the project. At the public hearing, four people signed in, three signed up to speak and two spoke in favor of the project (one person left before it was time to speak). We would like to thank TxDOT and the commissioners court, said Shannon Biggerstaff, president of the Ozona Chamber of Commerce. I am proud to see our community and TxDOT work together. The issue of flooding has been a concern for a long time. There are more positives than negatives in this project. PI Spotlight - Bryan District The Bryan District hosted the 2018 Active Transportation and Americans with Disabilities Act (ADA) Outreach public hearing event this spring for approximately 50 people. The purpose was to discuss the planning and development of Active Transportation facilities in the TxDOT Bryan District and to gather input. The public hearing kicked off with a creative open house stations format, which allowed the public to visit with representatives not only from the TxDOT Bryan District, but also from the Bryan/College Station Metropolitan Planning Organization, Texas A&M University, the City of College Station, the City of Bryan, and Texas A&M Transportation Services. An Engage Station also provided laptops for the public to take an online Active Transportation survey. The survey asked the public to rank bicycle and pedestrian mobility priorities and mark key locations of travel and issues on an interactive online map. Kudos to the district for their creativity and for gaining more than 100 survey responses! 2

52 Quote of the Quarter People need to be informed before they can get involved. Ma Jun, Environmentalist Online Engagement Spotlights The Reimagine I-10 project in the El Paso District is conducting an advanced planning study for the I-10 Corridor from the New Mexico/Texas state line to Tornillo. The online engagement tool in both English and Spanish was created for the second series of public meetings, seeking public input on priorities for the corridor, such as design, value and mobility, and circulation. Data results for online engagement for the FM 1281 (Horizon Boulevard) Corridor Study in the El Paso District are being presented in a TxDOT branded report format that highlights the public s priorities safety, reliable mobility and state of good repair as well as the overall vision for the corridor. The data report will be included in the overall public involvement summary for the project. TxDOT Leads Discussion on Online Engagement In April, the Public Involvement (PI) Section led a webinar titled How TxDOT Engages Beyond Meetings to an audience of transportation, public involvement and communications professionals from around the world. The webinar was hosted by MetroQuest and sponsored by the American Planning Association, International Association for Public Participation, National Coalition for Dialogue and Deliberation, and the American Association of State Highway and Transportation Officials. The PI Section staff shared the importance of TxDOT s Public Involvement Policy and how online engagement through the use of MetroQuest provides innovative ways to reach the state s population. Going beyond a public meeting with the use of MetroQuest proves to be accessible, engaging and outcome-oriented. In using examples from around the state, participants were able to see how TxDOT tailored multiple online surveys for specific projects and studies. There was emphasis on the fact that there is no project too large or too small. If TxDOT can reach someone that would not normally attend or comment at a public meeting, open house or public hearing the survey was worthwhile. Upcoming Events *2018 Transportation Planning Conference in Dallas June 5-7, 2018 *UTP Public Meeting via WebEx July 12, 2018 *2018 Environmental Conference in Dallas Sept , 2018 *Effective Public Involvement training OPI 100 in Austin Oct. 2, 2018 & Oct. 9, 2018 Interested participants learned new ways to build a MetroQuest site, including separate translated surveys, creative ways to market the online survey, and insightful ways to use the data gathered from the survey. If you are interested in learning more about engaging the public beyond the meeting contact your Regional Analyst to learn more. You can also view the presentation here. 3

53 PI Quick Hits The Amarillo District partnered with the City of Dumas in hosting an open house to inform the public in advance of a paving project on US 87/US 287. Informational flyers were translated into Spanish and distributed. More than 50 people attended the meeting, where TxDOT staff assisted Dumas city staff in answering questions concerning project information and timelines. The Paris District hosted its first Open House for US 75 in Sherman. A Welcome video, stationed at the entrance, provided an overview of the project. The District also placed street name pop-up labels prominently along the schematics so citizens could easily identify their area of interest. More than 130 people attended this highly successful meeting. The Odessa District has developed a project page for the Delaware Basin, using this tool uniquely to keep the public informed. In addition to routine maintenance that is performed weekly on US 285, five projects costing about $100 million are planned during the next few years between Pecos and the New Mexico state line. The Lufkin District recently developed a Notice of Impending Construction postcard to alert local stakeholders about the upcoming widening project on FM 2609 in Nacogdoches County. The postcard highlighted construction details, timing, cost and website information to help alert the public about what to expect. PI in Action Members of the public gathered in the Brownwood District for a public hearing on FM 45. Staff Contacts Director: Jefferson Grimes Jefferson.Grimes@txdot.gov East Region: Julie Beaubien Julie.Beaubien@txdot.gov North Region: Susan Howard Susan.Howard@txdot.gov South Region: Amy Redmond Amy.Redmond@txdot.gov West Region: Julie Jerome Julie.Jerome@txdot.gov Special Projects: Annie Sikes Annie.Sikes@txdot.gov Special Projects: Alicia Taliaferro Alicia.Taliaferro@txdot.gov Mission of the Public Involvement Section: To foster a culture where TxDOT makes decisions that are transparent and that consider and value public input. 4

54 Attachment F - Grievance Tracking Log

55 Tracking Number GRV#-Date CIV Rec-Yr Alleged DIS/DIV Complainant Name Location of Grievance CIV Received Type (I, C, L) ADA Grievance Tracking Log Internal Action FHWA Action Referral Agency Contact Complainant (Y/N) & date Date DIS/DIV responded Submitted to FHWA FHWA (F or NF) Req'd Barrier Removal Comments GRV SAT James Lawson Fredericksburg Road Handled by FWHA GRV DAL Jonathan Thome City of Dallas Handled by FWHA GRV HOU Pearl Ivey SH 99 & I /13/2016 C N/A N 1/6/2017 1/26/2017 NF N/A No Barrier Found GRV SAT Gregory Fountain Pat Booker Rd. & Palisades SH 218 5/3/2017 C N/A 5/17/2017 5/6/2017 6/28/2017 NF Y Based on the investigation, the crosswalk, sidewalks, and/or curb ramp were not accessible to individuals with disabilities. A temporary solution has been provided and a more permanent corrective action will be made through the 208 Preventative Maintenance Program. GRV WAC Karen Kimberly Powell Clark Street, Bartlett, Texas 5/2/2017 C N/A 5/5/2017 6/13/2017 6/28/2017 NF N Spoke with Mr. Powell because the complainant passed away before resolution. Upon investigation, all of areas of concerned were reviewed and met the applicable standards for the year they were designed. GRV HOU Charles Moore Project No. NH207(160) Cypress Creek Parkway (NW Harris County) 10/10/2017 C N/A 10/11/ /26/2017 Not Required N/A N Notified FHWA of complaint on 10/13/17. Investigative Planning Conference held 10/18/17. Nontraditional complaint - waste of money. In response to public hearing - held 4/27/17 & 8/10/17; HOU - district curb ramp improvement plan; and thus compliant with FHWA's Curb Ramp Program. GRV DAL William B. Franz Main Street I-35 Lewisville, TX 11/13/2017 C N/A 11/13/ /20/2018 1/31/2018 NF N No Barrier Found GRV HOU Tameca Jones Houston, Texas 12/4/2017 C Inspector General 12/13/ /13/2017 N/A N/A N/A No Action Required GRV009 Not Assigned DOJ-FHWA-CTS# HOU Douglas Reilly City of West University Handled by FWHA No Action Required GRV HOU William B. Franz Texas SH 121 Business where it crosses under I-35E Lewisville, TX 4/18/2018 C N/A N 6/13/2018 6/14/2018 NF Yes TxDOT-DAL will take corrective action to resolve the issues by installing curb ramps, adding back pavement markers and installing a median cut. TxDOT-DAL will ensure that an accessible path to all push buttons on the signal poles will be provided. DAL & City of Lewisville will work together on signage. Will be in August 2019 TP under CSJ ; will let September 2020; and construction start date schedule January GRV FTW Kathleen Watson Arlington, Texas 4/27/2018 I DMV 5/3/2018 5/3/2018 Y N/A N/A No Action Required GRV DAL Marie Mitchell- Morgan West 352 between Jim Miller Rd and Buckner Blvd 5/1/2018 I Handled by DAL District Office At the direction of Mr. Bass, Dallas office instructed to respond to Ms. Mitchell-Morgan. DES recommended a change order be submitted for this project to add sidewalks. GRV FTW Nancy Jakowitsch Rosedale Construction Project 6/13/2018 I N/A 6/13/2018 Legend Dis - District; Div - Division; I - Inquiry; C- Complaint; L - Lawsuit; Y - Yes; N - No; F - Finding; NF - No Finding 6/26/ CIV Y N/A Scheduled 2- TxDOT-FTW South Tarrant Area office is currently working with the City of Fort Worth to take the necessary 3 wks from steps to ensure sidealk accessibility, bus stop accessibility and safety in accordance with the ADA located at the date construction site near the public housing facility. A plan is being implemented to provide access utilizing responded permanent asphalt for stability.

56 Attachment G - Web-based Accessibility

57 DocuSign Envelope ID: 882FC C-B0628DBC4EA4 Becky Bloom Project Charter Browser Agnostic & Portability Version /08/2018 Project Charter Implement Multi-browser Compatibility (Browser Agnostic) & Multi-device Portability RITM Version: 0.5 Revision Date: 01/08/2018 Approval of the Project Charter indicates an understanding of the purpose and content described in this deliverable. By signing this deliverable, each individual agrees work will be initiated on this project and necessary resources are committed as described herein. Approver Name Title Signature Date Michael Sledge - CMD Joshua Hunter Julien Devereux Cassie Jordan Director, Creative Services Branch Manager, Web Services Branch Manager, Editorial Services Project Sponsor/Strategy Director 1/19/2018 1/11/2018 1/12/2018 1/19/2018 Mark Evans Strategy Owner 1/19/2018 *By authorizing this Charter, the Project Sponsor agree to the scope and requirements. Any additional scope or requirements identified after final technical approval (ARB) will need to be handled by a separate project. Revision History Identify document changes. Version Date Name Description /11/2017 Becky Bloom Initial draft /31/2017 Becky Bloom Transferred to new template /14/2017 Becky Bloom Incorporated feedback from NTT Data /05/2017 Becky Bloom Updates incorporated from feedback of team /08/2018 Becky Bloom Updated with feedback from CMD

58 DocuSign Envelope ID: 882FC C-B0628DBC4EA4 Becky Bloom Project Charter Browser Agnostic & Portability Version /08/2018 Section 1. Overview 1.1 Problem Statement Define what the root cause of the problem is, what problem is created by the root cause and what effect this has on achieving business goals TxDOT web-based applications and web content that have been published by IT are currently not supported on multiple browsers and devices. There are inconsistencies between applications and corresponding browser compatibility. The user interfaces are also not supported across multiple devices. Currently no defined standards exist for multi-browser or multi-device compatibility. 1.2 Project Description Define the objectives of the project and determine finite ending points for each objective. Largescale efforts should be divided into more manageable pieces of scope (e.g. objectives that will be accomplished in less than a year s time). The goal of this project is to ensure all TxDOT web based applications and web content published by IT updated so that they are consistent across multiple browsers and devices. This effort will include developing standards to ensure consistency across browsers and devices. This will reduce the number of service desk calls leading to lower operational costs. TxDOT will have an increase in productivity due to a seamless transition between devices and browsers. External users that were unable to access TxDOT web applications/content due to having a different browser or device will then have access. 1.3 Project Scope The scope defines project limits and identifies the products and/or services delivered by the project. The scope establishes the boundaries of the project. The project scope definition should also describe products and/or services that are outside of the project scope. Project Includes Development of standards. Operationalize the standards into existing application lifecycle management process. Updating all TxDOT web applications and web content published by IT to adhere to the defined standards. Project Excludes Applications that are not web based. Applications/content that is scheduled to be decommissioned or non-operational before 08/31/2019. TxDOT social media site content. 1.4 Current State of Associated Business Processes Define the business process for the defined scope of the project As-Is, present state process prior to Implementing this project. This should include input that is representative of all identified stakeholders for all division and districts. Provide a brief explanation of the process at a summary high level. If necessary, add a visual diagram to the appendices.

59 DocuSign Envelope ID: 882FC C-B0628DBC4EA4 Becky Bloom Project Charter Browser Agnostic & Portability Version /08/2018 There are currently no defined standards or processes related to the maintenance of compatibility for web applications and content published by IT to multiple browsers and devices. 1.5 Product Features Describe the end product that will be delivered as the result of this project. Briefly describe what the product will look like. Product Feature TxDOT Standards Web based applications and content published by IT Description Defined process for keeping web based applications and content consistent between multiple browsers and devices. Web based applications and content published by IT will retain consistent functionality across multiple browsers and devices. 1.6 Project/Product Requirements Describe the product requirements that must be met to satisfy the business objectives. Populate the Customer Need/Technical Assumption, Requirement Description, and Priority columns of the Requirements Traceability Matrix in Appendix 5.1. See attachment in Section 5. Section 2. Assumptions, Constraints, Dependencies 2.1 Assumptions Describe the assumptions made in establishing this project s requirements, scope, timeline, and budget. The existing non-functional requirements will remain as is. No enhancements or improvements to individual applications will be made. 2.2 Constraints/Limitations Describe the constraints and/or limiting factors that can affect the project. 2.3 Dependencies Describe the dependencies that can affect the project. Include any dependencies on existing projects, work streams, and/or systems. This project is dependent on acquiring a valid list of web based applications and content that TxDOT IT supports. The list is included in the Appendix. We must determine which of the applications/sites are currently compatible and which are not. Other projects need to be evaluated to identify if any application upgrades are already in progress. If it is found that an application is being altered in another project, it will be evaluated to determine the best venue for completion. List of approved browsers and devices required by DIR. (Does not include all browsers and devices.)

60 DocuSign Envelope ID: 882FC C-B0628DBC4EA4 Becky Bloom Project Charter Browser Agnostic & Portability Version /08/2018 Section 3. Project Stakeholders 3.1 Stakeholder Identification and Roles Identify roles for the stakeholders. (Include Subject Matter Experts (SMEs) and Approvers in this list.) User or Stakeholder Cassie Jordan Michael Sledge Joshua Hunter Julien Devereux Mark Evans Project Role Project Sponsor/Strategy Director Director, Creative Services Business Owner Branch Manager, Web Services Business Owner Branch Manager, Editorial Services Business Owner Strategy Owner 3.2 Responsibility Chart Identify responsibilities for the stakeholders. (Include Business unit and IMD/ Vendors on this chart.) Task Business Unit IMD/Vendor Update the CMDB list of applications with most current X X information. Determine data to be collected that will assist in X determining project size Participate in User Acceptance Testing X Review standards and provide feedback X Participate in the design throughout the project X X Section 4. Glossary Define all terms and acronyms required to interpret the Project Charter. Acronym or Term CMDB Definition Configuration Management Database Section 5. Appendices 5.1 Requirements Document Requirements - Browser Agnostic & Po

61 DocuSign Envelope ID: 882FC C-B0628DBC4EA4 Becky Bloom Project Charter Browser Agnostic & Portability Version /08/ Project Economics 5. 3 As-Is Process Visual (if needed) 5. 4 Supported Application List Supported Web Applications.xlsx

62 DocuSign Envelope ID: 882FC C-B0628DBC4EA4 IMD Project Charter RITM User Experience Version /14/2017 Project Charter User Experience Version: 0.4 Revision Date: 12/14/2017 Approval of the Project Charter indicates an understanding of the purpose and content described in this deliverable. By signing this deliverable, each individual agrees work will be initiated on this project and necessary resources are committed as described herein. Approver Name Title Signature Date Michael Sledge Communications Division Creative Services Director 1/19/2018 Cassie Jordan Project Sponsor/ IMD - Strategy Director 1/19/2018 Mark Evans IMD - Business Relationship Manager 1/19/2018 Joshua Hunter Julien Devereux Branch Manager Web Services Branch Manager Editorial Services *By authorizing this Charter, the Project Sponsor agree to the scope and requirements. Any additional scope or requirements identified after final technical approval (ARB) will need to be handled by a separate project. Revision History Identify document changes. Version Date Name Description /24/2017 Rikki Degelia Initial draft /31/2017 Rikki Degelia Transferred to new template /12/2017 Rikki Degelia Incorporate review comments /27/2017 Rikki Degelia Review comments from CMD and CIV incorporated 1/11/2018 1/12/2018 Section 1. Overview 1.1 Problem Statement Define what the root cause of the problem is, what problem is created by the root cause and what effect this has on achieving business goals 1

63 DocuSign Envelope ID: 882FC C-B0628DBC4EA4 IMD Project Charter RITM User Experience Version /14/2017 The current applications have differing page layouts and formats which cause potential confusion from a user experience perspective. The current applications lack TxDOT branding consistency, resulting in continued operational effort to train and/or answer questions related to the use of various applications. The websites lack accessibility compliance with TAC 206, TAC 213 and sections 504 and 508 of the Rehabilitation Act of 1973 which prevents some users from fully utilizing TxDOT resources and information provided. This item primarily impacts disabled users. 1.2 Project Description Define the objectives of the project and determine finite ending points for each objective. Largescale efforts should be divided into more manageable pieces of scope (e.g. objectives that will be accomplished in less than a year s time). Improve the user experience by creating a consistent web user interface that is in compliance with accessibility requirements. A roadmap generated will identify the specific web-based applications to be modified and allow us to prioritize which applications will be addressed in order to reduce the risks associated with non-compliance to accessibility. 1.3 Project Scope The scope defines project limits and identifies the products and/or services delivered by the project. The scope establishes the boundaries of the project. The project scope definition should also describe products and/or services that are outside of the project scope. Project Includes All web-based applications and web content published through IMD that is not specifically excluded as noted in Project Excludes section. Creation of standards for accessibility for web-based applications. Creation of standards for a consistent user interface for web-based applications. Mechanism to measure accessibility compliance for websites and web-based applications. Modifications to web-based applications to utilize the standards identified for accessibility and user interface. Project Excludes All applications which are not web-based. These are the mainframe applications without web components, for example, Traffic Log System and Right of Way. Any web-based applications that are scheduled for delivery. NOTE: if the sites are not created accessible or with the standard look and feel, they will need to be remediated in a subsequent request. Any web-based applications that are schedule to be removed from production operation prior to 8/31/2019. Specific web-based application functionality enhancements that are for a purpose other than making them accessible or to comply with the common user interface standards. Modifications to existing operational (non-functional) requirements including how the application performs or any security modifications. Modifications to existing methods that the user accesses the application other than the modifications for accessibility and user interface consistency. All TxDOT social media sites. (i.e. Facebook, Twitter, YouTube, etc.) 2

64 DocuSign Envelope ID: 882FC C-B0628DBC4EA4 IMD Project Charter RITM User Experience Version /14/2017 Project Excludes Modifications of existing Commercial Off-The-Shelf (COTS) applications to comply with TxDOT user interface standards. 1.4 Current State of Associated Business Processes Define the business process for the defined scope of the project As-Is, present state process prior to Implementing this project. This should include input that is representative of all identified stakeholders for all division and districts. Provide a brief explanation of the process at a summary high level. If necessary, add a visual diagram to the appendices. There are current standards for content creation and TxDOT branding. As websites and web-based applications are created and updated, there is not a set of user interface or accessibility standards to ensure that the information provided is available and easy to use by all users. This is especially true for users that have disabilities. See flow documentation for content updates (Content Flow.docx). This identifies the need for TxDOT.gov modifications. 1.5 Product Features Describe the end product that will be delivered as the result of this project. Briefly describe what the product will look like. Product Feature Accessibility Standards & Guidelines Web-based Application Common User Experience Standards & Guidelines Accessibility Compliance Methodology to include testing and validation. Web-based Application Enhancements for User Experience standardization and accessibility. Description This set of standards and guidelines will be a resource that is utilized for web-based application during requirements gathering, design, development and testing to ensure that the sites are accessible by as many users as possible, regardless of the user s method of accessing the site. The document will include basic operating procedures to ensure standards are followed. Baseline standards document is available. This set of standards and guidelines will be a resource that is utilized for web-based application during requirements gathering, design, development and testing to ensure that all sites are adhering to a consistent look and feel. The document will include basic operating procedures to ensure standards are followed. Baseline standards document is available. A method to assist in ensuring website and web-based application compliance to accessibility requirements. The tool will be able to check for section 508 of the Rehabilitation Act of 1973 and WCAG 2.0 AA standards compliance. The method will be used to assist in the monitoring of continued compliance for TAC 206 and 213 requirements. Each website and web-based applications that is in scope for the project will be modified where necessary to comply with accessibility and user interface standards. Each site may have various modifications based on the level of noncompliance that exists. 3

65 DocuSign Envelope ID: 882FC C-B0628DBC4EA4 IMD Project Charter RITM User Experience Version /14/ Project/Product Requirements Describe the product requirements that must be met to satisfy the business objectives. Populate the Customer Need/Technical Assumption, Requirement Description, and Priority columns of the Requirements Traceability Matrix in Section 5.1. See attachment in Section 5. Section 2. Assumptions, Constraints, Dependencies 2.1 Assumptions Describe the assumptions made in establishing this project s requirements, scope, timeline, and budget. Existing application requirement documentation is not available. There will be no changes to existing functional or operational (non-functional) requirements. The only application modifications will be related to meeting compliance and conforming to consistent user interface changes. 2.2 Constraints/Limitations Describe the constraints and/or limiting factors that can affect the project. Web applications developed using dated software may prove problematic to enhance without major application redesign. Existing application requirements documentation is not available, so ensuring existing functionality continues to operate as it currently does after the modifications for this user experience project. 2.3 Dependencies Describe the dependencies that can affect the project. Include any dependencies on existing projects, work streams, and/or systems. Current projects to upgrade applications to levels of supportable software versions. Section 3. Project Stakeholders 3.1 Stakeholder Identification and Roles Identify roles for the stakeholders. (Include Subject Matter Experts (SMEs) and Approvers in this list.) User or Stakeholder Michael Sledge Joshua Hunter Julien Devereux Cassie Jordan Juanita Webber Project Role Director, Creative Services Business Owner SME for website accessibility and usability SME for editorial Project Sponsor ADA Compliance Program Administrator 4

66 DocuSign Envelope ID: 882FC C-B0628DBC4EA4 IMD Project Charter RITM User Experience Version /14/2017 Application Owners (see list of applications in Section 5.3) Individual application owners will conduct user acceptance testing and verification of functionality when changes for accessibility and/or user interface have occurred. 3.2 Responsibility Chart Identify responsibilities for the stakeholders. (Include Business unit and IMD/ Vendors on this chart.) Task Business Unit IMD/Vendor Participate in User Acceptance Testing X X Review specific standards X X Participate in common user experience standards X X Prioritization of application enhancements X X Subject matter experts X Review Implementation Planning and Rollout Schedule X Section 4. Glossary Define all terms and acronyms required to interpret the Project Charter. Acronym or Term EIR TAC WIA W3C WCAG Section 504 Section 508 TAC 206 TAC 213 Definition Electronic and Information Technology Includes information technology and any equipment or interconnected system or subsystem of equipment that is used in the creation, conversion, duplication, storage, or delivery of data or information. Texas Administrative Code a compilation of all state agency rules in Texas. Web Accessibility Initiative - is an effort to improve the accessibility of the World Wide Web (WWW or Web) for people with disabilities. World Wide Web Consortium - the main international standards organization for the Internet. Web Content Accessibility Guidelines - a series of web accessibility guidelines published by the WAI of the W3C. Is a part of the Rehabilitation Act of 1973 that prohibits discrimination based upon disability. An amendment to the United States Workforce Rehabilitation Act of 1973, a federal law mandating that all EIR developed, procured, maintained, or used by the federal government be accessible to people with disabilities. Aligns state web accessibility standards with the federal regulations set forth in Section 508 of the Rehabilitation Act of Enacted state standardsfor procurement, development, or usage of EIR for people with disabilities and also aligns accssibility standards with the federal regulations set forth in Section 508 of the Rehabilitation Act of

67 DocuSign Envelope ID: 882FC C-B0628DBC4EA4 IMD Project Charter RITM User Experience Version /14/2017 Section 5. Appendices 5.1 Requirements Document See document Requirements Document RITM xlsx 5.2 Project Economics See document Economics RITM UX.xlsx 5.3 In Scope Applications Application Name (Supported by NTTD) PeopleSoft HCM - Succession Planning TxDOT Centennial Track the Truck (TrackTruck) V1 Project Tracker Paris GIS Cores (Paris GIS) OrigamiRisk ERMS (Origami) V1 Johnson Controls Metasys (Metasys) V8 Bridge Inspection Tool (InspectTech) V1 HCRS GIS Infrastructure Entry and Mapping (HCRS EDIT) Highway Assets Management Systems (HAMS) V1 Geospatial Roadway Inventory Database (GRID) V1 Enterprise Permitting System (EPS) V8 Design and Construction Information System GIS (DCIS GIS) Congestion Mitigation (Cong Mit) Advanced Outfall Tracking System (AOTS) - storm water discharges AVN MET TxDOT.gov TeleWork (Workwise) Visitor Service Totals (VST) Unified Transportation Program Utility Installation Review (UIR) V1 TxDOT Financial Assistance System (TxFAS) V1 Texas Rail Information Management System (TRIMS WEB) Sign Replacement Work Requests (SRWR) Signal Shop Call Out Log Senate Bill 20 (SB20) Roadway Weather Information System (RWIS) Region Support Center Data System (RSCDATA) Right of Way Strategy 102 Research Management System (RMS) Railroad Inspection System for the PC (RISPC) Revenue Finance System Revenue Public Transportation Formula Application (PTFA) Permanent Structure Number (PSN) Pavement Management Information Data Conversion Tool (PMIDCT) 6

68 DocuSign Envelope ID: 882FC C-B0628DBC4EA4 IMD Project Charter RITM User Experience Version /14/2017 Perspective Payment Card System (PCS) Pavement Analyst (PA) Open Records (OpenRecords) MyPrint (MyPrint) V1 Minute Orders Meteorological Evaluation Towers (MET) Inventory Purchasing and Planning (IPP) Heavy Equipment Scheduler (HES) Function 225 Request Fuel Card System (FCS) Federal Aid Funding Obligation System (FAFOS) Expenditure Transfer Voucher Log (ETV LOG) Electronic STIP Portal (ESTIP) Revenue Log (DLOG) Design and Construction Information System-FIMS (DCIS-FIMS) Customer Service Tracking and Resolution (C-STAR) Construction Records Database (CRD) Adobe CQ5 Content Management System (CQ) Child-support, IRS, Bankruptcy (CIB) Barcode Assistant (ASST) Drive Texas Virtual Earth DCIS (VE DCIS) TxDOTNow TxDOT Roadway Information Portal (TRIP) Straight Line Diagramming (SLiD) SiteManager GIS (SiteMgr GIS) Right of Way Map (ROW Map) Load Restricted Bridge Map (LRBM) Load Zoned Roads (Loadzone) Highway Conditions Reporting System (HCRS) Guardrail End Treatment (GET) Floodplain Management System (FPM) V1 DriveTexas (DRVTX) ArcGIS Online (AGO) Texas Airports Data System (TADS) State Vehicle Usage Subcontractor Monitoring System (SMS) Printer Usage Tracking (PUT) PMIS Process Control (PMISPC) Pavement Management Information System (PMIS) Pavement Data Collection (PCDC) MicroStrategy Electronic Grants (EGrants) Electronic Grants (EGrants_ENT) 7

69 DocuSign Envelope ID: 882FC C-B0628DBC4EA4 IMD Project Charter RITM User Experience Version /14/2017 Central Authentication and Authorization System (CAAS) Bid Proposal System (BPS) Bid Proposal Request System (BPRS) Adopt-A-Highway (AAH) -.Net Version Maintenance Management System (MMS) MMS Interface Manager (MIM) TRACK TRACK Complaint Case Management SharePoint Application (TRACK) V1 Electronic Legislative Inquiry Tracking Exchange (ELITE) V1 Adopt A Highway SharePoint Application (AAH) V2 VTC Report Center (VTCReports) V5 Bridge Under Clearance Database (UCDB) Texas Unified Certification Program (TUCP) Texas Environmental Compliance Oversight System (Texas ECOS) - DUPLICATE Statewide Traffic Analysis and Reporting System II (STARS II) Specification (SPEC) Professional Services Contract Administration and Management System (PS CAMS) Project Letting Approval Reporting System (PLARS) Plans Online (Plans Online_PLOL) Primavera P6 Enterprise Project Portfolio Management WEB (P6 WEB) Primavera P6 Enterprise Project Portfolio Management Timesheets (P6 TimeSheets) Online Manuals System (OMS) Inspection and Materials Management System (I2MS) Financial Forecasting Fin Admin (FIN ADMIN) FHWA 1391 Electronic Project Records System (EPRS) Estimate and Letting System (ELS) Electronic Bidding System (EBS) Consultant Certification Information System (CCIS) Clean Air Plan System (CAPS) GSD Work Order System (AMICS) NTC - Notice To Contractors TxDOT Enterprise Document Management System (TxDOT EDMS) TxDocs Online emanager Electronic Forms (EFORMS) Enterprise Document Management System (EDMS) Application Name (Supported by 3rd party vendor - not NTTD) Toll Management System (TMS) FLEET Navigator (FNAV) PeopleSoft SCM - Purchasing PeopleSoft SCM - Inventory PeopleSoft SCM - Asset Management PeopleSoft HCM - Time and Labor PeopleSoft HCM - Talent Management 8

70 DocuSign Envelope ID: 882FC C-B0628DBC4EA4 IMD Project Charter RITM User Experience Version /14/2017 PeopleSoft HCM - Security PeopleSoft HCM - Position Management PeopleSoft HCM - Performance Management PeopleSoft HCM - Payroll PeopleSoft HCM - Human Resources PeopleSoft HCM - Benefits PeopleSoft HCM PeopleSoft FSCM - Security PeopleSoft FSCM - Project Costing PeopleSoft FSCM - General Ledger PeopleSoft FSCM - Contracts PeopleSoft FSCM - Commitment Control PeopleSoft FSCM - Billing PeopleSoft FSCM - Accounts Receivable PeopleSoft FSCM - Accounts Payable PeopleSoft FSCM PeopleSoft ELM - Security PeopleSoft ELM - Learning Management Facilities Work Order Requests DallasFWHigh Speed Rail Audit Archiving Legislative Tracking System (LTS) State OJT Crash Records Information System (CRIS) Travel Demand Modeling (TDM) 9

71 DocuSign Envelope ID: 767C5831-6F8F-464B F E8 RITM : IMPLEMENT MULTI-BROWSER COMPATIBILITY (BROWSER AGNOSTIC) & MULTI-DEVICE PORTABILITY 02/23/2018 BRM Owner: Rikki Degelia NTT Data Architect: Ashish Bharal Prepared by: Simrita Ahluwalia/ Ashish Bharal TxDOT IT

72 Agenda DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Background Business Goals Affected Systems and Components Assumptions Recommended Solution Solution Options Browser and Device Compatibility Testing Tools Capability Matrix Alternatives for Development Tools/Cost Overall Approach Implementation Approach- Phase II onwards Factory Model Additional Items Needing to be Purchased Potential Stakeholders Appendix TxDOT IT 2

73 Background DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Problem Statement TxDOT web-based applications/sites are not supported on multiple browsers and devices. There are inconsistencies between applications and corresponding browser compatibility, as there are no defined standards in place. The user interfaces are not supported across multiple devices. TxDOT IT 3

74 Background DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Defined Requirements / Scope: There is a need for identified TxDOT web based sites and applications to be accessible when using Internet Explorer, MS Edge, Google Chrome, Firefox, Safari, and Opera browsers. There is a need for identified TxDOT web based sites and applications to be accessible when using ios and Android mobile devices. There is a need to have defined standards for maintaining the TxDOT web based applications to be functional with multiple browsers. There is a need to have defined standards for maintaining the TxDOT web based applications to be functional with multiple operating systems. These standards will define when and how the applications are maintained with continued compatibility. Security Considerations: Maintain existing TxDOT required security standards within all applications. Anything that does not meet basic security standards within the TxDOT web applications environment, will need to be addressed during the project via a change request. TxDOT IT 4

75 Business Goals DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Proposed Business Goals Increased user adoption Improved customer satisfaction Improve user productivity Reduce the number of service desk calls leading to lower operational costs. The methodology for calculation of reduction in service desk calls can be mutually agreed during the project. Commitments (Regulatory / Internal) The following commitments were identified: Section of the Texas Government Code Cloud Consideration TxDOT IT 5

76 Affected System(s), Component(s) DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Affected Systems: System that are interfacing by affected applications Affected Applications: Refer to the list of identified NTT DATA maintained web applications, based on the information as of 2/12/18. File Name: NTT Web Apps Feb 12, 2018.xlsx This list of applications is as best known, but may change during the project. Affected Components: Presentation Tier of in-scope web applications Critical Infrastructure: N/A TxDOT IT 6

77 Assumptions DocuSign Envelope ID: 767C5831-6F8F-464B F E8 The existing non-functional requirements will remain as is within all web applications. No enhancements or improvements to individual applications will be made, other than what is listed in the requirements document All social media sites used by TxDOT are excluded from project scope Non Web, Non-Operational, To be decommissioned (prior to Aug 2019) web applications are Out of Scope Standards and guidelines should be used for the modifications for this current initiative and the projects moving forward Browser Compatibility version is assumed to be N-1, however the web applications may not be compatible with the previous versions. It is assumed that web applications need to be functional on mobile devices, but not adaptive or responsive frameworks. The current technical stack of the applications supports the necessary changes that will be required for meeting requirements. If not, the specific application would need to be modernized. Tables within a web application may not be fully visible without scrolling vertically or horizontally. It is assumed that during the SRS stage for each application, there will be information provided on device version requirements and browser version information will be specified as well. Mobile devices include phones and tablets. COTS applications are out of scope. Some in-scope SaaS applications can be modified by NTT DATA, if there is a presentation layer that is accessible by NTT. This will need to be confirmed for each application during due diligence. TxDOT IT 7

78 Recommended Solution DocuSign Envelope ID: 767C5831-6F8F-464B F E8 1. Adopt a phased approach to make web applications browser and device agnostic. 2. Define web UI standards and guidelines document(s). 3. Deploy automated testing tools to identify gaps and validate browser and device agnostic capability. However, there will be some manual testing involved. 4. Use Web UI development tool to enhance productivity and quality. 5. Use a template based development approach to achieve consistency, reusability, productivity and maintainability. 6. Use one of the following solution options for making the web applications browser and device agnostic: a) As-Is UI with HTML5 (in initial requirements) b) Responsive Design c) Adaptive Design 7. Enhance standards and guidelines document(s) as needed in every iteration. 8. Define Factory Model in 1 st phase of the program to streamline future iterations. 9. The impact to bandwidth utilization for each in-scope web application will be based on the selected solution option during the Design phase of each application. The network team will be engaged to determine/verify the same. TxDOT IT 8

79 Solution Options Pros and Cons DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Alternative 1: Fluid UI with HTML5 Alternative 2: Responsive Design Alternative 3: Adaptive Design No Action Pros: Easier to design and add functionalities Media queries to identify devices and render content Multiple HTML files for different devices Less bandwidth utilization Less bandwidth utilization Cons: Applications will be fully functional but may not be as user friendly All the content is downloaded whether used or not. Templates are optimized for each device May not function on mobile devices. May need additional update in the future for mobile interface Higher bandwidth utilization Not supported on multiple browsers Inconsistencies between applications TxDOT IT 9

80 Browser & Device Compatibility Tools-Capability matrix DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Capability EndTest.io (Recommended) SauceLabs Test Automation Built-in Dependent on Selenium Webdriver Deployment Option Architecture Both on-premise and Cloud Scalable both Vertically and Horizontally Cloud Based SaaS Application Browserstack Dependent on Selenium Webdriver Cloud Based SaaS Application Coding Skills Not required Selenium Skills Selenium Skills Cost $500 per year + $3000 one time setup fee Supported browser & devices Limited but meets our requirement $10K per year $5000 per year 800 browsers and devices browsers TxDOT IT 10

81 Alternatives for Development Tools DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Criteria Dreamweaver CC (recommended) CKEditor 5 Roketcake WYSIWYG X X X Shared Editing X X Server Side Scripting X X X Support Java X X Support.NET X X X Support PHP X X Partial Development Productivity Supports Templates High High Medium X Mobile Support X X X Support Responsive Design X X X Cost per License $19 per month Open Source $60 (one time) *The selected development tool will be procured for both the User Experience Consistency & Browser Agnostic-Multi Device Portability initiatives. TxDOT IT

82 Overall Approach DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Utilize a phased rollout approach for the overall program/portfolio of web applications at TxDOT Phase I Discover Detailed Functional Requirements (SRS) for Baseline applications Define Standards & Guidelines Program level Detailed Design/Solution - for Baseline applications Templates Deliver Implement Pilot(s) of selected Baseline Web Applications Validate Effort Estimation/model and adjust as required Create Factory Blueprint Update grouping of applications for phased rollout, based on learnings Detailed Due Diligence for Phase II applications (for estimating Phase II effort) TxDOT IT 12

83 DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Implementation Approach - Phase II n Factory Model Utilize the standards and guidelines created in Phase I. Leverage all program level information. The roadmap (applications groups/phases) can be adjusted, based on ongoing learnings from prior phases, and external related projects Update factory model with learnings from each phase to improve overall efficiencies during planning and implementation in subsequent phases Update Standards and Guidelines with learnings from the current phase Conduct detailed due diligence for subsequent phases Note: Subsequent phases will follow the same approach as Phase II. Multiple phases can be executed in parallel. Phase n Phase III SRS Phase II Standards & Guidelines Document Design Specification Create Test Cases Automated Gap Analysis Build Automated Compatibility & Compliance Verification Functional Regression & Manual Test Next Phase Due Diligence Learnings and Re-usable Assets Process Optimization Compliant Web Apps TxDOT IT

84 Factory Model - Benefits DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Leverage/enhance during each phase of the project for improving efficiencies Program level Standards and Guidelines User Interface and Accessibility Best practices Re-usable Components Create a set of base UI templates that can be leveraged across applications. Keep building upon this in each phase for improved efficiencies. Components that implement common functionality or mechanisms like UI widgets, search etc. Project checklist Patterns Architecture Design patterns TxDOT IT 14

85 Factory Model - Application Grouping DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Criteria Applications can be grouped based on following criteria: Internal vs External facing Technology Java.NET ASP Classic SharePoint ESRI Other (PHP, Cold Fusion etc.) Complexity Level High Medium Low Recommendation Phase I (Pilot Phase): implement requirements across 3 or 4 applications with different technologies, internal facing and medium complexity. For subsequent phases: target low complexity applications first to leverage learnings for future more complex phases. TxDOT IT 15

86 Additional Items Needing to be Purchased DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Hardware: AWS EC2 instance Browser & Device compatibility testing tool Infrastructure: AWS EC2 instance Browser & Device compatibility testing tool Software Endtest.io (Browser & Device compatibility testing tool) Adobe Dreamweaver CC (The selected development tool will be procured for both the User Experience Consistency & Browser Agnostic-Multi Device Portability initiatives) Other: N/A TxDOT IT 16

87 Potential Stakeholder(s) DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Potential Stakeholder(s) list: Tower: Representative: Strategy BRM TxDOT EA TxDOT Security TxDOT Operations Strategy Director Mark Evans Matthew Alexander Yolanda Neisler Aileen Wade Cassie Jordan 2/27/2018 2/26/2018 2/27/2018 2/26/2018 2/27/2018 * All signatures are mandatory before going to ARB TxDOT IT 17

88 Appendix: Overall Approach DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Phased rollout approach for the overall program/portfolio of web applications at TxDOT. Selected Group/s of applications will be implemented within a phase. Phase I Create program level Standards and Guidelines for Browser Compatibility and Multi Device Portability. Go through full planning and implementation cycle for a select 3-4 baseline applications for creating a baseline approach. Do a full due diligence of the baseline applications for an accurate effort estimate. Identify whether the selected applications will need to be rewritten in order to make them browser agnostic Identify whether the selected applications will work only on certain browsers Due diligence will include detailed SRS and detailed design/solution as outcomes, which will be signed off by TxDOT. Apply changes as required. Create a factory model for repeatable work that can be leveraged for each application. Apply findings/learnings from the implementation of the baseline applications for updating the application groups for the rest of the applications portfolio. Check for any related projects in progress that may impact the applications rollout for Phase II. Conduct a due diligence (detailed SRS and detailed design signed off by TxDOT) exercise for Phase II applications. Write up Phase II SOW, based on effort estimates from the due diligence work. TxDOT IT 18

89 Appendix: Overall Approach (Cont.) DocuSign Envelope ID: 767C5831-6F8F-464B F E8 Phase II n Utilize the standards and guidelines created in Phase I. Leverage all program level information. The roadmap can be adjusted, based on ongoing learnings from prior phases, and external related projects Update factory model with learnings from each phase to improve overall efficiencies during planning and implementation in subsequent phases Update Standards and Guidelines with learnings from the current phase Conduct detailed due diligence for subsequent phases Note: Subsequent phases will follow the same approach as Phase II. Multiple phases can be executed in parallel. TxDOT IT 19

90 DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC RITM : USER EXPERIENCE CONSISTENCY 02/23/2018 BRM Owner: Rikki Degelia NTT Data Architect: Ashish Bharal Prepared by: Simrita Ahluwalia/ Ashish Bharal TxDOT IT

91 Agenda DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Background Business Goals Affected Systems and Components Assumptions Recommended Solution Accessibility Compliance Verification Tools Alternatives for Development Tools/Cost Overall Approach Implementation Approach- Phase II onwards Factory Model Additional Items Needing to be Purchased Potential Stakeholders Appendix TxDOT IT

92 Background DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Problem Statement The websites lack accessibility compliance. The current websites have differing page layouts and formats which cause potential confusion from a user experience perspective. The current applications lack TxDOT branding consistency, resulting in continued operational effort to train and/or answer questions related to the use of various applications TxDOT IT

93 Background DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Defined Requirements / Scope: requirements impact all internal and external web based applications There is a need to establish common user interface standards There is a need to define design and development standards for accessible web sites There is a need to identify tools to measure accessibility compliance There is a need to modify the web sites to become accessible with better usability, based on the standards identified. Security Considerations: Maintain existing security standards within all web applications. Anything that does not meet basic security standards within the TxDOT web applications environment, will need to be addressed during the project via a change request. TxDOT IT

94 Business Goals DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Proposed Business Goals Increased user adoption and customer satisfaction Ensure accessibility compliance with TAC 206 and TAC 213 Expanded user base, including persons with disabilities Improved user experience and consistency Reduce the number of service desk calls leading to lower operational costs The methodology for calculation of reduction in service desk calls can be mutually agreed during the project. Commitments (Regulatory / Internal) DIR Ensure Section 508 Compliance Section of the Texas Government Code Cloud Consideration TxDOT IT

95 Affected System(s), Component(s) DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Affected Systems: Systems that are interfacing with affected applications Affected Applications: Refer to the list of identified NTT DATA maintained web applications, based on the information as of 2/12/18. File Name: NTT Web Apps Feb 12, 2018.xlsx This list of applications is as best known, but may change during the project. Affected Components: Presentation Tier of in-scope web applications Critical Infrastructure: ADA compliance verification tool (to be purchased) TxDOT IT

96 Assumptions DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC The existing non-functional requirements will remain as is within all web applications. No enhancements or improvements to individual applications will be made, other than what is listed within the requirement document All social media sites used by TxDOT are excluded from project scope Non Web, Non-Operational, To be decommissioned (prior to Aug 2019) web applications are Out of Scope Standards and guidelines should be used for the modifications for this current initiative and the projects moving forward Accessibility and UI standards should not be conflicting. Accessibility takes precedence. The current technical stack of the applications supports the necessary changes that will be required for meeting requirements. If not, the specific application would need to be rearchitected for a newer technology. COTS applications are out of scope. Some in-scope SaaS applications can be modified by NTT DATA, if there is a presentation layer that is accessible by NTT. This will need to be confirmed for each application during due diligence. TxDOT IT

97 Recommended Solution DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC 1. Utilize a phased approach for the overall implementation. A phase will include the full rollout of group/groups of applications. 2. Define web UI and accessibility standards and guidelines document(s). 3. Deploy automated ADA compliance verification tool to identify gaps and validate Section 508 compliance. However, there will be some manual testing involved. 4. Utilize standard Web UI development tool to enhance productivity and quality. 5. Utilize template based development approach to achieve consistency, reusability, productivity and maintainability. 6. Enhance standards and guidelines document(s) as needed in every iteration. 7. Define Factory Model in 1 st phase of the program to streamline future iterations. TxDOT IT

98 Accessibility Compliance Verification Tools DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Criteria PowerMapper SortSite (recommended) Dyno Mapper Monsido Section 508 Compliance Testing X X X Generate Site Map X X X Suggest Solution X X X Visualization X Deployment Options Desktop & Cloud Only Cloud Only Cloud Security High Data exposed to third party Data exposed to third party Cost High Low Low TxDOT IT

99 Alternatives for Development Tools DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Criteria Dreamweaver CC (recommended) CKEditor 5 Roketcake WYSIWYG X X X Shared Editing X X Server Side Scripting X X X Support Java X X Support.NET X X X Support PHP X X Partial Development Productivity Supports Templates High High Medium X Mobile Support X X X Support Responsive Design X X X Cost per License $19 per month Open Source $60 (one time) *The selected development tool will be procured for both the User Experience Consistency & Browser Agnostic-Multi Device Portability initiatives TxDOT IT

100 Overall Approach DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Utilize a phased rollout approach for the overall program/portfolio of web applications at TxDOT Phase I Discover Detailed Functional Requirements (SRS) for Baseline applications Define Standards & Guidelines Program level Detailed Design/Solution - for Baseline applications Templates Deliver Implement Pilot(s) of selected Baseline Web Applications Validate Effort Estimation/model and adjust as required Create Factory Blueprint Update grouping of applications for phased rollout, based on learnings Detailed Due Diligence for Phase II applications (for estimating Phase II effort). TxDOT IT

101 DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Implementation Approach - Phase II n Factory Model Utilize the standards and guidelines created in Phase I. Leverage all program level information. The roadmap (applications groups/phases) can be adjusted, based on ongoing learnings from prior phases, and external related projects Update factory model with learnings from each phase to improve overall efficiencies during planning and implementation in subsequent phases Update Standards and Guidelines with learnings from the current phase Conduct detailed due diligence for subsequent phases Note: Subsequent phases will follow the same approach as Phase II. Multiple phases can be executed in parallel. Phase n Phase III SRS Phase II Standards & Guidelines Document Design Specification Create Test Cases Automated Gap Analysis Build Automated Compatibility & Compliance Verification Functional Regression & Manual Test Next Phase Due Diligence Learnings and Re-usable Assets Process Optimization Compliant Web Apps TxDOT IT

102 Factory Model-Benefits DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Leverage/enhance during each phase of the project for improving efficiencies Program level Standards and Guidelines User Interface and Accessibility Best practices Re-usable Components Create a set of base UI templates that can be leveraged across applications. Keep building upon this in each phase for improved efficiencies. Components that implement common functionality or mechanisms like UI widgets, search etc. Project checklist Patterns Architecture Design patterns TxDOT IT

103 Factory Model - Application Grouping DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Criteria Applications can be grouped based on following criteria: Internal vs External facing Technology Java.NET ASP Classic SharePoint ESRI Other (PHP, Cold Fusion etc.) Complexity Level High Medium Low Recommendation Phase I (Pilot Phase): implement requirements across 3 or 4 applications with different technologies, internal facing and medium complexity. For subsequent phases: target low complexity applications first to leverage learnings for future more complex phases. TxDOT IT

104 Additional Items Needing to be Purchased DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Hardware: 1 AWS EC2 instance Section 508 compliance verification tool Infrastructure: 1 AWS EC2 instance to deploy: Section 508 compliance verification tool Software PowerMapper SortSite (Section 508 compliance verification tool) Adobe Dreamweaver CC (The selected development tool will be procured for both the User Experience Consistency & Browser Agnostic-Multi Device Portability initiatives) Other: N/A TxDOT IT

105 Potential Stakeholder(s) DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Potential Stakeholder(s) list: Tower: Strategy BRM TxDOT EA TxDOT Security TxDOT Operations Strategy Director Representative: Mark Evans Matthew Alexander Yolanda Neisler Aileen Wade Cassie Jordan 2/27/2018 2/26/2018 2/27/2018 2/26/2018 2/27/2018 * All signatures are mandatory before going to ARB TxDOT IT

106 Appendix: Overall Approach DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Phased rollout approach for the overall program/portfolio of web applications at TxDOT. Selected Group/s of applications will be implemented within a phase. Phase I Create program level Standards and Guidelines for user experience consistency. Go through full planning and implementation cycle for a select 3-4 baseline applications for creating a baseline approach. Do a full due diligence of the baseline applications for an accurate effort estimate. Identify whether the baseline applications will need to be re-coded, to make them ADA compliant. Due diligence will include detailed SRS and detailed design/solution as outcomes, which will be signed off by TxDOT. Apply changes as required. Create a factory model for repeatable work that can be leveraged for each application. Apply findings/learnings from the implementation of the baseline applications for updating the application groups for the rest of the applications portfolio. Check for any related projects in progress that may impact the applications rollout for Phase II. Conduct a due diligence (detailed SRS and detailed design signed off by TxDOT) exercise for Phase II applications. Write up Phase II SOW, based on effort estimates from the due diligence work. TxDOT IT

107 Appendix: Overall Approach (Cont d) DocuSign Envelope ID: E803ED92-9E99-42D BC044D7FC Phase II n Utilize the standards and guidelines created in Phase I. Leverage all program level information. The roadmap can be adjusted, based on ongoing learnings from prior phases, and external related projects Update factory model with learnings from each phase to improve overall efficiencies during planning and implementation in subsequent phases Update Standards and Guidelines with learnings from the current phase Conduct detailed due diligence for subsequent phases Note: Subsequent phases will follow the same approach as Phase II. Multiple phases can be executed in parallel. TxDOT IT

108 Attachment H Executive Summary Update of Pedestrian Access Inventory and Self-Evaluation Peter B Krause, RLA - Design Division John Tyler, P.E. Pape-Dawson Engineers, Inc. June 14, 2018

109 Executive Summary Pape-Dawson Engineers, Inc. was contracted by the Texas Department of Transportation (the State) to develop procedures, program goals, and policy definitions to support the redevelopment of the Pedestrian Access Inventory (PAI) of infrastructure in the state right of way (ROW) and the collection effort associated with this inventory. Collected information and policy recommendations will be used as the basis for the State s Americans with Disabilities Act (ADA) Transition Plan and Curb Ramp Program Planning Document updates. Under the ADA, the State is required to develop a transition plan identifying the steps necessary to achieve full accessibility of its facilities and programming [Section d.1 ADA]. Additionally, the State must produce a schedule for elimination of architectural barriers where required, giving priority where defined by the law [Section d.2 ADA]. Federal expectation of fulfillment of these requirements includes periodic self-evaluation and planned access remediation utilizing the State s core programming, a dedicated remediation program, and maintenance activities with detailed documentation of progress toward achieving full access. The State completed a comprehensive self-evaluation (including its buildings and rest areas, programming policies, and employment) and published a transition plan in 1993 addressing those aspects of the ADA. An effort to update the original transition plan took place in extending to full inventory of curb ramps at all intersections on the state highway system. Existing curb ramps were assessed for compliance and assigned a static severity ranking by field collection staff with respect to the standards in effect at the time of collection and the proximity of each asset to nearby pedestrian activity generators. The inventory was used as the basis for the State's 2004 ADA Transition Plan. Over time, the 2003 inventory has become outdated due to uncaptured improvements made within the ROW and changes in the makeup and location of pedestrian attractors since the initial inventory was completed. The technology used to maintain the 2003 inventory was limiting as was universal knowledge of the system s existence amongst the various State stakeholders. Legal precedent has shown that an uncoordinated approach to documenting the construction of accessible pedestrian elements through the course of routine roadway projects, maintenance activities, and dedicated remediation programs could leave the State vulnerable to civil rights litigation. The advent of updated federal accessibility standards in 2010 has also contributed to the decline in usefulness of the 2003 inventory in selecting and prioritizing project components, thereby prompting the need for a new inventory. The Pape-Dawson team conducting the current self-evaluation and PAI of assets in the ROW aims to improve upon its predecessors through implementation of a dynamic severity- and activity-based ranking system of pedestrian facility components; efficient and integrated use of data collection and reporting technologies; and recommended policy changes for more effective coordination and integration within pertinent State agencies. The PAI encompasses a Page 2 of 14

110 comprehensive geometric assessment of on-system curb ramps, sidewalks, and transit stops that can be evaluated for compliance based on current or future standards. Importantly, the PAI integrates well with existing State planning tools and field collection systems using geographic information systems (GIS). The goal in producing the PAI is to equip the State with mechanisms to proactively select project components where accessibility needs are greatest (by accounting for both the ADA requirements and proximity to nearby pedestrian activity generators) while improving the documentation process of completed work for better compliance reporting and protection against potential litigation. The development of the PAI began with a pilot study in Austin, San Marcos, New Braunfels, and San Antonio to trial data collection methods; prioritization models, cost estimating, and reporting mechanisms; program planning tools; and documentation procedures prior to statewide implementation of the team s recommended policies. A representative selection of urban and rural areas was selected for the pilot study, including varied topography, population, density, and areas of historical significance. The pilot study tested the team s recommended methods for consistent and objective collection prior to statewide collection. Post-processing the data within the pilot study area using team-developed GIS tools demonstrated the effectiveness of project component ranking. Input from related State agencies, engaged citizens, key advocacy groups, and team experts was taken into account through a workshop series and focus group prior to forming the final recommended methodology, policies, and ranking criteria. The PAI dataset will overlay accessibility data with other mapped project selection factors found in the State s Statewide Planning Map to enable data-driven decision making for project planning in all aspects of transportation system. The State will perform ongoing updates to the PAI dataset through routine construction inspection activities for improved compliance documentation using the mobile application developed specifically for the PAI collection effort. Past State experience has demonstrated that the complexity of the ADA and its requirements have not been widely understood or consistently applied through the construction phase, nor has documentation of completed work been properly accounted for in FHWA compliance reporting. The Application aims to simplify much of the nuance of the accessibility requirements by guiding the user through a comprehensive compliance determination procedure for a more correct and consistent inspection process. The results of such inspections will be used to capture completion of accessibility improvements, advancing the State's federal compliance reporting and future project planning capabilities. Stakeholders and Team Organization The State assembled a project team in 2015 to develop the PAI. Overall responsibility resided with the TxDOT Design Division. Pape-Dawson Engineers, Inc. was selected to lead the project development and organize key subject matter experts to inform and guide policy decisions with several key State and public stakeholders. Figure 1 details the team and stakeholder structure. Page 3 of 14

111 Figure 1 Team and Stakeholder Structure Project Development: Workshop Series The project development followed a workshop series from legal requirements through implementation. Each workshop aimed to educate discussion participants on the requirements of the law, the division of compliance responsibilities within the State, current best practices, and existing programs as they relate to the State s obligation to meet accessibility requirements. The outcome of each workshop was an equitable participation in the development of new long-range policies that guide the data collection, prioritization, and implementation of access remediation for pedestrian facilities in the ROW. The ultimate product of the workshop series was a Web Page 4 of 14

112 Application (delivered in Workshop 11) as a graphical interface for state planners to use in implementation of the policies discussed herein. Each workshop, including important outcomes, is summarized below. Workshop 1: Legal and Policy Overview The team conducted a November 2015 examination of ADA policy, regulations, best practices, and federal expectations as to achieving accessibility in the ROW. The discussion identified existing laws to which the State is subject, including their respective requirements to establish the need for an update to the 2004 Transition Plan. The team explained a key facet of transition plans relates to providing program accessibility a legal term defined as an agency s operation of each program, service or activity in such a way that, when viewed in its entirety, is accessible [Section d.3.i-ii ADA]. Program accessibility was discussed further in Workshop 2. Decisions from Workshop 1 reflected the State's intention to improve upon past transition plans and their respective implementations with focus on better integration within existing State systems and processes. Workshop 2: Office of Civil Rights Transition Plan Integration The team led a November 2015 overview of current systems for access remediation and documentation, including requirements and best practices in implementing transition plans. The talk established the team s role in assisting the State with its compliance obligation under the ADA, the legal requirements of which extend into areas such as employment, communication with the public, and site/facility compliance in addition to the provision of access to the State s transportation facilities in the ROW. The team s scope is to support the State s overall transition plan development with policy recommendations and supporting data only for the ROW portion of its compliance obligation. The PAI was explained as a necessary component for fulfilling the team s purpose in the overall transition plan update. The team described the task of creating a pedestrian access inventory as similar to other State asset management tasks (e.g. pavement maintenance, traffic signal equipment inventory) and reviewed software options for tracking accessibility compliance information. GIS was the recommended format to pursue over other software platforms as it is well supported and compliments existing State systems. The discussion gave an overview of required public involvement activities and suggested methodology for conducting a public meeting with the recommendation to hold the meeting at or near the completion of the Pilot Study. The team gave an overview of data collection philosophies that would be further developed in Workshops 3 and 4, including decision matrices, mitigation schedules, and implementation policies. Page 5 of 14

113 Workshop 3: Pedestrian Access Inventory The PAI workshop, held in November 2015, offered ideas for improvement upon past inventory efforts using current technologies for collection, data management and identifying the most appropriate level of detail to conduct the collection effort. The team gave a comparison of limited vs. detailed collection methodologies, including their associated pros and cons as they relate to transition plan development. Limited collections were defined as observation-based visualdeterminations of compliance, often relying on a subjective grading scale (e.g. A-B-C-D-F or high-medium-low) and collection personnel s knowledge and experience recognizing compliance issues. In contrast, detailed collections were defined as objective recorded measurements, such as those taken with a tape measure or digital level, that could be assessed for compliance in the field or via postprocessing. Detailed collections are less reliant on collection personnel knowledge or experience in accessibility compliance. The team recommended detailed collections for both curb ramps and transit stops due to the complexity of requirements for those elements. Sidewalks offered an opportunity for a limited-detailed hybrid methodology which could be determined by a desktop study conducted prior to collection. Detailed collections using the team s Ultra Light Inertial Profiler (ULIP) technology (in which the ULIP device traverses a pedestrian Figure 2 ULIP Device and Operator element and records measured deficiencies and their respective locations) were cited to be the most efficient and accurate collection method for sidewalks in densely developed areas with continuous block-to-block sidewalk connectivity. Areas with less density of development, or where sidewalks lacked connectivity, were recommended for limited collection methodology. Consensus was reached to limit field collection personnel s required knowledge of accessibility requirements to the absolute Page 6 of 14

114 minimum, favoring a guided, step-by-step process for field measurements that can achieve repeatable results with statewide collection staff from varied backgrounds. Potential reporting structures, practicalities of administering a statewide collection effort, and data integration with the transition plan focused the discussion on how to implement the least subjective and most consistent collection methodology. The State concurred with the detailed collection approach for curb ramps, transit stops and sidewalks in urban areas. Limited collection methodology was also approved where ULIP operations become less efficient, particularly in suburban and rural areas. The State opted to use back-end processes or algorithms for compliance determination (as opposed to operator, field-assessed) in order to improve upon past inventory subjectivity and dataset consistency, a strategy that will enable the State to adapt to future standards without having to re-inventory its assets. Workshop 4: Survey Approach & Data Collection Criteria Workshop The team conducted a December 2015 discussion regarding elements subject to collection and how those elements would be collected and assessed in the field. Various mobile devices were debated, but the State confirmed the team s recommendation for tablet-based devices as they are already used for other State field collection efforts. The team navigated detailed logic maps, decision points, and the recommended/discouraged collection application software platforms by giving a detailed explanation of required collection application functionality, documented further in the 2015 Curb Ramp & Planning ADA Collection Application Guideline (separate cover). Specifically, the top ESRI products (an industry leader in GIS technology) were reviewed for applicability with the PAI Application requirements as shown in Figure 3. Figure 3 Collection Application Platforms Evaluated The team recommended the AppStudio platform as it provided the only widely supported, customizable and flexible solution that could implement all the necessary components of the PAI while maintaining a high degree of accuracy and efficiency. Furthermore, AppStudio was the only option that supported effective offline use a key required feature of the collection Application considering that many areas in Texas are remote or subject to poor cellular service coverage. Collector and Survey123 were cited as too limiting in functionality and too reliant on ESRI support to implement required software functionality not currently available. Discussion focused on consistency of statewide implementation and ease of collection. The team stressed that the user be guided by the Application through a series of technical questionnaires to Page 7 of 14

115 eliminate extensive training prior to the collection effort. A subsequent meeting in March 2016 with the State s IT Vendor delivered similar content to that of Workshop 4 where the team reviewed the Collection Application Specification Guideline to the IT Vendor s application developers. The State and the IT vendor selected the Survey123 platform for its compatibility with a broader transportation system asset management plan in effect at the time, which proved limiting in required functionality during field trials. The asset management plan was later discontinued. The team provided a critique of the Survey123 Application developed by the State s IT Vendor detailing several fatal flaws and areas where the interface would present operational challenges to an efficient statewide collection effort. Workshop 5: Legal Policy Update The team provided an August 2016 review of Workshop 1 to new staff within the Office of Civil Rights that were not present for the initial legal and policy overview. The content covered federal expectations, keys to successful transition plans, best practices for public involvement, an update regarding ongoing litigation, and a summary of notable civil rights settlements amongst similar agencies around the United States. The message of the discussion recommended the State improve its compliance documentation and reporting efforts to the Federal Highway Administration (FHWA) regarding capture of completed accessibility improvements made through its various programs, dedicated remediation programs, and maintenance activities in order to protect itself against potential civil rights litigation and demonstrate its good faith effort toward achieving compliance. Examples of notable settlements discussed include the City of Sacramento s agreement to spend 20% of transportation funding on curb ramps, sidewalks and crosswalks over a 30-year period in order to settle a discrimination suit [Barden v. Sacramento]. The City of Los Angeles s agreement to spend $1.4 billion on access remediation over 30 years was due to similar circumstances [Willits v. City of Los Angeles]. A notable ongoing discrimination case against the City of Seattle involves allegations of failure to provide curb ramps serving public accommodations, omission of curb ramp improvements in street overlay projects, and failure to maintain existing infrastructure to the point that it is unusable by those with disabilities. However, a case involving the City of San Francisco provides evidence supporting the team s recommendation to improve the State s compliance documentation in that the court found in the favor of the City on the basis of demonstrated progress toward achieving the remediation goals set forth in its transition plan. Having a detailed and regularly updated remediation plan with transparent operation and consistent implementation were cited as key factors in preventing settlements or plaintiff awards in discrimination litigation. Page 8 of 14

116 Workshop 6: Technical Prioritization The Team gave an August 2016 discussion of improvements to the 2003 inventory s ranking scheme using a new dynamic weighted average ranking scheme to determine the relative severity of an element s deficiencies against other collected elements. Curb ramp and transit elements, recorded as point entities in the PAI, would be evaluated individually based on the various criteria pertaining to their technical compliance (severity score) and proximity to nearby pedestrian activity generators (activity score). An overall element ranking system combining an element s severity and activity scores, as shown in Figure 4, was identified to be a critical component in drawing distinction between collected features in order to guide meaningful decisions during the project planning process. Figure 4 Dynamic Ranking System A similar approach to ranking sidewalks (logged as linear elements in the PAI) was explained using the severity of the individual deficiencies found along a given sidewalk segment to determine the overall segment severity. An alternative static severity ranking system (Figure 5), where severity is judged at the time of collection by field personnel similar to the 2003 inventory methodology was compared against the dynamic model. Page 9 of 14

117 Figure 5 Static Ranking System The State s past experience has shown that static element rankings tend to lose value over time due to the inability to adapt to changing regulations or the ever-changing landscape where activity generators are constantly being built, relocated or replaced through the course of regular development. The State selected the team s dynamic scoring system due to the benefits of finetuning that become available during post-processing and the flexibility to adapt to new regulations in the future. The team recommended basing compliance determinations in postprocessing off of Proposed Accessibility Guidelines for Pedestrian Facilities in the Public Rightof-Way (PROWAG) requirements where applicable, deferring to the ADA Standards for Accessible Design (ADASAD) elsewhere, as the PROWAG is widely considered best guidance for public right-of-way assets. Workshop 7: Planning and Project Development (Implementation) The team led a discussion in August 2016 regarding funding allocation approaches that utilize the PAI dataset components. The talk explained the funding allocation decisions are legally required to be planned for maximum benefit and thereby must only use the element severity ranking data when defining future projects, dedicated remediation programs, and maintenance activities. Consequently, factors such as population, density or other measures of urban vs. rural conditions cannot be the basis of funding allocation. The dynamic ranking model was designed to accommodate funding analysis separate from project planning analysis to facilitate the needs of both tasks with a common dataset. Page 10 of 14

118 The team introduced the concept of a corridor segment, or a micro-linear grouping, of collected elements from block-to-block as the smallest practical measure of potential project limits. Similarly, a corridor was defined as a macro-linear grouping of corridor segments (typically bound by intersections with other State routes). An example of corridor segment delineation along Wurzbach Parkway (FM 1502) in San Antonio, TX is shown in Figure 6. Collected data along the FM 1502 corridor from FM 1535 to FM 2696 is broken into 7 corridor segments shown in blue. Figure 6 Example of Corridor Segment Delineation The intent moving forward was to establish a grouping mechanism for project planners to use in identifying where routine projects (full reconstruction) are best suited to address compliance issues versus dedicated remediation projects (remediation) versus maintenance (minor repairs). Corridor ranking was explained as the weighted average of the constituent elements within the corridor limits, which allows for corridor-to-corridor comparison on a single scale founded on the severity and activity scores of its parts. The corridors with greatest aggregate severity scores will be selected for funding. Among those corridors, those with highest combined severity and activity would set the priority order of remediation. The team recommended for discretionary smoothing of allocations to fit reasonably sized projects for contracting efficiency and cost effectiveness. Page 11 of 14

119 Workshop 8: Weighting, Costs, and Corridor Definition In October 2016 the team worked through an assignment of numeric factors to severity and activity score components based on State feedback given during Workshop 8 to define the mathematical formula to be used in determining severity and activity for an individual element. A key recommendation was to develop an element ranking mechanism that: 1. Does not rely on subjectivity, 2. Is scalable, and 3. Can be dynamically updated (post-collection) if compliance criteria changes The State requested the ability for planners to adjust the breakdown of severity point allocations assigned to an element where local topography dictates. For example, in areas of flat terrain, the measured values for sidewalk cross slope are expected to be within a very tight range (e.g., 1-3%) just above or below the 2% compliance threshold whereas areas of steep terrain are likely to record more varied cross slopes (e.g., 1-8%) for the same types of elements. Similarly, activity scores were requested to be calculated based only on available comparison datasets within the area of interest rural areas may not have access to the same level of mapped comparison features (i.e., GIS layers for transit, government buildings, employment, recreation, etc.) as urban areas. An element s activity score should not be penalized or overcompensated where comparison data is not available. The results of the discussion were put into an electronic anonymous survey that was re-circulated amongst the State stakeholder departments to solicit additional feedback. Responses received formed the basis of the default prioritization formula utilized by the team s planning tool deliverable in Workshop 11. Exportable prioritization tools were also developed to allow usermodifications to severity and activity score breakdowns with side-by-side comparison to the default ranking formula. Workshop 9: Public Outreach Focus Group The team and the State conducted a November 2016 focus group with stakeholders to gain input from related State agencies, engaged citizens, and key advocacy groups used to shape PAI policy decisions. Workshop 10: State Administration Recap A revisitation of topics covered through Workshop 9 aimed at summarizing the project s development, collection methodology, and key policy recommendations with the ultimate goal of gaining State administration approval for statewide collection. Pilot Study data was reviewed to guide resource allocation and required collection time determinations. The State approved the detailed collection approach at curb ramps, dense urban sidewalks, and urban transit (see Page 12 of 14

120 Workshops 3-4), limited collection methodology for sidewalks in light-density suburban settings, and to use District staff for collection in rural areas. Additionally, State administration requested to see a working prototype of the Web Application to be used by planners to view and analyze the collected data prior to proceeding with statewide collection. More detail was requested on how the end-user would view the dataset, select project limits, interpret corridor segment rankings and remediation costs, assign elements to planned projects, and track remediation for FHWA reporting. Workshop 11: Web Application Demonstration The team demonstrated a prototype of the GIS-based Web Application as the culmination of the decisions made in Workshops 1-10, soliciting feedback from State stakeholders with the Design Division, Office of Civil Rights, Public Transportation Division, San Antonio, Austin, and Dallas Districts. Separate demonstrations were held for the aforementioned stakeholders in June-July Additional 2-3 minute self-guided training videos were provided with a brief (~2 week) trial period after the workshop to allow the State personnel time to learn and experience the Web Application. As seen in Figure 7, the Web Application featured data overlays from the Statewide Planning Map in context with the accessibility dataset collected in the Pilot Study area; map and table views of the data; user-selection/search/filter tools; cost estimating and prioritization summaries with detailed templates for external analysis; and remediation status tracking features. Figure 7 Web Application Page 13 of 14

121 The team received feedback on how to improve the prototype to compliment or enhance existing State processes for project planning and compliance tracking. A revised Web Application is scheduled for delivery to the State in June 2018 incorporating feedback from Workshop 11 and from discussions regarding traffic operations and construction management. Statewide PAI Data Collection The State has procured three consultant contracts to implement the Statewide PAI collection effort. The State has been geographically divided into three regions and the collection will be divided into urban and rural areas where each consultant team will collect data for curb ramps, sidewalks and transit stops within the state s major metropolitan areas. First priority will be collection of curb ramp and transit stop data across the State. The teams will then begin the mapping and evaluation of the sidewalk system and finish with a more detailed survey of the system as required. The combined collection effort will form the complete PAI in support of the upcoming ADA Transition Plan, Curb Ramp Program Planning Document updates, and core project planning activities. Work is currently underway to finalize the data collection application and database to accommodate multiple firm and multiple team deployment. The application is also being modified to collect data relating to pedestrian signal equipment. Data collection will begin once the system is deployed. Page 14 of 14

122 Attachment I - Transition Plan Development ADA Accessibility Program Stakeholders Meeting

123 TRANSITION PLAN DEVELOPMENT Division and District Updates TxDOT ADA Accessibility Program Stakeholders Meeting November 16, 2017 Public Transportation Division November 16, 2017

124 PUBLIC TRANSPORTATION DIVISION Footer Text Date

125 Public Transportation Division Programs The TxDOT Public Transportation Division administers federally funded programs that support access to transportation in rural and small urban areas of the state. Programs specifically targeted for services to disabled populations and/or improve mobility are listed below: Federal Transit Administration (FTA) funded programs: 5304, Public Transit - Human Services Transportation Planning 5310, Enhanced Mobility of Seniors and Individuals with Disabilities Federal Highway Administration (FHWA) funded programs Transportation Alternatives Program (TAP) Transportation Alternative Set Aside Program (TASA) Public Transportation Division November 16,

126 5304, Public Transit-Human Services Transportation Plans Purpose: Public transit-human services transportation plans assure a more efficient and effective network of public transportation services for people in Texas, including individuals with disabilities, so that people can get to destinations as desired. Planning occurs at the local level; Texas has 24 planning regions Diverse stakeholder groups, including individuals with disabilities, in each region develop & adopt a unique plan for their region every 5 years. Each plan identifies: Unmet transportation needs, service gaps & inefficiencies for individuals with disabilities (and other groups) Corresponding strategies for addressing these unmet needs, gaps & inefficiencies TxDOT provides funding for development of these plans through the FTA section 5304 program funds. Public Transportation Division November 16,

127 5304, Public Transit-Human Services Transportation Plans The 24 planning regions just completed new 5-year plans this year; Implementation begins this fall Public Transportation Division November 16,

128 5304, Public Transit-Human Services Transportation Plans Funding for implementation of the Plans After the development of the 5 year plan, funding is provided for ongoing regional planning. Regional stakeholders: Monitor & measure progress of plans Refine their plans with any newly identified unmet needs, service gaps, or strategies to address Implement & evaluate demonstration projects to see if strategies are effective & replicable Connection to 5310, Enhanced Mobility for Elderly and Disabled Program These regionally coordinated plans provide a basis for programming efforts of the FTA 5310 Program, for Enhanced Mobility of Seniors and Individuals with Disabilities Any project receiving Section 5310 funds must show that it is derived from a public transit-human services transportation plan Public Transportation Division November 16,

129 5310, Enhanced Mobility of Seniors and Individuals with Disabilities Purpose: FTA s Section 5310, Enhanced Mobility of Seniors and Individuals with Disabilities Program provides financial assistance for transportation services planned, designed, and carried out to meet the special transportation needs of seniors and individuals with disabilities in small urban and rural areas of Texas. Funds are awarded competitively to agencies that are private non-profits and state or local governmental authorities that are approved by a state to coordinate services for seniors and individuals with disabilities Public Transportation Division November 16,

130 Section 5310 Goal and Accomplishments As stated in the federal circular, the goal of the Section 5310 program is to improve mobility for seniors and individuals with disabilities throughout the country by removing barriers to transportation services and expanding the transportation mobility options available. Funding goes to many elements of providing service, including: Purchase of accessible vehicles; accessible rides programs that increase access to fixed route and demand response services; Trip planning activities for customers Ride referrals Centralized information on specialized transportation services in the community Travel training to enable access to demand response and fixed route service accessible infrastructure such as curb cuts and bus stops. Public Transportation Division November 16,

131 Section 5310 Goals and Accomplishments Annual apportionments for the program are approximately $7.3 million. The Public Transportation Division initiates a program call for funding applications every 2 years following a statewide outreach effort. Majority of funds are used to provide service and/or facilitate access to service. Some specific examples of asset and/or infrastructure projects funded over the past 2 years, include: 48 accessible vehicles *vehicles purchased with Section 5310 funds must be accessible unless a waiver is granted Curb cut project in Abilene Accessible bus stops in San Marcos and Paris Automated stop announcements for Longview Public Transportation Division November 16,

132 Section 5310, Other ADA Concerns Expanding the availability of accessible service among existing public transportation providers and other transportation service providers Replacement of non-accessible vehicles in fleets Proper maintenance of vehicle lifts, announcing systems, mobility device securements Driver training in customer service Public Transportation Division November 16,

133 TAP & TASA Program Overview TxDOT s 2015 Transportation Alternatives Program (TAP) and 2017 Transportation Alternatives Set-Aside Program (TASA) provides funding from FHWA to construct a variety of alternative transportation projects that improve mobility for non-motorized users and mitigate congestion by providing transportation options. Eligible project activities include construction of on- and off-road pedestrian and bicycle accommodations (including conversions of abandoned railroads), infrastructure for non-drivers, access to public transportation, and Safe Routes to School infrastructure. TAP/TASA funds are awarded through a competitive Call for Projects administered by TxDOT. Eligible projects must be located in population areas of 200,000 or less to be considered for funding. Public Transportation Division November 16,

134 TAP & TASA Eligible Project Activities Eligible TAP/TASA project activities include: 1) Construction of sidewalks 2) Infrastructure improvements to provide safer routes to school 3) Infrastructure-related projects to improve safety for non-drivers 4) Construction of on-road bicycle improvements 5) Construction of an off-road shared use path 6) Conversion of an abandoned railroad corridor to provide a shared use path Public Transportation Division November 16,

135 TAP & TASA Program Goals TxDOT s 2015 TAP & 2017 TASA Program projects must be ADA-compliant and support TxDOT s safety, mobility, and connectivity goals. TxDOT s Program Guide encourages project sponsors to submit projects that: Enhance bicycle and pedestrian safety for people of all ages and abilities Improve safety, access, or mobility for individuals with disabilities Construct on-system improvements in support of TxDOT s ADA/Pedestrian initiatives Provide access to or between existing bicycle and pedestrian facilities, public transportation, or other mobility options Connect important community destinations (such as schools, employment, downtown/commercial/historic districts, medical facilities, and recreational areas) Contribute to the development of a statewide or regional bicycle route for tourism Contribute, as an independent element, to a larger public project/investment Public Transportation Division November 16,

136 2015 Awarded TAP Projects Note: Funding amounts represent only the federal match authorized and do not include the local match Public Transportation Division November 16,

137 2017 Awarded TASA Projects Note: Funding amounts represent only the federal match authorized and do not include the local match Public Transportation Division November 16,

138 Public Transportation Division Program Contacts FTA Funded Programs Section 5304, Public Transit-Human Services Transportation Planning Steve Wright, (512) , Section 5310, Enhanced Mobility of Seniors and Individuals with Disabilities Kari Banta, (512) , FHWA Funded Programs Transportation Alternatives Program (TAP) & Transportation Set-Aside Alternatives Program (TASA) Teri Kaplan, (512) , Bonnie Sherman, (512) , Public Transportation Division November 16,

139 MAINTENANCE DIVISION Maintenance Division November 16, 2017

140 Safety Rest Areas Renovation Projects Completed in 2017 Maintenance Division November 16,

141 Safety Rest Areas Nolan County Issue: Handrails Maintenance Division November 16,

142 Safety Rest Areas Nolan County No guard rails at steep incline Maintenance Division November 16,

143 Safety Rest Areas Nolan County Maintenance Division November 16,

144 Safety Rest Areas Kerr County Issue: Handrails Maintenance Division November 16,

145 Safety Rest Areas Kerr County No handrails are a potential hazard for elderly, blind, or physically challenged. Maintenance Division November 16,

146 Safety Rest Areas Kerr County Maintenance Division November 16,

147 Safety Rest Areas Renovation Projects to be Completed in 2018 Maintenance Division November 16,

148 Safety Rest Areas Brooks County Issue: Tree obstructions along accessible paths of travel Maintenance Division November 16,

149 Safety Rest Areas Brooks County Tree grown into accessible path of travel Maintenance Division November 16,

150 Safety Rest Areas Brooks County Completed construction drawings show widening path of travel to meet ADA requirements. Maintenance Division November 16,

151 Safety Rest Areas Wise County Issue: Handrails Maintenance Division November 16,

152 Safety Rest Areas Wise County Maintenance Division November 16,

153 Safety Rest Areas Wise County Construction drawing showing new accessible handrail. Maintenance Division November 16,

154 Safety Rest Areas Gillespie County Issue: Accessible parking, accessible paths of travel Maintenance Division November 16,

155 Safety Rest Areas Gillespie County 1. No drop off striping 2. No signage 3. Improper slope Maintenance Division November 16,

156 Safety Rest Areas Gillespie County Potential hazard: Need accessible path to building from accessible parking. Maintenance Division November 16,

157 Safety Rest Areas Gillespie County Potential tripping hazard. Maintenance Division November 16,

158 New Safety Rest Areas West Pecos County Issue: Texas accessibility inspection by registered accessibility specialist Maintenance Division November 16,

159 New Safety Rest Areas West Pecos County Maintenance Division November 16,

160 New Safety Rest Areas Hopkins County Issue: Texas accessibility inspection by registered accessibility specialist Maintenance Division November 16,

161 New Safety Rest Areas Hopkins County Maintenance Division November 16,

162 Questions? Maintenance Division November 16,

163 COMMUNICATIONS DIVISION Support Services Division November 17, 2017

164 Website governance Phase I Website accessibility update Upgraded website: TxDOT.gov with updated software published July 28, Site is now accessible via mobile devices. Training: Staff training on new content management system s features is underway. The training includes more information about efforts to improve accessibility. Governance: Updated internal Web Publishing Guidelines to ensure TxDOT.gov and other TxDOT-owned sites are ADA-compliant. Accessibility: Web Publishing Guidelines include section on accessibility to ensure that staff are aware of requirements. Communications Division November 16,

165 Website governance Phase II Application standards: Identifying applications and software needed to comply with accessibility standards. User engagement: Talking to TxDOT.gov users about how we will improve our site to accommodate their needs through face-to-face meetings, webinars, surveys and more. Section 508: Will monitor and implement changes to accessibility standards required of state agencies. Outreach: Will continue to engage our constituents about what works and what doesn t on TxDOT.gov, and make appropriate adjustments. Ongoing improvements: Accessibility doesn t stop when all information is accessible it s a continuous improvement effort to which TxDOT is wholly committed! Communications Division November 16,

166 Website governance Ongoing improvement Accessibility is a jog, not a sprint! But we re picking up the pace! Communications Division November 16,

167 SUPPORT SERVICES DIVISION FACILITIES CAPITAL PROGRAM & ADA COMPLIANCE Robin Cappello, Director Facilities Planning and Management Warren Rose, Branch Manager Statewide Facilities Management Footer Text Date

168 TxDOT Facilities Capital Program Project Type Funding Requires Legislative Authorization Land Acquisition Capital Improvement Yes New Construction Capital Improvement Yes Deferred Maintenance Capital Improvement Yes Project Maintenance & Minor Repair Operating Funds No Dallas District Headquarters Administration Building Renovation Brownwood District Headquarters Administration Building Renovation Gonzalez Maintenance Office Roof Replacement Support Services Division November 16,

169 TxDOT Facilities Capital Program Facilities Portfolio (2,686 Total) Total # of Facilities over.5 FCI (511 Total) TxDOT Locations FCI Facilities Portfolio Average Office/ Laboratories Equipment Shops/ Warehouses FCI Material Storage 1, *Facility Condition Index is the total repair cost divided by the total replacement cost. FCI > 0.5 generally indicates it is more cost effective to replace a facility than to repair. Area Engineer Bldg. #10807 Tyler District, Tyler (North) Maintenance Special Crews Building Condemned Maintenance Bldg. # Dallas District, Dallas (South) Area Engineer FCI: 1.13 SF: 2,553 Area Engineer Bldg. # Dallas District, McKinney FCI:.91 SF: 1,824 Support Services Division November 16,

170 TxDOT Facilities Capital Program Facilities Condition Bring up to code Deferred Maintenance, PM & MR, Hurricane Harvey Rockport Maintenance Facility Demolished Deferred maintenance issues Support Services Division November 16,

171 TxDOT Facilities Capital Program Facilities Condition Bring up to code ADA Deficiencies Support Services Division November 16,

172 TxDOT Facilities Capital Program ADA Accessibility Assessment Phase 1 - Pilot Project - complete AUS District State Headquarters Phase 2 - Statewide Project scheduled for January through July 2018 Support Services Division November 16,

173 TxDOT Facilities Capital Program ADA Accessibility Assessment Project Project Planning & Implementation by Biennium Detail of Legend Support Services Division November 16,

174 Facilities Capital Master Plan Overview Target for land acquisition Support Services Division November 16,

175 INFORMATION MANAGEMENT DIVISION Support Services Division November 16, 2017

176 Information Management Division (IMD) - Accomplishments Appointed a secondary ADA liaison Report quarterly updates of data to the FHWA Annual Dashboard Ensure that employee ADA needs are addressed through cooperative work with our Human Resources and Civil Rights Division Ensure that equipment and software needs associated with approved ADA requests are coordinated with our Human Resources, Civil Rights and Procurement Divisions to ensure that needs are met in the most effective, efficient and timely manner possible Information Management Division November 16,

177 Information Management Division (IMD) - Accomplishments Provide technical support to our Communication Division to ensure that our web presence remains compliant with all current and future Section 508 web accessibility requirements Establish a project to review accessibility across all of our applications Evaluated work areas for potential ADA requirements Information Management Division November 16,

178 Information Management Division (IMD) - Goals Continue to actively attend all ADA trainings, meetings, and outreach events Upon request, provide assistance to our customers related to ADA questions and requests Work with and collaborate with other division ADA liaisons on ADA program initiatives Work with our Human Resources and Civil Rights Divisions to identify standardized IT solutions for ADA needs Information Management Division November 16,

179 Questions? Information Management Division November 16,

180 James Pennington Operations Section Director Information Management Division Information Management Division November 16,

181 AUSTIN DISTRICT ADA Accomplishments Footer Text Date

182 DISTRICT ACCOMPLISHMENTS Organizational TxDOT District Facilities Training Roadway Projects Austin District November 16,

183 DISTRICT ACCOMPLISHMENTS: ORGANIZATIONAL Organizational Changes at the Austin District Assigned an ADA liaison Formed an ADA committee Conducted quarterly ADA committee meetings Conducted an ADA self evaluation at the District Planned for multiple Outreach Events and took part in the ADA Fair Created a sub recipient list Austin District November 16,

184 DISTRICT ACCOMPLISHMENTS: ORGANIZATIONAL District ADA Liaison: Amro Gaber(Central Design) District ADA Committee: Tracey Janus (Environmental) Tracy Cooper (Construction) Lori Wagner (Maintenance) Bruce Byron (Public Involvement) James Chamberlin(District Design) Mahendran Thivakaran(Traffic) Austin District November 16,

185 DISTRICT ACCOMPLISHMENTS: TxDOT FACILITIES TxDOT Facility Changes: Developed an ADA site improvement plan for District HQ Area and Maintenance Supervisors assembled an inventory on all of District facility ADA barriers Minor barriers identified and corrected Major barriers identified and plan in place to correct Austin District November 16,

186 DISTRICT ACCOMPLISHMENTS: TxDOT FACILITIES Austin District HQ Site Improvement Plan Austin District November 16,

187 DISTRICT ACCOMPLISHMENTS: TRAINING Training on ADA Compliance Two plan review employees attended the Texas Accessibility Academy Internal Design Tips Class held at District HQ on the difference between PROWAG and TAS Guidelines Brown bag presentation by Pape-Dawson on ADA Access and Curb Ramp Program Austin District held an Adjunct Design and Construction for Pedestrian Access Class(DES 122) Austin District November 16,

188 DISTRICT ACCOMPLISHMENTS: ROADWAY PROJECTS Overview In Federal FY 2017(October 2016 to September 2017): 24 roadway projects totaling over $4,000,000 worth of pedestrian elements that completed construction 11 of the 24 construction projects involved RAS/TDLR inspection 50 design projects that had at least $50k of pedestrian elements finalized and submitted for bidding and construction in FY 2017 Austin District November 16,

189 DISTRICT ACCOMPLISHMENTS: ROADWAY PROJECTS FM 972 Walburg Full Rehab Project Additions: Sidewalk throughout Walburg s town limits Handrails on all drop offs near culverts Accessible routes and parking adjacent to the Community Center Building Accessible routes and parking adjacent to the German Restaurant Austin District November 16,

190 DISTRICT ACCOMPLISHMENTS: ROADWAY PROJECTS Walburg Community Center Building Walburg German Restaurant Austin District November 16,

191 DISTRICT ACCOMPLISHMENTS: ROADWAY PROJECTS Walburg Community Center Building Parking On Map Austin District November 16,

192 DISTRICT ACCOMPLISHMENTS: ROADWAY PROJECTS Walburg Community Center Building Parking Detail Austin District November 16,

193 DISTRICT ACCOMPLISHMENTS: ROADWAY PROJECTS Walburg German Restaurant Parking on Map Austin District November 16,

194 DISTRICT ACCOMPLISHMENTS: ROADWAY PROJECTS Walburg German Restaurant Parking Detail Austin District November 16,

195 DISTRICT ACCOMPLISHMENTS: ROADWAY PROJECTS Overlay projects to include curb ramps: Directive from Bill Hale, TxDOT Chief Engineer to increase scope of work on overlay projects to include curb ramp work Multiple overlay projects letting in FY 2018 are now being reviewed to ensure crossings within project limits have ADA Complaint curb ramps Towns and cities all over the Austin District where we have overlay projects are being reviewed to see if we can add or retrofit curb ramps Austin District November 16,

196 DISTRICT ACCOMPLISHMENTS: ROADWAY PROJECTS Austin District November 16,

197 DISTRICT ACCOMPLISHMENTS: ROADWAY PROJECTS Case Study: US 281 and Jackson St Intersection in Burnet, TX Austin District November 16,

198 DISTRICT ACCOMPLISHMENTS: ROADWAY PROJECTS Case Study: US 281 and Jackson St, Southwest Corner Austin District November 16,

199 DISTRICT ACCOMPLISHMENTS: ROADWAY PROJECTS Case Study: US 281 and Jackson St, Southeast Corner Austin District November 16,