Platform Release Notes - October 9th 2025
This is to provide an update on the latest fixes, feature improvements, and accessibility updates across the Colorado.gov CMS platform. Please review for any relevant information you may want to share with your CMS teams.
Known Issues:
- Description of Issue: The alternating white rows in tables are now gone, and are using the background color of the page/rows across the table cells.
Bugs and Feature Fixes Completed:
Events
- Description of Issue: The "Organizer Email" field in the Event content type was not displayed as a clickable hyperlink.
- Fix Description: ‘Organizer Email’ was converted into a link field so that any email address now appears as a hyperlink.
Accessibility Fixes Completed:
| Content Type / Feature | Issue | Fix |
|---|---|---|
| Google Translate / Search Results | The Google Translate widget was missing from search results pages, limiting accessibility for non-English-speaking users. | The widget has been added to the utility menu on search results pages, ensuring consistent access across the platform. 
|
| Jumbotron (Single Slide Instances Only) | Headings and text within Jumbotron slides were not being recognized by screen readers, impacting accessibility. | The role attribute on Jumbotron slide containers has been updated to ensure screen readers now correctly detect and read the slide content. |
| Jumbotron | The Jumbotron component included incorrect or invalid ARIA attributes, which could interfere with proper interpretation by assistive technologies. | The role and aria-label attributes have been removed from the div.slick-slider element, and the invalid aria-label has been eliminated from the div.slick-track element to ensure compliance with accessibility standards. |
| Jumbotron – Single Slide Accessibility | When the Jumbotron displays only a single image or slide, residual carousel-related code creates confusion for screen readers. | Template and ARIA references to the carousel component have been removed or updated for single-slide scenarios. Associated containers were adjusted, and carousel navigation buttons are now hidden from the DOM to improve accessibility. |
| Contact Card | The heading hierarchy in the Contact Card paragraph type was incorrect, with the "Name" field rendered as an H1. | The "Name" field has been updated to use an H3 heading, ensuring proper semantic structure and improved accessibility.  |
| Main Navigation – Mobile Accessibility | In mobile view, the Main Navigation lacked appropriate aria-controls attributes to indicate expandable content, affecting accessibility for assistive technologies. | Each control element now includes an aria-controls attribute to identify the associated expandable content. Additionally, aria-expanded="true" is applied when content is expanded, and aria-expanded="false" when collapsed, ensuring proper accessibility signaling. |
| Main Navigation – Mobile Screen Reader Order | In mobile view, the Main Navigation is accessed in an illogical order for screen readers | The menu has been updated in the DOM order to reflect a logical order for screen readers |
| Main Navigation – Semantic Structure | The Main Navigation was not enclosed within a <header> tag, leading to confusion for screen readers when interpreting the page structure. | The Main Navigation is now properly wrapped in <header> a tag, improving semantic clarity and accessibility for assistive technologies. |
| View Card - Calendar View Accessibility Update | The Calendar View was previously structured using table elements intended for layout rather than tabular data, which could lead to misinterpretation by screen readers. | Semantic and ARIA attributes have been added to clarify the Calendar View’s role as a calendar, improving accessibility and ensuring accurate interpretation by assistive technologies. |
| Resource Search - Filter Accessibility Enhancement | The filter checkbox set lacked semantic grouping, as it was not enclosed within a <fieldset> and <legend>, which are essential for screen reader navigation and accessibility compliance. | The template now uses <fieldset> elements in place of <div> containers, with a zero margin applied to override default spacing. This ensures proper semantic structure and improved accessibility for assistive technologies.
|
| Webforms | Certain webform message type styles did not meet minimum contrast requirements between text and background, potentially impacting readability and accessibility. | Color values on affected templates have been adjusted to ensure sufficient contrast ratios, improving compliance with accessibility standards and enhancing legibility for all users. |
We continue to make edits to the CMS site training/information as features change on the platform, but if you can’t find what you need please email partnersupport@www.colorado.gov.
*Points breakdown based off Taxation Site Improve report. Other sites may have either a higher or lower points gained based off occurrences.