the Django accessibility team (currently @tom, @sabderemane, @thibaudcolas) is switching to having regular meetings. As part of this switch, we’ll also start publishing our meeting notes, in this thread.
If you want to be aware when there are new meeting notes available, Discourse has per-thread “Watching” and “Tracking” modes which you can find at the very bottom of this page. You can also set this to “Muted” if you want.
Accessibility activities
If you’re wondering what we’re up to, aside from this thread, check out:
How to get involved
If you want to be involved with accessibility discussions, there are a lot of options:
5 Likes
Hello, I’m interested in joining your team.
yay @HamaBarhamou. For you and anyone else who’s interested – please message me in DMs here on the forum or in Discord, to say more about why you’re interested. Here are our official selection criteria. In addition you have to be a DSF Individual Member. Hope this helps!
Okay, thanks. I just filled out the DFS form.
2023-12-14 Woo!
Attendees: Sarah, Tom, Thibaud
Actions
Agenda
- Hi
- Djangonaut Space accessibility ideas
- 2-3 people likely interested in this
- Django ecosystem accessibility audits
- Django core UI development
- Django admin logical properties refactoring
- Accessibility improvements to Django admin
- Accessibility improvements to Django debug views (404, 500, etc)
- Documentation improvements and research
- Accessibility guidelines for contributors
- Accessibility guidelines for documentation
- Accessibility improvements in documentation
- Accessibility statement for djangoproject.com
- Django core tooling
- Accessibility tooling for Django
- Prettier: Auto-formatting CSS & JS
- Tom’s on it (or someone from Tom’s group – depends on time before the end of the year)
- Stylelint for CSS linting
- Better once Prettier is set up? Requirement for logical properties refactoring
- Join accessibility team meetings if keen?
- Not sure how many meetings there will be during this program?
- djangoproject.com
- Accessibility auditing for the website
- Accessibility improvements for the website code and design
- Accessibility improvements in website content
- Add them as DSF members
- Playwright rewriting of Django’s test suite would be cool
- Simpler Axe integration, already exists
- Growing the team
- Keen but have to be careful to only add people who are motivated for the right reasons.
- 2023 annual report
- “Don’t see why we shouldn’t”
- Nice way to advertise what we’re doing
- Possible outline?
- Statistics
- Number of accessibility PRs
- Big things
- DEP 11 finalized
- Dark mode? Which year was it?
- DjangoCon Edinburgh accessibility sprint
- DjangoCon Durham accessibility sprint
- Accessibility talks? Blog posts?
- Color blindness talk at Django Day – Micheal Something
- Lauren’s talk DjangoCon Europe about accessibility
- DjangoCon US Django’s accessibility track record
- DjangoCon Africa?
- DjangoCon Australia?
- Plans for 2024
- Fixed #34909 – Added aria-describedby to Admin Add/Change buttons #17388
- Thibaud to re-test one last time
- Accessibility guidelines for all contributors
- How-tos – recommend referencing external resources (MDN?) for fundamentals
- Can produce Django-specific resource to highlight particular areas of complexity (“here are top 10 things to test”)
- Keen to avoid writing extensive how-tos of our own otherwise
- Wagtail accessibility team keen to help
- Discussed in a recent team meeting
- Feature of the Django admin: multiple fields on the same line
- Might cause problem for PR where we stack label above input
- Halfway approach where we keep it in a row, but label on top of input nonetheless
- Be nice if we had full confidence that the demo had all the right features
- Improve the demo site generally?
- Recent discussion
- Future – Forum post about django-admin-demo
- Be nice to have other contributors try it out and report back what might be missing
- Use ModelAdmins from Django’s test suite?
- No data but cover everything the tests do
- Refs #34038 – Improve link readability and identifiability #17419
4 Likes
omg @sabderemane did a podcast! Django Chat: Accessibility - Sarah Abderemane 
2024-01-11 Happy new year
Attendees: Tom, Sarah, Thibaud
Actions
- Tom Review pull requests from past year to find highlights – nope (new todo app)
- Thibaud Draft 2023 annual report
- Tom Review draft 2023 annual report
- Sarah Review draft 2023 annual report
- Tom Comment on Refs #34038 -- Improve link readability and identifiability by yushanfans2233 · Pull Request #17419 · django/django · GitHub to proceed with contrast
- Tom Go through curated list of tickets to check how much accessibility in Djangonaut Space
- Thibaud Invite Djangonaut Space participants to meetings
- Thibaud Raise axe-selenium-python in board meeting
- Sarah ask for GitHub Actions support from
- Sarah / Thibaud follow up with django-debug-toolbar auditing as part of Djangonaut Space
- Tom Follow up on label placement in admin form templates (.wide fields)
- Thibaud Provide testable input date time demo for #15806
- Sarah Share next QA checklist draft with other team members
- Thibaud Review next QA checklist draft
Actions review
Agenda
2 Likes
2024-02-08 February FOSDEM vibes
Attendees: Tom, Sarah, Thibaud
Actions
- Thibaud Second draft 2023 annual report
- Tom Review draft 2023 annual report
- Sarah Review draft 2023 annual report
- Tom Comment on the correct ticket #34917 to say the accessibility team recommends adding an underline and that’s it. Djangonaut Space contribution?
- Thibaud Send calendar invite to 3 Djangonauts for next meeting
- Tom Consider inviting more Djangonauts
- Thibaud Again – raise axe-selenium-python in board meeting
- Sarah Share progress on django-debug-toolbar accessibility issues
- Thibaud Provide testable input date time demo for #15806
- Thibaud Review next QA checklist draft
- Tom Create ticket for search landmark improvements on changelists
- Sarah Creative genius for accessibility swag
- Thibaud Share django pony designs with Sarah
- Thibaud Coordinate call with prospective GSoC mentors for ideas
- Thibaud Coordinate Google Season of Docs proposals process
- Thibaud Follow up on “Thibaud’s static admin demo thing, can it be automated better / made generally available”
Actions review
Tom Review pull requests from past year to find highlights
- Thibaud Draft 2023 annual report
- Tom Review draft 2023 annual report
- Sarah Review draft 2023 annual report
- Tom Comment on Refs #34038 -- Improve link readability and identifiability by yushanfans2233 · Pull Request #17419 · django/django · GitHub to proceed with contrast
- Tom Go through curated list of tickets to check how much accessibility in Djangonaut Space
- Thibaud Invite Djangonaut Space participants to meetings
- Thibaud Raise axe-selenium-python in board meeting
- Sarah ask for GitHub Actions support from
- Sarah / Thibaud follow up with django-debug-toolbar auditing as part of Djangonaut Space
- Tom Follow up on label placement in admin form templates (.wide fields)
- Thibaud Provide testable input date time demo for #15806
- Sarah Share next QA checklist draft with other team members
- Thibaud Review next QA checklist draft
Agenda
- T-shirts or something cool I dunno, very important we discuss this, maybe move to the top of the agenda
- Something with a very cool graphic
- Says “Django” and “Accessibility”. Optionally it could say “team”
- Wear them to conferences
- Badge
- Shirt would be cool
- Django accessibility team pony. Pony in a wheelchair
- Axe-selenium-python
- Question from Chaim: “Why transfer vs a fork or vendoring? If we take it over how much on the hook will we end up being to maintain the community around what is a non-django app?"
- The package is 100 lines of code. Feels a bit silly to vendor or fork something that works fine as a separate package and is useful for other projects. Maintenance overhead should be minimal. If we can’t figure this out with the django org, the accessibility team can set up their own separate organisation.
- Sarah, Tom, Thibaud – happy to own long-term maintenance with no other involvement from other teams
- django-debug-toolbar
- Label placement in admin forms – wide fields
- To review #34917 (Links in the Django admin should be underlined.) – Django
- Add underline and move on. Tom to follow up
- Using multiple search roles or elements for one set of items (I know what I mean)
- Landmarks for search features in changelists
- Search landmark / element for search form, top links, filters
- Make sure each is labelled
- I sort of wonder if we can or should migrate the team into a working group
- Prominence of teams vs. working groups
- Not for now
- Something to consider for bigger / specific projects
- Obviously Thibaud finished the draft annual report so we should discuss it
- Thibaud’s static admin demo thing, can it be automated better / made generally available
- I will get back to you on that
- Djangonaut Space
- Invited to next meeting
- Ideally accessibility in next session
- Tom: captain possibly, not navigator
- Thibaud: I don’t know yet
- Sarah: “I’m an organizer” (no)
- Accessibility @ Google Summer of Code
- May to August
- Tom maybe, Sarah maybe, Thibaud yes
- Think of ideas by 10 days from now ish
- Keyboard shortcuts?
- 3-5 new components in admin?
- Accessibility @ Google Season of Docs
- Ideas:
- User documentation for the admin
- Accessibility improvements in code samples / dev docs
- It’s a Thibaud thing. Sarah happy to help with borken english
- Docs people for Django: Daniele, Carlton
1 Like
Note that @accessibility is setup and you are all owners of the group. You can hopefully tweak permissions around the group as you see fit but we can update something if not.
Full credit to @nessita for setting this up 
3 Likes
