Tablenator used to report a problem if a TH cell did not contain any text and there was an image with an alt tag. The tablenator does not report the cell as empty anymore.

Corrected bug introduced by v1.0.16 when I removed warnings about table order potentially being in the wrong order.

. Changed the Tablenator popup screen to show the label "Analyze all tables" to look more like a window title, and not clickable. Changed the text around keeping and removing content to include the fact that we are analyzing tables.
. Removed the warning about ids possibly being in the wrong order until I come up with a better algorithm.

Changed the top of the page so that there is now only one list of all of the tables found on the page. Each entry in the list of tables is linked to the table on the page. If the Tablenator/W3C finds any issues with a table, an indicator is shown next to table entry to show whether there is a Tablenator error, Tablenator warning, or W3C error.

o Display alert box if the user tries to analyze tables with or without content a second time.
o At the top of the page, display a list of all tables found on the page.
o Added error check logic. If a page has scope row/col and no scope rowgroup/colgroup and has rowspan/colspan then report an error.

o Tablenator will now report duplicate ids that span multiple tables.
o Tablenator will now report on duplicate ids within a header tag.
o Change the "Analyze all tables" to show page table information with and without the page content around the tables

- When you select the option to "Analyze all tables", the Tablenator will now also setup the tool to "Show table relationships". There is no longer any need to select this option seperately.
- The Tablenator will now report an error if a TH cell is empty.

o The Tablenator was reporting a warning that tables with no accessibilty tags which only had a th in the first row and/or first column as a simple table, but was not looking for rowspans and colspans. It is now looking for rowspans and colspans and is not reporting it as a simple table if the table has these.
o Changed the colours of the errors and warnings so that they are not so hard on the eyes and still accessible.

If the headers on a td cell were separated by more than 1 space, the numbering shown in the "Show table relationships" seemed to skip numbers. This has been corrected.

Fixed a bug where if the Tablenator did not find an ID referenced in a header attribute, the Tablenator stopped processing.

o Ensured that the error and warning message passed colour contrast rules.
o When looking at table relationships, and you hover over a cell, a popup appears with a list of the headers that are associated with the cell. This popup has been formated to display each associated cell onto a separate line.
o When looking at table relationships, the related cells are numbered in the order that an accessibility device would read out the headers. In the past, the order number would be shown in the cell, and depending on the amount of space in the cell, the cell size would change. This would cause the screen to jump around while hovering the mouse over cells. We now overlay the cell with the order number; this eliminate the screen jumping issue.

If you are showing table relationships, you can now hover over a cell, a tooltip will appear indicating the the headers associated with the cell. This will be useful if you have a large table, and the header cells are no longer on the screen.

-If a table is really simple (top header row OR left header column), and no scope or headers, now show as a warning only.
-The order of the ids in a headers attribute can now either be sorted in row first/column second or column first/row second order.

Changed the Tablenator logo ...again

Changed the Tablenator logo.

Changed the Tablenator menu to show buttons instead of links.

Corrected issue where the tool reported a Tablenator issue if there were extra spaces in the headers attribute.

-Fixed sorting of w3c table errors (e.g. table 11 comes after table 4 now)
-Corrected problem where tables were reporting W3C errors but there were none.