#2744 closed New Feature (duplicate)
<th> in Tables
Reported by: | Peter Ertman | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | |
Keywords: | Cc: |
Description
Work for a Federal agency, We have to comply with what is known as section 508 of the Americans with Disability Act. We are having problems with tables passing accessibility tests. Here are the two standards:
§1194.22 (g) Row and column headers shall be identified for data tables.
§11924.22 (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers
When FCKEditor generates a table it starts with <table>, <tbody>, etc, but there is NO <th> generated for the first row of the table, it uses <td>. So, do we need to look at something else other than FCKeditor? Is there a way to do this programmatically?
We are not allowing our authors to access or modify the underlying HTML so this needs to be done some other way. We could use <td> with a scope statement but again that would require modifing the underlying HTML which we will not allow authors to do.
In the response to the above posting, they suggested that I feature request the following: extend the table wizard/dialog to include checkboxes for <thead>/<tfoot>/<colgroup> and a <th> row/column.
Without this, I am concerned that we in the Federal service will not be able to use this editor since this is a fatal flaw in section 508 compliance. And, as you can see, the sooner the better.
Thanks,
P.
Change History (4)
comment:1 follow-up: 4 Changed 16 years ago by
comment:2 Changed 16 years ago by
Keywords: | Tables Header Row Column removed |
---|
comment:3 Changed 16 years ago by
Priority: | High → Normal |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
dup of #822
comment:4 Changed 16 years ago by
Replying to mosipov:
You could solve this by post-processing the HTML with XSLT.
Please read my original post. We do not allow authors or others to modify the underlying HTML which is part of our web content management system.
Also, I am confused. Is this functionality part of 2.6.4 or 2.7 (which will not be released due to 3.0) or the soon to be released 3.0?
Thanks,
P.
You could solve this by post-processing the HTML with XSLT.