Today’s Chart of the Day covers ADA Compliance
State highway sidewalk miles that are not compliant with ADA requirements
Percent of eligible state highway intersections with accessible pedestrian signals installed
Source: MnDOT Annual Transportation Performance Report 2012
Streets.mn is a non-profit and is volunteer run. We rely on your support to keep the servers running. If you value what you read, please consider becoming a member.
[…] highlighting pieces of MnDOT’s Annual Transportation Performance Report: Ride Quality, Compliance with ADA Requirements, and System Ownership. The other two charts compare projected ridership and capital costs for […]
streets.mn welcomes opinions from many perspectives. Please refrain from attacking or disparaging others in your comments. streets.mn sees debate as a learning opportunity. Please share your perspective in a respectful manner. View our full comment policy to learn more.
Thanks for commenting on streets.mn!
“Accessible Pedestrian Signals” — talking beg buttons, right? Are there any ADA-compliant signal setups that don’t involve beg buttons?
I’m sure that if the button only registered a person to talk for, it would be fine. (i.e. light will give walk anyways, just for standardization of interface)
I wonder if it means the pedestrian signals which have an audio component that lets blind people know when they can cross (“cross Snelling Avenue”) and/or helps guide them across the intersection (chirps on each side of the street)?
And this doesn’t even include the percentage of state highways which don’t have sidewalks at all (but still have 55 mph + speed limits).
The rural areas are a disaster in ADA terms.
There are no ADA compliant setups that do not include beg buttons. If you want to always provide a pedestrian phase, that’s still allowed, but there has to be a button there to talk and vibrate to you even if you don’t need to push it to get a Walk.
Actually, you can make the pedestrian phase talk *all the time*.
This is unpopular at night, understandably.