- From: Janina Sajka <janina@rednote.net>
- Date: Wed, 25 Mar 2015 15:26:42 -0400
- To: David Singer <singer@apple.com>
- Cc: Steve Faulkner <faulkner.steve@gmail.com>, Birkir Gunnarsson <birkir.gunnarsson@deque.com>, "public-w3process@w3.org" <public-w3process@w3.org>, W3C WAI Protocols & Formats <public-pfwg@w3.org>
David Singer writes: > > > On Mar 25, 2015, at 8:09 , Steve Faulkner <faulkner.steve@gmail.com> wrote: > > > > > > On 25 March 2015 at 14:59, Janina Sajka <janina@rednote.net> wrote: > > While we should be > > able to expect that readers would note publication dates and > > automatically suspect a document long unupdated > > > > Major issue here is that multi-page documents only have publication dates on front pages, for example: > > http://www.w3.org/TR/2006/WD-WCAG20-20060427/conformance.html#conformance-reqs has no pub date > > > > Also publication date alone does not provide a clear indication of a document being superseded or outdated, take for example > > http://www.w3.org/TR/WCAG10/ > > Right, this is like the IETF, where you have to notice ‘obsoleted by’ in the little header at the top of the RFC. > > The IETF is scared of newer technologies than teletypes :-), we’re not. We can do better, as you say (e.g. floating header/footer). > I understand how header/footer can help multi-page, but how does it help for WCAG 1.0? Or for HTML 4.01? Etc. Janina > David Singer > Manager, Software Standards, Apple Inc. > -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@asterisk.rednote.net Email: janina@rednote.net Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Protocols & Formats http://www.w3.org/wai/pf Indie UI http://www.w3.org/WAI/IndieUI/
Received on Wednesday, 25 March 2015 19:27:07 UTC