Total Validator Home Page

Page report

Issue report

Summary

Total errors found:
4
WCAG21 A [4]:
E885 [1], E887 [2], P967 [1]
Total warnings found:
7
HTML [5]:
W605 [4], W609 [1]
WCAG21 A [2]:
W874 [1], W884 [1]
HTML used for this page:
XHTML 1.0 Transitional

Page Layout

Display issue details:

The line numbers refer to lines in the original source. Any with a line number of '0' are implicit tags added by Total Validator:

Go to first issue

   1 next issueprevious issueW874 [WCAG21 2.4.1 (A)] Add a skip navigation link as the first link on the page:
If your document has structure then you should add a skip navigation link to make it easier for accessible users to get to the page's content. To ensure detection, skip navigation links should point to a <main> element, or an element with role='main'. See Understanding 2.4.1, and Skip Navigation.     <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   2 next issueprevious issueP967 [WCAG21 3.1.1 (A)] Use the 'lang' attribute to denote the primary language of the document:
You should always identify the primary natural language of a document using a 'lang' attribute on the <html> element. See WCAG 2.1 HTML Technique H57.     <html xmlns="http://www.w3.org/1999/xhtml">
   3   <head>
   4     <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
   5 next issueprevious issueW605 Duplicate tag found: See matching tag on line: 22
A duplicate tag has been found with the same attributes. Although this should not affect the page, it indicates that a mistake may have been made.         <meta http-equiv="Content-Style-Type" content="text/css" />
   6 next issueprevious issueW605 Duplicate tag found: See matching tag on line: 23
A duplicate tag has been found with the same attributes. Although this should not affect the page, it indicates that a mistake may have been made.         <meta http-equiv="Content-Script-Type" content="text/javascript" />
   7     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   8     <title>
   8       Amendments | Next Stage 4Life
   8     </title>
   9     <link rel='shortcut icon'
         href='https://www.proceduresonline.com/resources/logos/procedures/favicon.ico' type='image/x-icon'/>
  10     <link rel="apple-touch-icon"
         href="https://www.proceduresonline.com/resources/logos/procedures/apple-touch-icon-57x57-precomposed.png
         " />
  11     <link rel="apple-touch-icon"
         href="https://www.proceduresonline.com/resources/logos/procedures/apple-touch-icon-72x72-precomposed.png
         " />
  12     <link rel="apple-touch-icon"
         href="https://www.proceduresonline.com/resources/logos/procedures/apple-touch-icon-114x114-precomposed.png
         " />
  13     <link rel="stylesheet" type="text/css"
         href="https://www.proceduresonline.com/trix_cms_snippets/cookie/jquery.cookiebar.css" />
  14     <script type="text/javascript"
         src="https://www.proceduresonline.com/trix_cms_snippets/cookie/jquery.min.js">
  14     </script>
  15     <script type="text/javascript"
         src="https://www.proceduresonline.com/trix_cms_snippets/cookie/jquery.cookiebar.js">
  15     </script>
  16     <script type="text/javascript">
  21     </script>
  22 next issueprevious issueW605 Duplicate tag found: See matching tag on line: 5
A duplicate tag has been found with the same attributes. Although this should not affect the page, it indicates that a mistake may have been made.         <meta http-equiv="Content-Style-Type" content="text/css" />
  23 next issueprevious issueW605 Duplicate tag found: See matching tag on line: 6
A duplicate tag has been found with the same attributes. Although this should not affect the page, it indicates that a mistake may have been made.         <meta http-equiv="Content-Script-Type" content="text/javascript" />
  24 next issueprevious issueW609 The 'content-type' HTTP header specifies a character set of UTF-8, which is different to the value
              given here:
The 'content-type' HTTP header specifies a different character set to that specified in the tag. In this case the HTTP header takes precedence.         <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
  25     <meta name="author" content="Next Stage 4Life" />
  26     <meta name="description" content="Next Stage 4Life" />
  28     <meta name="robots" content="index, follow" />
  29     <meta name="rating" content="all" />
  30     <meta http-equiv="pragma" content="no-cache" />
  31     <link title="small" href="scripts/style.css" type="text/css" rel="stylesheet" />
  32     <link title="medium" href="scripts/style_larger.css" type="text/css" rel="alternate stylesheet" />
  33     <link title="large" href="scripts/style_largest.css" type="text/css" rel="alternate stylesheet" />
  34     <link title="hivis" href="scripts/style_hi_vis.css" type="text/css" rel="alternate stylesheet" />
  35     <script type="text/javascript" src="scripts/print.js">
  35     </script>
  36     <script type="text/javascript" src="scripts/styleswitcher.js">
  36     </script>
  37     <script type="text/javascript" src="scripts/highlight.js">
  37     </script>
  38     <script type="text/javascript" src="scripts/jquery.js">
  38     </script>
  39     <script type="text/javascript" src="scripts/pageOrganizer.js">
  39     </script>
  41   </head>
  42   <body onload="highlight();">
  43     <div class="banner">
  44     </div>
  45     <div id="buttons">
  45       <div id="menu">
  46         <ul>
  47           <li>
  47             <a href="index.html">
  47               Home
  47             </a>
  47           </li>
  48           <li>
  48             <a href="contents.html">
  48               Contents
  48             </a>
  48           </li>
  49           <li>
  49             <a href="local_resources.html">
  49               Local Resources
  49             </a>
  49           </li>
  50         </ul>
  51       </div>
  51       <div id="search">
  52         <form action="search/search.html" id="cse-search-box" style="margin: 0px;">
  53 next issueprevious issueI899 [WCAG21 1.3.2 (A)] Layout tables must represent their content in a meaningful sequence:
Screen readers can struggle to read out tables sensibly, so it is often better to use alternative mark-up and CSS to layout content. Try disabling the table mark-up to see if it still makes sense. See WCAG 2.1 Failure F49.               <table width="97%" border="0" cellspacing="0" cellpadding="0">
  54             <tr>
  55               <td>
  55 next issueprevious issueE885 [WCAG21 1.1.1/1.3.1/3.3.2/4.1.2 (A)] User interface controls should have a label or an accessible
              name:
Associate form controls with <label> tags, or use the 'aria-label' or 'aria-labelledby' attributes to label controls where it might be confusing or not possible to use a label. See WCAG 2.1 Failure F68.                     <input type="text" name="zoom_query" class="search_input" size="20" id="zoom_searchbox" value="Search this
                     manual" onfocus="this.value=(this.value=='Search this manual') ? '' : this.value;"
                     onblur="this.value=(this.value=='') ? 'Search this manual' : this.value;" style="margin-right: 5px;" />
  55               </td>
  56               <td>
  56                 <input type="submit" value="Go"/>
  56               </td>
  57             </tr>
  58           </table>
  59         </form>
  59       </div>
  59     </div>
  60     <div id="topper">
  60     </div>
  62     <div id="printReady">
  63       <div id="container">
  64         <div id="content_frame_overflow">
  65           <div class="content_text">
  66             <h1>
  66               Amendments
  66             </h1>
  67             <h2 class="h3">
  67               September 2020
  67             </h2>
  68             <br />
  69 next issueprevious issueI899 [WCAG21 1.3.2 (A)] Layout tables must represent their content in a meaningful sequence:
Screen readers can struggle to read out tables sensibly, so it is often better to use alternative mark-up and CSS to layout content. Try disabling the table mark-up to see if it still makes sense. See WCAG 2.1 Failure F49.                 <table width="95%" border="1" cellspacing="0" cellpadding="5">
  70               <tr class="greytableheader">
  71                 <td colspan="2">
  71                   Updated Chapters
  71                 </td>
  72               </tr>
  73               <tr class="greytableheader">
  74                 <td width="40%">
  74                   Chapter Title
  74                 </td>
  75                 <td>
  75                   Details
  75                 </td>
  76               </tr>
  77               <tr>
  78                 <td class="table_row_lightblue">
  78                   <a href="p_alleg_staff.html">
  78                     Allegations Against Staff
  78                   </a>
  78                 </td>
  79                 <td>
  79                   This chapter has been substantially updated and should be re-read.
  79                 </td>
  80               </tr>
  81               <tr>
  82                 <td class="table_row_lightblue">
  82                   <a href="p_accidents.html">
  82                     Recording and Reporting of Accidents
  82                   </a>
  82                 </td>
  83                 <td>
  83                   This chapter has been substantially updated and should be re-read.
  83                 </td>
  84               </tr>
  85               <tr>
  86                 <td class="table_row_lightblue">
  86                   <a href="p_notif_events.html">
  86                     Notification of Serious Events
  86                   </a>
  86                 </td>
  87                 <td>
  87                   This chapter has been substantially updated and should be re-read.
  87                 </td>
  88               </tr>
  89               <tr class="greytableheader">
  90                 <td colspan="2">
  90                   New Chapters and Features
  90                 </td>
  91               </tr>
  92               <tr class="greytableheader">
  93                 <td>
  93                   Chapter Title
  93                 </td>
  94                 <td>
  94                   Details
  94                 </td>
  95               </tr>
  96               <tr>
  97                 <td class="table_row_lightblue">
  97                   <a href="p_surveillance.html">
  97                     Surveillance and Monitoring
  97                   </a>
  97                 </td>
  98                 <td>
  98                   This chapter has been added to the manual.
  98                 </td>
  99               </tr>
 100             </table>
 101             <br />
 102 next issueprevious issueI899 [WCAG21 1.3.2 (A)] Layout tables must represent their content in a meaningful sequence:
Screen readers can struggle to read out tables sensibly, so it is often better to use alternative mark-up and CSS to layout content. Try disabling the table mark-up to see if it still makes sense. See WCAG 2.1 Failure F49.                 <table width="95%" border="1" cellpadding="5" cellspacing="0" class="table_row_lightblue">
 103               <tr>
 104                 <td>
 104                   <span class="bold">
 104                     Next Update:
 104                   </span>
 104                   September 2021
 104                 </td>
 105               </tr>
 106             </table>
 107             <h2 class="h2_underlined">
 107               <br />
 108               Archive
 108             </h2>
 109             <p>
 109               <span style="font-size:110%;">
 109 next issueprevious issueE887 [WCAG21 2.1.1/2.1.3/2.4.7/3.2.1 (A/AA/AAA)] Do not remove focus when focus is received:
The system focus indicator is an important part of accessibility for keyboard users. Removing focus entirely means the content can only be accessed by a pointer device. See WCAG 2.1 Failure F55.                     <a href="javascript:void(0)" class="headings" onclick="displaySubs('sub_2020')"
                     onfocus="if(this.blur)this.blur()">
 109                   2020 Amendments
 109                 </a>
 109               </span>
 109               <br />
 110               <br />
 111             </p>
 112             <div class="para" id="sub_2020" style="display:none">
 113               <h2 class="h3">
 113                 March 2020
 113               </h2>
 114               <br />
 115               <table width="95%" border="1" cellspacing="0" cellpadding="5">
 116                 <tr class="greytableheader">
 117                   <td colspan="2">
 117                     Updated Chapters
 117                   </td>
 118                 </tr>
 119                 <tr class="greytableheader">
 120                   <td width="40%">
 120                     Chapter Title
 120                   </td>
 121                   <td>
 121                     Details
 121                   </td>
 122                 </tr>
 123                 <tr>
 124                   <td class="table_row_even_bold">
 124                     Notification of Serious Events
 124                   </td>
 125                   <td>
 125                     This procedure, which sets out which agencies and individuals should be notified when a
                         serious event occurs in relation to a child living in a Children&rsquo;s Home, has been
                         updated to reflect revised guidance issued by Ofsted in August 2019. The revised guidance
                         sought to clarify what is meant by a &lsquo;serious event&rsquo; with the aim of reducing
                         the overall number of notifications made to Ofsted, and in particular reducing the number
                         of repeat notifications made as a result of submitting additional / updated information.
 125                   </td>
 126                 </tr>
 127                 <tr>
 128                   <td class="table_row_even_bold">
 128                     Moving to Another Placement
 128                   </td>
 129                   <td>
 129                     This guidance has been reviewed throughout and updated as required. Section 2,
                         Arrangements for the Transfer or Discharge has been updated to include a note on the
                         actions placing authorities are required to undertake if a young person is moving from the
                         home into an unregulated placement.
 129                   </td>
 130                 </tr>
 131               </table>
 131               <br />
 133             </div>
 134             <p>
 134               <span style="font-size:110%;">
 134 next issueprevious issueE887 [WCAG21 2.1.1/2.1.3/2.4.7/3.2.1 (A/AA/AAA)] Do not remove focus when focus is received:
The system focus indicator is an important part of accessibility for keyboard users. Removing focus entirely means the content can only be accessed by a pointer device. See WCAG 2.1 Failure F55.                     <a href="javascript:void(0)" class="headings" onclick="displaySubs('sub_2019')"
                     onfocus="if(this.blur)this.blur()">
 134                   2019 Amendments
 134                 </a>
 134               </span>
 134               <br />
 135               <br />
 136             </p>
 137             <div class="para" id="sub_2019" style="display:none">
 138               <h3 class="h3">
 138                 September 2019
 138               </h3>
 139               <br />
 140               <table width="95%" border="1" cellspacing="0" cellpadding="5">
 141                 <tr class="greytableheader">
 142                   <td colspan="2">
 142                     Updated Chapters
 142                   </td>
 143                 </tr>
 144                 <tr class="greytableheader">
 145                   <td width="40%">
 145                     Chapter Title
 145                   </td>
 146                   <td>
 146                     Details
 146                   </td>
 147                 </tr>
 148                 <tr>
 149                   <td class="table_row_even_bold">
 149                     Information Sharing
 149                   </td>
 150                   <td>
 150                     This chapter has been significantly updated.
 150                   </td>
 151                 </tr>
 152                 <tr>
 153                   <td class="table_row_even_bold">
 153                     Recognising Abuse and Neglect
 153                   </td>
 154                   <td>
 154                     Section 6, Sexual Abuse and Section 8, Bullying (including Online/Cyberbullying) have been
                         reviewed and completely updated.
 154                   </td>
 155                 </tr>
 156                 <tr>
 157                   <td class="table_row_even_bold">
 157                     Safeguarding Children and Young People from Sexual Exploitation
 157                   </td>
 158                   <td>
 158                     Links have been added to resources for practitioners working with children who have been,
                         or are at risk of, Child Sexual Exploitation published by Barnardos and Research in
                         Practice.
 158                   </td>
 159                 </tr>
 160                 <tr>
 161                   <td class="table_row_even_bold">
 161                     Notification of Serious Events
 161                   </td>
 162                   <td>
 162                     This chapter has been significantly updated.
 162                   </td>
 163                 </tr>
 164                 <tr>
 165                   <td class="table_row_even_bold">
 165                     Care and Placement Plans Guidance
 165                   </td>
 166                   <td>
 166                     This guidance has been reviewed throughout and updated as required. Information in
                         relation to Pathway Plans has been updated to reflect that care leavers can request
                         support from local authorities up to the age of 25 years.
 166                   </td>
 167                 </tr>
 168               </table>
 169             </div>
 170             <p>
 170               <br />
 171               <br />
 172             </p>
 173           </div>
 174         </div>
 175       </div>
 176     </div>
 177     <div id="footer-wrap">
 178       <div id="footer-container">
 178         <div id="footer">
 179 next issueprevious issueI899 [WCAG21 1.3.2 (A)] Layout tables must represent their content in a meaningful sequence:
Screen readers can struggle to read out tables sensibly, so it is often better to use alternative mark-up and CSS to layout content. Try disabling the table mark-up to see if it still makes sense. See WCAG 2.1 Failure F49.               <table width="100%" border="0" cellspacing="0" cellpadding="0">
 180             <tr>
 181               <td width="60%" align="left" style="padding-top: 0px;">
 181                 <a href="http://www.trixonline.co.uk/" target="_blank">
 181                   <img src="images/trix_logo.gif" width="57" height="22" alt="tri.x logo" border="0"/>
 181                 </a>
 181                 &nbsp;&nbsp;&nbsp;&nbsp;
 181                 <span class="darkdivider">
 181                   |
 181                 </span>
 181                 &nbsp;&nbsp;&nbsp;&nbsp;Copyright &copy;
 181                 <a href="http://www.trixonline.co.uk/" target="_blank">
 181                   tri.x
 181                 </a>
 181                 &nbsp;&nbsp;&nbsp;&nbsp;
 181                 <span class="darkdivider">
 181                   |
 181                 </span>
 181                 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 181               </td>
 182               <td width="40%" align="right" valign="top" style="padding-top: 0px;">
 184                 <div class="footer_box">
 184                   <a href="#">
 184                     visibility:
 184                   </a>
 184                   &nbsp;
 184                   <a href="#" onclick="setActiveStyleSheet('small'); return false;">
 184                     <img src="images/icons/small_a.gif" alt="View this website with small text" border="0" />
 184                   </a>
 184                   <a href="#" onclick="setActiveStyleSheet('medium'); return false;">
 184                     <img src="images/icons/medium_a.gif" border="0" alt="View this website with medium
                         text" />
 184                   </a>
 184                   <a href="#" onclick="setActiveStyleSheet('large'); return false;">
 184                     <img src="images/icons/large_a.gif" border="0" alt="View this website with large text" />
 184                   </a>
 184                   <a href="#" onclick="setActiveStyleSheet('hivis'); return false;">
 184                     <img src="images/icons/hivis.gif" border="0" alt="View this website with high
                         visibility" />
 184                   </a>
 184                   &nbsp;&nbsp;
 184                   <span class="darkdivider">
 184                     |
 184                   </span>
 184                   &nbsp;&nbsp;
 184                 </div>
 185                 <div class="footer_box">
 185                   <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
 185                     <img src="images/icons/favourite.gif" alt="Add this page to your favourites" width="18"
                         height="18" border="0" />
 185                   </a>
 185                   <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
 185                     favourites
 185                   </a>
 185                   &nbsp;&nbsp;
 185                   <span class="darkdivider">
 185                     |
 185                   </span>
 185                   &nbsp;&nbsp;
 185                 </div>
 186                 <div class="footer_box">
 186 next issueprevious issueW884 [WCAG21 2.1.1/2.1.3 (A/AAA)] Mouse/Pointer event handlers require keyboard equivalents:
When using mouse/pointer event handlers on elements that can be accessed by keyboard, ensure that you provide an equivalent keyboard handler. See WCAG 2.1 Failure F54.                       <input name="printMe" type="image" onclick="printSpecial()" value="Print this Page"
                       src="images/icons/print.gif" onmouseover="images/icons/print.gif'"
                       onmouseout="this.src='images/icons/print.gif'" alt="Print this page"/>
 188                   <a href="#" onclick="printSpecial()">
 188                     print
 188                   </a>
 188                   &nbsp;&nbsp;
 188                   <span class="darkdivider">
 188                     |
 188                   </span>
 188                   &nbsp;&nbsp;
 188                 </div>
 189               </td>
 190             </tr>
 191           </table>
 192         </div>
 192       </div>
 193     </div>
 194   </body>
 195 </html>