W3C home > Mailing lists > Public > wai-eo-editors@w3.org > March 2020

Re: [wbs] response to 'WAI-Curricula Eagle review for learning outcomes for module, learning outcomes for topic, and general modules and topics structure'

From: Sylvie Duchateau <sduchateau@access42.net>
Date: Fri, 13 Mar 2020 12:20:41 +0100
To: Daniel Montalvo <dmontalvo@w3.org>
Cc: wai-eo-editors@w3.org
Message-ID: <910bab3a-879e-ec51-59ab-2ebf23b9ca91@access42.net>
Hello Daniel,

Yes, what you write about images is what I mean:

"In learning outcomes of the first topic of this module, called "Images 
for all". we have:
"Recognize how screen reader user benefits from alternative text".
The learning outcomes could expand on how assistive technologies 
interpret images, as something that students would need to know after 
completion of the module. I feel we would be limiting the audience if we 
would be requiring that every student knew how assistive technologies 
handle images prior to this module. For instructors it is a different 
story, and we could well make the point that you mention clearer. "


Concerning your question:

"Do you mean the fact that screen readers do not process the image 
itself but read the alt text? Do you think students and instructors need 
to have this knowledge prior to this module? "

No, but students should learn this and instructors should know about this.

2. As far as tables are concerned, you write:

"And we could expand how exactly a screen reader user would navigate 
table cells, read table headers, etc. Is that what you mean?"

I mean that when reading a table, the screen reader does not repeat the 
column header when you move through the column, for example. And this is 
not an accessibility issue, but the normal behavior of the screen reaer. 
As you are in the same column, repating its header is not necessary.

3. Ok to change ECMA Script to javascript, it will be clearer.

4. Concerning informative / decorative images you write:

"It is true, though, that we could present the different types of images 
in a different way. We could make text, functional, and complex images 
fall under the umbrella of informative images, as they all convey 
information to the user. We could consider decorative images as a 
separate type of images, since they don't convey information. Is that 
what you think we should do?"

Yes, but it's only a suggestion.

5. OK for clarifying the summary attribute.

Best

Sylvie
Access42 		

*Sylvie DUCHATEAU*
Experte accessibilité numérique
09 72 45 06 14 — 06 62 33 68 12

Expertise et formation en accessibilité numérique

Site web <https://access42.net/> — Twitter 
<https://twitter.com/access42net> — LinkedIn 
<https://www.linkedin.com/company/access42> — Newsletter 
<http://eepurl.com/dgHY2b>

Organisme de formation référencé au DataDock
et certifié par i.Cert <https://www.icert.fr/certifie/access-42/> pour 
sa démarche qualité

Le 10/03/2020 à 16:04, Daniel Montalvo a écrit :
> Hello Sylvie,
>
> Thanks for submitting your answer to this survey. Some inline comments below.
>
> Daniel Montalvo
> Accessibility Education and Training Specialist
> W3C/WAI
>
> -----Original Message-----
> From: Sylvie Duchateau via WBS Mailer <sysbot+wbs@w3.org>
> Sent: Monday, March 9, 2020 12:51 PM
> To: sduchateau@access42.net; dmontalvo@w3.org; shadi+EOsurvey@w3.org
> Subject: [wbs] response to 'WAI-Curricula Eagle review for learning outcomes for module, learning outcomes for topic, and general modules and topics structure'
>
> The following answers have been successfully submitted to 'WAI-Curricula Eagle review for learning outcomes for module, learning outcomes for topic, and general modules and topics structure' (Education and Outreach Working
> Group) for Sylvie Duchateau.
>
>> ---------------------------------
>> Review level
>>
>> ----
>> What level of review did you do?
>>
>>
>   * ( ) I thoroughly reviewed the materials.
>   * (x) I skimmed them.
>   * ( ) I need more time and will review by the date provided below.
>   * ( ) I didn't get to it and will not in the near future. I abstain from providing comment.
>   
>
>
>>
>> ---------------------------------
>> General Dependencies
>>
>> ----
>> Please have a look at the section Prerequisites for Students. It
>> relates prior knowledge to the relevant modules of the Introduction to
>> Web Accessibility curriculum.
>> Please answer the following questions:
>>
>>   * Do you think these prerequisites are appropriate?
>>   * Do you think there is any prerequisites missing?
>>   * Would you add any other prerequisites?
>>
>>
> Comments:
> No particular comments on this part.
>
>>
>> ---------------------------------
>> Competencies for Modules
>>
>> ----
>> In addition to the above description, specific competencies  are added
>> at a module level for both students and instructors. Please have a
>> look at specific competencies for:
>>
>>   * Module 1: Essentials
>> of Accessible Development.
>>   * Module 2: Navigating Web Interfaces.
>>   * Module 3: Images
>> and Graphics.
>>   * Module 4: Tables.
>>   * Module 5: Forms.
>>   * Do you think these competencies are adequate?
>>   * Do you think there is any competencies missing?
>>   * Would you add any other competencies?
>>
>>
> Comments:
> I don't understand what "ECMAScript programming language" means in module 2, competencies for students and instructors.
>
> ECMAScript is the standard on which JavaScript is based. I will change it to JavaScript.
>
> In module 3, competencies for stuents and instructors: how images are handled by assistive technologies?
>
> In learning outcomes of the first topic of this module, called "Images for all". we have:
> "Recognize how screen reader user benefits from alternative text".
> The learning outcomes could expand on how assistive technologies interpret images, as something that students would need to know after completion of the module. I feel we would be limiting the audience if we would be requiring that every student knew how assistive technologies handle images prior to this module. For instructors it is a different story, and we could well make the point that you mention clearer.
>
> Do you mean the fact that screen readers do not process the image itself but read the alt text? Do you think students and instructors need to have this knowledge prior to this module?
>
> In module 4, for stuents and instructors : how assistive technologies handle with tables : navigating through tables, accessing tables headers...
>
> Same as above, in the learning outcomes of the first topic, "Navigating Tabular Information", we have:
> "Recognize the ability of assistive technology users to review one cell at a time using specific key combinations."
>
> And we could expand how exactly a screen reader user would navigate table cells, read table headers, etc. Is that what you mean?
>
>
> In module 5, I don't understand iether what "ECMA Script programming language" means.
>
> That will be changed to JavaScript.
>
>
>>
>> ---------------------------------
>> Modules and topics Structure
>>
>> ----
>> Please have a look at Modules and topics structure outline. If you
>> can, read the specific topics by following their corresponding links
>> in the outline.
>>
>>   * Do you think there are any unnecessary or unclear topics in the
>> current outline?
>>   * Do you miss any topic in the current outline?
>>   * Do you think there are overlaps in the current topic outline? If
>> so, how would you address them?
>>
>>
> Comments:
> In images, there should be somewhere a requirement saying that students should make the difference between informative and decorative images and what needs to be described.
> There is already, but it might not be clear. We have a learning outcome for topic saying:
> * Distinguish between informative, decorative, functional, text, and complex images.
> It is true, though, that we could present the different types of images in a different way. We could make text, functional, and complex images fall under the umbrella of informative images, as they all convey information to the user. We could consider decorative images as a separate type of images, since they don't convey information. Is that what you think we should do?
>
>
> In the tables module, not sure that summary attribute is still used?
>
> It is used as a fallback as it is now discontinued. I will clarify this.
>
>>
>> ---------------------------------
>> Additional comments
>>
>> ----
>> Use the space below to include any additional observations or
>> questions you would like to have considered during the extensive
>> discussion at the face to face meeting next week. Thank you!
>>
> Additional Comments:
>
>
>> These answers were last modified on 9 March 2020 at 11:49:25 U.T.C.
>> by Sylvie Duchateau
>>
> Answers to this questionnaire can be set and changed at https://www.w3.org/2002/09/wbs/35532/wai-curricula-2nd-curriculum-eagle-rev/
> until 2020-03-09.
>
>   Regards,
>
>   The Automatic WBS Mailer
>
>
Received on Friday, 13 March 2020 11:20:46 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 23 June 2020 20:41:59 UTC