RealJoshue108
commented
3 years ago A good catch Jason. I think a note to User need 2 'Motion Agnostic interactions' would be helpful here. I don't think we need a new requirement. How about this (which you have kindly written most of):
NOTE: There are accessibility issues specific to augmented reality. For example, the user may be expected to scan the environment, or scan physical objects, in order to determine the placement of virtual objects. The user may need to mark a location or an area in space so that the AR application can generate appropriate virtual objects. The user should be able to perform these actions in a motion agnostic way.
jasonjgw
There are accessibility issues specific to augmented reality. For example, the user may be expected to scan the environment, or scan physical objects, in order to determine the placement of virtual objects. The user may need to mark a location or an area in space so that the AR application can generate appropriate virtual objects.
Should we mention these issues in the document? Adding Notes to existing material may suffice. For example, these procedures often require specific physical movements - creating challenges for people with physical disabilities - and this is an issue that we cover quite generally. We could add a note or example to mention the AR-specific implications.
However, camera placement and orientation can present challenges to users who are blind, so the application may have to provide guidance/assistance for such functions. We don't mention the problem, and I'm wondering whether we should.
For a full treatment of these issues, and for the context of my questions here, see Herskovitz, J., Wu, J., White, S., Pavel, A., Reyes, G., Guo, A., & Bigham, J. P. (2020, October). Making mobile augmented reality applications accessible. In The 22nd International ACM SIGACCESS Conference on Computers and Accessibility (pp. 1-14).
My question is ultimately whether we should at least note the issues considered in this paper, or add a new User Need to cover what isn't addressed already in XAUR (e.g., assistance with nonvisual camera placement/orientation in AR applications).