@hexylena @ElectronicBlueberry @dannon In a meeting earlier today, @ElectronicBlueberry , @hujambo-dunia , and I talked about how to ensure that we are compliant with accessibility efforts. I suggested modifying the PR template as a reminder to devs to check with our latest compliancy guidelines.

Are there other guidelines created by us (Galaxy folks) or that are simple and concise enough that we should include them here?

What do you guys think about this update?

I like the idea of an additional checklist to make it clearer what a developer should check before opening a PR, but maybe make it more general instead of specific to accessibility, so it can include e.g.: "I have run make format (for Python changes)" and "I have run make client-format (for client changes)"

I definitely support adding more general guidance and linking up documentation talking about accessibility, formatting, linting, etc., (lots of which is in CONTRIBUTING.md, -- this actually came up recently when someone didn't know where exactly to look for that). This is a great idea.

That said, the headings rule seems overly specific to call out in the PR template to me. This is the kind of thing we really just need to enforce in linting and testing. Linting is now available using vue-a11y, which will catch a lot of specific local-to-component a11y issues. It can't catch the heading one, though, since it's testing components in isolation. But that's where the work (on the ui/ux roadmap) towards automated axe testing comes in.

closing this because it does not seem like the approach that folks want to take, but I'm glad that it prompted some discussion.