[11:01] == Kim_Patch [~Kim_Patch@public.cloak] has joined #mobile-a11y [11:02] == laura [~laura@public.cloak] has joined #mobile-a11y [11:10] <Kim_Patch> https://docs.google.com/document/d/1ouVFq4w-i0rchNHtTAG_JoRwHfYm9mN2MkxFBct1JSI/edit [11:10] == laura [~laura@public.cloak] has quit [laura] [11:11] <Kim_Patch> TOPIC: custom interactions [11:12] <Kim_Patch> Jake: the proposed SC text I completely changed, added a note, also cleaned up previous [CUT]
benefits, rewrote three paragraphs
Jake: first we need to have
consensus on the new success criteria text
... I hope we solved two problems – first, what is custom, we
turned it around to say what isn't custom, that makes it
easier
... also standards and how to deal with it. If they can be used
with the standard interactions than that one is also completely
off the table
but it leaves us with two questions. The definition of what is standard. We talked about it last time but I would like to see if it's feasible. We need to know if it's possible before we work it out.
so if it seems valid we can continue to work it out
Jake: there's one thing we didn't
solve now, but it's an interesting one. If you don't know there
is a custom interaction how can you test it?
... I know Detlev brought it up and it is logical because your
test procedure should be do everything humanly possible to see
if there is something, but I'm not sure if that's always needed
for Success criteria, because of that is so then you can never
get it.
... so the test procedure is an interesting one – how do you
know? You can look in the code or do we need to have another
approach. We know there is an interaction which is not standard
so it's custom let's see if it's documented – something like
that.
... everything before user benefits is new – the SC, the four
paragraphs
Reading the SC using suggesting mode
Jake: the most important part is the fourth paragraph in Benefits
Note – Forgot to start Trackbot at the start of the meeting, so I started it late and added the brief minutes.
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: Kim, Jennifer, Jake Present: Kim Jennifer Jake WARNING: Possible internal error: join/leave lines remaining: <Kim_Patch> [11:01] == Kim_Patch [~Kim_Patch@public.cloak] has joined #mobile-a11y [11:02] == laura [~laura@public.cloak] has joined #mobile-a11y [11:10] <Kim_Patch> https://docs.google.com/document/d/1ouVFq4w-i0rchNHtTAG_JoRwHfYm9mN2MkxFBct1JSI/edit [11:10] == laura [~laura@public.cloak] has quit [laura] [11:11] <Kim_Patch> TOPIC: custom interactions [11:12] <Kim_Patch> Jake: the proposed SC text I completely changed, added a note, also cleaned up previous [CUT] No ScribeNick specified. Guessing ScribeNick: Kim_Patch Inferring Scribes: Kim_Patch WARNING: No "Topic:" lines found. Found Date: 05 Dec 2019 People with action items: WARNING: Possible internal error: join/leave lines remaining: <scribe> [11:01] == Kim_Patch [~Kim_Patch@public.cloak] has joined #mobile-a11y [11:02] == laura [~laura@public.cloak] has joined #mobile-a11y [11:10] <Kim_Patch> https://docs.google.com/document/d/1ouVFq4w-i0rchNHtTAG_JoRwHfYm9mN2MkxFBct1JSI/edit [11:10] == laura [~laura@public.cloak] has quit [laura] [11:11] <Kim_Patch> TOPIC: custom interactions [11:12] <Kim_Patch> Jake: the proposed SC text I completely changed, added a note, also cleaned up previous [CUT] WARNING: Possible internal error: join/leave lines remaining: <scribe> [11:01] == Kim_Patch [~Kim_Patch@public.cloak] has joined #mobile-a11y [11:02] == laura [~laura@public.cloak] has joined #mobile-a11y [11:10] <Kim_Patch> https://docs.google.com/document/d/1ouVFq4w-i0rchNHtTAG_JoRwHfYm9mN2MkxFBct1JSI/edit [11:10] == laura [~laura@public.cloak] has quit [laura] [11:11] <Kim_Patch> TOPIC: custom interactions [11:12] <Kim_Patch> Jake: the proposed SC text I completely changed, added a note, also cleaned up previous [CUT] WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]