Accessibility team meeting notes

2026-02-26 - The good title got vultured

Attendees: Tom, Eli, Tim, Sage, Saptak, Sarah, Thibaud, Rahmat

Actions

GitHub Projects: django accessibility improvements, All Table

Actions review

GitHub Projects: django accessibility improvements, All Table

Agenda

  • Djangonaut Space :rocket:
  • Tom broke the last barriers for starting to work on JS / CSS formatting
    • Adding a formatter for CSS & JS
    • Logical properties could be tricky, more prone to cause regressions
      • Visual regression test suite would be helpful
      • Maybe BackstopJS
    • “There’s always regressions any time I change CSS” -Tom
  • PSF email thread: they want to do more a11y stuff and reached out
    • Sarah, Thibaud, Saptak in the email thread
    • Saptak took a look at the document linked in the email, it’s more focused on the accessibility of the events (PyCons, etc.) and adding an accessibility statement
    • Sarah and Saptak to answer email
  • Website redesign
    • Thibaud started making a record of the components (UI inventory). So far he’s got 65
    • Automate screenshot taking of the components
    • Automation-driven project so that other people can reproduce more easily
  • With DjangoCon Europe soon and DCUS starting to organize, do we want to move this forward again? New content: Accessibility guidelines for talks · Issue #2053 · django/djangoproject.com · GitHub
    • Turn into template view → good djangonaut space task
    • Reach out to conference organizers to remind them of the guidelines
  • Sage working on Pa11y C1 for the website
    • Work is currently on Sage’s fork
    • Do we merge this after fixing all the issues, or do we merge with red CI check ?
    • Disable contrast checks
      • Thibaud says they’re not super reliable
      • the color contrast issues depend on the website redesign
    • Sage to make PR
    • Website WG does not own deployment of website
    • Maybe run Pa11y CI once a week for now