Accessiblity statement or VPAT for compliance

,
1

Hey All,

I administer a local galaxy install on a small computational cluster at a tier 2 institution in the United States. I’m looking for a VPAT or some other formal documentation of accessibility to pas on to our administrative staff so that galaxy can be used in class, or for research that is graded. Any help is appreciated.

2

Hey!

I sure wish we had a formal VPAT, but nobody has commissioned a real audit. Accessibility is, however, something we care a lot about. Maybe this helps with your admin folks:

  • Our Selenium test suite runs axe-core against every page it touches, and CI fails on any critical-impact WCAG violation. Specific flows (login, registration, workflow index, history, etc.) are held to a stricter “moderate” threshold.
  • The Vue frontend is linted against eslint-plugin-vuejs-accessibility – alt text, heading structure, keyboard handlers on clickable things, etc. That also blocks CI.
  • We’ve been slowly swapping Bootstrap-Vue out for our own component library partly to get ARIA and keyboard/focus behavior right.

Honest caveat: axe-core does not catch all WCAG criteria. Things like whether alt text is actually meaningful, tab order makes sense, or a custom widget reads right in a screen reader still need a human evaluator, and we haven’t had that done.

If there are specific criteria your admins need answered, let me know and I can point at what’s covered or file issues for the gaps. (or you can, if you want!)

Hope this helps!

-Dannon