Re: Collaboration Tools, section 6.3

I agree, Lisa. Somehow our communications are breaking down. We need to
resolve that somehow.

In this specific instance Jason is referring to the section of CTAUR
that specifically addresses accessibility of change history and of
revision summaries. From RQTF's point of view this would be a
description of barriers encountered and some suggested approaches to
ameliorate those.

In this specific instance there's no meaningful distinction between
synchronous tools (like Google Docs) and asynchronous tools (like git).

So, no, we don't mention github specifically, but it is very much in
scope when it comes to identifying accessibility issues and proposed
solutions.

Might it help to point out that we've abstracted away from github, which
is a specific commercial instance of git revision control? We have
further abstracted revision control (like git) as asynchronous.

Let's discuss Tuesday!

Best,
Janina


Lisa Seeman writes:
> Thanks for forwarding this Janina,
> 
> I completely fail to understand this. We explained clear issues that are
> currently blocking people, inside the WAI , from using collabertive tools
> like github.
> 
> We were clearly told github  is in scope. I certainly did not see it
> included in the document in any clear form.  The reason then morfed into
> our suggestion not being clearly testable which is not even a  requirement
> of user needs!
> I think we are not communicating well. Suggestions for moving forward would
> be appreciated.
> 
> Thanks again for the effort in trying to address these issues.
> Lisa
> 
> 
> On Thu, 28 Mar 2024, 14:33 Janina Sajka, <janina@rednote.net> wrote:
> 
> > +COGA and our COGA participants at yesterday's RQTF telecon re CTAUR
> >
> > Jason White writes:
> > > I reviewed section 6.3 of Collaboration Tools Accessibility User
> > > Requirements.
> > >
> > https://w3c.github.io/ctaur/
> >
> > > I was unable to find anything discussed at the meeting yesterday with
> > > respect to change history and summaries of revisions that would not be
> > > addressed by the text of section 6.3, and which would lie within our
> > scope.
> > >
> > > Opinions are welcome.
> > >
> > >
> >
> > --
> >
> > 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/
> >
> >
> >

-- 

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 Monday, 1 April 2024 09:57:26 UTC