See also: IRC log
<elisabeth_UCF> Thanks, Sarah!
David: Introductions
... Background on community group
<sloandr> https://www.w3.org/community/accesslearn/wiki/Work_Streams#1._Gap_analysis_of_existing_WAI_documents
David: Workstream proposal
... Initial proposal based on discussions from last month's
meeting. Parallel activities probably
... One workstream looking at gap analysis, where do W3C
resources cover online learning, where are there gaps, what
additions might we recommend
... Our group does not have ability to produce documents, but
we can look at gaps in existing W3C and WAI resources
... Other workstream to look at what online learning community
needs, more open discussion of what's needed
... Two workstreams come together down the road to produce
recommendations for W3C
... Purpose of today's meeting to discuss workstream
proposal
... Do they make sense, are they activities the groups wants to
be involved in
... Open meeting to discussion of proposal
Lisa: Likes idea of two streams,
both can do different things but work together, two streams go
well together
... What kind of results are expected from workstreams? Is it a
report, webpage?
... What about a timeline?
... Survey and/or report, everyone could work on that no matter
where they are. We are in different parts of the world, what
works best.
Elizabeth: This group could come up with recommendations for improvement, not sure how it would be received.
David: We have links to W3C and
specifically WCAG WG, through Laura and Sarah especially. This
is a communications channel that our group can use.
... Also EOWG, if still active — test of how well community
group model works, whether our work can have an impact on W3C
processes/resources
... How can we make sure out work has a impact? Might be one
activity to determine that now, good conversation to have now.
Sarah and Dave will explore and report back to group
Sushil: On second workstream, are we looking at specific environments?
David: Have not arrived at formal definition of "education" — only constraints are W3C accessibility standards and how they apply to practice of designing and delivering online learning experiences
Lisa: Agrees with viewpoint of looking at museums, libraries, etc — will this work for everyone?
David: Identify variances in online learning community, perhaps one early activity would be to define range
Sushil: Will have to organize work by tools, e.g., learning management systems, museum online education program organized by exhibit, other tools like online conferencing systems, will need to come up with method of categorizing, will have to break into tools or some other classification to make specific recommendations.
David: Activities are very
different depending on context, for example, how to onboard
user, will be different depending on context (e.g., kiosk in
museum, MOOC, university student)
... Other comments on workstream proposal?
Sandra: Agrees on forming two workgroups, let's start organizing each group and let each group manage its work
David: Will need to decide on logistics, e.g., meeting times
Sushil: Have we identified W3C documents for first workstream?
David: Yes, posting link
<sloandr> https://www.w3.org/community/accesslearn/wiki/Relevant_W3C_Resources_on_Accessible_Online_Learning
David: First attempt at listing
resources from the W3C site, avoided (normative) guideline
documents, focused on guidance documents — a starter to give
sense of different available resources
... Will want to look beyond accessibility documents at others
that have an impact on accessibility
... For example, personas of students/instructors with
disabilities was identified as a useful resource. There are
"personas" on W3C site that include learners, so that might be
one worth expanding/developing
<egyrs> Agree ;-9
David: Use of surveys?
Sarah: Discussion of use of survey to make decisions for the group
David: Reminder to work on surveys that we had administered previously
Lisa: After today, how about
doing a survey everyone is in agreement for the two
streams
... Also use it to choose which workstream
... Then use surveys to decide on how the groups work
David: We also have the wiki to
work on and collaborate on documents
... The wiki is public, good evidence of our work
... Let us know if you have any issues getting access to edit
the wiki.
... Actions: a) update workstream proposal based on discussion,
b) launch survey to ask who wants to be invovled, c) Sarah and
Dave will propose a working model
... Ted asked about potential of group having informal meeting
at CSUN
... Who on call is planning to attend CSUN?
... CSUN is largest conference focused on digital
accessibility
... Will ask on the mailing list and see if we can make
something happen
<elisabeth_UCF> I was just able to log into the wiki
David: Next meeting time will be during CSUN conference, may try to meet up at CSUN, and next teleconference in April
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: SarahHorton Inferring Scribes: SarahHorton WARNING: No "Topic:" lines found. WARNING: No "Present: ... " found! Possibly Present: David Elizabeth Lisa Sandra Sandra_ECUADOR Sarah Sushil accesslearn egyrs elisabeth_UCF https sloandr You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 24 Feb 2016 Guessing minutes URL: http://www.w3.org/2016/02/24-accesslearn-minutes.html People with action items: 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[End of scribe.perl diagnostic output]