- From: David MacDonald <david100@sympatico.ca>
- Date: Tue, 19 Apr 2016 12:19:27 -0400
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- CC: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
- Message-ID: <BLU437-SMTP59540A3A1D5D49B68A7845FE6C0@phx.gbl>
I think there is plenty of precedence in WCAG for this type of conditional statement which starts with "**When** x condition applies, y characteristic is a passing condition". See below. *1.3.2 *When the sequence in which content is presented affects its meaning, a correct reading sequence <https://www.w3.org/TR/WCAG20/#correct-reading-sequencedef> can be programmatically determined <https://www.w3.org/TR/WCAG20/#programmaticallydetermineddef>. (Level A) *2.2.5 *When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. (Level AAA) *3.1.5 *When text requires reading ability more advanced than the lower secondary education level <https://www.w3.org/TR/WCAG20/#lowseceddef> after removal of proper names and titles, supplemental content <https://www.w3.org/TR/WCAG20/#suppcontentdef>, or a version that does not require reading ability more advanced than the lower secondary education level, is available. (Level AAA) *3.2.1 *When any component receives focus, it does not initiate a change of context <https://www.w3.org/TR/WCAG20/#context-changedef>. (Level A) *3.3.2 Labels or Instructions:* Labels <https://www.w3.org/TR/WCAG20/#labeldef> or instructions are provided **when** content requires user input. (Level A) On Tue, Apr 19, 2016 at 3:12 AM, Patrick H. Lauke <redux@splintered.co.uk> wrote: > It looks weird if "up event" is a conditional when the actual SC itself > mentions "up event" twice. > > P > > On 19/04/2016 03:09, David MacDonald wrote: > >> Maybe we can manage that with a conditional statement: >> >> 2.5.3 Up-Event Activation: When single touch and/or pointer activation >> can be triggered with the up-event, at least one of the following is >> true (Level A): >> >> - Activation is on the up event, >> - Confirmation is provided which can dismiss activation, >> - >> Activation is reversible, >> - >> A mechanism is available to allow the user to trigger activation on the >> up-event, >> - >> Timing of activation is essential; waiting for the up-event would >> invalidate the activity. >> Note: This is when platform assistive technology that remaps touch >> gestures is not turned on. >> >> >> On Mon, Apr 18, 2016 at 7:50 PM, Patrick H. Lauke >> <redux@splintered.co.uk <mailto:redux@splintered.co.uk>> wrote: >> >> We could start with some actual W3C docs... >> >> http://www.w3.org/TR/DOM-Level-3-Events/#event-type-click >> >> Note the absence of any talk about it being "complex", or >> necessarily involving a mousedown/mouseup (all the spec says is that >> it MAY be preceded by those events, but it also explains that click >> MUST be fired as part of general activation triggers, and that it >> goes beyond just being about mice - in fact, i can programmatically >> fire click events without any down or up events). >> >> p >> -- >> Patrick H. Lauke >> >> >> On 19 Apr 2016, at 01:11, David MacDonald <david100@sympatico.ca >> <mailto:david100@sympatico.ca>> wrote: >> >> >>> I'm fine if you find a more authoritative site that contradicts >>> it? I expect is a correct representation of Click in JavaScript >>> >>> >>>Also, would this be sufficiently clear to mere mortal developers? >>> >>> I expect we can manage it in the Understanding. We can explain >>> that a Click in languages such as JavaScript is a amalgamation >>> of down/up firing on up. >>> >>> On Mon, Apr 18, 2016 at 6:22 PM, Patrick H. Lauke >>> <redux@splintered.co.uk <mailto:redux@splintered.co.uk>> wrote: >>> >>> >>> >>> On 18/04/2016 23:14, Patrick H. Lauke wrote: >>> >>> >>> >>> On 18/04/2016 23:02, David MacDonald wrote: >>> >>> By definition "click" in JavaScript is a complex event >>> that triggers >>> after mousedown, then mouseup >>> >>> |click| >>> Triggered by a mouse click: mousedown and then >>> mouseup over an >>> element >>> source: >>> >>> http://javascript.info/tutorial/mouse-events#complex-events >>> >>> >>> Is there a more authoritative source for this sort of >>> explanation? >>> >>> >>> Notice how http://javascript.info/tutorial/keyboard-events >>> doesn't say anything about "click", even though that event is >>> also triggered by keyboard. So nope, not quite sure about how >>> all-encompassing and accurate the definitions provided on that >>> site are... >>> >>> >>> Also, >>> would this be sufficiently clear to mere mortal developers? >>> >>> P >>> >>> >>> -- >>> Patrick H. Lauke >>> >>> www.splintered.co.uk <http://www.splintered.co.uk> | >>> https://github.com/patrickhlauke >>> http://flickr.com/photos/redux/ | http://redux.deviantart.com >>> twitter: @patrick_h_lauke | skype: patrick_h_lauke >>> >>> >>> >>> >> > -- > Patrick H. Lauke > > www.splintered.co.uk | https://github.com/patrickhlauke > http://flickr.com/photos/redux/ | http://redux.deviantart.com > twitter: @patrick_h_lauke | skype: patrick_h_lauke > > >
Received on Tuesday, 19 April 2016 16:19:58 UTC