Wagtail upgrade PR's

[nickmoreton]

Can someone look at the PR's for Wagtail upgrade maintenance please.

https://github.com/wagtail-nest/wagtail-accessibility/pulls

[nickmoreton]

We are now working on the 7.2 upgrade: #21 but it's getting awkward to work on. Thanks

[SalahAdDin]

@nickmoreton wasn't this package added as built-in in Wagtail?

[nickmoreton]

@SalahAdDin Good question which I don't have an answer for, sorry.

[seb-b]

@SalahAdDin yeah this is mostly redundant now that there's built in accessibility tools. This uses an alternative library (https://github.com/jdan/tota11y) than the built-in tools so might be useful if you wanted extra checks?

From memory (the wagtail slack doesn't show past messages), I was going to deprecate this package (we no longer use it at NJ), but there was some appetite to move it to wagtail-nest so the community could keep it up to date. It doesn't look like that is really happening either 🤷

[SalahAdDin]

@SalahAdDin yeah this is mostly redundant now that there's built in accessibility tools. This uses an alternative library (https://github.com/jdan/tota11y) than the built-in tools so might be useful if you wanted extra checks?

From memory (the wagtail slack doesn't show past messages), I was going to deprecate this package (we no longer use it at NJ), but there was some appetite to move it to wagtail-nest so the community could keep it up to date. It doesn't look like that is really happening either 🤷

Are all the features of this package included in wagtail out-of-the-box? In such a case, the best is to deprecate this package.

[seb-b]

It does a few things differently. But with the deprecation of tota11y.js itself and by the looks of the increasing difficulty of keeping this package up to date I would generally agree it's probably time to sunset this package.

[SalahAdDin]

It does a few things differently. But with the deprecation of tota11y.js itself and by the looks of the increasing difficulty of keeping this package up to date I would generally agree it's probably time to sunset this package.

Missing features to be built-in and deprecating this package then.

[thibaudcolas]

Tota11y being deprecated doesn’t make it any less useful! I believe there are on the order of 30 sites that use this package. As far as the maintenance, I expect there’s not much movement here because the package "just works" really? Always has. The package isn’t under active development so there’s not a big need to update its compatibility matrix with new releases.

Long-term - I would like to see this package evolve to implement some of the more opinionated accessibility checks we won’t be able to do as core features. There’s a lot we could do in this space, and I think lots of projects will find it compelling.