DocID #77310v2
DRAFT On-Street Accessible Parking
Program Policy
Contents
Policy Statement .............................................................................Error! Bookmark not defined.
DRAFT On-Street Accessible Parking Program Policy .............................................................. 1 Purpose and Intent....................................................................................................................................................2 Scope ....................................................................................................................................................................2 Authority ......................................................................................................................................................................2 Definitions ...................................................................................................................................................................2 Background and Policy Context ...........................................................................................................................3 Relationship to Other City Plans and Programs........................................................................................3 Program Overview ....................................................................................................................................................4 Application and Workflow Process.......................................................................................................................4 Step 1. Submission .............................................................................................................................................4 Step 2. Review ....................................................................................................................................................5 Step 3. Decision and Notification.................................................................................................................. 7 Step 4. Implementation.................................................................................................................................... 7 Step 5. Appeals Process .................................................................................................................................. 7 Step 6. Closeout.................................................................................................................................................8 Applicant Fee..............................................................................................................................................................9 Eligibility and Site Selection Criteria.............................................................. Error! Bookmark not defined.
Applicant Eligibility...................................................................................... Error! Bookmark not defined.
Site Selection ................................................................................................ Error! Bookmark not defined.
Design Standards ................................................................................................ Error! Bookmark not defined.
Use, Enforcement, and Maintenance............................................................. Error! Bookmark not defined.
Use ................................................................................................................... Error! Bookmark not defined.
Enforcement.................................................................................................. Error! Bookmark not defined.
Maintenance and Removal ........................................................................ Error! Bookmark not defined.
Administration, Data Tracking, and Reporting.................................................................................................10 Departmental Responsibilities ......................................................................................................................10 Data Tracking.....................................................................................................................................................10 Public Reporting................................................................................................................................................10 City of Richmond Draft On-Street Accessible Parking Program Policy | 2 DocID #77310v2
Purpose and Intent
The City of Richmond is committed to providing equitable, consistent, and ADA-compliant access to on-street parking for people with disabilities. This policy establishes a standardized, transparent process for evaluating and implementing on-street accessible parking spaces (commonly known as "blue curb" spaces) within the City's public right-of-way, consistent with the applicable City of Richmond General Plan and the City's ADA Transition Plan, and establishes clear roles for all responsible departments and a formal application workflow from submission through appeals.
Scope
This policy applies to all requests for on-street accessible parking spaces within the City of Richmond public right-of-way. It does not apply to off-street parking facilities, parking within private developments, or parking within state or federal right-of-way.
Authority
This policy is adopted pursuant to California Vehicle Code Section 22511.7, 1 which authorizes a local
authority, by ordinance or resolution, to designate on-street parking spaces for the exclusive use of vehicles displaying a valid Disabled Parking Credential or disability license plate, and Section 22511.8, 2 which establishes the process by which local agencies respond to individual requests for such designations. Nothing in this policy shall be construed to limit the City's authority under applicable federal or state law, including the Americans with Disabilities Act of 1990 (ADA) and United States Access Board's Public Rights-of-Way Accessibility Guidelines (PROWAG). 3 Definitions
Definitions are as follows for key elements of this policy:
Access Aisle means the marked area adjacent to an accessible parking space that provides sufficient clearance for a person using a wheelchair, scooter, or other mobility device to enter or exit a vehicle. Access aisle dimensions shall conform to applicable ADA and PROWAG standards.
Applicant means any individual who submits an application requesting an on-street accessible parking space under this program. Submission of an application does not create an entitlement to installation of a space at any particular location. Block Face means one side of a city block, bounded by two consecutive intersections along a single street.
Block Perimeter means the four continuous block faces of a city block that a pedestrian can traverse without needing to cross a street. The block perimeter is the unit of evaluation used
1 Cal. Veh. Code § 22511.7 (West 2024),
https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=VEH§ionNum=22511.7 2 Cal. Veh. Code § 22511.8 (West 2024),
https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=VEH§ionNum=22511.8 3 USDOT Public Right-of-Way Accessibility Guidelines (PROWAG) (2011), R306.2: Public Right-of-Way Accessibility Guidelines (PROWAG) | FHWA
City of Richmond Draft On-Street Accessible Parking Program Policy | 3 DocID #77310v2
by the City to identify the most appropriate and feasible location for an accessible parking space in response to a given request.
Blue Curb Space — informal term for an On-Street Accessible Parking Space; the two terms are used interchangeably in this policy and in public-facing materials. Curb Ramp means an ADA-compliant sloped transition element connecting a sidewalk or pedestrian pathway to the roadway surface, providing a continuous accessible path of travel between an on-street parking space and the adjacent pedestrian network. Denial means a formal determination by the City that a request does not meet the criteria for installation of an on-street accessible parking space at any location within the evaluated block perimeter. A denial triggers the applicant's right to appeal. Disabled Parking Credential means a valid California DMV-issued parking placard or license plate issued to a person with a disability, as defined under California Vehicle Code Section 22511.5 et seq.
IMS (Infrastructure Management System) means the City's centralized tracking system used to log, manage, and report on requests submitted under this program, from initial submission through closeout. References in this policy to the "tracking system" or "centralized tracking system" mean the IMS.
On-Street Accessible Parking Space means a designated parking space located within the public right-of-way that is marked with blue curb paint and appropriate signage, reserved for the use of individuals displaying a valid Disabled Parking Credential. Such spaces are not exclusively reserved for any individual applicant.
Path of Travel means the continuous, unobstructed accessible route connecting an on-street accessible parking space to the sidewalk and adjacent destinations, consistent with ADA and PROWAG requirements.
Program means the City of Richmond On-Street Accessible Parking Program established by this policy.
PROWAG means the United States Access Board's Public Rights-of-Way Accessibility Guidelines, which establish accessibility standards applicable to pedestrian facilities in the public right-of-way, including on-street parking.
Background and Policy Context
This policy establishes a structured program that evaluates accessibility needs at the block-perimeter level, applies documented criteria to all requests, and supports ongoing coordination across City departments.
Relationship to Other City Plans and Programs
This policy shall be implemented in coordination with the following existing City plans and programs:
Americans with Disabilities Act (ADA) Transition Plan: Any updates or changes to the ADA Transition Plan shall be reviewed for consistency with this policy. Bicycle and Pedestrian Action Plan (BPAP): Corridor projects that modify roadway conditions relevant to accessible parking requests shall be communicated to Engineering staff administering this program.
City of Richmond Draft On-Street Accessible Parking Program Policy | 4 DocID #77310v2
Local Road Safety Plan (LRSP): Recommendations affecting on-street parking supply shall be considered in the context of accessible parking siting decisions. Curb Ramp Upgrade Program: Staff coordinating curb ramp installations shall consult with Engineering to identify any related accessible parking implications. Development Review: The City will proactively evaluate the need for accessible parking in conjunction with new development, roadway and complete streets projects and major maintenance projects, consistent with ADA and PROWAG standards.
Program Overview
The City of Richmond Public Works Department administers the On-Street Accessible Parking Program. The program is request-initiated: the Applicant applies by identifying a location where an on-street accessible parking space is needed. Each request triggers an evaluation of the full block perimeter to identify the most appropriate and feasible location, which may or may not be in the exact location requested.
The program applies a documented, objective evaluation framework to all requests. Decisions are informed by block-level context, long-term accessibility needs, and citywide curbside conditions.
The location and number of accessible parking spaces will balance accessibility needs with broader curbside demands, including general parking, loading, safety improvements, and multimodal uses.
Use
On-street accessible parking spaces installed under this program are available to any member of the public holding a valid California Disabled Parking Credential. Spaces are not exclusively reserved for the Applicant or any individual and may not be treated as private parking. The City shall communicate this clearly to applicants at the time of notification.
Enforcement
Accessible parking spaces installed under this program shall be enforced in accordance with Richmond Municipal Code Chapter 14.464 and applicable provisions of the California Vehicle Code.
Application and Workflow Process
The program follows a seven-step workflow. All phases are tracked in the City's centralized request tracking system called Infrastructure Management System (IMS). Each step has a designated responsible department, as described below.
Step 1. Submission & Applicant Eligibility
To be eligible to submit an application, an individual must:
4 City of Richmond Code of Ordinances, 14.46 – City Parking Regulations, https://library.municode.com/ca/richmond/codes/code_of_ordinances?nodeId=ARTXIVTR_CH14.46CIPARE City of Richmond Draft On-Street Accessible Parking Program Policy | 5 DocID #77310v2
1. Demonstrate a lack of accessible off-street parking at or immediately adjacent to residence or primary destination.
2. Be a City of Richmond resident or regularly use the requested location as a primary destination.
Submission of an application does not guarantee installation of a space at the requested location.
Eligible applicants will have their request evaluated under the criteria described in the Application and Workflow Process.
Requests for on-street accessible parking shall be submitted through the City's online submission portal. Walk-in or mailed submissions will be directed to the portal by City staff. Hard copies will be available for community members who are unable to submit electronically. Upon submission:
1. The request is automatically logged into the centralized IMS tracking system. Engineering Division staff logs hard copy requests into the IMS.
2. The Engineering Division receives an automated notification.
3. The Applicant receives an acknowledgment of receipt with an estimated review timeline of 14 days.
No application fee shall be collected unless and until the City Council adopts a separate fee resolution following required notice and public hearing. If an application fee is later adopted, any fee requirement shall be administered in accordance with that resolution. Required documentation at submission includes:
Requested parking location (address or nearest intersection). Applicant's residence address, if different from the requested location. Government-issued photo identification.
Valid Disabled Parking Credential (placard or license plate) issued by the California DMV.
Temporary placards are not eligible.
Description of functional accessibility need (e.g., mobility device used, required space type).
This information is used solely to determine the appropriate parking configuration and is not used to determine disability status.
Contact information (email required for notifications). Signature of property owner if the applicant is a renter. [IF A FEE IS ADOPTED BY SEPARATE CITY COUNCIL RESOLUTION: Proof of payment of the adopted application fee, unless waived or reduced pursuant to adopted fee waiver or reduction criteria.]
Step 2. Review & Site Selection
The Engineering Division of Public Works is responsible for evaluating each request using a standardized evaluation framework. Only complete submissions will be evaluated.
Evaluation criteria include, but are not limited to:
City of Richmond Draft On-Street Accessible Parking Program Policy | 6 DocID #77310v2
1. Availability of ADA-compliant curb ramps and access aisles at the requested location.
2. Lack of off-street accessible parking (e.g. driveway, garage, shared parking lot) available to the Applicant.
3. Existing on-street accessible parking on the block face.
4. Proximity to special-use destinations (hospitals, clinics, community facilities).
5. Existing curbside obstructions (fire hydrants, utility poles, planters, driveways).
6. Whether the required access aisle would encroach into the vehicular travel lane, if applicable.
7. Consistency with applicable ADA and PROWAG dimensional standards.
The review proceeds in three stages:
1. Initial In-Office Review. The Engineering Division reviews the request using a standardized site assessment checklist, virtual street review (i.e., referencing Google StreetView or similar), GIS data, and other available sources. The evaluation considers the full block perimeter and documents preliminary findings in the IMS tracking system.
2. Field Verification. One staff member will visit the site to measure curb ramps for ADA compliance and confirm that the candidate space meets required dimensions and is free of obstructions. A standard field checklist and assessment form will be used to facilitate a consistent approach to field verification (refer to Attachment A – Field Checklist and Attachment B – Site Assessment Example). Field findings are documented in the tracking system.
3. Determination. The Engineering Division summarizes the draft determination and shares it with the Operations Division to discuss before finalizing.
Site Selection
Site selection is guided by the block-perimeter evaluation approach. The City will identify the location within the block perimeter that best satisfies ADA requirements, physical feasibility, and overall accessibility benefit. This location may not be directly in front of the Applicant's residence.
Decisions are not made on a first-come, first-served basis. Instead, the City applies standardized, objective criteria consistently across all requests to ensure equitable and ADA-compliant outcomes.
Design Standards
All on-street accessible parking spaces installed under this program shall conform to current ADA Standards for Accessible Design and PROWAG requirements to the maximum extent feasible given existing roadway and curbside conditions. Design elements include:
1. Minimum space dimensions per ADA/PROWAG standards, including required access aisle width, if applicable.
2. Confirmed ADA-compliant curb ramp(s) providing a continuous accessible path of travel from the parking space to the adjacent sidewalk.
3. Blue curb paint marking and approved accessible parking signage per California Manual on Uniform Traffic Control Devices (CA MUTCD) standards.
4. Clearance from fire hydrants, driveways, intersections, and other obstructions per applicable standards.
City of Richmond Draft On-Street Accessible Parking Program Policy | 7 DocID #77310v2
Where full ADA compliance cannot be achieved due to existing physical constraints, the Engineering Division shall document the constraint and, where feasible, identify an alternative location within the block perimeter that meets standards.
Step 3. Decision and Notification
Upon completing the review, the Engineering Division makes a final determination for approval or denial and updates the tracking system accordingly:
Approval: The request is transferred to the Operations Division through the IMS tracking system. The Applicant is notified of preliminary approval with a description of the final determination and transfer of the application to the Operations Division.. If the request for onstreet accessible parking is approved, staff will draft and mail a letter to all residents on the block to inform them of the installation.
Denial: The Applicant is notified in writing with the specific reason(s) for denial and information regarding the appeals process, which involves City Engineer review. No appeal fee shall be collected unless and until the City Council adopts a separate fee resolution authorizing an appeal fee following required notice and public hearing.
For approved requests, the Engineering Division shall follow up with the Operations Division within 30 days of transfer if the tracking system has not been updated to confirm scheduling.
Step 4. Implementation
Upon receiving an approved request, the Engineering Division generates a work order to the Operations Division. The Operations Division will provide scheduling details for field installation and update the work order in the tracking system. The Applicant is notified of the potential installation date.
Possible outcomes of the implementation phase include:
Completed: Installation is carried out as scheduled according to the City's standard detail (see Attachment C – On-Street Detail); the work order is marked "Complete" and the IMS tracking system is updated.
Delayed: If field review and potential implementation is delayed due to staff availability, inclement weather or other issue, the Applicant is notified with a revised schedule. Denied Due to Field Constraints: If unforeseen field conditions prevent installation (e.g., utility conflicts, substandard pavement, sidewalk obstructions), the constraint is documented in the IMS tracking system, the evaluation checklist is updated for future reference, and the Applicant is notified. The request may be eligible for appeal with details shown below.
Step 5. Appeals Process
An Applicant whose application was denied may submit a written appeal within 60 calendar days of the denial notice. No appeal fee shall be required unless and until the City Council adopts a separate fee resolution authorizing an appeal fee following required notice and public hearing. The appeal must state the reason(s) the Applicant believes the denial should be reconsidered. Appeals will reopen the request in the IMS tracking system for re-evaluation.
City of Richmond Draft On-Street Accessible Parking Program Policy | 8 DocID #77310v2
The City Engineer will review the appeal considering the appeal request and the following factors:
Recently installed curb ramp or sidewalk infrastructure that may not have been reflected in the original review.
An expanded study area of up to two additional blocks beyond the original block perimeter. Updated on-street parking restrictions or curbside conditions in the vicinity.
Following re-evaluation, the City Engineer will issue a written decision either upholding or overruling the denial. A decision overruling the denial will return the application to Step 4. Implementation. A final decision upholding the denial closes the application. The Applicant is notified of the final decision in writing, including the reason for the decision. The decision is final and not appealable.
Step 6. Closeout
Once implementation is complete and the eligible appeals timeline has run its course or an appeal has been closed, the Operations Division updates the tracking system with the final status and the Applicant receives a final notification confirming completion and providing relevant information about the installed space. The request is then closed in the system for two years when renewal is required.
Step 7. Renewal, Maintenance and Removal
Renewal
This section applies to on-street accessible parking spaces installed following adoption of this policy.
Existing on-street accessible parking spaces installed before adoption of this policy will be reevaluated over time.
Renewal of the need for the on-street accessible parking space is required every two years, which corresponds with the permanent placard for people with a long-term or permanent disability that limits mobility. This placard is generally valid for two years and is automatically renewed by the DMV for most holders. The applicant will be sent a notification requiring them to respond for renewal. For applicants who do not respond, the Engineering Division will contact the applicant to confirm the continued need for the on-street accessible parking space. If the on-street accessible parking space is no longer needed then the Operations Division will remove the blue curb and associated sign.
Maintenance and Removal
The City shall maintain installed accessible parking spaces, including markings and signage, as part of routine right-of-way maintenance. The need for each space is subject to periodic review. A space may be removed or relocated under the following circumstances:
1. The space no longer meets ADA standards due to changes in adjacent infrastructure.
2. The space conflicts with an approved capital project, safety improvement, or other Cityinitiated right-of-way change.
3. Field conditions have changed such that the space is no longer feasible or beneficial.
4. The demonstrated need that supported approval no longer exists (e.g., the original Applicant no longer resides at or regularly uses the location), and removal has been requested by an City of Richmond Draft On-Street Accessible Parking Program Policy | 9 DocID #77310v2
adjacent resident in writing using a form to be published on the program webpage. In this instance, the original Applicant is contacted to determine if the space is still being used.
Prior to removal, notification will be sent to all residents on the block perimeter of the on-street accessible parking space and posted at the space itself. A 14-day appeal period for the determination will follow. If determined to be active or currently being used by others, the party that initiated the request for removal will be notified and the accessible parking space will remain in place. If determined to not be in use, the application will be approved and curb markings will be removed. The outcome of this process will be updated in the centralized tracking system.
In case of emergency utility work, roadway reconstruction, or some other identified public safety need, immediate removal or relocation of the space may occur without complete notification process.
Applicant Fee
The City may consider establishing a fee in the future to partially offset administrative costs associated with processing on-street accessible parking applications, including staff review time, field verification, and system tracking. No fee shall apply unless and until adopted by separate City Council resolution following required notice and public hearing.
Any such fee shall be established only by separate resolution of the City Council following notice and public hearing consistent with California Government Code Section 66016. 5 If the City Council adopts a fee by separate resolution, the following principles shall guide fee administration:
1. The fee, if established, shall be due at the time specified in that resolution and shall be nonrefundable, except where the City initiates a denial prior to completing any site review or as otherwise provided in the adopted fee resolution.
2. IF AUTHORIZED BY THE FEE RESOLUTION: The Director of Public Works shall establish criteria and procedures for fee waivers or reductions for qualifying applicants, which shall be published on the program webpage.
3. Any adopted fee amount shall be reviewed periodically and adjusted as needed to reflect actual program costs, subject to City Council approval.
While many peer cities do not charge for on-street accessible parking requests, the City may evaluate whether a fee is appropriate to offset a portion of staff time, field verification, system tracking, and implementation costs. Any proposed fee amount, fee waiver or reduction process, and effective date shall be presented to the City Council for separate consideration and shall not take effect unless adopted by City Council resolution following required notice and public hearing.
5 Cal. Gov't Code § 66016 (West 2024),
https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=GOV§ionNum=66016 City of Richmond Draft On-Street Accessible Parking Program Policy | 10 DocID #77310v2
Administration, Data Tracking, and Reporting
Departmental Responsibilities
Program administration is shared across the IT Department and two divisions of the Public Works Department:
IT Department: Manages the online submission portal and centralized IMS tracking system; ensures system capacity for application logging, work order tracking, and status updates. Engineering Division of the Public Works Department: Conducts all site reviews and makes approval/denial determinations; maintains the standardized evaluation checklist and coordinates with other City programs, as required.
Operations Division of the Public Works Department: Discusses draft determinations and appeals; executes approved installations; closes out completed or denied requests in the tracking system.
City Engineer: Manages the appeals process.
Data Tracking
All requests shall be logged and tracked in the City's centralized IMS system from submission through closeout or final denial and for the renewal/maintenance/removal phase. The tracking system shall capture, at minimum: submission date, applicant contact information, requested location, review findings, decision and date, installation date (if applicable), and final status.
Records containing personally identifying information shall be retained and managed in accordance with the City's records retention schedule and applicable privacy requirements.
Public Reporting
The City will publicly document and report on program activity to support accountability and transparency. An annual program report shall be published with other Public Works reporting, and include, at minimum:
1. Total applications received, approved, denied, renewed and withdrawn.
2. Average processing time from submission to decision and from approval to installation.
3. Number of appeals filed and outcomes.
4. A map or database of all active on-street accessible parking spaces citywide.
The annual report shall be made available on the City's program webpage and provided to the City Council.
Attachment A. Field Checklist
Attachment B. Site Assessment Example
Attachment C. On-Street Detail