RE: CAUR feedback

Apologies – forgot to cc my response to the list, yes happy to merge.

Scott.

Dr Scott Hollier
CEO & Co-founder
[Centre for Accessibility Australia logo]<https://www.accessibility.org.au/>
Centre For Accessibility Australia Ltd.
Phone: +61 (0)430 351 909
Email: scott.hollier@accessibility.org.au<mailto:scott.hollier@accessibility.org.au>
Address: 92 Adelaide Street, Fremantle WA 6160

accessibility.org.au<https://www.accessibility.org.au/>
Subscribe to our newsletter<http://eepurl.com/drA-ib>
[Instagram icon]<https://www.instagram.com/centreforaccessibility/> [Facebook icon] <https://www.facebook.com/centreforaccessibility>  [Twitter icon] <https://twitter.com/centrefora11y>  [LinkedIn icon] <https://www.linkedin.com/company/centreforaccessibility/>

CFA Australia respectfully acknowledges the Traditional Owners of Country across Australia and pay our respects to Elders past, present and emerging

From: Jason White <jason@jasonjgw.net>
Sent: Friday, 12 August 2022 8:44 PM
To: public-rqtf@w3.org
Subject: Re: CAUR feedback


Scott sent me a message (apparently not copied to the mailing list) generally approving the proposed changes.

I think that's a good enough reason for me to merge them. They can, of course, be reverted at any time, so if you are uncomfortable with the revisions, there's still ample opportunity to have them revisited.
On 11/8/22 11:55, Jason White wrote:

I've created the following pull request to address most of Scott's comments.

https://github.com/w3c/caur/pull/1


Review would be welcome and appreciated.

Some additional responses appear in-line below.
On 10/8/22 08:37, Scott Hollier wrote:
REQ1: propose that user has choice of status message being provided as user may prefer screen reader or other assistive technology to read current placement
It wasn't clear whether this issue was already addressed by User Need/REQ 3, and, if not, what more should be said.

The needs interchange between general documents and coding tools. I think we should separate these out.

  1.  I think there may be some specific guidance for different types of software, e.g. word processor guidance, spreadsheet guidance, presentation slides guidance
  2.  Spreadsheets for example may need guidance on how much of a cell is visible if a neighbouring cell has content and how a restricted collaboration tool might need to default

I've left this alone for now, but we can add application-specific guidance if we find that there are needs/requirements which don't apply to collaborative systems generally.

I think we should revisit this question if there are more examples of application-specific issues that can't be reasonably generalized. Also, we could address application-specific issues by providing examples accompanying our more general requirements, instead of creating application-specific guidance.