- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Fri, 15 Dec 2017 12:03:59 -0600
- To: Michael Cooper <cooper@w3.org>
- Cc: AG WG <w3c-wai-gl@w3.org>
Hi Michael, Thank you very much for working on this. > https://w3c.github.io/wcag21/understanding/ I noticed some links come up 404 on that page such as: https://w3c.github.io/wcag21/understanding/21/text-spacing.html https://w3c.github.io/wcag21/understanding/21/label-in-name.html https://w3c.github.io/wcag21/understanding/21/target-size-enhanced.html https://w3c.github.io/wcag21/understanding/21/reflow.html Might be a good idea to run a link checker though. Thanks again for all of your hard work. Kindest regards, Laura On 12/14/17, Michael Cooper <cooper@w3.org> wrote: > As we discussed Tuesday, I've merged all the Understanding working > branches in their current state into the editors' draft: > > https://w3c.github.io/wcag21/understanding/ > > and the publication location referenced by the official WCAG 2.1 Working > Draft is updated: > > https://www.w3.org/WAI/WCAG21/Understanding/ > > 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. > > Michael -- Laura L. Carlson
Received on Friday, 15 December 2017 18:04:22 UTC