testilo 19.1.3 → 19.1.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "testilo",
-  "version": "19.1.3",
+  "version": "19.1.5",
   "description": "Prepares and processes Testaro reports",
   "main": "aim.js",
   "scripts": {

package/procs/digest/tdp37/index.html

@@ -31,31 +31,13 @@
       </header>
       <h2>Introduction</h2>
       <p>How <a href="https://www.w3.org/WAI/">accessible</a> is the __org__ web page at <a href="__url__"><code>__url__</code></a>?</p>
-      <p>This digest can help answer that question. Nine different tools (Alfa, ASLint, Axe, Equal Access, HTML CodeSniffer, Nu Html Checker, QualWeb, Testaro, and WAVE) tested the page to check its compliance with their accessibility rules. In all, the tools define about 960 rules, which are classified here into about 290 accessibility issues. The results were interpreted to yield a score. If the page passed every test, its score would be 0. The score for this page was __total__.</p>
-      <h2>Total score</h2>
-      <p>The total score is the sum of five components.</p>
-      <table class="allBorder secondCellRight">
-        <caption>Score summary</caption>
-        <thead>
-          <tr><th>Component</th><th>Score</th><th>Description</th></tr>
-        </thead>
-        <tbody class="headersLeft">
-          <tr><th>issue</th><td>__issue__</td><td>Severity and number of reported defects</td></tr>
-          <tr><th>tool</th><td>__tool__</td><td>Tool-by-tool defect ratings</td></tr>
-          <tr><th>prevention</th><td>__prevention__</td><td>Failed attempts by tools to test the page</td></tr>
-          <tr><th>log</th><td>__log__</td><td>Browser warnings about the page</td></tr>
-          <tr><th>latency</th><td>__latency__</td><td>Abnormal delay in page responses</td></tr>
-        </tbody>
-        <tfoot>
-          <tr><th>total</th><td>__total__</td><td>Sum of the component scores</td></tr>
-        </tfoot>
-      </table>
-      <h2>Issue scores</h2>
-      <p>The score on an issue depends on the <dfn>severity</dfn> (user impact and certainty) of the issue and on how many instances were reported (by one or more tools).</p>
+      <p>This digest can help answer that question. Nine different tools (Alfa, ASLint, Axe, Equal Access, HTML CodeSniffer, Nu Html Checker, QualWeb, Testaro, and WAVE) tested the page to check its compliance with their accessibility rules. In all, the tools define about 960 rules, which are classified here into about 300 accessibility issues.</p>
+      <p>The results were interpreted to yield a score, with 0 being ideal. The score for this page was __total__, the sum of __issue__ for issues, __tool__ for tool-by-tool ratings, __prevention__ for the page preventing tools from running, __log__ for browser warnings, and __latency__ for delayed page responses.</p>
+      <h2>Issue summary</h2>
       <table class="allBorder thirdCellRight">
         <caption>Summary of issues</caption>
         <thead>
-          <tr><th>Issue</th><th>WCAG</th><th>Score</th><th>Tools Reporting the Issue</th></tr>
+          <tr><th>Issue</th><th>WCAG</th><th>Score</th><th>Tools reporting the issue</th></tr>
         </thead>
         <tbody class="headersLeft">
           __issueRows__

package/procs/score/tsp37.js

@@ -95,7 +95,7 @@ exports.scorer = report => {
           // Add this to the score.
           details.prevention[which] = preventionWeight;
         }
-        // Otherwise, if a successful standard result exists:
+        // Otherwise, if a valid standard result exists:
         else if (
           standardResult
           && standardResult.totals
@@ -125,6 +125,7 @@ exports.scorer = report => {
               // Add the instance to the issue details of the score data.
               if (! details.issue[issueName]) {
                 details.issue[issueName] = {
+                  summary: issues[issueName].summary,
                   score: 0,
                   maxCount: 0,
                   weight: issues[issueName].weight,