W3C home > Mailing lists > Public > public-rqtf@w3.org > June 2021

Re: XAUR and COGA input branch for review

From: White, Jason J <jjwhite@ets.org>
Date: Tue, 29 Jun 2021 15:32:14 +0000
To: Joshue O'Connor <joconnor@w3.org>, RQTF <public-rqtf@w3.org>
CC: Scott Hollier <scott@hollier.info>
Message-ID: <BL0PR07MB801921B65D44BB60D47EC5A2AB029@BL0PR07MB8019.namprd07.prod.outlook.com>
Thank you, Josh, for working on this branch. Itís a substantial move in the directions discussed at recent Task Force meetings.

My main suggestion would be to consider the text of the proposed user needs (e.g., User Need 13), which in some cases are more of a problem statement describing what users can have difficulties with, rather than a statement of what their needs are. I think a slight rewording would help to clarify the needs more effectively

For example, in User Need 13,. The actual need is for support in the user interface to enable users to avoid losing focus or becoming disoriented. The need is for something in the application to avoid or prevent the disorientation/loss of focus, which can then be satisfied by implementing one or more of the requirements listed under User Need 13.



From: Joshue O'Connor <joconnor@w3.org>
Date: Tuesday, June 29, 2021 at 10:52
To: RQTF <public-rqtf@w3.org>
Cc: White, Jason J <jjwhite@ets.org>, Scott Hollier <scott@hollier.info>
Subject: XAUR and COGA input branch for review
Hi all,

Just a heads up that I have minted a new branch for us to review tomorrow on our call.
Please have a look beforehand if possible. The main parts to note are:

Relating to #180 - Wayfinding

I've changed the name of two categories to 'Orientation and navigation' as well as 'Spatial orientation: Mono audio option' - and edited User Need 13 to include people with spatial orientation impairments. I like this as it broadens the net for the basic user need. Most of the wording for the user need is from David Fazio, as he clearly articulates it.


Relating to #181 and #184 - Actionable Targets.
I've taken the suggested new user needs/requirements and now refer to them in a note, and then riff on the need for accessibility APIs to map custom user interface actions to control types as suggested last week.  I've also referenced in the note the content usable doc to provide useful patterns for the reader.


Then we have issues 176 and 183 to also discuss tomorrow.


Emerging Web Technology Specialist/Accessibility (WAI/W3C)


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.

Received on Tuesday, 29 June 2021 15:32:30 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 17 January 2023 20:26:48 UTC