E1 Are links in server-side image maps repeated elsewhere in the page that are non-graphical, e.g. a normal list of links? F1 Are client-side image maps used instead of server-side image maps? F2 Do client-side image maps have appropriate alternative text for the image, as well as each hot spot region? G1 For tables containing data, do elements appropriately define th every row and/or every column headers? G2 For tables containing data, do elements contain the scope th attribute for row and/or column headers that are not logically placed, e.g. in the first row and first column as applicable? G3 For tables containing data, is the summary attribute used to explain the meaning of the table if it is not otherwise evident from context? For tables that are used for layout, are elements or G4 th summary, or attributes NOT used at all? headers, scope, abbr, axis For complex tables, do elements appropriately define row and/or H1 th column headers? H2 For complex tables, does each element contain an attribute th id unique to the page and/or does each element and any th td element that acts as a header for other elements contain a scope attribute of or row, col, rowgroup, colgroup? H3 For complex tables, does any element that is associated with td more than one element contain a attribute that lists the th headers attribute for all headers associated with that cell? id H4 Are the attribute and and elements used to summary thead tbody clarify the table meaning and structure if needed?
E1 Are links in server-side image maps repeated elsewhere in the page that are non-graphical, e.g. a normal list of links? F1 Are client-side image maps used instead of server-side image maps? F2 Do client-side image maps have appropriate alternative text for the image, as well as each hot spot region? G1 For tables containing data, do th elements appropriately define every row and/or every column headers? G2 For tables containing data, do th elements contain the scope attribute for row and/or column headers that are not logically placed, e.g. in the first row and first column as applicable? G3 For tables containing data, is the summary attribute used to explain the meaning of the table if it is not otherwise evident from context? G4 For tables that are used for layout, are th elements or summary, headers, scope, abbr, or axis attributes NOT used at all? H1 For complex tables, do th elements appropriately define row and/or column headers? H2 For complex tables, does each th element contain an id attribute unique to the page and/or does each th element and any td element that acts as a header for other elements contain a scope attribute of row, col, rowgroup, or colgroup? H3 For complex tables, does any td element that is associated with more than one th element contain a headers attribute that lists the id attribute for all headers associated with that cell? H4 Are the summary attribute and thead and tbody elements used to clarify the table meaning and structure if needed?