Page MenuHomePhabricator

Investigate which is the best option for accessibility testing to new lexeme special page CI
Closed, ResolvedPublic1 Estimated Story Points

Description

Solutions to look into:

Timebox: [8 hours]

Event Timeline

(We should probably see if we can assert some more states than just the initial empty form. Maybe a state with error messages visible and one with some content in one of the lookups?)

Prio Notes

  • Will help improve UX and accessibility → Affects End users down the Line
  • Ensures engineers comply with a11y best practices ⇉ Affects Current and Future development efforts (Devs and New Devs)
  • Tests UX flows and designs for a11y pitfalls → Affects UX Process owners

vue-axe hasn't been updated in more than a year. Has it not been updated because it is not needed? Or is this lib at risk of being considered unmaintained soon?

This article discusses some considerations on the use of focus in unit tests (jext-axe) vs integration tests (cypress-axe).

It’s debatable whether a unit test should assert actual focus in the DOM, such as document.activeElement being an expected element. Unit testing tools frequently fail at the task, and you’ll end up chasing down bugs related to your test harness instead of writing useful test cases.

If we are considering testing focus of the dom this should be taken into consideration.

guergana.tzatchkova renamed this task from Add accessibility testing to new lexeme special page CI to Investigate with is the best option for accessibility testing to new lexeme special page CI.May 3 2022, 9:07 AM
guergana.tzatchkova renamed this task from Investigate with is the best option for accessibility testing to new lexeme special page CI to Investigate which is the best option for accessibility testing to new lexeme special page CI.
ItamarWMDE claimed this task.

Accessibility testing options have been compared and merged \o/