Re: WAI Curricula Task Force Meeting April 21

Hi Daniel,

I personally like how you provide the learning outcomes for Module 1, 
yet I also like the mappings to the WCAG Success Criteria. I wonder if 
it is worthwhile to put the corresponding SCs in brackets after each 
learning outcome (eg. "Markup the different sections of a web page (SC 
1.3.1)"), or to list all corresponding SCs in another sections right 
after learning outcomes (eg. "SCs related to this module")?

Best,
   Shadi


On 28/04/2020 13:02, Daniel Montalvo wrote:
> Hey Howard, Stella, Shadi,
> 
> We are not having a teleconference today. It took me a bit more time 
> than expected to implement last week’s feedback on learning outcomes for 
> module 1 and I could not build an agenda with enough time for you to be 
> prepared for the discussion. I invite you to use the scheduled 
> teleconference time to go through the questions below. You can answer to 
> this email with your views on them, ideally by Thursday EOB.
> 
> Please find the current draft at 
> https://wai-curricula.netlify.app/curricula/developing-accessible-content/
> 
>   * How to include success criteria in learning outcomes. In module 1,
>     success criteria are not mentioned explicitly but they are tied to
>     each of the learning outcomes. In other modules, they are listed all
>     together in a specific learning outcome that talks about analyzing
>     (or determining) if these success criteria are met (which may seem a
>     bit disconnected. I plan not to mention them but make sure each
>     learning outcome that we use covers at least a success criterion,
>     i.e., following the approach in module 1. Do you have further
>     thoughts about this approach?
>   * Making learning outcomes more specific -- Based on your feedback
>     that learning outcomes were too general, I have detailed learning
>     outcomes more. But details can be provided in different ways. In
>     module 1, I have qualified the outcomes, but specific techniques are
>     not mentioned at a module level. However, in the rest of the modules
>     there are specific mentions to techniques at a module level, which
>     may overlap with learning outcomes for topic. My plans are to
>     qualify the outcomes at a module level and dive into specific
>     techniques in teaching ideas and topics to teach as we do now in
>     module 1. This leaves us room for the details of specific techniques
>     in topics to teach sections. Do you have further thoughts about this
>     approach?
>   * Use of "Understand" is often considered too passive a verb to be use
>     in learning outcomes. However, there is also literature that
>     introduces its use within the cognitive domain, revising the Bloom's
>     taxonomy. Some examples of our use are:
>     “Understand how different assistive technology users orient and
>     navigate web pages”.
>     “Understand how several groups of users interact with navigational
>     elements”.
>     “Understand how several groups of users access information contained
>     in graphical elements”.
>     “Understand various strategies for users to navigate and process
>     information presented in tables”.
>     “Understand how some users navigate, fill in, and perceive
>     information from form fields”.
>     We previously had “recognize”, and we could have something like
>     “Acknowledge”, “Familiarize with”, “Become familiar with” or “get
>     acquainted with”. I see all of these examples as different ways to
>     actually mean understand, so I would mildly go for “understand”. Do
>     you suggest other phrasings of these sentences [to avoid using the
>     term understand]?
> 
> Thanks.
> 
> Best.
> 
> Daniel Montalvo
> 
> Accessibility Education and Training Specialist
> 
> W3C/WAI
> 
> *From:* Howard Kramer <howard.kramer@colorado.edu>
> *Sent:* Tuesday, April 28, 2020 5:25 AM
> *To:* Daniel Montalvo <dmontalvo@w3.org>; public-wai-curricula@w3.org
> *Subject:* Re: WAI Curricula Task Force Meeting April 21
> 
> Are we having a meeting on Tuesday? I haven't seen anything.
> 
> -Howard
> 
> ------------------------------------------------------------------------
> 
> *From:*Daniel Montalvo <dmontalvo@w3.org>
> *Sent:* Tuesday, April 21, 2020 7:20 AM
> *To:* public-wai-curricula@w3.org <public-wai-curricula@w3.org>
> *Subject:* WAI Curricula Task Force Meeting April 21
> 
> Hello all:
> 
> Today we are going to have another of our weekly meetings.
> 
> Please use this phone bridge for the call:
> 
>    -
> 
> https://mit.zoom.us/j/108109976
> 
> Password: curricula
> 
> An agenda follows:
> 
> # Discussing survey results
> 
> https://www.w3.org/2002/09/wbs/35532/wai-curricula-tf-learning-outcomes-revie/results
> 
>   * Changing scope of learning objectives for the sub bullets under
>     https://wai-curricula.netlify.com/curricula/developing-accessible-content/
>     <https://secure-web.cisco.com/1sXDQZu4yC4lrdWXnifKr_bkHmWeQXDNtd0IZVxC4sYlRZQYaSXR0NSX682P9NvN27X3567Bu7QQMqaankAnjmfsvDSRmOjROsnCloAWylArP5lUQO5_gS6kJgXRZyx6oMYKQWgY4ebq68a82AZj4d6CxNMhhMx0_bxDx0iTqRH8Nsud114EijWKElqUswClj5A3VOsTM1DCNXQMksc1IAlFdFaOR4JV0i_QtilJXvvOMMRWaDhyQFTtv7a9vkiqdXtipzo-F4T-rpmP1evw1aEfdlNCUTEgtxEBrn9ZgmIDLA-hVZHjMjlLHEYjqB5aS0bnOMTAEmvFlT4D4b5v2ii5SXQjTPtBjFs2wB6gLP64JOGHHAx5lyQe061kEUI84OW6RYxZHiUSqkSrqYseI20_M8wK6IoD9hTrLoTAyTFr6PaXC7D5WtGvz0vg-0VFeq9dQ5T5DaVUi_nxKy8rt_A/https%3A%2F%2Fwai-curricula.netlify.com%2Fcurricula%2Fdeveloping-accessible-content%2F>.
>     Making reference to further modules and topics instead of types of
>     disabilities and functionality.
>   * Removing learning outcome about focus and visibility techniques in
>     module 1.
>   * Adding learning outcomes specifically about labeling sections of
>     websites (tied to SC 1.3.1) in module 1.
>   * Adding references to language identification and language change.
>   * Tying each referenced success criteria to one or more learning
>     outcomes instead of referencing all success criteria at once.
> 
> Thanks.
> 
> Best.
> 
> Daniel Montalvo
> 
> Accessibility Education and Training Specialist
> 
> W3C/WAI
> 

-- 
Shadi Abou-Zahra - http://www.w3.org/People/shadi/
Accessibility Strategy and Technology Specialist
Web Accessibility Initiative (WAI)
World Wide Web Consortium (W3C)

Received on Monday, 4 May 2020 11:27:03 UTC