Timed interactions refer to any interaction with an application with a time constraint. This could be a login session that expires after a certain time, a payment gateway that times out if the user takes too long to complete the transaction, or any other interaction with a time limit. Testing the accessibility of these interactions involves ensuring that users can complete the interaction within the given time limit and that the application provides clear feedback when the time limit is about to expire.
Timeouts refer to the period of time after which an application stops waiting for a response from the user and takes action on its own. For example, if a user is inactive for a certain amount of time, the application may log them out automatically. Testing timeouts involves ensuring that the application handles timeouts gracefully, providing clear feedback to the user, and allowing them to resume their activity without losing data.
3 Common Accessibility Issues with Timed Interactions
- Timeouts that cannot be controlled: For security purposes, many forms, especially purchasing forms, expire after a set time period. However, using forms with a screen reader or another assistive device often takes longer. Users must be able to know when the form is about to expire and extend the time limit when needed.
- Insufficient time to complete an interaction: Visitors using assistive web technology to fill out a form may need some extra time to do so. Besides, they may not even know there is a time limit and end up with an expired form. This problem can be prevented by removing the timeouts on forms or providing enough information to inform the user. Alternatively, you can offer an option for assistive technology users to extend the time limit to have enough time to complete the process.
- Unclear feedback on time constraints: Users must be able to know when the form is about to expire, and they must be able to extend the time limit when needed. It is important to ensure that users can complete the interaction within the given time limit and that the application provides clear feedback when the time limit expires.
Timed Interactions for Users with Disabilities
One way to make timed interactions more accessible is to offer alternatives for users who need more time. For example, if a website has a strict time limit, consider adjusting the implementation of the timeout or offering alternatives that will benefit users with disabilities. This could include providing a phone number for users to call to complete a transaction or allowing users to pause a page to prevent content from disappearing.
Another way to make timed interactions more accessible is to give users control over time limits. If a time limit is not essential or related to a real-time event, provide users with options to turn off the time limit before encountering it, adjust the time limit over a wide range, or extend the time limit with a simple action such as pressing the spacebar or activating a button. Users can continue the activity without losing data after re-authenticating if an authenticated session expires.
It is also essential to provide clear feedback to users when a time limit is about to expire and allow them to extend the time limit if needed. This can be done by providing a warning dialog that allows users to extend the time limit by a simple keypress, such as pressing the spacebar. Additionally, limit the number of pop-up notifications and other interruptions and ensure that all notifications are accessible for screen readers and other assistive technologies.
Specific Features that Make Timed Interactions Accessible
Some specific features that make a website or app’s timed interactions accessible include:
- Providing enough time for users to complete tasks: This can be achieved by providing mechanisms to stop, extend, or adjust time limits, except where necessary. Additionally, it is important to pause, stop, or hide moving, blinking, or scrolling content, postpone or suppress interruptions, except where required, and re-authenticate when a session expires without losing data.
- Offering alternatives for users who may need more time: If a website has a strict time limit, consider adjusting the implementation of the timeout or offering alternatives that will benefit users with disabilities. For example, an auction website cannot disable time limits on real-time auctions but provides a phone number that people can call to place bids. A news website provides instant updates about an ongoing story, but users can pause the page, preventing the old posts from disappearing.
- Giving users control over time limits: If a time limit is not essential or related to a real-time event, provide users with options to turn off the time limit before encountering it, adjust the time limit over a wide range, or extend the time limit with a simple action such as pressing the spacebar or activating a button. Users can continue the activity without losing data after re-authenticating if an authenticated session expires.
- Providing clear feedback when a time limit is about to expire: This can be done by providing a warning dialog that allows users to extend the time limit by a simple keypress, such as by pressing the spacebar. Additionally, limit the number of pop-up notifications and other interruptions and ensure that all notifications are accessible for screen readers and other assistive technologies.
- Limiting interruptions and ensuring accessibility for all notifications: It is important to ensure that all notifications are accessible for screen readers and other assistive technologies. Additionally, limit the number of pop-up notifications and other interruptions.
In conclusion, testing the accessibility of interactions with time constraints and handling timeouts gracefully is an important aspect of ensuring that an application meets its users’ needs.
