The section on voice commands (section 4.6, but also all of section 4) really made me think, as with other user needs sections, that we need existing AT to be able to work with XR, where it makes sense, in order to avoid wheel reinvention. Having said that, content design choices can make so much difference and ensure that people are kept immersed in the world, rather than being brought back out by the experience of using traditional AT. I think the focus on user needs - not how to meet them - is very helpful here, as those needs are not going to change.

My question is: is it within the remit of XAUR to provide some context on that larger AT/content-design combo, as it does with explaining the fundamentals of XR and AT above?

This needs to have the XAUR label, but I don't have permissions to make that change on this repo.

Original feedback email, for reference