RE: Call for Consensus (CfC): Device Orientation Ac

Hi Dr Keith, all,

 

Thanks for your suggestions. We have a convention that we can make editorial changes as part of the CfC, and I think that your changes are good, and would count as editorial changes. I think we should accept them – though with a slight adjustment to the last one, as follows.

 

The sentiment of your last suggested change – that the user should be able to use some other means, like a button, to access the function – is of course right. However, this is in the section of the advice that is about browser (or, more likely, OS) features. However, it would be up to the web app to provide such an alternative for the user to use, and the simplest way for it to do that would be for there to be such a button in the UI all along. So I would tweak the wording slightly, to something like 'and provide the input via an appropriate accessible means, such as a button'.

 

Thus my vote is +1 to the comment, with the editorial changes above included (thanks again for your input).

 

Best regards,

 

 

Matthew

 

Matthew Atkinson

Head of Web Standards

Samsung R&D Institute UK

Samsung Electronics

+44 7733 238 020

 

Samsung R&D Institute (SRUK), Communications House, South Street, Staines-upon-Thames, Surrey, TW18 4QE. A division of Samsung Electronics (UK) Limited, a limited company registered in England and Wales with registered number 03086621 and whose registered address is Samsung House, 2000 Hillswood Drive, Chertsey, Surrey, KT16 0RS, UK. This email (including any attachments) is private and confidential, and may be privileged. It is for the exclusive use of the intended recipient(s). If you have received this email in error, please inform the sender immediately and then delete this email. Unless you have been given specific permission to do so, please do not distribute or copy this email or its contents. Unless the text of this email specifically states that it is a contractual offer or acceptance, the sender does not intend to create a legal relationship and this email shall not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of Samsung.

 

From: Keith Newton <newtonsgroove2@gmail.com> 
Sent: 24 February 2024 20:11
To: Janina Sajka <janina@rednote.net>
Cc: public-apa-admin@w3.org
Subject: Re: Call for Consensus (CfC): Device Orientation Ac

 

My comments on the document are as follows:

1.  " It's important that users can undo any accidental input".  I would change to " It's ESSENTIAL that users can undo any accidental input"

2. "It's important that the user is able to turn off the use of gesture or
motion-based input" I would change to "It's IMPORTANT that the user is able to DISABLE the use of gesture or
motion-based input AND HAVE THE ABILITY TO ASSIGN THE FUNCTION OF THE MOTION-BASED INPUT TO A BUTTON OR [OTHER]"


Dr. Keith



Dr.  Keith Newton (Call me "Dr. Keith")

Executive Leader and Strategic a11y in Digital Accessibility Experience
614-654-4116 <tel:%28614%29%20654-4116>  | https://www.linkedin.com/in/dr-keith-newton <https://protect2.fireeye.com/v1/url?k=faabb7fe-a5308ee1-faaa3cb1-000babdfecba-c25c4156f6641f8a&q=1&e=52da98ad-445e-42ac-a409-bc0a7365b985&u=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fdr-keith-newton>   | newtonsgroove2@gmail.com <mailto:newtonsgroove2@gmail.com> 

 

 

On Sat, Feb 24, 2024 at 1:36 PM Janina Sajka <janina@rednote.net <mailto:janina@rednote.net> > wrote:

Colleagues:

This is a Call for Consensus (CfC) to the Accessible Platform Architectures (APA) Working Group testing for agreement on an Accessibility Considerations addition to the Device and Sensors Working Group's Device Orientation API. The candidate AC section is attached to this email. The API is specified here:

https://www.w3.org/TR/orientation-event/


The review request for this specification is logged here:

https://github.com/w3c/a11y-request/issues/71 <https://protect2.fireeye.com/v1/url?k=73a19389-2c3aaa96-73a018c6-000babdfecba-58f6056357720363&q=1&e=52da98ad-445e-42ac-a409-bc0a7365b985&u=https%3A%2F%2Fgithub.com%2Fw3c%2Fa11y-request%2Fissues%2F71> 

*** Action to Take ***

This CfC is now open for objection, comment, as well as statements of support via email. Silence will be interpreted as support, though messages of support are certainly welcome.

If you object to this proposed action, or have comments concerning this proposal, please respond by replying on list to this message no later than 23:59 (Midnight) Boston Time, Wednesday 28 February.

NOTE: This Call for Consensus is being conducted in accordance with the APA Decision Policy published at: http://www.w3.org/WAI/APA/decision-policy


-------------------------------------------------------------------------------

Janina Sajka (she/her/hers)
Accessibility Consultant https://linkedin.com/in/jsajka <https://protect2.fireeye.com/v1/url?k=d50df72b-8a96ce34-d50c7c64-000babdfecba-ab0d25e199b284f3&q=1&e=52da98ad-445e-42ac-a409-bc0a7365b985&u=https%3A%2F%2Flinkedin.com%2Fin%2Fjsajka> 

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures     http://www.w3.org/wai/apa


Linux Foundation Fellow
https://www.linuxfoundation.org/board-of-directors-2/



Received on Monday, 26 February 2024 09:39:59 UTC