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

Hello Howard,

Thanks for filling in the survey. Some comments 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/

Proposals below.

> > ---------------------------------
> > 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:
> I thought everything fit together very well. One suggestion: I thought the first learning outcome for complex tables "explain the scope and
> purpose of complex tables" should avoid the term 'scope' because it has a specific meaning in relation to tables.

Good catch. I will take a pass on the whole curriculum to see where we can qualify this expression.  I am afraid this can not only be ambiguous here, but also in other places.

This learning outcome now reads:

"explain what complex tables mean in the context of Web accessibility"

Are you comfortable with this suggestion?

> > ---------------------------------
> > Module 5: Forms and Input Elements
> >
> > ----
> > Please focus on Module 5: Forms and Input Elements
> >  * 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 5 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 Forms and Input
> > Elements
> >
> Comments:
> I thought there should perhaps be some mention of 'grouping' in 'the courses based on this module," such as:
> explain how form labels, [grouping markup], instructions, and notifications allow people with disabilities to understand and fill in form
> controls.
> 
> Seemed like overall implication is that 'grouping' is only used to group radio buttons or controls but it can group an entire section of a form,
> such as "speaker information".

For me, grouping is more related to the coding aspect, and I have added this to the first of the bullets. These groups produce the structures you mention. The user may not be aware that some grouping stuff is behind the scenes, but it is true that they need some structure (be it conveyed through grouping or not) to understand the overall form structure
I have tweaked these two introductory bullets as follows.

* "demonstrate use of appropriate code to label and group form controls, as well as to provide instructions and notifications for users to fill in forms"
* "explain how form structures, labels, instructions, and notifications allow people with disabilities to understand and fill in form controls"

Is that what you mean?

> 
> I thought the assessment 'Practice — Students are presented with overall instructions for a set of form controls and are asked to code them
> appropriately. Assess students’ knowledge about different ways to code overall instructions' might be a little vague.
> 
I have qualified these two ideas for assessment a little bit.

* "Practical — Students are presented with overall instructions for a set of form controls such as the current and total number of steps of the form and are asked to code them appropriately. Assess students' knowledge about how to code overall instructions".
* "Practical — Students are presented with in-line instructions for form controls such as examples of how data should be entered and are asked to code them appropriately. Assess students' knowledge of the different techniques to code in-line instructions".

Is this detail what you were missing?

--

Daniel Montalvo

Accessibility Education and Training Specialist
W3C/WAI

Received on Friday, 21 August 2020 11:06:39 UTC