RE: [wbs] response to 'WAI Curricula Starfish review for Modules 4, 5, and 6 of curriculum Developing Accessible Content'

[Adding public-wai-curricula@w3.org]

--

Daniel Montalvo

Accessibility Education and Training Specialist
W3C/WAI

> -----Original Message-----
> From: Daniel Montalvo <dmontalvo@w3.org>
> Sent: Thursday, August 20, 2020 12:13 PM
> To: 'gn@ki-i.at' <gn@ki-i.at>; 'shadi+eosurvey@w3.org' <shadi+eosurvey@w3.org>
> Subject: RE: [wbs] response to 'WAI Curricula Starfish review for Modules 4, 5, and 6 of curriculum Developing Accessible Content'
> 
> Hello Gerhard,
> 
> Many thanks for your feedback. Some comments and proposals below.
> 
> You can see a preview of my proposed changes at https://deploy-preview-241--wai-curricula.netlify.app/curricula/developing-accessible-
> content/
> 
> There you can navigate the different modules and topics. This is a life draft which I will be updating based on Task Force feedback.
> 
> The editor's draft (now frozen for people to review), continues to be at https://wai-curricula.netlify.com/curricula/developing-accessible-
> content/
> 
> > > ---------------------------------
> > > Module 4: Tabular Information
> > >
> > > ----
> > > Please focus on Module 4: Tabular Information
> > >  * Are all points covered - is anything missing?
> > >  * Is there anything in there that should not be in there?
> > >  * Do you agree with the overall topic structure?
> > > Please focus on Learning outcomes for module 4 and contrast them
> > > with the learning outcomes for each of the topics in the module. Do
> > > you think they fit well together?
> > > You can comment below or leave a GitHub Issue about Tabular
> > > Information
> > >
> > Comments:
> > Summaries for tables are not mentioned in the learning outcomes for module, just descriptions.
> 
> I have changed "names" to "summaries".
> 
> That learning outcome now reads:
> 
> * "code mechanisms to provide meaningful summaries and descriptions for tables"
> 
> Does this address your comment?
> 
> >
> > Learning outcomes for simple tables:
> > - identify table headers
> 
> I agree with you that some knowledge to identify these headers is needed. There are other people's comments, though, that if we put too
> much emphasize for this that may overlap with future curricula we develop for content authors and designers. Certainly, the developer may
> take decisions about the table structure (and not just the coding), but there might be other occasions where these structures are already
> defined at an information architecture level.
> 
> I have added "and identify" to what we previously had. These learning outcomes now read:
> 
> * "mark up and identify table headers using the HTML element `th`"
> * "mark up and identify table data cells using the HTML element `td`"
> 
> Does this address your comment?
> 
> > - associate table headers to table data cells using the attribute
> > scope
> 
> Do you really think scope is needed for a simple table where there is only one column or row header? Definitely we need to mention scope
> in the next topic, but I think ATs and browsers can deal with table headers using only th.
> 
> > Learning outcomes for complex tables:
> > - identify table headers
> 
> Same as in previous topic, I have added:
> 
> * "mark up and identify the direction of the headers using the HTML attribute `scope`"
> * "mark up and identify headers that span several columns using the HTML elements `col` and `colgroup`"
> * "mark up and identify headers that span multiple rows using the HTML element `tbody`"
> 
> Does this address your comment?
> 
> > > ---------------------------------
> > > Module 6: Widgets
> > >
> > > ----
> > > Please focus on Module 6: Widgets
> > >  * Are all points covered - is anything missing?
> > >  * Is there anything in there that should not be in there?
> > >  * Do you agree with the overall topic structure?
> > > Please focus on Learning outcomes for module 6 and contrast them
> > > with the learning outcomes for each of the topics in the module. Do
> > > you think they fit well together?
> > > You can comment below or leave a GitHub Issue about Widgets
> > >
> > Comments:
> > Keyboard conventions are missing in the learning outcomes for module.
> 
> I have added a specific learning outcome that reflects this. It says:
> 
> * "code widgets so that they are operable through keyboard interfaces"
> 
> Does this address your comment?
> 
> > > ---------------------------------
> > > Module 3: Images and Graphics
> > >
> > > ----
> > > Please focus on Module 3: Images and Graphics
> > >  * Are all points covered - is anything missing?
> > >  * Is there anything in there that should not be in there?
> > >  * Do you agree with the overall topic structure?
> > > Please focus on Learning outcomes for module 3 and contrast them
> > > with the learning outcomes for each of the topics in the module. Do
> > > you think they fit well together?
> > > You can comment below or leave a GitHub Issue about Images and
> > > Graphics
> > >
> > Comments:
> > Learning outcomes for each of the topics fit together with those of the module.
> >
> > Learning outcomes for module:
> > - distinguish simple, functional, complex, and decorative images
> 
> I am afraid "distinguish" may be too much of a burden for a purely developer-based curriculum. See rationale for tables below. I agree,
> though, that they should be familiar with (and identify) different types of images they may have to code.
> 
> I added:
> 
> * "identify simple, functional, complex and decorative images"
> 
> Do you think this wording covers your point?
> 
> > > ---------------------------------
> > > Module 2: Navigation and Menus
> > >
> > > ----
> > > Please focus on Module 2: Navigational Menus.
> > >  * Are all points covered - is anything missing?
> > >  * Is there anything in there that should not be in there?
> > >  * Do you agree with the overall topic structure?
> > > Please focus on Learning outcomes for module 2 and contrast them
> > > with the learning outcomes for each of the topics in the module. Do
> > > you think they fit well together?
> > > You can comment below or leave a GitHub Issue about Navigational
> > > Menus
> > >
> > Comments:
> > Learning outcomes for each of the topics fit together with those of the module.
> >
> > Application menus are not really good as main navigation for websites.
> > This should be discussed.
> 
> We now have:
> 
> Learning outcome: "identify use cases for application menus Teaching idea: "Show examples of different application menus. Emphasize that
> these types of menus are used when desktop functionality needs to be recreated and are not advised for navigational menu purposes.
> Explain that additional markup is necessary for assistive technologies to render these menus adequately. Examples of how to code
> application menus are provided in the WAI tutorials on [Additional markup](https://www.w3.org/WAI/tutorials/menus/application-
> menus/#additional-markup)".
> 
> How do you think we can make clearer that these are specific type of menus and should only be used in particular scenarios?
> 
> I am thinking of putting this idea up-front in the introductory paragraph for the topic, like:
> 
> Show examples of specific scenarios where navigational menus can be used, such as recreating a desktop environment in a web application.
> 
> IS this what you mean?
> 
> > > ---------------------------------
> > > Module 1: Page Structure
> > >
> > > ----
> > > Please focus on Module 1: Page Structure
> > >  * Are all points covered - is anything missing?
> > >  * Is there anything in there that should not be in there?
> > >  * Do you agree with the overall topic structure?
> > > Please focus on Learning outcomes for module 1 and contrast them
> > > with the learning outcomes for each of the topics in the module. Do
> > > you think they fit well together?
> > > You can comment below or leave a GitHub Issue about Page Structure
> > >
> > Comments:
> > Module 1: Structure and Semantics:
> > Learning outcomes for each of the topics fit together with those of the module.
> >
> > What about the HTML element quote in 'Sections of Content'?
> 
> I have added references to "q" and "blockquote" in learning outcomes, teaching ideas, and ideas to assess knowledge.
> Please see
> https://deploy-preview-241--wai-curricula.netlify.app/curricula/developing-accessible-content/page-structure/#topic-sections-of-content
> Does this address your point?
> 
> >  Regards,
> >
> >  The Automatic WBS Mailer
> 
> Thanks.
> 
> Best.
> 
> --
> 
> Daniel Montalvo
> 
> Accessibility Education and Training Specialist W3C/WAI

Received on Thursday, 20 August 2020 10:25:39 UTC