<sloandr> scribe: sloandr
daniel: proposing edits revising warning to instructors over use of flashing and flickering content, including a direct warning not to use blinking or flashing content that can cause seizures
<Howard> scribe: Howard
Daniel: Comfortable with not showing examples of flashing content?
<estella> +1 for the new wording
David: like the idea of having students doing the research themselves...
Then their decision whether to look at it.
Carlos: I agree with general direction. Have some concerns - can be ...
dangerous of problems flashing content can cause...
Suggest we retain warnings of flashing content so students ...
not surprised or adversely affected by flashing content.
Daniel: room to add something in
teaching idea.
... Let students know about danger of flashing content.
Howard: wouldn't students already be aware of their sensitivity to ...
flashing content?
David: emphasize dangers to others if accessing in a group.
Sarah: may be possibility of adult onsite photo-flashing sensitivity.
Estella: agree with all comments. But even if aware of seizures, might not be aware ...
of what seizures cause. Maybe explain different types of effects.
Explain what seizure means.
Sarah: photo-sensitivity could be a side-affect of some medications.
But don't want to go into medical detail.
Daniel: agree not to go into medical detail.
Brent: this is not the curriculum, this is the content that can be ...
brought into the curricula. Communicating to the instructor, not the students.
Brent: does Estella think there should be links to more info on seizures ...
or should there be actual language about it in the resource?
Estella: students and teachers need to know that this does ...
really affect end users.
Daniel: don't usually point to outside sources but may want to in this case.
Brent: not sure if there will be a persona who has seizures.
Not aware of a perspectives video planned that will address this.
Howard: wouldn't go into too much detail on the various types of seizures ...
and the detailed affects on end-users.
Daniel/Brent: probably plan to just have a link for more information.
<sloandr> +1 to Howard. We need to be careful to emphasise that this is an accessibility issue that can only be resolved by taking steps to avoid exposing affected users to problematic content (rather than e.g. editing the content). That’s non-negotiable, and we don’t want to imply that we need to have user stories of the experience of real users who had seizures to justify or persuade designers (or instructors) to deal with the problem.
Sarah: may be some non-English speakers where a link could help them better understand...
the issue.
Daniel: will research what specific resource they can point to.
Daniel: feedback that learning outcomes were using 'design' too much.
<dmontalvo> https://deploy-preview-433--wai-curricula.netlify.app/curricula/designer-modules/
<dmontalvo> Topic Naming and Grouping, last bullet. "associate controls that share the same purpose, such as those collecting personal information, payment methods, and consent to legal conditions, and communicate such groups visually and non-visually"
Daniel: any comments on use of verb 'associate'
<dmontalvo> Navigation Design -- Learning outcomes for module, fourth and fifth bullet
No feedback from group.
Daniel: under Navigation Design, Learning Outcomes. Changed verb from 'define' to
'specify' in some places (bullet item 4 & 5)
Brent: 'defining' could have a specific meaning to a developer, hence the need ...
to use a verb such as 'specify'.
Daniel: needs to check that bullets 4 and 5 are properly updated.
Any comments on these changes?
No feedback from group.
<dmontalvo> Images and graphics Topic Informative Images, third bullet: "cooperate with developers and content authors to use styled text when the technology in use can provide the desired visual presentation"
David: would say 'collaborate' instead of 'cooperate.' First sounds more like an equal partnership.
<brent> +1 to collaborate
+1 to collaborate.
<BrianE> +1 to collaborate
Daniel: has cooperate in a few places. Will make change in other places also.
<dmontalvo> Forms Design
<dmontalvo> Topic Labels and Instructions, third bullet. Grouped related bullets. "specify visual and non-visual instructions for required input fields; changes in context before the component that originates such changes; existing time limits in a form and how to adjust them, extend them, and turn them off; the current step and the total number of steps involved in a multi-step form"
David: 'provide' or 'write' could also be used in lieu of 'specify'. Although 'write' might imply the role of ...
the 'content author.'
Estella: likes 'specify,' more specific and narrow.