First accessibility issues observed by a VoiceOver user - acli/ATutor GitHub Wiki
An attempt was made to create a course, create a forum, post a thread, and post several replies, all by using VoiceOver only. This experiment revealed these first accessibility issues observed by a VoiceOver user (an occasional one, i.e., myself).
My position has always been that session timeouts are generally speaking wrong, especially when they are either unpredictable or too short for an indecisive person to complete the task at hand.
- Typing up a course description that was made up on the fly caused ATutor to display the session timeout message
- A future experiment need to be done to confirm whether this session timeout is announced through VoiceOver. (I do not remember hearing it, though I am not sure VoiceOver was turned on, thus the need for a future experiment.)
- Session timeout too short, as noted above
- No obvious way to create a new course category
- The Javascript links “Bold”, “Underline”, etc. were not read
- Very hard to find the Post button
- If no body was entered, the screen refreshed with the cursor positioned at the Subject. The error message was not read.
- If body was entered the Subject was cleared, causing another error message (!)
- Pressing Reply in the reply list sometimes caused the cursor to be positioned in an unknown location
- The list of posts appears after the cursor, so the user would become completely confused
- The activity cookie does not seem to be updated correctly, since typing in the course description field did not update it
- The Session Timeout message is “Your session is about to expire. [ Logout Now ] [ Stay Connected ]”
- Pressing the “Stay Connected” button when the Session Timeout message appears resets the cookie to the current date and time
- The cookie looks like this: Mon%20May%2013%202013%2019%3A25%3A47%20GMT-0400%20(EDT)
- The session timeout appeared to be around 17 minutes, which is obviously too short for most tasks students do