See also: IRC log
http://www.w3.org/WAI/EO/Drafts/training/2009/scenarios.html#eg5outline
Darren: Day 1 is quite action packed
Shadi: Would mention mobile Web
early on and relate that to accessibility issues to make them
more relevant to developers.
... Can Inform About column be the actual topic? beg "Introduce
Accessibility" which would then link back to the topic. The
outline would then be described as text without further links
in short bullets
... idea would be to use the topics to create a training
outline yourself rather than recreate the topics
William: Presenting to an audience of a certain level so trainers will have to tailor the topics to the audience's needs.
Shadi: Agrees with William.
Current approach is very fixed to one audience. need to allow
more flexibility
... Learning objectives are daunting and should be reduced. No
more than 3 or 4 learning objectives. We currently have more of
an outline than learning objectives
... learning objectives are too fine grained for this
setting
William: Agrees
Andrew: Agrees
Darren: Agrees
<Andrew> ACTION: EG5 learning objectives - move them up a level (currently too fine grained) [recorded in http://www.w3.org/2010/03/10-waiage-minutes.html#action01]
Andrew: More like Day 2 "Implementing WCAG 2.0" where the level of detail is not as great
Shadi: What we're trying to say
is that you can use topics to build a training programme. The
examples should show instances of taking those topics and
piecing them together. Current format is not clear how these
topics were used.
... Also need to be careful linking. Some links are useful and
some aren't so useful in the outline
... Use action words and bullets in outline beg Revise;
Demonstrate; Describe; etc
Andrew: Merge the cells for each
subtopic and have a suggested time for each topic as a whole,
giving the presenter more flexibility
... but the multi-day outline should be treated differently
from the short presentations as we're providing so much
material
Shadi: Might be useful to develop an agenda and build the training sessions around that.
Andrew: The "Inform About" column was a pass at an agenda
William: How many people will be using this to conduct the 3 day training?
Andrew: Been given feedback that multi-day training is common.
Shadi: Seen a hunger from people throughout the world who want to provide training but not sure how to give it
Andrew: Look at
http://www.w3.org/WAI/EO/Drafts/training/2009/scenarios.html#s2
... Any alternative names? Promoting doesn't seem quite
right.
William: Example "Gaining
commitment to web accessibility;" isn't clear.
... Who will be giving this talk to senior managers
Shadi: usually an internal staff
member who champions Web Accessibility.
... "Web Accessibility Business Case"
William: Should focus on the uptake of mobile devices in the business case
Shadi: The outline for the business case can be done in the same style as the three day training
William: The note is important
Shadi: We need to look at where those notes live as they're getting lost underneath the table. This is fine tweaking that can be done later on.
<shadi> http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/scenarios.html
Shadi: Based upon feedback the scenarios have been tweaked. Any other comments?
Darren: Prefers the phrase
Journalist in Scenario 2
... Will the links to the previous documents be removed
Shadi: yes, this is just for the
review period
... Technical people tend to look at the Accessibility
Provisions and people from disability groups focus more on the
disabilities and barriers.
... the aspects of age were blended into the scenarios rather
than have specific age-related scenarios.
William: Thinks that this is a good idea as age effects us all.