- From: Michael Cooper <cooper@w3.org>
- Date: Tue, 8 Mar 2016 15:49:24 -0500
- To: "lisa.seeman" <lisa.seeman@zoho.com>
- Cc: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
- Message-ID: <56DF3AD4.8050700@w3.org>
Yes On 08/03/2016 2:55 PM, lisa.seeman wrote: > > Michael, will you be available to talk us though it on Mondays call? > > All the best > > Lisa Seeman > > LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter > <https://twitter.com/SeemanLisa> > > > > > ---- On Tue, 08 Mar 2016 18:39:17 +0200 *Michael > Cooper<cooper@w3.org>* wrote ---- > > A complete list would be an infinite set. Some things I can think > of right now: > > * Spell check (for U.S. English) > * Grammar check - complete sentences, fragments, etc. > * Structure check - does the document flow in the optimal manner > * Code check - is the code well formed and resulting in the > structure we intend, every sub-section wrapped in a <section> > with a <hx> element > * Naked URIs need to be removed, wrapped around link text > * References need to follow W3C format, lots of the inline URIs > actually should be treated as references > * Understandability of reading it top to bottom > * Good introduction sections > * Follow W3C manual of style http://www.w3.org/2001/06/manual/ > * Cross references using relative URIs so we can adjust them easily > * No references to wiki or rawgit (temp resources) > > Michael > > Michael > > > On 08/03/2016 9:10 AM, lisa.seeman wrote: > > 5d9a876952.5879706686331314790@zoho.com" type="cite"> > Michael, could you send a complete list of what we need to do > with each issue paper. > > > All the best > > Lisa Seeman > > LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter > <https://twitter.com/SeemanLisa> > > > > > >
Received on Tuesday, 8 March 2016 20:49:34 UTC