Re: WCAG2ICT this week and a proposed approach to incorporating the Text/CLI updates

Matthew, All:

Thanks for raising strike-through as a screen reader challenge. Jason
may have a different experience, but as a SR user depending mostly on
TTS, I don't find it very usable. In fact it's one of the edge
capabilities where we believe overlays can be helpful described in our
emerging draft community group report here:

https://a11yedge.github.io/capabilities/#pricing


In fact you're pointing out that we should generalize our comments in
the CG about strike-through. Currently they're specific to pricing, but
you're demonstrating how the problem is more general. I suppose RQTF may
also cover this in CTAUR.

Best,

Janina

Matthew Atkinson writes:
> Hi Mary Jo, all,
> 
> This plan works for me too. I just looked at the PR [1] and found that there are some comments on specific lines, still; the first one looks like another that we discussed, and can be marked as resolved, so it disappears. The other comments are timestamped before our meeting last week, but the look new to me, so I must have missed them.
> 
> As the GitHub PR comments (on specific lines) feature is not accessible, we should address the questions raised in those comments either by "normal" comments on the "Conversation" task, or over email, so that Jason and Janina can opine on them. If we do it via GitHub comments, I don't think we should use text formatting such as strikethrough, because I don't think that comes across by default with SRs, but Janina and Jason are the experts on that!
> 
> On top of those comments that are outstanding, there are a couple of things I want to check on the PR, but that won't take long once we've cleared up the comments, it's literally just a mention of the fact that AT is now less specifically tailored to console apps then it once was.
> 
> Best regards,
> 
> 
> Matthew
> 
> [1] https://github.com/w3c/wcag2ict/pull/172
> -- 
> Matthew Tylee Atkinson (he/him) 
> -- 
> Principal Accessibility Engineer 
> TPG Interactive 
> https://www.tpgi.com 
> A Vispero Company 
> https://www.vispero.com 
> -- 
> This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately. 
> Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful. 
> 
> 
> 
> 
> On 30/06/2023, 02:16, "Janina Sajka" <janina@rednote.net <mailto:janina@rednote.net>> wrote:
> 
> 
> CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender.
> 
> 
> 
> 
> Thanks, Mary Jo. This also works for me.
> 
> 
> Janina
> 
> 
> Jason J.G. White writes:
> > I'm comfortable with that solution; just notify me when there's a complete
> > pull request ready for review.
> >
> > Regards,
> >
> > Jason.
> >
> > On 29/6/23 17:10, Mary Jo Mueller wrote:
> > >
> > > Hi everyone,
> > >
> > > Thanks Matt for the heads-up on your availability for the next couple of
> > > weeks. Mitch and maybe others will be away for a couple of weeks too. I
> > > also have been super-busy readying the WCAG2ICT editor’s draft for its
> > > review by the AG WG and publication as a first public working draft.
> > > There’s just been too much work on to be done to make the FPWD happen,
> > > so I have not completed drafting the per-SC details yet. I apologize for
> > > being the bottleneck, but it is a work in progress. Realistically, I
> > > think it will be good to have at least a couple of weeks for me to get
> > > the content together.
> > >
> > > I’m thinking a reasonable plan would be not to include the text / CLI /
> > > terminal emulator per-SC details in the first public draft. Instead we
> > > could add it to the 2^nd public working draft which will happen probably
> > > late October or early November. These sections are less time-critical.
> > > If the others agree, we could potentially take the existing pull request
> > > <https://github.com/w3c/wcag2ict/pull/172> <https://github.com/w3c/wcag2ict/pull/172&gt;> forward to the task force and
> > > get that content incorporated into the FPWD. That could give me more
> > > time to create the per-SC details for the second public draft.
> > >
> > > We could then suspend meeting for at least 2 weeks, maybe 3, and then
> > > resume working on the per-SC details.
> > >
> > > What does everyone think about that approach?
> > >
> > > Best regards,
> > >
> > > Mary Jo Mueller
> > >
> > > IBM Accessibility Standards Program Manager
> > >
> > > *From: *Matthew Atkinson <matkinson@tpgi.com <mailto:matkinson@tpgi.com>>
> > > *Date: *Wednesday, June 28, 2023 at 3:41 PM
> > > *To: *Mary Jo Mueller <maryjom@us.ibm.com <mailto:maryjom@us.ibm.com>>
> > > *Subject: *[EXTERNAL] WCAG2ICT this week
> > >
> > > Hi Mary Jo,
> > >
> > > I was wondering if it's OK if I skip this week? I've had a lot going on
> > > both work and at home, and I think I could best use my time reviewing
> > > the proposed changes, and text for each SC that we are proposing (if you
> > > could direct me to the latest proposal for the message for each SC,
> > > please do).
> > >
> > > I've looked into some of the examples I have listed, and am going
> > > through those steadily. I expect, given delays that have cropped up this
> > > week, it'll take another couple of weeks for me to complete that, and
> > > give you final comments on the proposed text (in which case, skipping
> > > two meetings, and closing things in the third might work well, but I'll
> > > let you know about next week as we get closer to it).
> > >
> > > This has been, and continues to be, really interesting work, and I am
> > > looking forward to continuing to contribute to it as we get towards
> > > publication.
> > >
> > > Best regards,
> > >
> > >
> > > Matthew
> > > --
> > > Matthew Tylee Atkinson (he/him)
> > > --
> > > Principal Accessibility Engineer
> > > TPG Interactive
> > > https://www.tpgi.com <https://www.tpgi.com> <https://www.tpgi.com> <https://www.tpgi.com&gt;>
> > > A Vispero Company
> > > https://www.vispero.com <https://www.vispero.com> <https://www.vispero.com> <https://www.vispero.com&gt;>
> > > --
> > > This message is intended to be confidential and may be legally
> > > privileged. It is intended solely for the addressee. If you are not the
> > > intended recipient, please delete this message from your system and
> > > notify us immediately.
> > > Any disclosure, copying, distribution or action taken or omitted to be
> > > taken by an unintended recipient in reliance on this message is
> > > prohibited and may be unlawful.
> > >
> > >
> > >
> 
> 
> --
> 
> 
> Janina Sajka (she/her/hers)
> Accessibility Consultant https://linkedin.com/in/jsajka <https://linkedin.com/in/jsajka>
> 
> 
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa <http://www.w3.org/wai/apa>
> 
> 
> Linux Foundation Fellow
> https://www.linuxfoundation.org/board-of-directors-2/ <https://www.linuxfoundation.org/board-of-directors-2/>
> 
> 
> 
> 
> 

-- 

Janina Sajka (she/her/hers)
Accessibility Consultant https://linkedin.com/in/jsajka

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa

Linux Foundation Fellow
https://www.linuxfoundation.org/board-of-directors-2/

Received on Friday, 30 June 2023 13:42:55 UTC