The Web and Open Data Validator (formerly the WPSS Validation Tool) provides web developers and quality assurance testers the ability to perform a number of web site, web page validation and Open data validation tasks at one time.
How hard would it be to look back up the node tree of an error and find the container landmark? Then put that container in a separate column in the CSV.
If the error is a child of one of these landmarks it would be easier to group errors and to separate template issues from content issues:
In HTML the landmark element are:
<main><header><footer><nav><aside>
or the aria role counterparts
<... role="main"><... role="banner"><... role="contentinfo"><... role="navigation"><... role="complementary"><... role="search">
Common id values for landmarks
<div id="content" ...<div id="main-content" ...<div id="main" ...<div id="footer" ...<div id="header" ...<div id="navigation" ...<div id="nav" ...
The new column would just be a list of the container landmark code snip next to each issue.
How hard would it be to look back up the node tree of an error and find the container landmark? Then put that container in a separate column in the CSV. If the error is a child of one of these landmarks it would be easier to group errors and to separate template issues from content issues:
In HTML the landmark element are:
<main>
<header>
<footer>
<nav>
<aside>
or the aria role counterparts<... role="main">
<... role="banner">
<... role="contentinfo">
<... role="navigation">
<... role="complementary">
<... role="search">
Common id values for landmarks<div id="content" ...
<div id="main-content" ...
<div id="main" ...
<div id="footer" ...
<div id="header" ...
<div id="navigation" ...
<div id="nav" ...
The new column would just be a list of the container landmark code snip next to each issue.
<footer>
<header>
role="banner
id="content