Skip to content
This repository has been archived by the owner on Oct 30, 2019. It is now read-only.

Minor editorial changes #17

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

Minor editorial changes #17

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions SCs/m5.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,9 @@ General principles while developing include the following:

## Examples

If a developer assigns a double tap as a custom gesture, as the only way to complete an action, a user who is blind using VoiceOver will not have access to that action because VoiceOver reserves the double tap to activate an item.If a developer assigns a swipe right as the only way to open a menu, the VoiceOver user will not be able to do that action, because VoiceOver takes over the right swipe as a way to move from element to element. To avoid this problem, the developer could ensure there is a mobile menu button that works with touch as another way to bring up the menu.
If a developer assigns a double tap as a custom gesture, as the only way to complete an action, a user who is blind using VoiceOver will not have access to that action because VoiceOver reserves the double tap to activate an item.

If a developer assigns a swipe right as the only way to open a menu, the VoiceOver user will not be able to carry out that action, because VoiceOver takes over the right swipe as a way to move from element to element. To avoid this problem, the developer could ensure there is a menu button that works with touch as another way to bring up the menu.

## References

Expand All @@ -59,7 +61,7 @@ If a developer assigns a double tap as a custom gesture, as the only way to comp

# Testability

Test functionally by turning on the assistive technology (AT) for the platform (e.g. VoiceOver on iOS or TalkBack on Android). Conduct QA functional testing such as activating menus, filling in form fields, expanding collapsed content clicking buttons, scrolling down and swiping using the platform gestures. Expected result is that all functionality should be achievable with the AT on.
Test functionally by turning on the assistive technology (AT) for the platform (e.g. VoiceOver on iOS or TalkBack on Android). Conduct QA functional testing such as activating menus, filling in form fields, expanding collapsed content clicking buttons, scrolling down and swiping using the platform gestures. Expected result is that all functionality should be operable with the AT on.

# Techniques

Expand Down