When to confirm an action using UIAccessibilityAnnouncementNotification
My company is developing an application that support general file management operations. We are making a conscious and concerted effort to be best in class from a VoiceOver accessibility standpoint.
One point of contention on our team is whether to confirm actions using the "UIAccessibilityAnnouncementNotification" after completing the action. We used the iOS Mail app as a guideline - after deleting an email there is no confirmation spoken by VoiceOver of the action.
In our application, when running internal accessibility tests as sighted users, we found having VoiceOver confirm our actions helpful.
Is confirming actions such as "file deleted" or "new folder created" useful to users of VoiceOver? Or is the "new-screen" chime sufficient and the notifications of your actions serve to slow down your use of an application?
I prefer to have it configurable. When I'm first working with an app, I may like a confirmation screen to help keep me from making rookie mistakes. As I become familiar with the app, I may wish to turn this off to make use more efficient.
Does it have to be an "either or" situation?
Just to confirm, we are not presenting the user with an alert where they must explicitly confirm the action - we are giving voice feedback to the user after the action has been completed.
VO: "Document 1 - Swipe up or down to select a custom action, then double tap to activate"
User: [[Swipes up]]
User: [[Double taps]]
VO: "Alert - delete document"
VO: "Are you sure you want to delete?"
VO: "Cancel - button"
VO: "Delete - button"
User: [[Double taps]]
VO: "Document deleted" (this feedback is the debatable one that the Mail app does not provide)
Is this still a case where you would prefer to not have the feedback to increase efficency?
Your proposed flow chart is exactly how I'd like it. I appreciate the voiced confirmation of the deletion. iOS would make a sound when the Delete button was pressed, so, having a voiced announcement of confirmation is really no less efficient.
Thanks for the clarification, and for the initial question. Of course I am an N of 1, so perhaps others will chime in with their thoughts.
I am suggesting the voiced acknowledgement in addition to the standard iOS "button pressed" acknowledgement sound - this would not be confusing to you as a user?
I would not find the extra confirmation Voice Over to be confusing. I only mentioned the sound confirmation as an acknowledgment that some audible response is expected, so a voice prompt would not be unexpected or intrusive.
I'm in agreement with your proposal.