<scribe> Scribe: Jade
<kakinney> scribe: Jade
<shawn> https://github.com/w3c/wai-intro-wcag/issues/197
<shawn> updated discussion draft https://deploy-preview-196--wai-intro-wcag.netlify.app/standards-guidelines/wcag/new-in-22/
First up, brainstorming the section headings. Some ideas: In Brief, Summary, Briefly, Overview, Outline, Synopsis
Michelle: preference for 'in brief', doesn't give the impression that everything will be covered, but sets the tone of a context piece.
Shawn: in brief vs briefly?
Michelle: it doesn't sound like a heading
<Laura> +1 to Michelle's comments
<shawn> Jade: Summary is easiest word. More recognizarbl,. especially global.
Kris Anne: has AG looked at this?
Shawn: not really, we need to come up with ideas and then suggest
If we don't have a problem with 'In brief' then we should stick with it.
Shawn: we'll want comments on the content, but might not get to it today.
<shawn> qustion -- Bullets as ul rather than dl or p?
Michele: bullets keep it short and in plain language, but they need to be clearly defined.
Shawn: need to decide on consistency and use of 'what' and 'why'
Shadi: preference for what and why bolded
Kris Anne and Rabab agree
Michele: it's easier to write for that too and keep it focused.
Shawn: so this group is sayingtwo bullets, what, why probably bold andfollowed by a colon
+1
<kakinney> +1
<Michele> +1
<Laura> +1
<shawn> Rabab +1
Shawn: anythign quick on the wording? (We'll focus on that later though)
Shadi: Key beneficiaries, the why, some other use cases need to come in here, but don't know how to incorporate this without making uing it longer.
Shawn: this doesn't have to cover everything, we'll follow up after the meeting.
Michele: is there leeway for this to be more unstructured than the understanding documents?
<shadi> [it's not the items that are not visible or should be visible, but rather the indicators that are not visible or should be visible]
<shawn> [COGA beneficiary]
Shawn: we have flexibility but it'll be approved by the AG working group
<shadi> [beneficiaries missing people with cognitive and learning disabilities (i.e. who can use a mouse)]
Shadi: commented that it's looking good, and clear!
Shawn: questions around the differences and preferred approach, we'll have a reading break.
Shadi: thanks to those of you for
your reviews, there were a lot of comments, mostly editorial. I
want to focus on comments about the level of depth, approach
and tone.
... the Elias story is more detailed about their life, Lexie is
shorter. So they're different approaches, and we need to
discuss the differences and which direction should we take with
the aproach? Do we want to align them all?
<shadi> qq+ rabab
<Zakim> rabab, you wanted to react to shadi
Rabab: noticed the length, but
the other user stories, some have single disabilities, but the
people with multiple disabilities are longer.
... longer, enabled me to develop more empathy with the
story.
... Raises awareness of people with multiple disabilities as
there's less awareness of this on the whole.
<shawn> [ Rabab says better what I was thinking !]
<shawn> Jade: Like the longer one. Add more context. THinking how someone use the page. Put enough in written peice to support the video.
<shawn> ... if too long on page, maybe break up the person's story?
<shawn> Jade: align with same headings, even if tone different
<Zakim> shawn, you wanted to say compassion and understanding
Shawn: agree with Rabab. Elias is someone that we want to explain and build the story, for Lexie, colour blindness is more widely understood. So each story can have the consistency with the heading and be a little different and appropriate for the stuation
Michele: suggested in my comments
that the style needed work, more context adding about her life
would help the two parts of her story together
... Elias, I felt like I was reading a story, Lexie, more of a
description.
Shadi: Even after working on some
of the elements of flow and bringing it together, but some
aspects need more storytelling than others
... some stories will be drier than others.
Michele: It shouldn't be that
certain disabilities receive more attention or empathy than
others
... I think there is work to do around building empathy in the
'drier' stories
Shadi: In Elias, there's also some mythbusting and breaking through stereotypes in there as well as info about the disability.
Kris Anne: I read Lexie first, then Elias, which was a much more vivid description of his life. It isn't easy to find examples of colour blindness, but Lexie's story was a lot drier.
Kris Anne: appreciate how hard it is to write these stories though.
Shadi: A little bit more for Lexie and her story and life needed, some flow issues, but it's OK that the stories are slightly different with different lengths and approaches. There are other ways to show consistency between the stories.
Kris Anne: it might be more extreme here because the stories are so different.
Shawn: We want to get this done, Shadi is big time busy, let's think about how we're presenting disabilities and preventing misunderstandings, but consider not spending too much time on changing tone and polishing?
Shadi: agree we need to find a
balance here. Next step: finishing these two then introducing
the others.
... question, how does everyone feel about how long the first
two stories took?
Rabab: each story took me 30 mins
<kakinney> https://twitter.com/w3c_wai/status/1663879749180194816
<kakinney> https://lists.w3.org/Archives/Public/public-wai-announce/2023AprJun/0004.html
<kakinney> https://www.w3.org/WAI/update/#specific-invitations
Shawn: we've been discussing
different options for people who aren't from member orgs and
don't qualify as an invited expert. We made some announcements
to encourage participation, share with individuals who you
think might be good contributors.
... question, any thoughts on how to make work for this week
more user friendly?
Rabab: itemising, 1, 2, 3 if you want to contribute, providing links, the time for the task is useful
Kris Anne: we'll put the time estimate in the work for this week
Shawn: note sure of also want also Github instructions?
Kris Anne: it'd be useful to sit down with Rabab and discuss the onboarding and how comfortable you are so we know how we can encourage peope to stay.
<shawn> [discuss calendar invites]
<shawn> Rabab: The calendar invite worked for me.
<shawn> scribenick+ shawn
I like knowing that I can opt out of surveys by just ticking that I haven't focused on something, so I can focus more on the work I have been actively involved in.
Completing the survey is the most important thing, even if it's just to say that they haven't got round to a piece of work.
<shawn> https://github.com/w3c/wai-intro-accessibility/issues/78
[ scribe's attention taken by topic, and forgot to scribe :-]
[ discussion of
terminology - and noting differences among disability
organizations and others around the world ]
Jade: For our profiles we landed on 'partial sight and visual issues' as we felt that this encompassed things like migraines causing visual disturbances.
?Shadi: Terminology is such a controversial issue and something we keep coming back to. There are questions around what the disability community and organsiations are saying and whether they're actively pushing for this debate.
Rabab: If we look at disabilities from a social model, then looking at 'vision' comes from a medical perspective surely?
<shawn> latest version https://deploy-preview-113--wai-people-use-web.netlify.app/people-use-web/abilities-barriers/
This is the closest we have to the latest definition.
Any more thoughts on this, please add to Github issue: https://github.com/w3c/wai-intro-accessibility/issues/78
Evaluation tools list approval to publish survey closes monday
EOWG meeting attendance survey, please complete this to indicate when you're here/not here.
<shawn> update your availableity for meetings -- links in https://www.w3.org/WAI/EO/wiki/EOWG_Meetings#Upcoming_Teleconferences_and_Meeting_Availability_Surveys
TPAC availability in the survey
This is scribe.perl Revision VERSION of 2020-12-31 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s|https://www.w3.org/WAI/EO/wiki/EOWG_Meetings#Agenda|| Succeeded: s/so we're saying /so this group is saying/ Succeeded: s/why bold and /why probably bold and/ Succeeded: s/Rebab says better/Rabab says better/ Succeeded: s/So each story needs to be independent/So each story can have the consistency with the heading and be a little different/ Succeeded: s/but leave tone and polishing until later/but consider not spending too much time on changing tone and polishing/ Succeeded: s/also Github instructions./note sure of also want also Github instructions?/ WARNING: Replacing previous Present list. (Old list: Brian, Shawn, Rabab, Sharron, Laura, Shadi, Kevin, Michele, krisanne, BrianE, Jade, kakinney) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ Laura, Jade, Shadi, Rabab, Shawn, Michele, KrisAnne Present: Laura, Jade, Shadi, Rabab, Shawn, Michele, KrisAnne Found Scribe: Jade Found Scribe: Jade Inferring ScribeNick: Jade Found Date: 02 Jun 2023 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]