- From: lisa.seeman <lisa.seeman@zoho.com>
- Date: Wed, 05 Jul 2017 14:05:56 +0300
- To: Michael Pluke <Mike.Pluke@castle-consult.com>
- Cc: "W3c-Wai-Gl-Request@W3. Org" <w3c-wai-gl@w3.org>, "public-cognitive-a11y-tf" <public-cognitive-a11y-tf@w3.org>
- Message-Id: <15d126d9115.125bfee7d24099.5242659933971168206@zoho.com>
Hi mike Answering your questions 1.This does not include “context sensitive help” - , there were issues with this on the call on Thursday and so I left it out 2. contextual information is defined in the issue 3. common form elements will definitely need to be precisely defined. I was thinking in the definition we could list them. As I mentioned in the proposal , we could also ensure that we have supportive techniques for each one. Hope this clarifies it lisa ---- On Tue, 04 Jul 2017 18:03:53 +0300 Michael Pluke<Mike.Pluke@castle-consult.com> wrote ---- Hi As written, it doesn’t actually make sense as a sentence – with two “is”s. Is this following re-write what is intended? Programmatically determinable contextual information is available for regions, common form elements, common navigation elements and common interactive controls. This does not include “context sensitive help” from the current wording – is this deliberate or an omission? I still think that there may be the following problems: Don’t some people have a problem with the words “contextual information”. What qualifies as contextual information and are there existing standards or published schema that define the appropriate semantics? Then there is the word “common”. This will clearly need to be precisely defined. Without a definition it could mean: commonly used across websites – a tester would have no way of knowing the frequency of use different types of interactive controls for example. Commonly used within a website – which would need to be backed by testing of all pages or author provided statistics of which are the most commonly used types. Or something else … All of this needs to be clarified before this is likely to be acceptable. Best regards Mike From: lisa.seeman [mailto:lisa.seeman@zoho.com] Sent: 04 July 2017 13:01 To: W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org>; public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org> Subject: Moving personlization forward - wording suggestion Hi Folks Moving personlization forward - how about we replace the second option in the current wording as follows: contextual information is available for regions, common form elements, common navigation elements and common interactive controls is programmatically determined. We would then specify what is included in common form elements, common navigation elements and common interactive controls in the definitions and make sure we have good supporting techniques for each one. Does that sound like a good approach? Current wording: For pages that contains interactive controls or with more then one regions, one of the following is true: a mechanism is available for personalization of content that enables the user to add symbols to interactive controls OR contextual information or context sensitive help is availible for regions, form elements, main navigation elements and interactive controls is programmatically determined.
Received on Wednesday, 5 July 2017 11:06:32 UTC