Release 1.18

Have more questions? Submit a request

2024-11-17

This release marks a significant milestone in our accessibility journey, introducing improvements that bring us closer to full WCAG 2.1 AA compliance. These enhancements demonstrate our commitment to creating an inclusive platform that works for everyone.

Features ⭐️

Accessibility Improvements

We've implemented significant accessibility improvements across both the frontend and backend of District Engage, aligned with WCAG 2.1 AA guidelines. These enhancements ensure our platform is more inclusive and usable for everyone, with particular attention to users of assistive technologies like screen readers and keyboard navigation.

 

Survey Tool Accessibility
  • Enhanced keyboard navigation for ranking questions
  • Improved screen reader support for Likert Scale questions
  • Better announcement of question text and descriptions
  • Keyboard-accessible multi-select dropdowns
  • Optimised mobile rendering of survey content
Map Functionality Improvements
  • Keyboard navigation for all map elements such as pins and shapes
  • Enhanced ARIA labelling for map pins and shapes
  • Keyboard-accessible map-based project search
General Interface Enhancements
  • Improved focus states across the platform
  • New "Skip to main content" shortcut in the backend
  • Enhanced popup behaviour with immediate focus
  • Accessible dashboard advanced filters
  • Keyboard-accessible block builder
  • Keyboard-accessible Rich Text Editor

 

New Card List Block

We've introduced a new Card List block feature that provides more flexibility in displaying content in a card format. This addition offers new layout options for showcasing your content. Read more about content blocks and groups here.

 

Fixes 🐛

  • Fixed an issue where the Enter key would refresh the page instead of triggering the intended action
  • Resolved keyboard navigation issues with the splash overlay
  • Improved ARIA elements for video and embedded content
  • Fixed survey content rendering issues on mobile devices
  • Fixed a notification count discrepancy where initial project publication was not correctly filtering for users who had opted in to receive category notifications

 

What's Next?

We're continuing our commitment to accessibility and user experience improvements. Look out for more enhancements in upcoming releases.

 

If you encounter any issues with this release or have feedback about the new accessibility features, please reach out to the District Engage Support Team.

Was this article helpful?
0 out of 0 found this helpful