I recommend the accessibility problems reported in these comments be created as separate issues to be prioritized. Specifically:
- #15 🐛 Feedback on Modern Drupal.org Design Active reported by yesct
- #173 🐛 Feedback on Modern Drupal.org Design Active reported by xmacinfo
This issue is dedicated to feedback. However, the items above have been lost in the thread and I believe are not properly prioritized. These are usability issues that have a direct impact on site visitors. Additionally, I feel these detract from Drupal's credibility and our commitment to accessibility.
Personally, I am advocating for #173 🐛 Feedback on Modern Drupal.org Design Active to be resolved because I recommended an engineer to follow Drupal's approach for "Skip to" links and they reported that these were broken on the home page and caused unnecessary confusion.
teknorah → credited andrewozone → .
Attended!
Attended!
@itmaybejj please disregard! In our projects, we had an issue where configuration for "Check content in these containers" wasn't correct. Editoria11y was failing silently due to this bad config. We were able to correct our configuration and everything is now working as desired.
When I rolled back to 2.2.5, the config for "Check content in these containers" was reset, so that is the reason it worked again. It had nothing to do with version. It had everything to do with bad config causing silent failures.
Apologies for the confusion! Silent failures are the hardest to troubleshoot!
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
@itmaybejj I'm sorry to report that heading detection is no longer working in version 2.2.6. Our websites have the setting "Auto-detect any Web components" checked on and Editoria11y no longer detects web component headings skipped nor does it detect straight up HTML headings skipped.
I have attached screenshots for context. Can you please verify that indeed this latest release 2.2.6 is no longer checking headings properly? I'm happy to provide more context or additional testing.
For now, I am recommending that our sites roll back to Editoria11y version 2.2.5 until we get a point of view from y'all. Thank you!
@itmaybejj I have confirmed this is fixed by testing version 2.2.5.
I first tested with the new param "Auto-detect any Web components" turned on. Success!
Next, I tested with only the "Check inside these specific Web components" with the value "pds-heading". Also success!
Screenshots attached of my local testing as editoria11y-test-1.png, editoria11y-test-2.png, editoria11y-test-3.png
Thank you so much for addressing this issue. Our Content Authors will be very relieved they can rely on this tool once again to catch skipped headings. Our team appreciates you and this module!
Attended!
Attended!
Slides have been updated: https://docs.google.com/presentation/d/1PXdsKeHRmuDJkeXtysGIOhz5JBgcMAWP...
Webpage has also been updated: https://www.midcamp.org/2025/speaker-resources
All dates have been updated from 2024 to 2025. This was done in a planning meeting by @froboy and @teknorah.
@andrewozone went through each slide in the template and confirmed contrast passes WCAG 2.2. Screenshots of each background and text contrast combination used in the template are attached to this ticket.
The following article "Make your PowerPoint presentations accessible to people with disabilities" was also used to review the slides and adjustments added.
andrewozone → created an issue.
Andrew Olson has performed a first pass at the audit. Issues can be found in the Google Spreadsheet in the 2025 Accessibility folder on the MidCamp Google Drive.
In addition, Editoria11y roles have been (or soon will be) updated and issues are now captured in the Admin at the following link: https://www.midcamp.org/admin/reports/editoria11y
Please reach out to get an updated role and view this link if you are interested in contribution and unable to view the link.
Next steps
- A Drupal developer works on remediation tasks identified in the Google Spreadsheet
- Content remediation using Editoria11y. Reach out if you have issues with access or roles.
Hello, attended to discuss a11y things.
teknorah → credited andrewozone → .
Attended!
Hello, attended and participated.
Attended and talked about Accessibility things.
Additional screen shots added to provide context on our Heading web component structure.
Agree with @matthand on the need to check inside the web component and not only the slot. Unfortunately, this update did not resolve our issue due to the structure of our Heading web component. Editoria11y is not able to check all our Heading web components at the moment.
Attached is a screenshot of our Heading web component structure where the heading tags are outside the slot. We only have text inside the slot, so this is ignored by Editoria11y. You can visit this page on our web site to see the H1 as our Heading web component. https://www.principal.com/finpro/policy-riders-and-endorsements.
teknorah has been able to coordinate with DePaul to get free monitors for live captioning main sessions. MidCamp is able to use 2x (40)” TVs on a cart and 1x (50)” TV on a cart. Andrew Olson the sizes will work great for live captioning!
Phil Alonso and Andrew Olson met to discuss the accessibility audit on Wednesday, January 15.
From this conversation, Phil was able to coordinate with the website team to get the Editoria11y module installed on the MidCamp website 📌 Install and Enable Editoria11y Accessibility Checker Fixed . A preliminary list of issues has been captured by the Editoria11y module and is attached as a CSV. Note that these issues need to be reviewed and tasks defined to fix them.
Phil and Andrew also identified which tools will be used for the audit in addition to the Editoria11y module. The following Chrome browser extensions will be used to identify issues:
Phil reached out to AmyJune Hineline (volkswagenchick) and was able to get a copy of a spreadsheet template we can use to capture the accessibility issues. Phil plans to share this spreadsheet by uploading it to the 2025 MidCamp Google Drive "Accessibility" folder.
Next steps are to use the tools to identify issues, then add them to the template spreadsheet. Once identified, we will create tasks to address the issues and keep the spreadsheet up to date with progress.
Here!
andrewozone → created an issue.
andrewozone → created an issue.
Sorry for the major delay on this update, but I have reviewed and concur this has been resolved on the current MidCamp site.
We are due for another accessibility audit, so I will work on creating another ticket and see if anyone on the team is interested in auditing the current MidCamp site.
teknorah → credited andrewozone → .
Joined the planning meeting.
Attended the planning meeting.
Attended today and discussed A/V and Accessibility things.
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
All subtitles / captions in YouTube have been updated with the files provided by AI Media. The SRT files were downloaded from the account created at AI Media. The following videos have been updated with the transcripts:
- ChatGPT for Drupal content editors
- Tighten up your Drupal code using PHPStan
- Prompt Engineering, Generative AI, and Drupal
- Maximizing Visual Studio Code with DDEV for Drupal developers
- Replacing Your Engine: Rules to ECA
- Next Js with Storybook and Drupal
- From Lando to DDEV: A side by side migration
- What a component isn't
- Unburdening Teams, Unleashing Potential: New Strategies for Digital Agency Success
- Effective Project Management: How to Grow High-Value Partnerships
- Getting your feet wet - you're not alone (a beginner's resource guide)
- The Time to Decouple Your Search is Now
- Comparing Layout Systems - Backdrop CMS vs Drupal
- The Drupal API Client
- Revolutionizing Conversations: AI Chat Integration on YaleSites
- Web Accessibility in Developing Countries
- Ambitious projects with constrained budgets - Drupal 7 moving to Backdrop CMS
- Ethical Implications of Artificial Intelligence
- Documentation for developers: A gift to your future self
- Security in Drupal: what can go wrong?
- Elevate Your Approval Processes: Mastering Complex Workflows
- Making the Case for Open Source Code Contribution
- Let's Get Uncomfortable: How to Ask For and Process Feedback
The following pages have been updated with the transcripts:
- ChatGPT for Drupal content editors
- Tighten up your Drupal code using PHPStan
- Prompt Engineering, Generative AI, and Drupal
- Maximizing Visual Studio Code with DDEV for Drupal developers
- Replacing Your Engine: Rules to ECA
- Next Js with Storybook and Drupal
- From Lando to DDEV: A side by side migration
- What a component isn't
- Unburdening Teams, Unleashing Potential: New Strategies for Digital Agency Success
- Effective Project Management: How to Grow High-Value Partnerships
- Getting your feet wet - you're not alone (a beginner's resource guide)
- The Time to Decouple Your Search is Now
- Comparing Layout Systems - Backdrop CMS vs Drupal
- The Drupal API Client
- Revolutionizing Conversations: AI Chat Integration on YaleSites
- Web Accessibility in Developing Countries
- Ambitious projects with constrained budgets - Drupal 7 moving to Backdrop CMS
- Ethical Implications of Artificial Intelligence
- Documentation for developers: A gift to your future self
- Security in Drupal: what can go wrong?
- Elevate Your Approval Processes: Mastering Complex Workflows
- Making the Case for Open Source Code Contribution
- Let's Get Uncomfortable: How to Ask For and Process Feedback
andrewozone → created an issue.
andrewozone → created an issue.
The following people helped with onsite accessibility.
- Oz Heller (oheller)
- Brian Smith (brianbrarian)
- Chris Greatens (cgreaten)
- Bob Snodgrass (bsnodgrass)
- Brad Czerniak (ao5357)
- Andrew Olson (andrewozone)
andrewozone → created an issue.
volkswagenchick → credited andrewozone → .
I was on the team for Code of Conduct at MidCamp.
tekNorah → credited andrewozone → .
tekNorah → credited andrewozone → .
tekNorah → credited andrewozone → .
tekNorah → credited andrewozone → .
tekNorah → credited andrewozone → .
tekNorah → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
Hello, I attended today!
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
I joined a little late.
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .
volkswagenchick → credited andrewozone → .