Meeting minutes
Setting up meeting, choosing scribe https://www.w3.org/WAI/EO/wiki/WAI_Curricula/WAI_Curricula_Task_Force_Meetings#Scribe_Rotation_List
Designers' responsibilities for images and graphics https://deploy-preview-347--wai-curricula.netlify.app/curricula/designer-modules/images-and-graphics/ -- taken up
Daniel: What additional designer responsibilities should we cover regarding images and graphics beyond the current list?
<Daniel> - Text alternatives for functional images.
<Daniel> - Visual requirements for images
<Daniel> - Coordination with authors for text alternatives and descriptions for complex images and images of text.
<Daniel> - Identification of requirements for developers to code images.
<Daniel> Are all designers' responsibilities covered? Anything that is missing? Anything that overlaps with other roles and should be clarified?
Donal_Rice: likes the cadence presented in the learning outcomes, supportive of what's there. Relationship with developers and content authors is clear
wondering about clarifying "wherever possible" regarding using text rather than images of text, to consider valid situations where images of text might be necessary, such as exceptions in WCAG SC 1.4.5
GN: language of "Identify related requirements" is improved now
GN: important for designers to communicate what in a visual design is a graphic, and what is text (that should be implemented as markup), helping developers make decisions on implementation approach
Donal-Fitzpatrick: possible scope for expanding learning outcomes to address how the image fits into the overall user interface, for example, where images need to be presented in a certain way, or their relationship needs to be communicated in an accessible way
Daniel: this may be more the role of a content author?
Donal-Fitzpatrick: Thinking of a recent situation encountered when reviewing a PowerPoint template
Daniel: considering how we describe different types of images based on purpose, are these different types coming through clearly in current text?
sloandr: For consistency's sake, it may be worth replacing "Ornamental Graphics" with "Decorative Images" as a module topic title
How should we include the designer's responsibility with regards to promoting accessible media players
Daniel: there was feedback suggesting Module 6 should cover media player selection, based on accessibility support. Should designers and content authors be capable of describing characteristics of an accessible media player, and promote their use in development?
Daniel: developer modules covered aspects of implementing an accessible application, which could cover a media player, although media players are not addressed directly. Assumption is that developers would be most likely to select a third party player, and may need guidance on accessibility features when selecting an option
GN: designers should indicate that media is present in content, with accessibility features such as transcript, captions, audio descriptions, and the developer is responsible for choosing a suitable media player to support these features
Carlos: suspect this question will be dependent on organisation. For some places, the responsibility will fall on designers, in other places, responsibility will be the developer's. In our curricula, we should promote this as a shared responsibility
Donal_Rice: makes sense to me
Howard: +1
Donal-Fitzpatrick: +1
New scope for topic Grouping and Sorting Information https://deploy-preview-347--wai-curricula.netlify.app/curricula/designer-modules/information-design/#topic-grouping-and-sorting-information -- taken up [from Daniel]
Daniel: Module 4, Information Design, has been restructured and expanded with topics previously in other modules. Includes a module on Grouping and Sorting Information for consideration. Some content is best practice rather than required for WCAG conformance. Is this content appropriate? Is it in scope?
Donal-Fitzpatrick: 2 facets to data visualisation. 1. What data is in there? 2. How are data elements associated/related?
Daniel: the grouping and sorting topic tries to go further, to provide hints to designers to provide best practice on easier keyboard operation
Carlos: looks clear, worth including, even as a best practice. Do we need to explicitly identify material as best practice, i.e. not directly mapped to specific WCAG SCs?
Daniel: we are encouraged by EO to be cautious about going too far into best practices, without clear justification
+1 to Carlos, this is good content
Donal-Fitzpatrick: +1
Daniel: Data visualisation content now included in Module 5: Images in Graphics. Will work on communicating importance of relationships between components in images
Next Steps
Daniel: will plan for another meeting next week, looking at module structure and distribution of content across each. Next survey will be after current outstanding issues have been addressed