"signposting" in developing for designing and writing

Hi Daniel and all,

Ref: https://deploy-preview-238--wai-curricula.netlify.app/curricula/developing-accessible-content/structure-and-semantics/
under Topics to Teach
under Topic: Section Headings
under Learning Outcomes for Topic
[[...
 * list requirements for content authors to write heading texts that convey meaning and structure
 * list requirements for designers to use unique styles for each of the heading rank levels
]]

First, I haven't followed this issue, and I understand that you have discussed different options. I didn't dig for record of your previous discussions. Here is "my 2 cents":

Since we are developing separate curricula for different roles/tasks (developing, designing, writing) I think we want to avoid much overlap, and keep focused on the roles/tasks in the specific curricula.

For the example above, it seems to me that developers need to *know* that there is guidance for writing and designing Headings, yet they do not need to be able to "list requirements" for others. That is, they need to be aware of them, but not be able to list the specifics.

I don't feel strongly.

Best,
~Shawn

Received on Wednesday, 12 August 2020 21:25:26 UTC