W3C

– DRAFT –
WAI Curricula Task Force Teleconference

19 May 2020

Attendees

Present
Estella, Howard, Shadi
Regrets
-
Chair
Daniel
Scribe
Daniel, Howard

Meeting minutes

section>

Restructuring in module 1

<Daniel> Previous version Module 1 Page structure

<Daniel> Previous version Module 2 Navigation and Menus

<Daniel> Live draft Module 1 Page Structure

<Daniel> Live Draft Module 2 Navigation and Menus

Daniel: Shadi had said the topics were not specific enough.
… Therefore Daniel split module 1 into two topics...

Topics in module 1 are: Headings, Page Regions, Marking up Page Contents, Contextual Information of Pages

Howard: That is an improvement, good point from Shadi.

Estella: seems that the interaction part has been lost.

Daniel: tried to incorporate how users interact with each feature/topic area, for example, "headings."
… Therefore no information is intended to be dropped.

Howard: I combine what we had in the first curriculum, we went from how people with disabilities use the Web, different personas, and then we go to structure and semantics. I don't divide this way. Would it make sense ot have a topic as a review of how people with disabilities use the Web?

Daniel: might not be enough to just reference back to how people with disabilities use the web. Not sure.
… We might still need an introductory review of how p\wd use the web.
… Will continue to wrestle that balance.

<Howard> Maybe the fact that you cover it in each topic would address the issue

Estella: Would it be better instead of saying "Courses based on this module:", to say "needed prerequisites."
… or "In order to take this module, you should be familiar or understand these topics:"

Howard: would agree rewording is needed.

Daniel: would agree wording is a little ambiguous but it is same language used in introductory course.
… Probably want to keep consistent with Introductory course.

Daniel: would probably make more explicit references to previous modules needed to have looked at in competencies section.

Use of verb "understand"

Daniel: use of verb understand is considered passive. (this was discussed last year).
… Blooms' taxonomy does include it.
… But has tried using "recognize," "become familiar with," etc.
… Is word "understand" is too passive?

Howard: I don't just say understand, maybe understand and implement. Everything could be understand, so we need to qualify

Estella: agree with Howard. Understand for what?

Daniel: For example, how different users use AT to interact with web pages. Students need to do more than identify these issues.

Estella: maybe "describe" is an action that should be combined with "understand."

Daniel: will work on language that expands beyond just "understanding."

Howard: You could say understand and be able to describe. You have to have a suggested assignment that includes that. Little different because this course is kind of the second part. But you might have people taking this module and not taking the first one.

Howard: Suggests adding "and describe" to the first learning outcome.

Daniel: will try to incorporate that suggestion.
… in one form or another.

Providing more guidance on teaching ideas

Daniel: feedback from survey - instruction was a little too generic.
… For example, in module 1, headings, the first teaching idea - how people with ...
… disabilities use the web...

<Daniel> https://‌www.w3.org/‌2002/‌09/‌wbs/‌35532/‌wai-curricula-teaching-ideas/‌results

<Daniel> https://‌deploy-preview-172--wai-curricula.netlify.app/‌curricula/‌developing-accessible-content/‌navigation-and-menus/

Howard: sees need for consistency and not having links to resources in the competencies.

Estella: agrees we should keep it consistent and put at bottom under resources.

Shadi: agree with more hands-on and apply for assignments. Only concern is with technology such as ...

screenreaders. That type of hands-on can be confusing because developers don't always use such ...

technology correctly. Torn between balance of "empathy" and "doing the right thing."

Maybe have a video where someone watches a user of a screenreader interact with a site instead...

of developer trying to use it themselves.

Shadi: screenreader use can be overwhelming to someone not familiar with it.

Daniel: probably won't meet next week. Will be working on incorporating feedback but will open up ...

another survey next week.

But in 2 weeks module should look more complete.

Minutes manually created (not a transcript), formatted by scribe.perl version 117 (Tue Apr 28 12:46:31 2020 UTC).

Diagnostics

Succeeded 1 times: s/form Shadi/from Shadi/g

Succeeded 1 times: s/I don't just say understand,/Howard: I don't just say understand,/g

Found 'Agenda:' not followed by a URL: ''.

Maybe present: Daniel, Shadi