RE: Checklist proposal for XAUR document

To Josh

I really like the checklist idea. I agree with Jason's' original point that guidance is needed, but not at the expense of the simplicity the current document provides. As discussed on the call, the current document works well in terms of introducing people to the XR space and I wouldn't want to see this lost.

As such, the checklist idea is a really good one: it retains the XAUR informative process of guiding people through access considerations, then in the checklist provides XR specific guidance to developers/designers that need it Best of all, it does this without taking away the normative value of standards that will cover this space in the future. In fact it may even provide such standards an opportunity to draw on the checklist for guidance. 

+1 from me - best of both worlds IMHO. . 


Dr Scott Hollier 
Digital Access Specialist 
Mobile: +61 (0)430 351 909
Technology for everyone
Australian Access Awards 2019 Call For Nominations – celebrate best practice by nominating your favourite accessible Australian website or app. It’s free!  
Keep up with digital access news by following @scotthollier on Twitter and subscribing to Scott’s newsletter. 

-----Original Message-----
From: Joshue O Connor <> 
Sent: Thursday, 29 August 2019 11:22 PM
To: White, Jason J <>; RQTF <>
Subject: Re: Checklist proposal for XAUR document

On 29/08/2019 15:15, White, Jason J wrote:

> Another drafting possibility: we could express the major points as questions for developers to consider in creating their new XR technologies/libraries/frameworks/XR applications.

Good suggestion - lets discuss that on Weds call. I will have some more concrete example to populate the various sections by then, and we can work out if that format works, or if the questions format is better.



Emerging Web Technology Specialist/Accessibility (WAI/W3C)

Received on Friday, 30 August 2019 02:12:38 UTC