frontpage should help me design ADA compliant tables.

[tenable]

creating ADA compliant tables is a real chore. FrontPage should provide an
automated mechanism to make table ADA compliant.

There are tags that are not shown in the table tools that relate to ADA
compliance (e.g., <caption>.) This could be added to the <table> properties
dialog.

Also, easy to add ID-to-HEADER identifiers should be added to the "column"
properties dialog.

And, the "summary" attribute should be added to the <table> properties
dialog or a special ADA table toolbar.

 

[Kathleen Anderson [MVP - FrontPage]]

FrontPage doesn't know whether you are creating a data table or a layout
table - those attributes you mention would be invalid for layout tables.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

 

[Murray]

Actually, they are not invalid for any table, but they might not make sense
for a data table. You have no obligation to actually USE them, but you
should be able to do so via a UI somewhere.

 

[Kathleen Anderson [MVP - FrontPage]]

I agree that they are valid, however, I believe the OP is referring to the
Section 508 standards 1194.22 (g) and (h), and WCAG Guideline 5. Create
tables that transform gracefully, which require the use of certain table
attributes when marking up a data table. WCAG Checkpoint 5.4 also says: If a
table is used for layout, do not use any structural markup for the purpose
of visual formatting. [Priority 2] For example, in HTML do not use the TH
element to cause the content of a (non-table header) cell to be displayed
centered and in bold.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

 

[Murray]

Sure - it's easy to misuse any HTML tag - take <blockquote> for example.
How many times do you see this used as a layout device - heck even &nbsp;
suffers that ignominious fate!

But - one should have the opportunity somewhere in FP's UI to enter those
attributes/tags.

--
Murray
============

I agree that they are valid, however, I believe the OP is referring to the
Section 508 standards 1194.22 (g) and (h), and WCAG Guideline 5. Create
tables that transform gracefully, which require the use of certain table
attributes when marking up a data table. WCAG Checkpoint 5.4 also says: If
a
table is used for layout, do not use any structural markup for the purpose
of visual formatting. [Priority 2] For example, in HTML do not use the TH
element to cause the content of a (non-table header) cell to be displayed
centered and in bold.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

Actually, they are not invalid for any table, but they might not make
sense for a data table. You have no obligation to actually USE them,
but you should be able to do so via a UI somewhere.

 

[Kathleen Anderson [MVP - FrontPage]]

I agree with you 1000%

--
~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

Sure - it's easy to misuse any HTML tag - take <blockquote> for example.
How many times do you see this used as a layout device - heck even &nbsp;
suffers that ignominious fate!

But - one should have the opportunity somewhere in FP's UI to enter those
attributes/tags.

--
Murray
============

I agree that they are valid, however, I believe the OP is referring to the
Section 508 standards 1194.22 (g) and (h), and WCAG Guideline 5. Create
tables that transform gracefully, which require the use of certain table
attributes when marking up a data table. WCAG Checkpoint 5.4 also says:
If a
table is used for layout, do not use any structural markup for the
purpose
of visual formatting. [Priority 2] For example, in HTML do not use the TH
element to cause the content of a (non-table header) cell to be displayed
centered and in bold.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

Actually, they are not invalid for any table, but they might not make
sense for a data table. You have no obligation to actually USE them,
but you should be able to do so via a UI somewhere.


in message FrontPage doesn't know whether you are creating a data table or a
layout table - those attributes you mention would be invalid for
layout tables.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


creating ADA compliant tables is a real chore. FrontPage should
provide an automated mechanism to make table ADA compliant.

There are tags that are not shown in the table tools that relate to
ADA compliance (e.g., <caption>.) This could be added to the
<table> properties dialog.

Also, easy to add ID-to-HEADER identifiers should be added to the
"column" properties dialog.

And, the "summary" attribute should be added to the <table>
properties dialog or a special ADA table toolbar.

 

[tenable]

But, what about the idea of having an ADA Dialog box one could use to create
simple ADA compliant data tables?

I agree with you 1000%

--
~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

Sure - it's easy to misuse any HTML tag - take <blockquote> for example.
How many times do you see this used as a layout device - heck even
suffers that ignominious fate!

But - one should have the opportunity somewhere in FP's UI to enter those
attributes/tags.

--
Murray
============

I agree that they are valid, however, I believe the OP is referring to the
Section 508 standards 1194.22 (g) and (h), and WCAG Guideline 5. Create
tables that transform gracefully, which require the use of certain table
attributes when marking up a data table. WCAG Checkpoint 5.4 also says:
If a
table is used for layout, do not use any structural markup for the
purpose
of visual formatting. [Priority 2] For example, in HTML do not use the TH
element to cause the content of a (non-table header) cell to be displayed
centered and in bold.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


Actually, they are not invalid for any table, but they might not make
sense for a data table. You have no obligation to actually USE them,
but you should be able to do so via a UI somewhere.


in message FrontPage doesn't know whether you are creating a data table or a
layout table - those attributes you mention would be invalid for
layout tables.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


creating ADA compliant tables is a real chore. FrontPage should
provide an automated mechanism to make table ADA compliant.

There are tags that are not shown in the table tools that relate to
ADA compliance (e.g., <caption>.) This could be added to the
<table> properties dialog.

Also, easy to add ID-to-HEADER identifiers should be added to the
"column" properties dialog.

And, the "summary" attribute should be added to the <table>
properties dialog or a special ADA table toolbar.

 

[Kathleen Anderson [MVP - FrontPage]]

Wouldn't that be great? You can send that suggestion to the Microsoft Wish
Program: http://support.microsoft.com/default.aspx?kbid=114491

--
~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

But, what about the idea of having an ADA Dialog box one could use to
create
simple ADA compliant data tables?

I agree with you 1000%

--
~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

Sure - it's easy to misuse any HTML tag - take <blockquote> for
example.
How many times do you see this used as a layout device - heck even
suffers that ignominious fate!

But - one should have the opportunity somewhere in FP's UI to enter
those
attributes/tags.

--
Murray
============

in
message I agree that they are valid, however, I believe the OP is referring to
the
Section 508 standards 1194.22 (g) and (h), and WCAG Guideline 5.
Create
tables that transform gracefully, which require the use of certain
table
attributes when marking up a data table. WCAG Checkpoint 5.4 also
says:
If a
table is used for layout, do not use any structural markup for the
purpose
of visual formatting. [Priority 2] For example, in HTML do not use the
TH
element to cause the content of a (non-table header) cell to be
displayed
centered and in bold.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


Actually, they are not invalid for any table, but they might not make
sense for a data table. You have no obligation to actually USE them,
but you should be able to do so via a UI somewhere.


in message FrontPage doesn't know whether you are creating a data table or a
layout table - those attributes you mention would be invalid for
layout tables.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


creating ADA compliant tables is a real chore. FrontPage should
provide an automated mechanism to make table ADA compliant.

There are tags that are not shown in the table tools that relate to
ADA compliance (e.g., <caption>.) This could be added to the
<table> properties dialog.

Also, easy to add ID-to-HEADER identifiers should be added to the
"column" properties dialog.

And, the "summary" attribute should be added to the <table>
properties dialog or a special ADA table toolbar.

 

[tenable]

You are so cool. that's the link I was looking for!!!! And, you can vote
for it here, too.

Wouldn't that be great? You can send that suggestion to the Microsoft Wish
Program: http://support.microsoft.com/default.aspx?kbid=114491

--
~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

But, what about the idea of having an ADA Dialog box one could use to
create
simple ADA compliant data tables?

I agree with you 1000%

--
~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx



Sure - it's easy to misuse any HTML tag - take <blockquote> for
example.
How many times do you see this used as a layout device - heck even
suffers that ignominious fate!

But - one should have the opportunity somewhere in FP's UI to enter
those
attributes/tags.

--
Murray
============

in
message I agree that they are valid, however, I believe the OP is referring to
the
Section 508 standards 1194.22 (g) and (h), and WCAG Guideline 5.
Create
tables that transform gracefully, which require the use of certain
table
attributes when marking up a data table. WCAG Checkpoint 5.4 also
says:
If a
table is used for layout, do not use any structural markup for the
purpose
of visual formatting. [Priority 2] For example, in HTML do not use the
TH
element to cause the content of a (non-table header) cell to be
displayed
centered and in bold.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


Actually, they are not invalid for any table, but they might not make
sense for a data table. You have no obligation to actually USE them,
but you should be able to do so via a UI somewhere.


in message FrontPage doesn't know whether you are creating a data table or a
layout table - those attributes you mention would be invalid for
layout tables.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


creating ADA compliant tables is a real chore. FrontPage should
provide an automated mechanism to make table ADA compliant.

There are tags that are not shown in the table tools that relate to
ADA compliance (e.g., <caption>.) This could be added to the
<table> properties dialog.

Also, easy to add ID-to-HEADER identifiers should be added to the
"column" properties dialog.

And, the "summary" attribute should be added to the <table>
properties dialog or a special ADA table toolbar.