- From: John Foliot <john.foliot@deque.com>
- Date: Thu, 12 Oct 2017 19:43:52 -0500
- To: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <CAKdCpxy-VazZaPZwrjs+gcbwGeboFWNusLO+QPLFQeTm1S2wWg@mail.gmail.com>
FWIW, I agree with Micheal that promoting Benefits to sibling of Intent has a positive benefit, and I'd support that idea going forward. Could we strike up a straw poll around this, to take an internal temperature of the WG? Chairs? JF On Oct 11, 2017 10:15 AM, "michael-n-cooper" <notifications@github.com> wrote: *@michael-n-cooper* commented on this pull request. Reviewing structurally only: my major comment is that where new headings beyond the template are introduced, the heading and content related to that heading should be enclosed in a element. This would be used for script processing such as generating TOC, or style, referencing, etc. Having a bunch of new in the Intent section causes the Benefits section to get lost in the shuffle. However, I've been wondering if we should promote Benefits to be a sibling of Intent rather than a child of it (in spite of the structure that was used for WCAG 2.0 Understanding), so this may trigger the answer into a "yes, that matters" state. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <https://github.com/w3c/wcag21/pull/500#pullrequestreview-68622080>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABK-cwUY6LEdWKA2ubBDqyNohZm4Qg63ks5srM2agaJpZM4PzJme> .
Received on Friday, 13 October 2017 00:44:24 UTC