8000 Backport policy for UI and accessibility fixes · Issue #13095 · wagtail/wagtail · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Backport policy for UI and accessibility fixes #13095

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
thibaudcolas opened this issue May 7, 2025 · 3 comments
Open

Backport policy for UI and accessibility fixes #13095

thibaudcolas opened this issue May 7, 2025 · 3 comments
Assignees
@thibaudcolas
Labels
Accessibility component:Design system Including the pattern library (Storybook) Documentation

Comments

@thibaudcolas
Copy link
Member

Pertinent section of the Wagtail docs

Wagtail’s release process - Supported versions

Details

We need to clarify our policy for backports, largely based on that of Django, to make it clearer how we handle:

  • Accessibility fixes. Where there might not be a direct crash for all users or most users, but some users might be experiencing major issues equivalent preventing them to do certain tasks
  • UI fixes. Where here as well there might not be a crash or major issue, but certain small issues can have an outsize impact on the user experience.

In both cases we want more leeway than just looking at "critical problems".

Working on this

Assigning to myself as I have a specific idea of the kind of wording I’m after. But comments / feedback in this issue is very welcome.
@thibaudcolas thibaudcolas self-assigned this May 7, 2025
@thibaudcolas thibaudcolas added Documentation Accessibility component:Design system Including the pattern library (Storybook) labels May 7, 2025
@lb-
Copy link
Member
lb- commented May 7, 2025

Do we want to provide a schedule of what accessibility tooling we support (alongside browser support)?

As for the backport policy, we could include a threshold that aligns with the WCAG framework? E.g. any A level item that is part of core admin functionality.

@thibaudcolas
Copy link
Member Author

@lb- we do, it’s here: Accessibility targets :) Yeah I think that kind of threshold could work, though we probably need more flexibility than that. For example #8334 was a blocker for WHCM users, which lots of people argue isn’t part of WCAG.

@lb-
Copy link
Member
lb- commented May 8, 2025

Ahh. Forgot that we alihad that. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thibaudcolas thibaudcolas

Labels
Accessibility component:Design system Including the pattern library (Storybook) Documentation
Projects
WCAG 2.2 & ATAG 2.0
Status: No status
Wagtail 7.1* release planning
Status: No status
Wagtail Design Backlog
Status: New
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thibaudcolas @lb-
0