LB (Ben Johnston)

As per https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/#changes-from-wcag-21-to-wcag-22 > WCAG 2.2 provides 9 additional success criteria since WCAG 2.1. They are introduced on this page. > > The 2.0 and 2.1 success criteria are essentially...

As per https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/#changes-from-wcag-21-to-wcag-22 > WCAG 2.2 provides 9 additional success criteria since WCAG 2.1. They are introduced on this page. > > The 2.0 and 2.1 success criteria are essentially...

OK @ljharb would you like me to further refine this PR with additional context where the links exist? Or are you happy with it in its current state?

@ayaan-qadri there's already a Wagtail (core) issue to cover CSP items, feel free to do an assessment / suggestion for changes on those issues. https://github.com/wagtail/wagtail/issues/1288 & https://github.com/wagtail/wagtail/issues/7053 As for this...

Thanks for adding screenshots

We probably should add this to our Stylelint checks at some point. I will raise an issue. Update: Raised https://github.com/wagtail/stylelint-config-wagtail/issues/44

I think it would be good to somehow include the pattern for JSON rendering using normal Page routing. Essentially each Page path can have a different request header and then...

Another long-standing issue with the current API is that we cannot easily generate an OpenAPI specification See https://github.com/wagtail/wagtail/issues/6209 I would say that we must have a documented or even out...

Have not reviewed in full but generally this seems like a super helpful change. Thanks for picking up the keyboard shortcut issue also, not sure how we missed that one...

@laymonage just a note, the `mod+s` behaviour was copied verbatim from previous code. Observe that the previous code simply searched for any `action-save` classes, and this was on publish buttons...