HB26-1320 · Bill · 2026 Regular Session · Colorado

Accessible Language Statutory Ballot Title Requirements

Concerning statutory requirements for ballot title language, and, in connection therewith, requiring the use of accessible language and allowing for the modification of statutorily required ballot title language.

Official status: Became Law

7 proposed amendments

Prime sponsors

Progress (from the official record)

Official summary

Official text — shown in English exactly as published by the official source. The official text controls.

Under current law, the title board must set a ballot title for an initiative petition that is brief, does not conflict with another title for an initiative petition filed for the same election, and is in the form of a question that may be answered 'yes/for' or 'no/against' and that unambiguously states the principle of the provision sought to be added, amended, or repealed by the initiative. The act adds a requirement that the title board write a ballot title using accessible language, which means plain language that is understood by the widest possible audience. In determining whether a ballot title is written using accessible language, the title board may consider whether the title: Avoids using legal, technical, or specialized terminology when possible; Clearly identifies the principal change in law or policy proposed by the proposed statutory or constitutional amendment; Avoids unnecessary qualifiers, double negatives, and overly complex phrasing; Organizes clauses so that the effect of a 'yes/for' or 'no/against' vote is readily understood; and Presents necessary information within the ballot title in a logical and readable order. In addition, current law requires that specific language appear in the ballot title for certain initiatives that increase or reduce tax revenue. For initiatives that reduce state tax revenue or local district property tax revenue through a tax change, this required language must appear at the beginning of the ballot title. For initiatives that increase tax revenue for any district through a tax change, this required language must appear directly after language required by the Taxpayer's Bill of Rights. The act modifies these statutory provisions so that the required ballot title language must only be substantially similar to the specific statutory language and may appear anywhere in the ballot title. The act applies to initiative petitions submitted to the secretary of state for title setting on or after the effective date of the act. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1320, oldest first
DateLocationAction
03/04/2026HouseIntroduced In House - Assigned to State, Civic, Military, & Veterans Affairs
03/23/2026HouseHouse Committee on State, Civic, Military, & Veterans Affairs Refer Amended to House Committee of the Whole
03/25/2026HouseHouse Second Reading Special Order - Passed with Amendments - Committee
03/26/2026HouseHouse Third Reading Laid Over Daily - No Amendments
03/27/2026HouseHouse Third Reading Passed - No Amendments
03/31/2026SenateIntroduced In Senate - Assigned to State, Veterans, & Military Affairs
04/21/2026SenateSenate Committee on State, Veterans, & Military Affairs Refer Amended to Senate Committee of the Whole
04/24/2026SenateSenate Second Reading Passed with Amendments - Committee
04/27/2026SenateSenate Third Reading Passed - No Amendments
04/28/2026HouseHouse Considered Senate Amendments - Result was to Laid Over Daily
05/04/2026HouseHouse Considered Senate Amendments - Result was to Concur - Repass
05/21/2026HouseSigned by the Speaker of the House
05/21/2026SenateSigned by the President of the Senate
05/21/2026GovernorSent to the Governor
05/29/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (7 proposed amendments)

Amendments proposed to HB26-1320, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.002Committee amendment — State, Civic, Military, & Veterans Affairs (House)03/23/2026PassedView official document
L.004
Sponsor: Representative Luck
Floor amendment — Second Reading (House)03/25/2026LostView official document
L.005
Sponsor: Representative DeGraaf
Floor amendment — Second Reading (House)03/25/2026LostView official document
L.006
Sponsor: Representative DeGraaf
Floor amendment — Second Reading (House)03/25/2026LostView official document
L.007
Sponsor: Representative DeGraaf
Floor amendment — Second Reading (House)03/25/2026LostView official document
L.003
Sponsor: Representative Luck
Floor amendment — Second Reading (House)03/25/2026LostView official document
L.008Committee amendment — State, Veterans, & Military Affairs (Senate)04/21/2026PassedView official document

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

Full text

Official record

View HB26-1320 on leg.colorado.gov

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

Verify this record

This record carries a fingerprint of its official content, computed by our data pipeline with the SHA-256 algorithm — a real computation over the record itself, not a badge we award ourselves. Anyone can recompute it from the official source and compare.

SHA-256 fingerprint

27de726349a402ca7a7be0c77663e0e1b1b1e8b1179759cabfa191586b72a7a5

What it covers: the record exactly as the official source publishes it — its identifiers (bill number, session, jurisdiction), its official title and long title, its official summary, its status, its sponsors in published order, every recorded action, every recorded vote, and the link to each official text version — assembled in a fixed canonical form described on the How this data works page.

Computed 2026-11-06 · Algorithm: SHA-256 · Canonical form: rogata-canonical-v1

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

The fingerprint does not cover our retrieval date (the “Data as of” stamp in the source line): re-fetching unchanged official content produces the same fingerprint, while any change to the official content changes it.

If you recompute the fingerprint from the official source and get a different value, one of us is out of date — please report it through the corrections log.