RE: [wbs] response to 'Curricula -- Designer Modules Eagle Review'

Hello Gerhard,

Thanks for going through the survey. I have general questions based on the comments you made about the following learning outcomes.

> identify related requirements for developers to ensure that headings are coded appropriately and are nested according to the hierarchical
> structure of the page -> IMO, its going to far.
> describe related requirements for developers to make language of page and language of parts programmatically determined -> its going to
> far?
> describe related requirements for developers to ensure that table header and data cells are programmatically associated ->  IMO, its going
> to far.
> identify related requirements for developers to ensure alternatives and descriptions are programmatically associated to their corresponding
> component ->  IMO, its going to far.
> identify related requirements for developers to ensure that properties of custom user interface components, such as names, states, and
> instructions are perceived visually and can be programmatically determined ->  its going to far?
> identify related requirements for developers to ensure that labels and instructions are programmatically associated to their corresponding
> user interface component ->  IMO, its going to far.
> 

These learning outcomes try to act as a cross-reference. They are there for the designer to be conscious that he can count on the developer for these coding aspects with which designers might not be very familiar. What is exactly what you think is going too far here? Is it the level of detail we are providing? Is it the "describe/identify related requirements" part that might be too hard from a designer's perspective?

> describe related requirements for content authors to provide texts that do not require reading ability more advanced than the lower
> secondary education level -> IMO, its going to far.

I am assuming you think we are going too far here because:

* this is linked to a AAA SC
* it would not be possible in all scenarios to provide such texts.

Are these assumptions right?

Thanks.

Best.
--

Daniel Montalvo

Accessibility Education and Training Specialist
W3C/WAI

Received on Wednesday, 7 April 2021 09:02:49 UTC