<LisaSeemanKestenbaum> The Web pages
<LisaSeemanKestenbaum> Moving ahead with terms
<LisaSeemanKestenbaum> Wcag updates
<LisaSeemanKestenbaum> +agenda gap analisis
<LisaSeemanKestenbaum> scribe: jennie
Began meeting with introductions, new member: David
<LisaSeemanKestenbaum> https://docs.google.com/document/d/1aJE2C0FzzzXgydEp0MNGSdDDvUTTsANViUVvciFK36k/edit#
1. Check that we have all the design patterns - at first draft.
Steve: there were a couple I could not find
<LisaSeemanKestenbaum> https://w3c.github.io/coga/design/#make-the-purpose-of-your-page-clear
<LisaSeemanKestenbaum> +agenda jennies questions
<LisaSeemanKestenbaum> +agenda humen help
<LisaSeemanKestenbaum> +agenda abis question
Abi: drafting one today, and hopes to have a complete draft by the end of the day
Jennie: after clarification today, I hope to have my draft completed by the end of the day.
Steve and E.A. were having trouble finding some that need to be written.
<LisaSeemanKestenbaum> https://w3c.github.io/coga/design/#make-the-purpose-of-your-page-clear
Lisa: after the first half were completed, I copied them over, and added an editor's note.
<LisaSeemanKestenbaum> https://w3c.github.io/coga/design/#make-it-easy-for-the-user-to-undo-actions
Lisa: they are in the working
draft, but they don't have an editor's note.
... I think they just need review.
Steve: for the ones that don't
need addressing in the Google doc, they don't need to go
through this process at all.
... so does this mean that people have their names on things
that are already complete?
Lisa: yes, people have put their names on things that are already complete.
Steve: I will go through and separate them, and will ping people to inform them if they do not need to work on ones they think they do.
Lisa: great.
Ready to discuss review process?
+1
<LisaSeemanKestenbaum> https://docs.google.com/document/d/1GvlmwHCsWobTgXx9LTWmbRBM6jT8s5lZcardq8u_Ge4/edit#heading=h.um7nz5ganbi3
Lisa: process for review - did anyone try to use it?
Steve: I tried. At the moment, I just put comments in the Google doc.
Lisa: that's fine.
Steve: next step, I will inform the person.
Lisa: I tried one, and I found
there was a lot of content missing from the github COGA
one.
... the history in the one I was reviewing - lots was
missing.
Steve: in the help one - I got confused, because the original one had been split into several patterns.
Lisa: Maybe it lost in 2 different items.
Steve: it is tricky to figure out what is missing.
Lisa: we really don't need to do
a review of one together, because it is not an easy
process.
... I think going through the reviews, we really need to set a
time for a review call - anyone that wants to do reviews.
... I was hoping to do one today, but I doubt people are
available. The one last week did not work out.
... I'm going to assume everyone will need that. You might feel
it more when you try to do review.
Steve: +1
... some of the questions I had were cross cutting questions.
E.g. how much personalization should be mentioned?
Lisa: Either we find a time to do
it mid week, or in the call in 2 weeks we take a call to do
review items.
... one time we could do it in is an hour after this
call.
... what about Tuesday? The same time as this call?
Tuesday march 19th
Jennie (as herself): I have a previous meeting scheduled and cannot make that time.
Steve: +1
Lisa: proposed having a meeting an hour earlier on the 19th of March than this meeting
Jennie, Steve, Lisa can attend.
More on the list are welcome to join.
Steve will send a meeting invite.
Lisa: if there is content that
was in the link to stuff, to check that if it is not in that
pattern, it is in a different pattern. Most likely the pattern
before or after, but check that it has not gotten lost.
... Are people ok if we start answering people's questions?
+1
<LisaSeemanKestenbaum> https://github.com/w3c/wcag21/issues/39
<LisaSeemanKestenbaum> https://github.com/w3c/wcag21/issues/26
Look at the technical resources at the bottom Issue 26 and 39: these were the source ones One is critical features above the fold, and you can find them That there are clear structures and relationships
<LisaSeemanKestenbaum> ?
Question 1: do we want to include tools that appear but are not always visible?
Lisa: need to divide into really important vs less important features.
<LisaSeemanKestenbaum> acl l
Lisa: critical controls are easy
to find, don't disappear. In later details, ok to say it is ok
if they are also somewhere else in a disappearing menu.
... Question 2: is this already included elsewhere
... we are having trouble finding the design pattern Jamie
completed.
... I will ask Jamie to find out what happened to it. I will
also update the table of contents.
Jennie: I will hold on further work on my design pattern, then once I hear back from Lisa about the missing one (so I can determine which components have already been covered in the one he completed), then I can finish the draft. In the mean time, I can work on the review items assigned to me.
<stevelee> https://cloudfour.com/thinks/seriously-dont-use-icon-fonts/
<LisaSeemanKestenbaum> https://w3c.github.io/coga/design/#use-clear-text-and-voice
Discussed Abi's question.
Lisa: E.A. had added some information in about issue about how things appear and are announced based on punctuation and use of symbols.
Janina: what is doing the reading?
Abi: what you would get with a
screen reader vs a text to speech tool.
... e.g. clipboard text to speech. You need the correct mark up
to ensure the pronunciation is correct.
Janina: you get to defer this.
You should push any requirements to the brand new pronunciation
group.
... we are going through the process - gap analysis, use cases,
requirements. Make sure your use cases get in.
... how things get pronounced is hard to specify because it is
different in different geographic regions. E.g. zed vs
zee.
... some locale issues are specified already, but we will work
to further refine this.
Lisa: maybe what we want to say
is use pronunciation best practices, and have a link to this
task force, but also list examples we know well.
... just because it is being addressed in a broad scope, does
that mean we should leave it out of the design patterns?
Janina: yes, but the problem will be how do you know it will reliably make it to the end user. The TTS tools are all over the map. If we could rely on the technology currently available, we would not need the task force.
Abi: that's great to hear that
task force is going ahead. There is also a role to be played by
content creators. So I agree with continuing to include it in
the design patterns.
... the other side is what happens with visual transformation:
removing symbols because of how it is inserted into the
content, because of font changes. I am aware that there are
personalization issues being discussed elsewhere, but those
tend to focus on the changing of text.
Lisa: I don't mind including it, and breaking it into two. Or we could have it as one pattern, but we will want a link to the task force that will have more stuff.
Janina: and anything you do by way of examples will come into scrutiny because of internationalization. Simple example: displaying monetary amounts is displayed differently in different countries.
Abi: I will try to write this pattern as I think I should, and then please comment on it.
Janina: there is also CSS specifications that Lisa has reviewed in the past.
Lisa: this audience is different
Janina: maybe this now needs to be reflected in those CSS Specifications.
Lisa - yes
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: Jennie, AbiJ, stevelee, LisaSeemanKestenbaum Present: Jennie AbiJ stevelee LisaSeemanKestenbaum Found Scribe: jennie Inferring ScribeNick: Jennie WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 14 Mar 2019 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. 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]