Open tander08 opened 3 years ago
Of all the '?' help texts shown, the first one was tab-able and had no name. For now, I've changed it to be like the others. We could look instead at making all the help texts tab-able and having names.
I'm going to leave this open -- let's figure out what are best practices and how screen readers handle this. I don't think hover over information necessarily needs to be tabable, but it must be reachable.
I don't know what happens for screen readers. I don't see Wave raising any issues (or Axe) but I don't know if that means all is good or if they also don't see the information. I guess we could try a screen reader. I haven't found anything online yet that gives any clues.
https://inclusive-components.design/tooltips-toggletips/ has some suggestions how to handle these.
Issue: ARIA Commands must have an Accessible Name:
Data for: Qualitative Data Sharing: Participant Understanding, Motivation, and Consent: https://data.qdr.syr.edu/dataset.xhtml?persistentId=doi:10.5064/F6YYA3O3