ADA Compliance Checklist Guidance

Similar documents
DELAWARE COUNTY SECONDARY ROAD DEPARTMENT POLICY AND PROCEDURE MEMORANDUM

Access Field Entrance Other Constructed Yes (Type)

COMMISSION POLICY POLICY #9.16

SCOPE OF SERVICES FIBER OPTIC NETWORK DESIGN CITY OF OVERLAND PARK, KANSAS


Development of Software Tools for ADA Compliance Data Collection, Management, and Inquiry

SPECIFICATIONS - DETAILED PROVISIONS Section Pre-Construction Audio Video Recording Above Ground Facilities C O N T E N T S

ARLINGTON COUNTY, VIRGINIA. County Board Agenda Item Meeting of September 20, 2014

CITY OF KIRKLAND TRAFFIC IMPACT ANALYSIS GUIDELINES

CITY OF DRAPER PROPERTY & PUBLIC RIGHTS OF WAY ENCROACHMENT PERMIT APPLICATION & AGREEMENT

PUBLIC WORKS ORGANIZATIONAL CHART

Overview September 7, 2017

ARLINGTON COUNTY, VIRGINIA. County Board Agenda Item Meeting of September 15, 2012

Design Manual. for the Installation of Network Nodes and Node Support Poles pursuant to Tex. Loc. Gov. Code, Chapter 284.

ARLINGTON COUNTY, VIRGINIA

Environmental Impact Questionnaire

TABLE OF CONTENTS. Section 2.0 GENERAL PLAN REQUIREMENTS 05/2011. Section 100 ROADWAY DESIGN 01/2016

Community Design Guidelines Document (CDG)

Work Type Definition

CITY OF TORONTO TELECOMMUNICATION TOWER AND ANTENNA PROTOCOL (Industry Canada Local Land-use Authority Consultation)

City of Tyler, Texas Design Manual for the Installation of Network Nodes and Node Support Poles pursuant to Tex. Loc. Gov. Code, Chapter 284.

Mailbox Policy for the Municipality of Fort Fairfield

TRAINING GUIDE. Lucity Mobile In Depth

Intelligent Transportation Systems (ITS)

OUR COMPLETE SPECIFICATION WORDING LIBRARY IS AVAILABLE ONLINE FOR DOWNLOAD IN PDF FORMAT AT VOLUME 2 DESCRIPTION

Request for FTE Design Exceptions & Variations Checklist

ATTACHMENT A. Appendix A. for the Installation of Network Nodes and Node Support Poles pursuant to Tex. Loc. Gov. Code, Chapter 284.

STUDY REPORT #1 ADDENDUM

DATE: September 2014 Project Sponsors Rachel Schuett and Transportation Team Transportation Demand Management (TDM) Data Collection

Advisor Advanced Pedestrian System (AAPS) Installation Guide

KANABEC COUNTY HIGHWAY DEPARTMENT Chad T. Gramentz, P.E. County Engineer 903 Forest Avenue East Mora, MN

Wire Communications Design jfm 07. An Inside Look at Outside Plant

CHARTER TOWNSHIP OF ALLENDALE, OTTAWA COUNTY, MICHIGAN WIRELESS COMMUNICATION FACILITIES APPLICATION

Geometric Layout for Roadway Design with CAiCE Visual Roads

Page 2D-12 Revised the following language in the last sentence on the page from; as shown in Figure 2D-3. To; as shown in Chapter 2H, Figure 2H-35.

Frequently Asked Questions

Director of Public Works/City Engineer. Secretary. Word Processor. Streets and Facilities Supervisor. Traffic Signal Technician.

How to submit a Mileage Expense Claim

Chapter 1 Introduction to Outside Plant

Installation of RSA/K&C Shallow Mount Bollards

Deltek Vision 7.6. Technical Overview and System Requirements: Advanced Deployment (150 or More Employees)

My Sysco Reporting Job Aid for CMU Customers. My Sysco Reporting. For CMU Customers (Serviced by Program Sales)

2009 MUTCD CONTENT Introduction Part 1 General Part 2 Signs Part 3 Markings Part 4 - Highway Traffic Signals Part 5 Traffic Control Devices for Low

Wireless Telecommunication Facility

Wireless Communication Device Use Policy

Study Area and Location District PSA Ward ANC Phase Description G Planned Connecticut Avenue Northbound at Military Road Northwest

SGI HUB Navigation Guide

CASE NUMBER: 15SN0646 APPLICANT: Bon Secours Richmond Health System

CODE OF PRACTICE FOR CITY INFRASTRUCTURE and LAND DEVELOPMENT ENGINEERING STANDARDS MANUAL SECTION 8

17. Microwave Collocation 17.1 General

Revisions to the Right-of-Way Management Ordinance for Wireless Providers Implementing SB1004

Nokia N9 How to. Issue 1

DATE: April 8, 2013 REPORT NO. CD TYPE OF REPORT CONSENT ITEM [ ] ITEM FOR CONSIDERATION [ X ]

SPECIFICATIONS - DETAILED PROVISIONS Section Pre-Construction Audio Video Recording Pipelines and Roadways C O N T E N T S

SharePoint Online 101

STAFF REPORT. Meeting Date: To: From: La Cienega Station. Subject: Attachments:

CASE 1 TWO LANE TO FOUR LANE DIVIDED TRANSITION GEO-610-C NOT TO SCALE GEOMETRIC DESIGN GUIDE FOR MATCH LINE LINE MATCH. 2 (0.6m) shoulder transition

CITY OF CORINTH, TEXAS WIRELESS SERVICES (SMALL CELLS) DESIGN MANUAL

Applicant Type (Conditional Use Permit, Variance, Tract Map, etc.): Applicant: Address: Phone(s): Fax:

July EDGAR Filer Manual (Volume I)

Alberta One-Call Online Request Process

MoDOT s 3D Design Implementation, Electronic Deliverables, and E-Construction. Ashley Buechter, P.E. MoDOT CADD Support Engineer

Installation Quick Start Guide for in2/iccu-s System

PLANNING COMMISSION WORK SESSION

Frequently Asked Questions (FAQ):

{ Mobile Printing Send Print Jobs from any Location }

Verification Plan: Mitchell Hammock Road. Adaptive Traffic Signal Control System. Prepared by: City of Oviedo. Draft 1: June 2015

Table of Contents. Note to Self-Paced Users of the Day 2 Seminar Handbook. Notices 1. Quick Reference 2. Seminar Outline 14

Table of Contents 6.1 CORRESPONDENCE

CHAPTER WIRELESS TELECOMMUNICATION FACILITIES

EASTSIDE CITY OF BELLEVUE/ PRIVATE PRIVATE PRIVATE MULTI-PRIVATE MULTI-PRIVATE

Automatic 3D control system for SP 15 / SP 15 i / SP 25 / SP 25 i. AutoPilot 2.0

Introduction. We are excited about the possibility of bringing Google Fiber to your city and look forward to working with you.

ECONOMIC DISCLOSURE STATEMENT AND AFFIDAVIT (EDS) The web link for the Online EDS is

City Avenue District. City Avenue Rezoning Workshop January 25, :30 p.m. Board of Commissioners

STREET EVENT PERMIT APPLICATION FORM LOW & HIGH IMPACT EVENTS

USER GUIDE: NMLS Course Provider Application Process (Initial)

GREEN POINT CITY IMPROVEMENT DISTRICT IMPLEMENTATION PLAN

Printing Solutions for Higher Education. Secure, on-premise mobile printing platform

SGI HUB Navigation Guide

Mn/DOT CADD DATA Standards General Information

PROGRAM 1 MANAGEMENT, COMMUNICATION & OPERATIONS ACTION STEPS RESPONSIBLE FREQUENCY per year

NATIONAL DEMOLITION ASSOCIATION PROJECT PRE-START SURVEY

MICHIGAN DEPARTMENT OF TRANSPORTATION SPECIAL PROVISION FOR MICROWAVE VEHICLE DETECTION SYSTEM

HangarStack User Guide Version 1.41 Build 41

1. YOUR TEACHER WILL MAKE THE NECESSARY FILE AVAILABLE TO YOU THROUGH ONE OF A VARIETY OF METHODS. MANY

Useful Information for App Verification

SECTION 115 MATERIALS CERTIFICATION SCHOOLS PROGRAM

Electronic Appraisal Delivery (EAD) Portal. FHA EAD General User Guide

Reporting Period Information SMR for Standard Discharge Permittees Help sheet for the Industrial Online Reporting System

EXHIBIT 2. [Revisions to Division II of the San Francisco Transportation Code.] Resolution amending San Francisco Transportation Code, Division II, by

EXPENSE Training Guide. Quick Start Guide

The Municipality of Anchorage ProjectDox Applicant User Guide

NOTE ACCT #41211 MTR # ACCT #41212 MTR # ACCT #41210 MTR # ACCT #41213 MTR # ACCT #41209 MTR # ACCT #41214 MTR #728841

ORDINANCE NO APPROVING A MAILBOX ORDINANCE FOR SHAWANO COUNTY

TRUCK PARKING STALL DESIGNER'S NOTES:

The University of British Columbia Board of Governors

Web Portal Manual. For Self-Managing Clients. manawanui INDIVIDUALISED FUNDING SUPPORT

GENERAL REGULATIONS TARIFF CONTENTS

How to Add a Claim for Mileage or Travel Expense

Transcription:

V2.0 [8/25/2017] ADA Compliance Checklist Guidance ACCESSIBLE PEDESTRIAN SIGNALS [APS] All* projects from 2014 and onward with ADA work including carryover projects need to follow this guidance and compliance forms need to be entered electronically *Projects completed in 2013 and before can be submitted in paper checklist that was published before the electronic version.

Contents INTRODUCTION... 1 Key Points... 1 1. Filling out the right SP Number... 2 2. Determine the intersection names... 2 3. City... 2 4. District... 2 5. Construction Year... 2 6. Quadrant... 2 7. Push Button Orientation... 3 8. Push Button Landing... 3 9. Distance from Crosswalk Edge... 3 10. Distance from Push Button to Back of Curb... 3 11. Distance between Push Buttons... 4 12. Push Button Height... 4 13. Push Button Side Reach... 4 14. APS Compliance... 4 15. Non-Compliant Explanation/Reason... 4 16. Maintenance Access Route... 5 17. Push Button Placement... 5 18. Hand Holes... 5 19. Push Button According to Plan... 6 20. Printed Name... 6 21. Printed Date... 6 22. Information Accuracy... 6 23. Submission... 6 APPENDIX... 7 Figure 1: APS Guidance (1)... 7 Figure 2: APS Guidance (2)... 8 Figure 3: Push Button Height... 8 Figure 4 Intersection and Quadrant identification (1)... 9 Figure 5 Intersection and Quadrant identification (2)... 9 i

INTRODUCTION The APS Compliance Checklist form runs complementary to the Curb Ramp Compliance Checklist forms. The primary purpose of moving the checklist forms to an online database is to reduce processing error, paper waste, and staff hours repetitively filling out forms. For more information such as step-by-step guide on accessing the SharePoint form library or the Frequently Asked Questions (FAQ) section, please refer to http://www.dot.state.mn.us/ada/pdf/adacompliancechecklistguidanceforcurbramps.pdf Key Points a) MnDOT employees are able to access the ADA SharePoint Library by default using their state account credentials. Local agency staffs or Consultants will have to request for access to SharePoint following the instructions here: http://www.dot.state.mn.us/ada/pdf/ada-sharepoint-site-howto.pdf b) Submit forms electronically for all compliant AND noncompliant ramps including their redo s Turn in copies of all noncompliant ramp forms to the project engineer as well. If any portion of a ramp is non-compliant, be sure to document the pre-construction and post-construction ramp conditions. If the ramp could have been constructed compliant but the Contractor failed in constructing the ramp in accordance with Special Provisions 1803 Special Project ADA Requirements, it is the Contractor s responsibility to rebuild the ramp at the Contractor s expense. c) The online compliance form can only be used with an internet connection. If forms are to be used in the field, ensure there will be a signal at the project location before utilizing mobile devices/tablet (e.g. ipad) for form submission. d) Compliance checklists should be done weekly (or at least monthly) as project progresses and submitted to SharePoint. e) For projects located in areas with limited connectivity (weak signal/no internet), print out the PDF compliance checklist forms and fill it out on site. Enter all the acquired information on SharePoint (as shown in the next section) when internet is available. Download the form here: http://www.dot.state.mn.us/ada/pdf/pdfcurbrampform.pdf f) DO NOT use Safari browser (the default browser for Apple devices) on ipads (or any other tablet that uses Safari) to fill out the compliance checklist form. The form may work but any attempt at uploading attachment(s) will crash the form. Alternatively, you can download Google Chrome (tested) or any other browser of your preference off App Store. g) Refer to http://www.dot.state.mn.us/ada/construction.html for sample filled forms. Do not submit incomplete forms as it will be deleted and you will be asked to submit another one. Page 1

1 2 3 4 5 Figure 1 - APS Form Header 6 1. Filling out the right SP Number Depending on the plan sheet, key in the relevant SP number that has the intersection associated with it. If it is a state aid project, enter the SAP number. 2. Determine the intersection names State the intersection by combining the name of the street and trunk highway where the curb ramp is located. If there are no intersections, place the nearest landmark for easier identification through the use of Google Maps or similar web map services. Refer to Appendix for visual aid on how the intersections are named. 3. City Fill in the name of the city the ramp is located in. 4. District Put in the district number here depending on where the project is situated. For Metro, key in M. 5. Construction Year Enter the year that the APS was installed/constructed on in yyyy format. 6. Quadrant Determine the quadrant of the related curb ramp by facing True North. For Island/Pork Chop, Median, or Mid-block put <Quadrant Here>"Island/Median/Midblock" e.g. SE Island. Exception is allowed for mid-block along loop or roundabout that is difficult to be assigned a specific ordinal (NW, NE, SW, and SE) or cardinal direction (N, W, E, and S). In this situation, numbers are applicable should it compliment the intersection description. Refer to Appendix for visual aid on how the quadrants are determined. Page 2

7 8 9 10 11 12 13 Figure 2 APS Compliance Form (cont. 1) 7. Push Button Orientation When facing the intersection, the push button for the crosswalk on your left should also be located to your left on the outside edge of the crosswalk, and the push button for the crosswalk on your right should be located to your right on the outside edge of the crosswalk. The push button face should also be aligned parallel with the direction of travel. Refer to Appendix for visual clarity. 8. Push Button Landing The push button shall have a 4 X 4 landing adjacent to the face of the push button with less than a 2% cross slope in all directions. Center the push button on the landing if possible to do so without violating any of the requirements in the Special Provisions. The landing must be connected to the pedestrian access route. Refer to Appendix No.1 for visual clarity. 9. Distance from Crosswalk Edge The push button shall be offset up to 5 feet maximum from the lateral projection of the outside edge of the cross walk. Refer to Appendix No. 1 for visual clarity. 10. Distance from Push Button to Back of Curb The push button shall be 1.5 feet to 10 feet from the back of curb and ideally it will be approximately 6 feet from the back of curb. Refer to Appendix No. 1 for visual clarity. Page 3

11. Distance between Push Buttons The push buttons should have at least 10 feet of separation between them. If located on a pork chop/island, the minimum separation between the push buttons should be at least 6. Refer to Appendix No. 1 for visual clarity. 12. Push Button Height The push button(s) shall be at a height of 42. With MnDOT approved extension bracket, the push button height on signal poles shall be 42. Refer to Appendix No. 3 for visual clarity. 13. Push Button Side Reach The push button side reach measured perpendicular to the button face unobstructed at ground level should be 0 but is allowed up to 10. 14 15 16 18 17 Figure 3 APS Compliance Form (cont. 2) 14. APS Compliance If any of these standards are violated and the compliance shows up as Non-Compliant after clicking the Check button, provide an explanation describing which parameters were violated and why. Provide additional attachment as needed (file size does not exceed 6MB) but make sure to NOT use Safari browser on tablet such as ipad to upload attachment. 15. Non-Compliant Explanation/Reason If APS system shows up as non-compliant, provide explanation here and check the necessary box(es) located below (Topography, Utilities, Structure, Contractor, MnDOT). The following are details for each failure option. Page 4

i) Topography The landing couldn't be constructed to compliance because of the surrounding topography such as elevated road slopes or steep existing flow line. ii) iii) iv) Structure(s) Push button couldn't be constructed to compliance due to existing structure such as doorways, buildings, steps, street sign and etc. One example would be walkway attempting to tie in the nearby entrance/step and reducing space for compliant push button construction. Utilities Existing utilities in the area that could not be moved as part of the project prevented the push button from being installed/constructed compliantly. Example of utilities could be from both surface or underground utilities such as power poles, fire hydrants, traffic signal poles, manholes, vaults, and etc. Contractor The push button could have been constructed compliantly, but the contractor did not properly construct the push button in accordance with provision 1803 Special Project ADA Requirements. If any compliance standards are not met due to contractor performance, REWORK IS REQUIRED before the project is substantially complete. See Specification 1503 (Conformity with Plans and Specifications) for further justification. v) MnDOT Gave guidance that resulted in a noncompliant facility (Plans, Inspection or Surveys). REWORK IS REQUIRED. 16. Maintenance Access Route The Maintenance Access Route (MAR) has been mentioned in bubble note No.2 in the Appendix Figure No. 2. Provide a MAR wherever possible for snow removal purposes. A MAR requires minimum 6 clear distance along the PAR between a push button station and any obstructions, including buildings, v-curb, electrical foundations, signal cabinets, or another push button. 17. Push Button Placement The button should be placed 2 feet minimum from both ramp grade break and back of walk for accessibility purposes. For visual on how the push button should be placed, please refer to the Appendix Figure No. 2. 18. Hand Holes Newly constructed hand-hole(s) should always be placed outside of the PAR. Page 5

19 22 20 21 23 Figure 4 - APS Compliance Form (cont. 3) 19. Push Button According to Plan Determine if the push buttons are placed according to plan details or changed in the field to meet compliance. 20. Printed Name Fill in the name of the person who gathered/filled out the information. 21. Printed Date Fill in the date when the form was filled. 22. Information Accuracy Check the box to indicate that all information entered is gathered as is from the field without any unauthorized modification. 23. Submission Click the button Submit to SharePoint Library to upload the form to ADA Form Library. Page 6

APPENDIX The bubble note in each figure represents the required data on the APS compliance checklist form. Numbers on figure and on DESCRIPTION the APS form 1 Push button orientation 2 Push button landing 3 Distance from crosswalk edge 4 Distance from back of curb 5 Distance between push buttons 9 Maintenance access route (MAR) 10 Distance of push button(s) to front and back of landing Figure 1: APS Guidance (1) Page 7

Figure 2: APS Guidance (2) Figure 3: Push Button Height Page 8

Figure 4 Intersection and Quadrant identification (1) Figure 5 Intersection and Quadrant identification (2) Page 9