Accessibility Education and Outreach Working Group (EOWG) Teleconference -- 08 Oct 2021

trackbot, start meeting

<trackbot> Meeting: Accessibility Education and Outreach Working Group (EOWG) Teleconference

<trackbot> Date: 08 October 2021

<scribe> Scribe: Sharron

Curricula

<dmontalvo> https://wai-curricula.netlify.app/curricula/designer-modules/

Landmarks

<shawn> cues

<shawn> from agenda: visual aspects included in Module 1: Visual Design, Topic: Cues -- No use of "landmark", instead "cues" and "headings" to define page regions

<shawn> GitHub issue: https://github.com/w3c/wai-curricula/issues/372

Daniel: The point was raised landmarks and cues were being confused. We have been working on them and made them more clear. We have added the topic Cues and described what it means to use visual cues. We realte them to spacing and how they convey structure.

<dmontalvo> https://wai-curricula.netlify.app/curricula/designer-modules/visual-design/#topic-cues

Daniel: We have tried to distinguish between that and the landmarks defined within the code.

<dmontalvo> https://wai-curricula.netlify.app/curricula/designer-modules/information-design/#topic-text-and-structure

Daniel: What do people think about the distinctions made? Are they clear enough? Are wecomfortable with them?

<Zakim> kevin, you wanted to ask if 'cues' works

Kevin: The distinctions are fine, it unpacks the difference between visual elements and programmatic element. Given the confusion around the word "cues" might we want to be more clear? Navigation cues or some more definitive word - it may not be a problem?
... I just trip up every time I read it and then think OK I kind of know what that is.

Sharron: maybe a bit more defintition.

Kevin: Caution that visual cues may be the wrong tern since there are aspects that are not visual like headings. Not sure what the encompssing term might be.

Daniel: What about "orientation." May have visual and nonvisula elements.

Kevin: Yes, possible.

Sharron: +1

<Vicki> +1 for "Orientation cues"

<Laura> +1

<estella> +1

<Leticia> +1

Daniel: Change the section title to "Orientation Cues"

Brent: Will you also add to the intro sentence?

Daniel: Yes

Coverage of Media Player Design

<dmontalvo> https://wai-curricula.netlify.app/curricula/designer-modules/multimedia-and-animations/

Daniel: It is found within the media module. There was discussion of the fact that we did not point out that the first step is to choose an existing media player with strong accessibility features. So we have added that step to the guidance of how to choose one.

<kevin> 1+

Daniel: they are pointed to the media guide.

Kevin: I was thinking about that the change in this content makes me wonder if it is too little. There is a lot more about designing an accessible media player than only those 4 things. There may not be enough of a connection between those two things.

Daniel: I was thinking of it as an introductory process. I would advocate for making the connection clearer.

Kevin: Yes because the title does not refer to the player. It may just need something in the learning outcome section about how to make accessible media players.

Daniel: I am hearing the disconnect and we need to add "some of the things you need" and make the conection to the player. We want to provide guidance on how to design media players and can see how it requires more alignment.

Kevin: The Learning Outcomes could be quite high level, no need for specific detail.reference

Daniel: And may need to add that these are "some" of the things to do not "all" and making a stronger connection to the player.

Disacription Terminology

<dmontalvo> https://github.com/w3c/wai-media-guide/issues/182

Daniel: THis was the issue discussed last week in the work on the Media Guide and carries over to the learning module. The agreement was that we use descriptions of visual information and then trhoughout the resource simpoly use the word description. Audio description is used in many standards and so maybe a further explanation is needed. So we developed that and it is in the first bullet.

<kevin> +1

<brent> +1

<estella> 0

<Laura> +1

<Vicki> +1

<shawn> minor question/suggestion - use singular "... different terms, such as audio description, video description, and described video"

Brent: Carrying forward the decision from last week into the curricula and calling out to instructors to clarify the terms as thye are used.

<shawn> +1

Daniel: Understood, will change audio description to singular
... and Estella, you were not convinced?

Estella: We had the conversation around this and the term that is most commonly used is audio description but I will not oppose the decision.
... the other question is "description of visual information" a standardized term?
... While I understand the need for clarity, in the long term people will refer to guidelines and standards to do their jobs - are these standards related terms?

Shawn: I want to support what you said Estella, there are different terms in different countries arounf the world. Since that is the fact there are different terms used in formal standards
... but we are not trying to coin a new term but only to explain the concpet and relate it to those different standardized terms used in formal docs aroung the world.
... And people will customize the curricul to thier own environment using the appropriate term in thier own country.

Daniel: So my takeaway is to keep as it is

<shawn> here's the sentence: "Terminology: Description of visual information provided via audio is called “audio description” in Web Content Accessibility Guidelines (WCAG). In some regions and documents it is called “video description” or “described video”. "

<shawn> Depending on the type of video and media player, description can be:

<shawn> integrated into the main script and recording (which works well for some training videos, yet not most stories)

<shawn> narration added to the main audio track and provided in an alternative version of the video (for stories)

<shawn> provided in a text file or as a separate audio track (if supported by the media player)

<shawn> [ Shawn very curious what we'll do for terminology for WCAG 3 ]

Keep Info Design as a Module

<dmontalvo> https://github.com/w3c/wai-curricula/issues/391

Daniel: The was a perception that visual and programmatic elements were not clearly enough defined and distinguished. So we have made information design more separate from visual design and feel that is it now more clear that it is now clearer and more coherant.
... it is now 1. Visual Design 2. Information Design 3. Navigation Design and 4. Interaction Design and the proposal is to retain this structure.

Brent: Any objection to this at all?

Daniel: I followed up with the original commenter and she feels it makes much more sense, so ...
... will polish a bit and there may be one more issue befor the survey but really next steps will be survey and publish.

<Vicki> Well done, Daniel!

Accessibility of Remote Meetings

<shawn> https://raw.githack.com/w3c/apa/9c9109f52551b42e27f77a61b30415602df39565/remote-meetings/index.html

Brent: A group has distributed a document and we will ask you to look and comment.
... you find the Editor's Draft arounf this topic. We want to do a couple of things - EO has resources that could be referenced within the doc and how to provide feedback that encourages the group to use them,
... and also provide that feedback in a specific way "use the resource, it might fit here" etc
... also as you review, see if there are elements of this that we could use to make our resources better? There is a two question survey that guides you to think about this.
... any questions about this, the background, our goals?

Kevin: Will this doc be in TR space?

Shawn: It was oringnally a series of points in a wiki page that were going to be integrated into EO resources but now it is a Note and they are super open to our resources.
... not yet determined and while I wish we'd known about it sooner, they are open and we can help them shape it.

Brent: we'll open the survey today through Monday the 18th.

Replacing color blindness

Brent: Github issues raised about

Shawn: It is a misnomer, and can cause misunderstanding

Brent: Here are some readings, take a few minutes and then we'll discuss what you think and how we might address the issue.

Kevin: Is the question should we change it - yes it is confusing and a misnomer. The problem may be finding all the instances where it is found.

Shawn: The Low Vison TF is working on a final rec for a term and I am bringing it here since we want more input. We will make no changes until final recs are in place.

Kevin: Color blindness is ubiquitous so the term will be around for a long while

<shawn> ... and we'll be sayinog color vision deficiency ("color blind")

KrisAnne: As I read it talks about color perception - I know of people who can't see a difference between red and black for example. Not that they don't see color but don't see differences in color.
... don't like the word "deficiency"

<Laura> What about "color differentiation deficiencies"?

Shawn: Definciency is the medical term, while we may not want to use a medical term I hesitate to coin a new term. KrisAnne, with your idea of color perception how would you name the user story with a person of that condition? Now it is "Lee, Online Shopper with color blindness"
... how could we name that to reflect the color perception idea?

Kris Anne: I introduce the topic with the idea that people see color differently

<Zakim> dmontalvo, you wanted to support "perception" "vision" seems like redundant to me when in conjunction with color

Daniel: I would like to support the use of the term perception it is better. Also the idea of Lee a shopper who perceives color differently.

KrisAnne: Reduced color perception?

Brent: It is not reduced is it, more like it is perceived differently

Shawn: My understanding is that they don't see certain color
... it is the action of the rods and the brain, maybe I am getting too medical.

KrisAnne: A friend explained that the cones in his eyes would react to color in different ways depending on the angle of the light - would see the same thing as different colors in different circumstance.

Shawn: An idea to keep on the table "perceives color differently"

<dmontalvo> +1 to "perceives color differently"

<estella> +1

Kevin: Somewhat aligned with "cognitive differences"

<brent> +1

<krisannekinney> +1

<kevin> +1

<Vicki> +1

<CarlosD> +1

<Laura> +1

Shawn: I will propose this for consideration to the Low Vision TF.

Wrap

Brent: Will have the Work for this Week updated, may post minor changes to works in progress...any other questions or business?
... if you are registered for TPAC there are meetings coming up in the next few weeks, have a great weekend.

trackbot, end meeting

- DRAFT -

Accessibility Education and Outreach Working Group (EOWG) Teleconference

08 Oct 2021

Attendees

Contents

Curricula

Landmarks

Coverage of Media Player Design

Disacription Terminology

Keep Info Design as a Module

Accessibility of Remote Meetings

Replacing color blindness

Wrap

Summary of Action Items

Summary of Resolutions

Scribe.perl diagnostic output