RE: [wbs] response to '[Curricula] Review of changes before Butterfly Approval'

Happy New Year Daniel!

Your changes work for me. Thanks for the your consideration of my comments.  

Laura


-----Original Message-----
From: Daniel Montalvo <dmontalvo@w3.org> 
Sent: Thursday, January 07, 2021 5:07 AM
To: Keen, Laura <lkee@loc.gov>; shadi+eosurvey@w3.org
Cc: wai-eo-editors@w3.org
Subject: RE: [wbs] response to '[Curricula] Review of changes before Butterfly Approval'

Hey Laura,

Happy new year, and sorry for the late response.

> I recently read: https://thoughtbot.com/blog/alt-vs-figcaption.  The article enlightened me on the use of alt and figcaption together.  As well as why it's a bad idea to have an empty alt within figure/figcaption.  I wonder if we should cover this also.

This is good point.

My main take away from this article is that use of figcaption does not exclude use of alt for individual images if needed. So, I have added a reference to alt and individual images in the learning outcomes for complex images in module 3.

[[
HTML elements `figure` and `figcaption` (and HTML attribute `alt` when individual images require specific descriptions) ]]

Would this work for you?

Many thanks.

Best.

--

Daniel Montalvo

Accessibility Education and Training Specialist W3C/WAI

> -----Original Message-----
> From: Laura Keen via WBS Mailer <sysbot+wbs@w3.org>
> Sent: lunes, 14 de diciembre de 2020 17:54
> To: lkee@loc.gov; dmontalvo@w3.org; shadi+eosurvey@w3.org
> Subject: [wbs] response to '[Curricula] Review of changes before Butterfly Approval'
> 
> The following answers have been successfully submitted to '[Curricula] 
> Review of changes before Butterfly Approval' (Accessibility Education and Outreach Working Group (EOWG)) for Laura Keen.
> 
> >
> > ---------------------------------
> > Introduction
> >
> > ----
> > This is another thorough review survey to discuss changes resulting
> > from:
> >      * EOWG Monkey Review survey.
> >          * Brainstorm for Clarifying curricula titles survey
> >          * Approval of changes after thorough review Task Force survey
> >          * EOWG discussion 30 October
> >          * EOWG discussion 6 November
> >     Preview with proposed changes is at:
> >
> https://deploy-preview-273--wai-curricula.netlify.com/curricula/develo

> per-modules/
> >
> >
> > Main changes include:
> >      * Rewritten overview page based on requirements analysis for 
> > supporting materials
> >          * Added Module 7: Rich applications, to better clarify 
> > scope for accessible rich applications
> >          * Streamlined learning outcomes to better relate to 
> > accessibility requirements
> >          * Define accessibility related terms such as simple and 
> > complex images and tables consistently throughout the resource
> >          * Qualify specific situations where several techniques can 
> > be used to provide labels or descriptions, such as alternative texts 
> > for images, table descriptions, or labels for forms and controls
> >          * Renamed some modules to better reflect their actual content
> >          * Renamed topics and reorganized their contents to 
> > facilitate teaching sequence
> >     The following questions will guide you through the most 
> > significant changes. Please provide any specific feedback you have, 
> > especially if you don't agree with the proposed changes.
> >
> >
> Comments:
> I agree with the changes
> 
> >
> >
> > ---------------------------------
> > General Changes
> >
> > ----
> > The following is a list of general changes affecting the whole resource.
> >
> >      * Changed introductory paragraph at the top of each of the 
> > modules from "Courses based on this module:" to "Courses based on 
> > this module should:" Example at Introduction for module 1Rationale: 
> > This clarifies that the below bullets are expected goals or 
> > objectives for the courses and not actual courses that we are listing.
> >      * Changed order of bullets in the introductory paragraphs for 
> > each of the modulesExample at Introduction for module 1Rationale: 
> > New order better reflects how accessible coding benefits people with disabilities.
> >      * Changed "summarize" to "recite" when providing sign posting 
> > references to other roles responsibilities in learning
> > outcomes.Rationale: It better communicates the importance of knowing 
> > such requirements, instead of just summarizing them.
> >      * Change explanatory sentence at the "topics to teach 
> > level":from "Optional topics to achieve the learning outcomes"to 
> > "Topics to achieve the learning outcomes".Rationale: A specific 
> > order or teaching method is not required, but all topics are recommended for the teaching sequence.
> >      * Changed idea to assess knowledge for module: "Practical — 
> > Students are guided to use mechanisms that assistive technologies 
> > provide to [...]"
> >     from "Short answer questions"
> >     to "Practical",
> >     Rationale: It better reflects the assessment type.
> >     Is there anything from these changes that you would disagree with?
> > Please provide comments on the below box or open a GitHub issue on 
> > general changes
> >
> >
> >
> Comments:
> Looks good.  I agree with the changes.
> 
> >
> >
> > ---------------------------------
> > [New] Module 7: Rich Applications
> >
> > ----
> > Module 7: Rich Applications has been added to clarify scope for rich 
> > applications, such as Single Page Applications (SPA), and others 
> > generated by JavaScript.
> > This is a thorough review of this module.
> > What you're reviewing is everything in the final draft.
> >  * This is EOWG's pre-publication review, our internal "last call".
> >  * Review and comment on anything and everything, including 
> > copy-editing as needed.
> >  * Speak now or forever hold your peace.We hope there will not be 
> > any more new comments after this review.For more details about 
> > EOWG's review process, check Review Stages and Levels Please provide 
> > comments in the below box or open a GitHub issue about module 7
> >
> >
> Comments:
> No comments.
> 
> >
> >
> > ---------------------------------
> > Changes in Module 1: Page Structure
> >
> > ----
> > Please have a look at module 1 page structure, specifically focusing 
> > in the following:
> >  * Changed module and topic titles. Current proposal is:
> >      * Module 1: Page Structure
> >        * Topic: Section Headings
> >        * Topic: Sections of Content
> >        * Topic: Page Regions
> >        * Topic: Page Composition
> >
> >  * Added or reworded learning outcomes for module.
> >  * Added and reworded learning outcomes for topics "Section 
> > Headings", "Sections of Content", "Page Regions", and "Page Composition".
> > Is there anything from these changes that you would disagree with?
> > Please provide comments on the below box or open a GitHub issue
> >
> Comments:
> No comments.
> 
> >
> >
> > ---------------------------------
> > Changes in Module 2: Menus
> >
> > ----
> > Please have a look at module 2 Menus specifically focusing on the
> > following:
> >  * Changed module and topic titles. Current proposal is:
> >      * Module 2: Menus
> >        * Topic: Menu Structure
> >        * Topic: Menu Styling
> >        * Topic: Fly-out Menus
> >        * Topic: Application Menus
> >
> >  * Reworded learning outcomes for module.
> >  * Reworded learning outcomes, teaching ideas, and ideas to assess 
> > knowledge for topics "Menu Structure", "Menu Styling", "Fly-Out Menus"
> > and "Application Menus".
> > Is there anything from these changes that you would disagree with?
> > Please provide comments on the below box or open a GitHub issue
> >
> Comments:
> No comments.
> 
> >
> >
> > ---------------------------------
> > Changes in module 3: Images
> >
> > ----
> > Please have a look at module 3 Images specifically focusing on the
> > following:
> >  * Changed module and topic titles, as well as reorganized topic 
> > contents. Current proposal is:
> >      * Module 3: Images
> >        * Topic: Text Alternatives
> >        * Topic: Functional Images
> >        * Topic: Complex Images
> >
> >  * Reworded learning outcomes for module.
> >  * Content related to images of text moved to topic "Complex Images"
> > (was previously under topic "Simple Images")
> >  * Reworded learning outcomes, teaching ideas, and ideas to assess 
> > knowledge for topics "Text Alternatives", "Functional Images", and 
> > "Complex Images".
> > Is there anything from these changes that you would disagree with?
> > Please provide comments on the below box or open a GitHub issue
> >
> Comments:
> I recently read: https://thoughtbot.com/blog/alt-vs-figcaption.  The 
> article enlightened me on the use of alt and figcaption together.  As well as why it's a bad idea to have an empty alt within figure/figcaption.  I wonder if we should cover this also.
> 
> >
> >
> > ---------------------------------
> > Changes in module 4: Tables
> >
> > ----
> > Please have a look at module 3 Images specifically focusing on the
> > following:
> >  * Changed module and topic titles. Current proposal is:
> >    * Module 4: Tables
> >        * Topic: Simple Tables
> >        * Topic: Complex Tables
> >        * Topic: Table Descriptions
> >
> >  * Reworded learning outcomes for module.
> >  * Reworded learning outcomes, teaching ideas, and ideas to assess 
> > knowledge for topics "Simple Tables", "Complex Tables", and "Table 
> > Descriptions".
> > Is there anything from these changes that you would disagree with?
> > Please provide comments on the below box or open a GitHub issue
> >
> Comments:
> I agree with the changes.
> 
> >
> >
> > ---------------------------------
> > Changes in module 5: Forms
> >
> > ----
> > Please have a look at module 5 Forms specifically focusing on the
> > following:
> >  * Changed module and topic titles, as well as reorganized topic 
> > contents. Current proposal is:
> >    * Module 5: Forms
> >        * Topic: Controls and Labels
> >        * Topic: Instructions
> >        * Topic: Notifications
> >
> >  * Reworded learning outcomes for module.
> >  * Content moved to topics "Instructions" and "Notifications" (was 
> > previously under topic "Time Limits" now removed).
> >  * Reworded learning outcomes, teaching ideas, and ideas to assess 
> > knowledge for topics "Control Labels", "Instructions", and 
> > "Notifications".
> > Is there anything from these changes that you would disagree with?
> > Please provide comments on the below box or open a GitHub issue
> >
> Comments:
> I agree with the changes
> 
> >
> >
> > ---------------------------------
> > Changes in module 6: Custom Widgets
> >
> > ----
> > Please have a look at module 6 Custom Widgets specifically focusing 
> > on the following:
> >  * Changed module and topic titles, as well as reorganized topic 
> > contents. Current proposal is:
> >    * Module 6: Custom Widgets
> >        * Topic: Role Definitions
> >        * Topic: Accessible Names and Descriptions
> >        * Topic: States and Properties
> >        * Topic: Keyboard and Focus Management
> >
> >  * Reworded learning outcomes for module.
> >  * Content related to live regions partly moved to topic "States and 
> > Properties", and partly expanded in new module 7, Rich Applications 
> > (was previously under Topic "Live Regions" now removed).
> >  * Reworded learning outcomes, teaching ideas, and ideas to assess 
> > knowledge for topics "Role Definitions", "Accessible Names and 
> > Descriptions", "States and Properties", and "Keyboard and Focus 
> > Interactions".
> > Is there anything from these changes that you would disagree with?
> > Please provide comments on the below box or open a GitHub issue
> >
> Comments:
> I agree with the changes.
> 
> >
> >
> > ---------------------------------
> > Changes in Developer Modules overview page
> >
> > ----
> > Please have a look at Developer Modules overview page specifically 
> > focusing on overall wording to outline the curricula contents.
> > Is there anything from these changes that you would disagree with?
> > Please provide comments on the below box or open a GitHub issue
> >
> Comments:
> I agree with the changes.
> 
> >
> >
> > ---------------------------------
> > Changes in Curricula on Web Accessibility overview page
> >
> > ----
> > Please have a look at Curricula on Web Accessibility page 
> > specifically focusing on the following:
> >  * Changes in structure resulting from EOWG discussions
> >  * Overall wording and tone
> > Is there anything from these changes that you would disagree with?
> > Please provide comments on the below box or open a GitHub issue
> >
> Comments:
> I agree with the changes.
> 
> >
> >
> > ---------------------------------
> > Additional comments
> >
> > ----
> > Please provide any other additional comments or suggestions you may 
> > want to see addressed before we bring the curriculum back to the 
> > whole EOWG for Butterfly Approval (Approval to publish) survey.
> >
> > Please provide comments on the below box or open a GitHub issue
> >
> Comments:
> This resource is well written and comprehensive. It will be a valuable tool for many organizations. Great work!
> 
> >
> > These answers were last modified on 14 December 2020 at 16:53:13 U.T.C.
> > by Laura Keen
> >
> Answers to this questionnaire can be set and changed at 
> https://www.w3.org/2002/09/wbs/35532/curricula-review-before-butterfly

> /
> until 2020-12-15.
> 
>  Regards,
> 
>  The Automatic WBS Mailer

Received on Thursday, 7 January 2021 11:59:35 UTC