https://www.w3.org/WAI/EO/wiki/WAI_Curricula/WAI_Curricula_Task_Force_Meetings#Scribe_Rotation_List
<scribe> scribe: dmontalvo
https://deploy-preview-389--wai-curricula.netlify.app/curricula/designer-modules/
Carlos: Agrees, probably more
adapted to designer structure
... Not really sold yet on the landmarks and text topics
... where are you placing headings
... Also not sure about widgets on module 7, you will get there
as you write the module
Donal: Also think landmarks and
text is weird, and interested on how module 7 will evolve
... landmarks I see that term being used by people in the
accessibility world, not so in the design world. Is landmarks
almost a term that is used exclusively by accessibility
specialists?
... Generally when I talk about is from and information design
perspective I talk about structure
https://github.com/w3c/wai-curricula/issues/377
https://deploy-preview-389--wai-curricula.netlify.app/curricula/designer-modules/navigation-design/
https://github.com/w3c/wai-curricula/issues/377
https://deploy-preview-389--wai-curricula.netlify.app/curricula/designer-modules/navigation-design/
Carlos: I like the distinction
between site and page navigation, even though there are
mechanisms that are used in both.
... WE can add some note in there when we present these
mechanisms, but I don't think that is a huge problem
... Last topic I am not sure about, maybe we need to get rid of
it, its contents could be covered in the site navigation
topic
... also headings relate both to page and site navigation
Donal: Conceptually page
identification has always be more related to the structure of
the page rather than navigation
... But also the indication about the current page on the menu
needs to be signaled
... The use of behaviors and patterns is weir, maybe we need to
call this just "Menus", although "behaviors" is helpful
here
... Also very valid point that you raised about page internal
menus,
Carlos: Agree with Donal on the
menu behaviors and patterns topic, we only use patterns in the
name of the topic and on one of the ideas to assess
knowledge
... We also use types so maybe replacing these for patterns
would help consistency if we still want to keep patterns
Donal: I would be totally
satisfied with a module on forms and nothing else. Forms is
really the main type of interaction of public bodies with the
public.
... What is here seems comprehensive. I don't know here
something like CAPTCHAs fall in this
scribe: Maybe a place for CAPTCHAs here
Carlos: +1 to include some of the
CAPTCHA here, cross referencing to images and graphics
... Could have a learning outcome on custom widgets, like
design accessible custom input fields
... I am not sure if the learning outcomes cover label
positioning currently, it should be more explicit
... I would put explicitly error messages in the notifications
sublist