RE: Accessible tables - more research

Barry,

From: http://www.access-board.gov/sec508/508standards.htm

"Paragraphs (g) and (h) permit the use of tables, but require that the
tables be coded according to the rules for developing tables of the markup
language used. When tables are coded inaccurately or table codes are used
for non-tabular material, some assistive technology cannot accurately read
the content. Many assistive technology applications can interpret the HTML
codes for tables and will most likely be updated to read the table coding of
new markup languages. (See ?1194.23(c)(8-9) in the NPRM.) The Board will be
developing technical assistance materials on how tables can comply with this
section. In addition to these specific provisions, the technical assistance
materials will address all of the provisions in this part.

Comment. Commenters were concerned by the preamble discussion in the NPRM
which advised against the use of table tags for formatting of non-tabular
material.

Response. The Board understands that there are currently few alternatives to
the use of tables when trying to place items in predefined positions on web
pages. These provisions do not prohibit the use of table codes to format
non-tabular content. They require that when a table is created, appropriate
coding should be used. Paragraph (g) incorporates the exact language
recommended by the WAI in their comments to the proposed rule. Paragraph (h)
uses language that is not substantively different than WCAG 1.0 and was
supported in the WAI comments to the proposed rule. No substantive changes
have been made to this provision in the final rule."

Now I'm no lawyer, but when I read "When tables are coded inaccurately..."
and then I hear that you are being forced to provide summaries for layout
tables, that, to my lay ears (and feeble brain) smacks of "inacurate".

As always, JMHO

JF




> -----Original Message-----
> From: owner-aware-techniques(at)hwg.org
> [mailto:owner-aware-techniques(at)hwg.org]On Behalf Of Barry Johnson
> Sent: February 26, 2002 7:56 PM
> To: brian walker; aware-techniques(at)hwg.org
> Subject: RE: Accessible tables
>
>
> Thanks for your input Brian.
> However, as a developer for the US Federal Govt, most
> of the agencys I deal with have very strict guidelines
> and a review panel for every page that goes up. The
> Access Board, DoT, DoJ and Treasury all require
> reqiure a complete summary attribute for all tables
> (layout or not) as well as "blank" in all empty cells
> and "spacer" in all place holding gifs.
> I use IBM Hompage and JAWS to double check the flow of
> the pages, but they still have to go to a review
> committee, each of whom rely on assistive technologies
> to do thier jobs.
> OK, when I do non-Gov sites I tend to follow your
> model but they do not have to be 508...
>
> Barry
>
> --- brian walker <bwalker5(at)tampabay.rr.com> wrote:
> > As a screen reader user, I personally do not want
> > layout tables identified
> > as such. It is just extra verbiage.
> >
> > The table specific commands available through my
> > screen reader are
> > intentionally not functional in tables with only one
> > row. This works very
> > well.
> >
> > I do not use summary attributes in the tables I
> > create unless they are:
> >
> > 1. data tables
> > 2. complex enough that a summary truly adds value,
> > i.e. makes the table
> > easier to understand.
> >
> > I may be blind, but I do not think it is that
> > difficult to figure out.
> >
> > However, I recognize that mileage may vary for
> > others.
> >
> > Brian
> >
> > -----Original Message-----
> > From: owner-aware-techniques(at)hwg.org
> > [mailto:owner-aware-techniques(at)hwg.org]On Behalf Of
> > Barry Johnson
> > Sent: Tuesday, February 26, 2002 3:05 PM
> > To: aware-techniques(at)hwg.org
> > Subject: Re: Accessible tables
> >
> >
> > Until all browsers recognize CSS, the Accesibility
> > Community has nothing against using tables for
> > layout,
> > as long as they are identified as such...
> >
> > Barry
> >
> > --- Pam Ware <tam(at)gn.apc.org> wrote:
> > > At 10:59 26/02/02, Barry wrote:
> > > >But don't forget to use the summary attribute!
> > > ><table (size) (border) (etc) summary="Table used
> > > for
> > > >layout.">
> > > I thought the goal was to use tables only for
> > table
> > > data, not for layout -
> > > and move towards CSS positioning? If so, any
> > > suggestions of how best to do
> > > that in order to include navigation bars, related
> > > links etc. as well as
> > > main page content?
> > > TIA,
> > > Pam
> > >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Greetings - Send FREE e-cards for every
> > occasion!
> > http://greetings.yahoo.com
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Greetings - Send FREE e-cards for every occasion!
> http://greetings.yahoo.com
>

HWG: hwg-basics mailing list archives, maintained by Webmasters @ IWA