Manual testing requires a person to view and interact with the website or application. This type of testing is often done through user testing with people with disabilities, as they are experts in their lived experience and assistive technology. This is highly recommended, as it allows for an in-depth understanding of how the website or application works and how it can be improved for people with disabilities.
Allow users to save data after a session timeout
Define status messages in markup
Don't use flashing lights
Get rid of background noise in audio
Describe errors to users
Make all functionality available through the keyboard
Make multiple types of input available
Make sure the user knows where they are
Make sure there are no keyboard traps
Make time limits adjustable or not essential
Prevent errors when handling legal and financial data
Provide ASL interpretation of video
Provide a way to expand abbreviations
Provide a way to pause audio that plays automatically
Provide a way to turn off character key shortcuts
Provide a way to turn off moving content and animation triggered by interaction
Provide a way to zoom in and resize text up to 200%
Provide audio descriptions of videos
Provide captions
Provide consistent UI components
Provide conventional interactions (instead of motion-activated interactions)
Provide media alternatives of video
Provide more than one way to locate a page
Provide pronunciation for ambiguous words
Provide the option to turn off interruptions
Use suggestion for corrections of errors
Use consistent navigation
Use hover and focus best practices
Use responsive layouts
Use single-pointer gestures
Warn users about timeouts (No surprise to users)
Write descriptive link text
Write clear instructions
No comments:
Post a Comment