Choosing scribe https://www.w3.org/WAI/EO/wiki/WAI_Curricula/WAI_Curricula_Task_Force_Meetings#Scribe_Rotation_List

<scribe> scribe: shadi

Coverage of Dom Management techniques for accessible rich applications

https://deploy-preview-273--wai-curricula.netlify.app/curricula/developer-modules/rich-applications/

DM: moved from "State Changes" to "Document Object Management"
... not about showing or hiding but more about managing nodes

CD: we addressed live regions in previous module?

DM: yes but in the context of individual widgets

CD: here you are speaking of adding or removing DOM nodes
... think also need to speak of changing content
... maybe with reference to live regions in previous module

DM: good point

HK: always get confused by "Courses based on this module"
... know this is template but confuses me

DM: this was put to clarify that this is not a course

CD: maybe add the word "should", as in "Courses based on this module should"?

DM: it is shorthand for "What courses based on this module should do"

HK: adding the word "should" makes a big difference
... keep thinking the list below are courses based on this module

SAZ: "Courses based on this module will teach you:"
... something like that to remove "should"
... sometimes considered normative language

CD: would remove "you" because this is for teachers not for students
... we use "should" directly below

HK: understand the argument but end up with complex language to avoid a simple sentence

DM: coming back to prior point from Carlos about changes
... does this need to be a separate learning outcome or get added to existing one?

CD: think can be added, does not need separate
... confused by "visual appearance" in the first learning outcome

DM: intent is to match "visual appearance"

CD: didn't get the grammar

SAZ: not sure about "matching visual order"
... sometimes doesn''t
... needs to be logical or coherent or such

CD: could separate into two
... one on adding, removing, and changing in accessible way
... the other is ensuring DOM has logical sequence

SAZ: think this topic could be disolved into the other topics

HK: maybe connect the first and second topics more closely

SAZ: missing the impact of this topic to accessibility
... showing, hiding, or changing will likely impact structure and relationships, keyboard and interaction, or notifications

CD: could try

Standard versus non-standard keyboard shortcuts

DM: using terms "standard shortcuts" and "non-standard shortcuts"

CD: wouldn't understand these terms immediately and would appreciate examples

https://www.w3.org/TR/wai-aria-practices-1.1/#kbd_shortcuts

SAZ: maybe link back to this to ensure nuance

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: Carlos Daniel Howard shadi
Regrets: Donal_J. Donal_F. Gerhard Estella
Found Scribe: shadi
Inferring ScribeNick: shadi

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)