You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We just started using the Time Warp app at the University of Arizona, and after an accessibility review we discovered some issues around accessibility. The elements on the timeline are not available to a screen reader, and are not tabable for a user who is only using a keyboard and not a mouse. The date filters are also not accessible to these users.
Describe the solution you'd like
We are in the early discovery stages of how to solve these issues, but if you have any suggestions on solutions or approaches we would love your input!
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
Hello @acobbb , thank you for submitting an issue we appreciate your time. We will take a look and give you an update as soon as we can. We aim for a 72 hour response time.
These are important updates but will need help from the community to suggest what needs to be done and how to do it. If there's anyone with experience that can guide the conversation feel free to comment.
@its-me-mario is our UX designer. He is out of the office until next week, but should be able to provide some more details on the specifics of what came out of the accessibility review.
Is your feature request related to a problem? Please describe.
We just started using the Time Warp app at the University of Arizona, and after an accessibility review we discovered some issues around accessibility. The elements on the timeline are not available to a screen reader, and are not tabable for a user who is only using a keyboard and not a mouse. The date filters are also not accessible to these users.
Describe the solution you'd like
We are in the early discovery stages of how to solve these issues, but if you have any suggestions on solutions or approaches we would love your input!
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: