RE: WAI Curricula Task Force Meeting November 10 2020

Hello all,

As a follow-up on yesterday's email, here are some use cases that may help us steer the discussion this afternoon, to better
determine the best way for us to cover them in the curricula.

If you can, please skim them prior to the meeting.

* A "simple" single page application, such as the WCAG-EM Report Tool.
    https://www.w3.org/WAI/eval/report-tool/
* A web-based email client, that tries to give the user the experience of a desktop email client
* A web-based spreadsheet or word processor, that tries to give the user the experience of a desktop application.
* A user interface built with several custom widgets together. Maybe a carousel, an expandable-collapsible menu, an auto-updating
news feed, a chatbot.

We could:

* Work to include those in the structure that we already have. We would add the corresponding knowledge to structure and semantics,
menus, tables, forms and input elements, and custom widgets.
* Add the above use cases to the existing "Custom widgets" module. This way we would avoid making the previous modules too dense
for those who are new to accessibility.
* Create a new module (current proposal). This will clearly identify these use cases from the outside and will help us communicate
that we are indeed covering them.

Find below participation, agenda, and link for the currently drafted learning outcomes.

---

Hello all:

Tuesday November 10 we are going to have another WAI Curricula Task Force 
teleconference.

Topic: WAI Curricula Task Force Weekly Meeting
Time: November 10, 2020 5:00 PM CET (Central Europe Time)

Participation Info:
https://www.w3.org/2017/08/01-eowg-info.html

IRC:
http://irc.w3.org?channels=#wai-curricula

Port 6665.
Channel #wai-curricula

Agenda:

Agenda+ Early concept draft -- Learning Outcomes for Module 7, Rich Applications
https://deploy-preview-273--wai-curricula.netlify.app/curricula/developer-modules/rich-applications/#learning-outcomes-for-module
<https://deploy-preview-273--wai-curricula.netlify.app/curricula/developer-modules/rich-applications/> 

I am looking for first thoughts, reactions, things you miss or things that should not be there.

**Background**: We received comments that SPAs coverage was missing from these curricula. We were discussing how single page
applications could be covered and concluded that a specific module along the lines of "applications" or "Rich applications" would
better communicate that these are covered to people that is not very familiar with accessibility. We proposed to add a new module
that would cover rich applications, including aspects such as dynamic content, focus and keyboard interactions, navigational
mechanisms, and notifications and updates. For details, see October 27 minutes at:
https://www.w3.org/2020/10/27-wai-curricula-minutes.html/#item02 <https://www.w3.org/2020/10/27-wai-curricula-minutes.html/> 

---

		Join Zoom Meeting

		https://mit.zoom.us/j/757978651
		One tap mobile
		+16465588656,,108109976# US (New York)
		+16699006833,,108109976# US (San Jose)

		Meeting ID: 108 109 976
		US : +1 646 558 8656 or +1 669 900 6833

		International Numbers: https://mit.zoom.us/u/aB9ZEzaQH

		Join by SIP
		108109976@zoomcrc.com <mailto:108109976@zoomcrc.com> 

		Join by Skype for Business
		https://mit.zoom.us/skype/108109976


--

Daniel Montalvo

Accessibility Education and Training Specialist
W3C/WAI