WCAG 2.2 AAA* audit of the Wagtail admin – Nov 2023 #11180
Replies: 8 comments 14 replies
-
Meeting notes – 2023-11-03 10:15ActionsAlbina
Thibaud
Later
DecisionsScope
ViewsViews to test:
Reporting
Testing methodologyMust:
Should:
Could:
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @thibaudcolas I will like to participate in the Accessibility audit testing. This will enable me to be able to gain further experience on Accessibility. Having read about the implementation of ATAG, it will be more exciting to be able to demonstrate some skills for a successful audit. |
Beta Was this translation helpful? Give feedback.
-
|
hi @ArafatAbdussalam 👋 Based on my comment below, are you still keen to help with this? If so perhaps you could test the following views for us?
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @thibaudcolas Yes, sure. I am still keenly interested in the audit. I have been taking my time to understand the next step to be taken but I am quite lost as I was unable to attend the last meeting. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @thibaudcolas I will love to work with the team on this! |
Beta Was this translation helpful? Give feedback.
-
|
hi @yigakpoa 👋 Based on my comment below, do you still want to do this? Here are views I think you could help us test:
|
Beta Was this translation helpful? Give feedback.
-
|
@thibaudcolas let me know where I can help with the auditing. |
Beta Was this translation helpful? Give feedback.
-
|
@SaptakS 🙌 please see my comment below. If you want to help with this, I think we could use extra expertise on testing the user bar: #10674 |
Beta Was this translation helpful? Give feedback.
-
|
I will take a look at it |
Beta Was this translation helpful? Give feedback.
-
|
@thibaudcolas I'd love to be on the auditing team. |
Beta Was this translation helpful? Give feedback.
-
|
hi @praiztech 👋 Based on my comment below, do you still want to do this? Here are views I think you could help us test:
Alternatively, since you have much more experience with this than most, I’d be keen to possibly give you an assignment that requires more autonomy? Let us know what your plans are. |
Beta Was this translation helpful? Give feedback.
-
|
@thibaudcolas Sure! Let me know what the assignment is about. |
Beta Was this translation helpful? Give feedback.
-
|
@praiztech could you read my comment below that I linked to and let me know if you have questions? This is an accessibility audit of Wagtail, we’ve detailed the methodology towards the top of this discussion thread and with the recent update from @albinazs. For you specifically, I shared four different views in the CMS right above that you could help test. |
Beta Was this translation helpful? Give feedback.
-
|
@thibaudcolas my comment was in response to your asking if I was available for an assignment. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @thibaudcolas I will like to participate in the Accessibility audit testing. |
Beta Was this translation helpful? Give feedback.
-
|
hi @ShubhamOulkar 👋 Based on my comment below, do you still want to do this? Here are views I think you could help us test:
|
Beta Was this translation helpful? Give feedback.
-
Update 13-12-2023Spreadsheet with audit output (still WIP) Pages checked:Testing methods:
This audit hasn’t produced as many significant issues as the previous one due to ongoing accessibility improvements. There are still some things to consider, mostly regarding the new rules of best practices that go beyond WCAG. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @albinazs What tool do we get to use for the audit testing? Following through with your comments. Can I use Accessibility insights and Sally as well? |
Beta Was this translation helpful? Give feedback.
-
|
@ArafatAbdussalam yes, please use the same tools as Albina did |
Beta Was this translation helpful? Give feedback.
-
|
Hi all, I have updated our living accessibility audit with the results from Albina’s work. As we can see in the "Scope overview" tab, there are a lot of pages within the CMS that remain untested simply due to time constraints. Contributing to the auditFor anyone wanting to help with this, please:
As far as reporting the results of your testing, please make a copy of our spreadsheet like Albina did, then adding your findings there, and share the link to the sheet in this thread. Where to testWe use the https://static-wagtail-v5-2.netlify.app/admin/ website to do our testing for this audit. It’s a static copy of Wagtail, not a real site instance. This helps a lot in making sure we all test the same thing, but does mean not all functionality in the CMS is testable this way. What to testHere is a list of available views in our demo site, if you’re keen to help let us know here and I’ll keep track of who tests what in the one table :) |
Beta Was this translation helpful? Give feedback.
-
|
hey I would like to test /admin/pages/60/ this page, if its available? Also could you let me know some examples where I can have a look for the same? |
Beta Was this translation helpful? Give feedback.
-
|
Alright @thibaudcolas Thank you for the resources. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
👋 opening this for discussion of an upcoming WCAG audit of the admin. We’re looking for feedback / guidance / suggestions (or even just kind words of support!) on how we plan the audit, specifics of the testing, and how we share reports / tackle the issues.
Context
As part of our ATAG 2.0 audit, we succinctly reviewed the accessibility of the Wagtail admin. There were clear gaps so for WCAG conformance we focused on automated tests, and spent our manual testing budget on other ATAG criteria.
Now – we need to go back to WCAG auditing, and test the relevant parts of the admin more meaningfully.
Audit requirements
Standards
For Guideline A.1.1: of ATAG 2.0 – the audit should include all of WCAG 2.2 AA-level (Recommendation as of October 2023), and some of AAA-level guidelines as well as best practice recommendations as we see fit. We could also attempt to cover a few concepts from WCAG 3.0 (draft), such as color contrast. So the options are:
We could also possibly try to cover legal requirements from:
Scope
For ease of auditing and of reviewing / sharing audit results, I would like us to focus on features of the admin accessible via one of my static "snapshot" copies of Wagtail: https://static-wagtail-v5-2.netlify.app/admin/. This limits our possible scope but greatly simplifies having access to features and sharing links to specific parts of Wagtail when reporting issues.
From there have a lot of options for how we go about this. Here are the ones I could think of:
Reporting
We have a lot of options here:
Testing methodology
Essentially TBC, but I would like us to focus on manual testing, since we got lots of reports from automated tests already.
Semi-automated WCAG testing
Similar to past accessibility team reviews of Wagtail 3.0 and 4.0 via screenshots in Figma.
Manual WCAG testing
Across a representative sample of admin views,
Audit planning
Beta Was this translation helpful? Give feedback.
All reactions