# Accessibility team meeting notes

**URL:** <https://forum.djangoproject.com/t/accessibility-team-meeting-notes/26133>\
**Category:** Accessibility\
**Created:** [December 13, 2023, 1:03pm UTC](https://forum.djangoproject.com/t/accessibility-team-meeting-notes/26133 "2023-12-13T13:03:32Z")\
**Posts on this page:** 1\
**Showing post:** 36

<div class="post-metadata">

**Author:** ![erosselli](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/erosselli/32/18891_2.png) [@erosselli](https://forum.djangoproject.com/u/erosselli)\
**Post date:** [June 28, 2026, 11:03pm UTC](https://forum.djangoproject.com/t/accessibility-team-meeting-notes/26133/36 "2026-06-28T23:03:36Z")

</div>

## 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](https://github.com/orgs/django/projects/7/views/8)

### Actions review

GitHub Projects: [django accessibility improvements, All Table](https://github.com/orgs/django/projects/7/views/8)

### Agenda

- Djangonaut Space 🚀
  - [Accessibility issues with page navigation on News page · Issue #2507 · django/djangoproject.com · GitHub](https://github.com/django/djangoproject.com/issues/2507) → example issue that got “vultured”
  - Can only assign people who are either in the org or have interacted with the issue → djangonaut can leave a comment in the issue and then Eli can assign them
  - Thibaud has some ideas but has to write them down

- Tom broke the last barriers for starting to work on JS / CSS formatting
  - [Adding a formatter for CSS & JS](https://forum.djangoproject.com/t/adding-a-formatter-for-css-js/25754)
  - Logical properties could be tricky, more prone to cause regressions
    - Visual regression test suite would be helpful
    - Maybe [BackstopJS](https://github.com/garris/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
    - This was done with [Crawlee](https://crawlee.dev/)

- 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](https://github.com/django/djangoproject.com/issues/2053)
  - Turn into template view → good djangonaut space task
  - Reach out to conference organizers to remind them of the guidelines
    - [hello@djangocon.us](mailto:hello@djangocon.us) for DCUS
    - [content@djangocon.eu](mailto:content@djangocon.eu) for DjangoCon Europe
    - Eli to open PRs against conference websites to add link to 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

---

_[View the full topic](https://forum.djangoproject.com/t/accessibility-team-meeting-notes/26133)._