I would agree only because we have enough v4 browsers around campus that are vocal that force some level of usability to be given to them. They don't mind getting text only pages, just unusable pages get them to fire up pine. I don't think <br /> are evil if used wisely... Easy enough to strip in the future.
Jesse On 1/17/05 9:15 PM, "Terrence Wood" <[EMAIL PROTECTED]> wrote: > text-only and v4 browsers lack support for fieldsets, so one is really > stuck with using <br /> as the the leanest code solution. > > Terrence Wood. > > > Patrick H. Lauke wrote: >> a slippery slope, in my opinion...starting to add what is, in this case, >> visual markup to compensate for lack of CSS... >> >> i usually only worry about accessibility in cases where CSS is not >> available, but i do take your point on usability. if i absolutely had to >> cater for non-CSS browsers this way, i guess i would wrap each >> label/control pair in their own fieldset to keep it non-presentational >> (although that leads to drastic code bloat) > ****************************************************** > The discussion list for http://webstandardsgroup.org/ > > See http://webstandardsgroup.org/mail/guidelines.cfm > for some hints on posting to the list & getting help > ****************************************************** ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
