W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2017

Understanding updated

From: Michael Cooper <cooper@w3.org>
Date: Thu, 14 Dec 2017 22:31:02 -0500
To: AG WG <w3c-wai-gl@w3.org>
Message-ID: <ad6bb1d4-3e31-948f-8e52-39238b8c5910@w3.org>
As we discussed Tuesday, I've merged all the Understanding working 
branches in their current state into the editors' draft:


and the publication location referenced by the official WCAG 2.1 Working 
Draft is updated:


After last week's merges of a few branches I received a couple comments 
about out of date content. I believe today's merge fixes that, let me 
know if not.

Most of the merges went smoothly. I had trouble with 
identify-common-purpose, graphics-contrast, accessible-authentication, 
label-in-name, and pointer-gestures. In many cases this was because 
there was additional content in the branches besides Understanding 
content; in some cases it was a simple consequence of renaming. Although 
I believe the Understanding content made the transition ok, people 
working on those branches should check especially carefully that it's 
current. There is a chance it will be more difficult to merge those 
branches in the future.

Remember that I renamed the working branches for SC that were renamed. 
If you were working on a SC that has been renamed, continue your work in 
the branch that reflects the new name. I have updated the Accepted SC 
wiki page with the new branch names. If branches (re)appear under the 
old name, they will likely be overlooked.

Also remember that the branches named like the SC are for Understanding 
work. If you are doing other work, such as proposing a SC rewording, 
that should be done in a different branch. Most obvious to me is to name 
the branch like the SC but put your name initials in the name as well, 
or put "SC" or something in the name to clarify its purpose.

If you have been working on a proposal for an Understanding document in 
a private branch that you were hoping to eventually merge into the main 
Understanding branch for the SC, that content has *not* been merged. 
Branch managers will need to ping by email or pull request when new 
content should be merged into master again, or we will probably do 
another wholesale merge at some point in January to catch things up 
prior to doing CfCs on the Understanding content.

Received on Friday, 15 December 2017 03:42:55 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:18 UTC