My LocalGov Drupal contributions for week-ending September 13th, 2024

Need LocalGov Drupal services? Give Big Blue Door a shout.

Meetings and Meet-ups

1. Merge Tuesday: Another productive meeting. I'm especially happy with the merge to localgov_paragraphs to add the new "Show all" accordions widget.
2. Content Group: We had a great chat about what people are enjoying about LGD - microsites, subsites extras, and replicate all came up. And a WHOLE LOTTA Love for Miro.
3. Tech Group Governance: Nice to get to this monthly meeting. Today we discussed stabilising microsites, preparing for Drupal 11, and the community fund.
4. Tech Group Drop-in: Lots (and lots and lots) of talking about maps, maps, and mapping.

Code Contributions

1. We're preparing for Drupal 11 support, so the week began with reviewing/approving PRs for some of the items that I maintain - LocalGov Sa11y, LocalGov Scarfolk, LocalGov Base, etc.
2. Most councils want a "Feedback form". Those small forms that say "was this page useful?" and ask you to give some details if it wasn't. Here's a PR to create that feature. Remind me to stop creating forms, they're tricker little things.
3. I love when we get accessibility issues submitted for LocalGov Drupal. It means when we fix them, we make the web better for everyone. Bisd posted one recently about our "Read more" for service status pages not being translatable. After a little bit of investigating, it turns out it was translatable, and we also have a corresponding aria-label to be more expressive for people using assitive technology.
4. The "move components to single-directory components" issue is moving along very nicely. Just one tiny comment or two from me to Christopher and then I think we're good to go.
5. We've been discussing our approach to checking if a region is empty before rendering it for the past few weeks. What we currently have might has an effect on caching (it's a long-running Drupal core issue too). But any solutions to it throw up other issues as well. I tried, and have nearly succedeeded, in a CSS-only answer to it, but I'm stumped on the if/else clauses for sidebars in the page.html.twig file. If you'd like to contribute to the conversation, please do.
6. Will mentioned that it might be helpful for editors to more clearly see what heading levels that have used in the wysiwyg. I put together a quick proof of concept to show how we could achieve this with just some simple CSS.
7. We have an open issue in the LocalGov Sa11y module to prevent sa11y from running on wysiwyg fields. After a bit of testing, it turns out it already does not run on ckeditor fields. It only runs on rendered content, not editing content, and only runs on the frontend, not while viewing an admin theme. And even testing it on the frontend by creating a comments field showed it was working as expected. We now no longer have this open issue.
8. Last week at the LocalGov Accessibility Meetup, Michael from Big Blue Door gave a really interesting talk about automated accessibility tools, which allow you to scan a page to automatically detect accessibility issues. One of the questions that came up was if you can scan more than one page at a time. I put together a demo repo of code to show how this can be done, then made a video to explain it, and a blog post too.

Filed Under:

1. Drupal Planet
2. Drupal
3. Open Source
4. LocalGov Drupal