Meeting minutes
Announcements
<Chuck> woot woot!
maryjom: We published Tuesday!
maryjom: As we get responses, I will try to assign out for leads per issue
… we already have comments, but i think that will help us stay on top
Chuck: WRT 2.2, chairs are processing two formal objections, no news other than that.
maryjom_: not hearing other announcements, moving on, non specific comment from Craig Allen Keefer
<Chuck> yes you are
PhilDay: I'm happy if its useful to work with someone on a response. I know Craig. We were working with Kiosk Manufactures Association for a while. We know him.
PhilDay: With addition of IBM, we've been considering kiosk requirements.
discussion about comment maybe not being on topic
MaryJo: Do comments come only to chair? I'll forward to you.
maryjom_: will forward to phil
PhilDay: Is there a place where we can all view them?
<maryjom_> public-wcag2ict-comments@w3.org
Discussion about listserv comments being availalbe...
MaryJo: It's in the public wcag2ict comments. That's where it goes to. Listserv for emails. Perhaps you have to sign up?
maryjom_: may need to subscribe
PhilDay: Thanks, I may have overspoken.
<Zakim> Chuck, you wanted to ask about scribing and make a comment on comments
Chuck: Point of order, please avoid being judgemental
Bruce: I have some experience with Craig. I can reply back to him. I bet the comments are archived.
bruce: i have worked with kiosk association and craig allen keefer
<PhilDay> Web link to the email archives: https://
maryjom_: Commenters have option to email rather than file issues
Phil Day volunteered to draft reply for group.
Craig email to list: https://
Survey Results: Review draft updates to SC Problematic for Closed Functionality
1.4.10 reflow
<maryjom_> https://
maryjom screen shares
<maryjom_> Option 1 – as proposed: 1.4.10 Reflow—Many closed functionality products do not allow users to modify the viewport or change font sizes, so there would be no need to impose a requirement on all closed functionality that content is able to reflow. Additionally, many closed functionality products do not display large chunks of text and only have UI controls. In such cases, two-directional scrolling to access the text and UI controls may be[CUT]
<maryjom_> Option 2 – with edits: 1.4.10 Reflow —Where closed functionality prevents users from modifying the viewport, but provides a different mechanism for resizing text: ensure that resizing does not cause loss of information or functionality and does not require two-dimensional scrolling. Additionally, content which meets the two-dimensional layout exception may be more common in closed functionality products, such as products with only UI con[CUT]
<maryjom_> text.
maryjom shares doc with side-by-side edits, please read two proposals.
maryjom_: any discussion on proposed changes?
<Sam> Still like Option 1
mitch11: My edit was meant to apply some clarification. Summary sentence only mean "essential exception"
maryjom_: So you think it cannot possibly pass ?
mitch11: As with other commenters on GitHub, one does not pass just because technology supported.
maryjom_: What about if functionality is there?
maryjom_: It will have limited functionality , so with a reason would not have reason to have feature on product.
mitch11: Did we have similar SC whith enlargement ?
bruce_bailey: want to +1 Mitch and GitHub thread that not-a-pass might be better than not-applicable
LauraBMiller: Not needed or not possible given the platform should be same as not applicable
Sam Ogami: We had this discussion before and we agreed not applicable should be a pass.
Mike_Pluke: We don't want to pass just because not support by hardward.
mitch11: Please see note 6 on the screen. Can sometimes fail because not possible and can sometimes be done.
FernandaBonnin: I would like to support idea behind note 6
Mike_Pluke: Reflow would not be applicable where technology simply does not support, not quite the same as for magnification, we might just say it cannot be met
Sam: I am hearing conflation of failing and not applicable. They are two different things.
mitch11: To me, not applicable means a pass...
… WCAG does not have N/A but in WCAG, N/A is a pass. We seem to mean really not applicable as could not be considered.
mitch11: I am okay with first sentence as-is, but would like more clarity on concluding sentence.
<Zakim> FernandaBonnin, you wanted to say more thank support the idea behind 6, I want to understand difference of NA vs fail and outline in a note
mitch11: even changing period to semi-colon helps with clarity.
FernandaBonnin: Even more than supporting Note 6, I encourage to provide a little more clarity especially for this SC.
… The main concepts are conflicting, moreso than with magnification.
Sam: This is closed functionally, which is different than with magnification as ICT might have feature for larger text.
Mike_Pluke: First sentence is already describing non-applicable situation.
… those are the cases we are talking about reflow not being possible.
<LauraBMiller> +1 Mike
maryjom_: Those are the situations were are trying to carve out. Can't have reflow when there is one screen of data. There is not scroll bars and not concept of page is not applicable.
Mike_Pluke: Agree that those are situations where technology means reflow is not applicable.
Chuck: Agree that WCAG does not have "not applicable" but we do have concept in some SC examples, for example orientation mentions piano keys which cannot rotate
PhilDay: I am not comfortable with implicit definition so I think we may need to define not applicable more explicitly.
maryjom_: VPATs have not applicable as an option, and includes definition.
[mary jo goes to ITIC page to check]
<maryjom_> VPAT has this answer and definition: Not Applicable: The criterion is not relevant to the product.
maryjom_: finds excerpt to past into IRC
This success criterion is generally not applicable when the content repeats or is synchronized with other content, so long as the information and data is adjustable or otherwise under the control of the end user. Examples of time limits for which this success criterion is not applicable include scrolling text that repeats, captioning, and carousels.
Chuck: Previous WCAG2ICT had description and analysis of not applicable for some of its SC
Chuck: See Timing Adjustable
<Mike_Pluke> When one of the pre-conditions is false the requirement is not applicable. Consequently, the result of the tests in Annex C can be: not applicable, pass, fail, or (in exceptional circumstances) not testable.
Mike_Pluke: I will share some prose from EN 301 549 which has similar concept of not applicable.
… We have preconditions, so ICT only tested if precondition is met.
<Zakim> PhilDay, you wanted to say We may need to poll changes to the reflow words, then separately if we need a definition
PhilDay: Might two polls be clearer?
<maryjom_> Poll: Which do you prefer? 1) Option 1 – as proposed, 2) Option 2 – with edits, 3) Option 3 – Remove bullet, or 4) Something else
<Sam> 1
<FernandaBonnin> 2
<ThorstenKatzmann> 1
<LauraBMiller> 1
<Mike_Pluke> 1
<Devanshu> 1
<ChrisLoiselle> 1
PhilDay: We may need to poll changes to the reflow words, then separately if we need a definition
<PhilDay> 1 or 3 - not sure what is meant by removing bullet
<PhilDay> then 1
PhilDay: I am not clear what "remove bullet" means in option 3
7 1's, 2 2's
maryjom_: That we don't need it because, dissimilar with magnificaiton SC
<PhilDay> I think Mitch had an edit: 1.4.10 Reflow—Many closed functionality products do not allow users to modify the viewport or change font sizes, so there would be no need to impose a requirement on all closed functionality that content is able to reflow. Additionally, many closed functionality products do not display large chunks of text and only have UI controls; in such cases, two-directional scrolling to access the text and UI controls may be[CUT]
<PhilDay> This was changing the period to a semi
FernandaBonnin: I can live with one
bruce: we need some kind of edit -- even just the semi colon proposal
Chuck: I think we have us at a consensual possition.
… There are also other that have spoken aobut "live with" so use "can tolerate" please.
maryjom_: Okay, but we are a little happier.
RESOLUTION: Update 1.4.10 Reflow bullet using Option 1, with minor edit as shown in the minutes above.
<Sam> +1
<Mike_Pluke> +1
maryjom_: Took us a bit, but we did it! Reflow definitately tricky.
<Devanshu> +1
maryjom_: Text spacing is next, we have 15 min., so try.
Text Spacing 1.4.12
<maryjom_> https://
<LauraBMiller> +1
maryjom_: from survey, 7 okay as is. A couple editorial suggestions.
[maryjo screen shares to highlight differences]
maryjom_: Asked in survey why are we repeating, when covered with introduction of topic of closed functionality.
… the working group recommened highlighting per SC so harder for anyone to miss
<maryjom_> Option 1 – as proposed: 1.4.12 Text Spacing—Applicability of this Success Criterion to closed functionality software is limited to software implemented using markup languages, which is rare. Closed functionality technologies also rarely support user modification of line, paragraph, letter or word spacing. Therefore, there is no need to impose this requirement on all closed functionality software.
<maryjom_> Option 2 – with edits: 1.4.12 Text Spacing—Applicability of this Success Criterion to closed functionality software is limited to software implemented using markup languages, which is rare. Closed functionality technologies also rarely support user modification of line, paragraph, letter or word spacing. In such infrequent cases the SC applies as written.
LauraBMiller: Seems like we should be consistent with previous decision and just say NA. Where NA, it applies.
… Use same phrasing regarding where it applies or not.
maryjom_: Okay, be clear if it is not using a markup language
Bruce: I think this one, the markup language prerequisite is even more concrete/blatent than the prior. This will be extraordinarily rare for the display to be using markup languages.
bruce: Not only re-use, re-enforce that this makes it even more rare than reflow.
bruce: The applicability of the SC for "mark up language" make the SC very very rarely applicable.
Mike_Pluke: We are relizing in our world that the internal representation might be a markup language but thats not apparent to user.
… but to complicate things,, reference to mark up language more confusing even than that!
PhilDay: I think phrasing in option 2 needs more editiing. I suggest combining closed functionality with mark up language.
<PhilDay> Proposed edit: 1.4.12 Text Spacing—Applicability of this Success Criterion to closed functionality software is limited to software implemented using markup languages, which is rare. Closed functionality technologies also rarely support user modification of line, paragraph, letter or word spacing; this requirement is only applicable to systems that do support these modifications.
PhilDay: Option one is "when the cases apply" that makes more sense as an approach to me. Option 2, applies as written, completely different
… subgroup wrote this as we did, because of the structure
Mike_Pluke: The use of mark up language is not relevant, because ICT might allow editing and might be a useful feature.
… if the SW supports, then can be applied directly/
maryjom_: not sure we are going to get to consensus today on this
maryjom_: let me compare to reflow...
maryjom_: This also points out that "apply wcag as written" is not so useful. If ICT allows these sort of changes, requirement should be use.
… to mikes point, the mention of "markup language" is a red herrring.
… but our TF is limited.
I must drop