CAUR feedback

To the RQTF

I've spent this week reviewing the CAUR and thought I'd put them in e-mail at this stage for discussion.

Jason: happy to work on changes myself or if you'd like to take the feedback on in your own work it's all good.

Comments:

Abstract, introduction: all looking good, happy to tweak
User need definition: would be good to expand across different disabilities, seems weighted to vision and cognitive but there may also be mobility issues such as someone trying to edit when page suddenly moves because another user has inserted an image or other content in the document. potential to expand


  *   User need 1: great
  *   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
  *   User Need 2 and REQ2: great for screen reader users, but people with mobility may prefer to stay in current view so inserted content does not interrupt their view mid typing, making it difficult to get back to the right spot
  *   User need 3 and REQ 3: agreed, no changes
  *   User need 4 and REQ 4: agreed, a hotkey would be useful, the only question that I have is if there are multiple collaborators, at which case there should be multiple hotkeys, e.g. (CTRL+1) for first user, (CTRL +2) for second user, etc.
  *   User need 5 and REQ 5: agreed
  *   User need 6 and REQ 6: rather than suppression, I think the ability to easily toggle may be appropriate and this could be either screen reader or collaboration tool itself, I don't think we need to specifically state it's the screen reader responsibility
  *   User need 7 and REQ 7: agreed, very useful. This may also be useful beyond screen readers as extracting an annotation list will be handy for everyone
  *   User need 8 and REQ 8: agreed
  *   User need 9 and REQ 9: I also would add beyond screen readers the need to not rely on colour. Appreciate this is WCAG 1.4.1 but I also think it should be specifically mentioned here to avoid the constant comment "I've marked my changes in red."
  *   User need 10 and REQ 10: agreed

Other thoughts:

  *   The needs interchange between general documents and coding tools. I think we should separate these out.
  *   I think there may be some specific guidance for different types of software, e.g. word processor guidance, spreadsheet guidance, presentation slides guidance
  *   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'm also thinking a quick list of specific collaboration tool shortcuts for the application in use would be useful



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