- From: Daniel Dardailler <danield@w3.org>
- Date: Thu, 04 Feb 1999 16:09:36 +0100
- To: "Neff, Robert" <Robert.Neff@usmint.treas.gov>
- cc: "'w3c-wai-eo@w3.org'" <w3c-wai-eo@w3.org>, "'dd@w3.org'" <dd@w3.org>, "'jbrewer@w3.org'" <jbrewer@w3.org>
> >4. Image Maps Use client-side MAP and text link for hotspots. > ROB>Disagree, feel we are confusing the issue and recommend, > Use client-side MAPs, ALT Tags for hotspots and text links. > > Justification: ALT Tag for hotspots and text links are two separate issues. > The ALT Tag for the Hotpsot provides users with a visual description of the > hotspot, whereas Text Link provides text links of each hotspot for the > graphic. No, they are exactly the same thing (remember ALT is the function) so we're talking redundancy here, for legacy situation mostly. > >7. Page Organization Use headings, lists, and consistent structure. Use CSS > >for layout and style. > ROB> I still disagree with the statement, "Use CSS for layout and style." The last version has "Use CSS for layout and style wherever possible" which I think covers your (and others) worries that we're asking too much to authors. > Suggest we say, "For layout and style, recommend CSS or accessible HTML" "Accessible HTML" is all this card is about, I don't think adding it here is adding anything. > >11. Tables Make line by line reading sensible. Provide a Summary. Avoid > >using tables for column layout. > Rob> Seems I am going to have to agree to disagree on the last statement, OK thanks. I don't want to argue again about this one. Please keep in mind this is just a tip.
Received on Thursday, 4 February 1999 10:09:48 UTC