You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm testing a website using AXE chrome extension and it is reporting an incorrect usage of the scope attribute.
The html chunk that is producing the error is: <th style="" scope="col">Product</th>
What I understand of the error is that scope can only be used on TH tags, but that's the case, so it's not clear why it is being reported.
The output of the extension is here:
Ensures the scope attribute is used correctly on tables
(More Info)
best-practice
Target:#partner-signup > div:nth-of-type(2) > .main-col > .order-confirmation > table > thead > tr > th:nth-of-type(1)
HTML:
<th style="" scope="col">Product</th>
Summary:
Fix all of the following:
In HTML 5, scope attributes may only be used on table header elements (<th>)
The text was updated successfully, but these errors were encountered:
matiasmm
changed the title
Reporting an incorrect usage of the scope="col" on TH tag
Reporting an incorrect usage of scope attribute on TH tag
Oct 25, 2016
The problem is in the <!DOCTYPE> tag. I'm using a doctype for html4: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> instead of <!DOCTYPE html> for html5.
I think the error message could be more clear, it is checking two things: that the page is html5 and that the scope is being used in a TH tag, but it's only reporting the second issue.
Uh oh!
There was an error while loading. Please reload this page.
I'm testing a website using AXE chrome extension and it is reporting an incorrect usage of the scope attribute.
The html chunk that is producing the error is:
<th style="" scope="col">Product</th>
What I understand of the error is that scope can only be used on TH tags, but that's the case, so it's not clear why it is being reported.
The output of the extension is here:
The text was updated successfully, but these errors were encountered: