Re: Proposal for WCAG 2.1 editing / review process

We have that for GitHub, and you don’t even need to press a button, it just happens automatically.

I’ll take a look at Steve’s note, haven’t had a chance yet.


Andrew Kirkpatrick
Group Product Manager, Standards and Accessibility

From: Gregg Vanderheiden <<>>
Date: Wednesday, March 15, 2017 at 09:39
To: Steve Lee <<>>
Cc: Wayne Dick <<>>, "Repsher, Stephen J" <<>>, Michael Cooper <<>>, WCAG <<>>
Subject: Re: Proposal for WCAG 2.1 editing / review process
Resent-From: WCAG <<>>
Resent-Date: Wednesday, March 15, 2017 at 09:40

do we have a “COMPILE” button somewhere where we can press it and it will compile a latest doc with everything in it — no matter how ugly?


Gregg C Vanderheiden<>

On Mar 15, 2017, at 7:09 AM, Steve Lee <<>> wrote:

I agree separat files makes every sense from a tracking and history point of view. It does complicate the 'build' and cognitive load though.

Slightly off topic but I see<> from fogbuzz has gone for a google doc-like shared editing experience, rather than VC complexities. That said, their requirements are different.

Steve Lee

On 14 March 2017 at 19:58, Wayne Dick <<>> wrote:
Dear Michael,

I think this is a very good start and one that can be usable by the whole group, but there are clear difficulties.

How do we keep one depositories with multiple views? That is the problem. I do not think we can skirt it.

Are there ways to link something like Google Docs, a clear favorite among COGA members, and github.

This is the classic data independence problem faced in early databases. GitHub is the DBMS, but there need to be alternative views that connect smoothly.


Received on Wednesday, 15 March 2017 13:52:59 UTC