Total Validator Home Page

Page report

Issue report

Summary

Total errors found:
4
WCAG21 A [2]:
E958 [1], P908 [1]
WCAG21 AA [2]:
E910 [1], E916 [1]
Total warnings found:
1
WCAG21 A [1]:
W889 [1]
HTML used for this page:
HTML5

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 <!doctype html>
   2 <html lang="en">
   3   <head>
   4     <meta charset="utf-8">
  12 next issueprevious issueE916 [WCAG21 1.4.4 (AA)] Do not use 'viewport' settings which prevent the user from zooming in:
Using 'user-scalable=no' or 'maximum-scale' with a value less than 2.0 may prevent people with sight difficulties from being able to 'zoom in' to pages to read them. See Understanding 1.4.4.         <meta name='viewport' content='width=device-width, initial-scale=1, maximum-scale=1'>
  12     <title>
  12       Placement Planning and Disruption Meetings
  12     </title>
  13     <link href='css/css.php' rel='stylesheet' type='text/css' id="main_style"/>
  14     <link rel='shortcut icon' href='images/favicon.ico' type='image/x-icon'/>
  16     <link rel="apple-touch-icon" href="images/apple-touch-icon-57x57-precomposed.png" />
  17     <link rel="apple-touch-icon" sizes="72x72" href="images/apple-touch-icon-72x72-precomposed.png" />
  18     <link rel="apple-touch-icon" sizes="114x114" href="images/apple-touch-icon-114x114-precomposed.png" />
  20     <meta name="application-name" content="Placement Planning and Disruption Meetings" />
  21     <meta name="msapplication-TileColor" content="#301880" />
  22     <meta name="msapplication-square70x70logo" content="images/smalltile.png" />
  23     <meta name="msapplication-square150x150logo" content="images/mediumtile.png" />
  24     <meta name="msapplication-wide310x150logo" content="images/widetile.png" />
  25     <meta name="msapplication-square310x310logo" content="images/largetile.png" />
  29     <link href='normal.css' id='switch_style' rel='stylesheet' type='text/css'>
  32     <link rel='stylesheet' media='(max-width: 1100px)' href='css/colours_mobile.css' />
  36     <link href='css/print.css' rel='stylesheet' type='text/css' media='print'>
  37     <link href='css/print_colours.css' rel='stylesheet' type='text/css' media='print'>
  39     <script src="scripts/print.js">
  39     </script>
  40     <script src="scripts/jquery-1.6.4.min.js">
  40     </script>
  41     <script src="scripts/jquery-dateFormat.min.js">
  41     </script>
  42     <script src="scripts/js.cookie.js">
  42     </script>
  43     <script type="text/javascript" src="scripts/highlight.js">
  43     </script>
  44     <script src='https://www.google.com/recaptcha/api.js'>
  44     </script>
  45     <script type="text/javascript" src="scripts/jquery.js">
  45     </script>
  46     <script type="text/javascript" src="scripts/pageOrganizer.js">
  46     </script>
  47     <script>
  54     </script>
 116     <style>
 117       #new_print {
 118         display:block;
 119       }
 120       #old_print {
 121         display:none;
 122       }
 123     </style>
 131     <style>
 132       ol {
 133         counter-reset: item;
 134         z-index:-1;
 135       }
 136       ol li.sub_list {
 137         display: block;
 138         position: relative;
 139       }
 140       ol li.sub_list:before {
 141         content: counters(item, ".")".";
 142         counter-increment: item;
 143         position: absolute;
 144         margin-right: 100%;
 145         right: 3px;
 146       }
 147       ol li.remove_bullet:before {
 148 next issueprevious issueP908 [WCAG21 1.3.1 (A)] Do not insert content using CSS:
Content inserted using CSS may not appear when CSS is turned off, or the user is using their own accessible style sheet. See WCAG 2.1 Failure F87.             content:"\ \ \ ";
 149         display:none;
 150       }
 151     </style>
 155     <style>
 156       .remove_bullet {
 157         list-style:none;
 158       }
 159     </style>
 183   </head>
 184   <body onLoad="if (document.getElementById('zoom_searchbox'))
       {document.getElementById('zoom_searchbox').focus();}">
 186     <div id="skip">
 186       <a href="#main_content" class="section_links">
 186         Skip navigation to sections
 186       </a>
 186     </div>
 187     <div id="cookie_bar">
 187       We use cookies to track usage and preferences.
 187       <a href="https://www.trixonline.co.uk/privacy-policy#cookies">
 187         View our Cookie Policy
 187       </a>
 187       <div id="cookie_agree">
 187         I Accept
 187       </div>
 187     </div>
 190     <div id="head_bar">
 192       <header>
 193         <div id="grey_bar">
 194           <div id="logo_holder">
 195             <img src="images/client_logo.png" height="85" alt="Bexley Logo"/>
 196           </div>
 196         </div>
 198         <div id="title">
 199           <h1>
 199             Bexley
 199             <span id="h1_sub">
 199               Children's Services Procedures Manual
 199             </span>
 199           </h1>
 201         </div>
 205         <div id="access_holder">
 205           <div id="access_text_hold" onclick="location.href='accessibility.html';">
 205             <a href="accessibility.html">
 205               Accessibility
 205             </a>
 205           </div>
 205         </div>
 206       </header>
 207     </div>
 208     <nav>
 210       <div id="sticky_navigation_wrapper">
 211         <div id="sticky_navigation">
 212           <div id="demo_container">
 213             <div id="menu_toggle">
 213               <img src="images/menu_white.png" id="drop_menu_button" height="20" alt="Menu toggle for
                   Mobile"/>
 214             </div>
 216             <div id="menu_items">
 217               <ul>
 218                 <li>
 218                   <a href="index.html">
 218                     Home
 218                   </a>
 218                 </li>
 219                 <li>
 219                   <a href="contents.html">
 219                     Contents
 219                   </a>
 219                 </li>
 220                 <li class="dropdownmenu" id="doubletap1">
 221 next issueprevious issueE958 [WCAG21 4.1.2 (A)] The 'aria-haspopup' attribute is not allowed in this context:
The ARIA specification only allows certain 'aria-...' attributes to be used with certain roles. See ARIA 1.2.                       <a class="toplink" href="menu.html" aria-haspopup="true">
 221                     Resources
 221                     <b>
 221                       &#9662;
 221                     </b>
 221                   </a>
 222                   <ul id="port_drop1" aria-label="submenu">
 223                     <li>
 223                       <a href="local_resources.html" tabindex="-1">
 223                         Policy Update
 223                       </a>
 223                     </li>
 224                     <li>
 224                       <a href="http://trixresources.proceduresonline.com/nat_key/index.htm" target="_blank"
                           tabindex="-1">
 224                         Glossary
 224                       </a>
 224                     </li>
 225                     <li>
 225                       <a href="http://trixresources.proceduresonline.com/nat_cont/index.htm"
                           target="_blank" tabindex="-1">
 225                         Contacts
 225                       </a>
 225                     </li>
 226                   </ul>
 227                 </li>
 228                 <li>
 228                   <a href="using_this_manual.html">
 228                     Using this Manual
 228                   </a>
 228                 </li>
 229                 <li>
 229                   <a href="http://www.londoncp.co.uk/" target="_blank" rel="noopener">
 229                     London Child Protection Procedures
 229                   </a>
 229                 </li>
 231               </ul>
 232             </div>
 236             <div id="search">
 236               <div id="search_contents">
 237 next issueprevious issueE910 [WCAG21 1.4.4 (AA)] Use relative rather than absolute units:
Using relative units helps the page to be rendered correctly at different resolutions and allows people with sight difficulties to 'zoom in' to pages to read them. See Understanding 1.4.4.                     <form method="get" action="search_site.php" style="font-size:10px;">
 239                   <div id="input_holder">
 241 next issueprevious issueW889 [WCAG21 4.1.2 (A)] Avoid using accessible names created from fallback attributes:
An accessible name generated from 'title', 'placeholder' or default values for <input> buttons, typically yields a low quality accessible name. Instead use the recommended way of setting the accessible name for this element. See Avoid Fallback, and Accessible Name Computation.                         <input type="text" name="zoom_query" placeholder="Search Manual" spellcheck="true" title="search"
                         class="search_bar">
 242                   </div>
 243                   <div id="mag_holder">
 244                     <input class="imagelink" type="image" src="images/mag_white.png" id="mag_glass"
                         height="25" alt="Search" title="Search">
 246                   </div>
 246                 </form>
 246               </div>
 246             </div>
 248           </div>
 251         </div>
 253       </div>
 258     </nav>
 259     <div id="main_content" tabindex="-1">
 260       <main>
 263         <div id="print_watermark">
 263           This document is only valid 72 hours after printing
 263           <script>
 263           </script>
 263           . For the latest version please visit
 263           <noscript>
 263             the online manual.
 263           </noscript>
 263           <script>
 263           </script>
 263         </div>
 265         <div id="chapter_title">
 268           <div id="print_holder">
 272             <div id="new_print">
 272               <a onClick="window.print();" tabindex="0" class="imagelink" href="#">
 272                 <img id="print_img" src="images/print_black.png" height="30" alt="Click here to print"/>
 272               </a>
 272             </div>
 276             <div id="old_print">
 276               <form id="printMe" name="printMe">
 276                 <input class="imagelink" name="printMe" type="image" onclick="printSpecial()"
                     id="print_img_ie" src="images/print_black.png" height="30" width="33" alt="Print this
                     page" title="Print Button">
 276               </form>
 276             </div>
 279           </div>
 282           <h2>
 282             Placement Planning and Disruption Meetings
 282           </h2>
 284         </div>
 287         <div id="scope_box">
 288           <h3>
 288             AMENDMENT
 288           </h3>
 289           <p>
 289             This chapter was reviewed and amended by Bexley in April 2017 to confirm that a Disruption Meeting
                 should be convened if the placement is at risk of breaking down. The meeting should be chaired by
                 the fostering manager if the child is placed in a Bexley placement, or otherwise the IRO or
                 Placement Manager.
 289           </p>
 290         </div>
 291         <div id="sections">
 293           <h3 id="sections_list">
 293             Contents
 293           </h3>
 294           <ol>
 295             <li>
 295               <a href="#placemeet">
 295                 Placement Planning Meetings
 295               </a>
 295             </li>
 296             <li>
 296               <a href="#disruptmeet">
 296                 Disruption Meetings
 296               </a>
 296             </li>
 297           </ol>
 298           <h3 id="placemeet">
 298             1. Placement Planning Meetings
 298           </h3>
 299           <p>
 299             Placement Planning meetings should be convened as part of the process of identifying and placing a
                 child - as set out in the
 299             <a href="p_place_fost_care.html">
 299               Placements in Foster Care Procedure
 299             </a>
 299             and the
 299             <a href="p_place_resi_care.html">
 299               Placements in Residential Care Procedure
 299             </a>
 299             . The first Placement Planning Meeting in relation to a placement should be held before the
                 placement. Where this is not possible because of the urgency of the situation, it should be held
                 in order that the Placement Plan is prepared within 5 working days of the start of the placement.
 299           </p>
 300           <p>
 300             Further Placement Planning Meetings should be held at intervals agreed with the manager of the
                 residential home or the foster carers and their supervising social worker - or as required for
                 example where there are issues to be resolved in relation to the day to day arrangements for the
                 placement.
 300           </p>
 301           <p>
 301             The social worker and home manager/foster carers supervising social worker will agree the best
                 format and venue for the meeting and who will chair the meeting.
 301           </p>
 302           <p>
 302             The people listed below should contribute to the meetings:
 302           </p>
 303           <ol>
 304             <li>
 304               The child's social worker and/or other professional associated with the child e.g. Personal
                   Adviser or advocate;
 304             </li>
 305             <li>
 305               The child;
 305             </li>
 306             <li>
 306               The child's parents;
 306             </li>
 307             <li>
 307               For children in residential care, the child's link worker/keyworker and, where appropriate the
                   home manager;
 307             </li>
 308             <li>
 308               For children in foster care, the foster carers and their supervising social worker.
 308             </li>
 309           </ol>
 310           Before any meeting, the chairperson should obtain or be updated on the following, if available:
 311           <ul>
 312             <li>
 312               The child's Placement Plan (recorded on the Placement Information Record on ICS);
 312             </li>
 313             <li>
 313               Any work which has been undertaken in supporting the child's placement;
 313             </li>
 314             <li>
 314               If relevant: the child's Care Plan, Personal Education Plan and Pathway Plan.
 314             </li>
 315           </ul>
 316           <p>
 316             Where the proposed placement has the effect of disrupting the arrangements made for the child's
                 education and training - see
 316             <a href="p_educ_lac.html">
 316               Education of Looked After and Previously Looked After Children Procedure
 316             </a>
 316             .
 316           </p>
 317           <p>
 317             Where the proposed placement is out of area, see
 317             <a href="p_out_area_place.html">
 317               Out of Area Placements Procedure
 317             </a>
 317             .
 317           </p>
 318           <p>
 318             The chairperson should also ensure that the child, parent(s) and others who have been asked to
                 contribute understand the purpose of the meeting, how it will be conducted and are given the
                 opportunity to put their views and suggestions.
 318           </p>
 319           <p>
 319             If there are concerns about the suitability of the placement, consideration should be given to the
                 following:
 319           </p>
 320           <ul>
 321             <li>
 321               Whether it is possible to sustain the placement until the next Looked After Review by, for
                   example, providing additional support to the placement;
 321             </li>
 322             <li>
 322               Bringing forward the date of the next Looked After Review;
 322             </li>
 323             <li>
 323               Ending the placement.
 323             </li>
 324           </ul>
 325           <h3 id="disruptmeet">
 325             2. Disruption Meetings
 325           </h3>
 326           <p>
 326             <a href="files/disruption_meeting_policy.docx" target="_blank" rel="noopener">
 326               Click here to view Bexley Disruption Meetings
 326             </a>
 326             .
 326           </p>
 327         </div>
 330       </main>
 331     </div>
 334     <footer>
 335       <div class="footer">
 336         <div>
 337           <p>
 337             <a href="privacypolicy.html">
 337               Privacy Policy
 337             </a>
 337             <br>
 338             <span style="font-size:small;">
 339               <span id='desktop_button' tabindex='0'>
 339                 Desktop
 339               </span>
 339               |
 339               <span id='mobile_button' tabindex='0'>
 339                 Mobile
 339               </span>
 339               |
 339               <span id='responsive_button' tabindex='0' style='text-decoration:underline'>
 339                 Responsive
 339               </span>
 339             </span>
 339           </p>
 341           <div id="trix_logo">
 342             <a href="https://www.trixonline.co.uk/" target="_blank" class="imagelink">
 342               <img src="images/trixlogo.png" height="40" alt="Tri.x Logo links to Tri.x homepage"/>
 342             </a>
 343           </div>
 344         </div>
 345       </div>
 347     </footer>
 348     <div id="desktoptest">
 348     </div>
 349     <script>
 476     </script>
 478     <script>
 487     </script>
 489     <script>
 536     </script>
 539     <script>
 541     </script>
 549     <script>
 588     </script>
 589     <script type="text/javascript">
 589     </script>
 591     <script>
 630     </script>
 634     <script type="text/javascript">
 646     </script>
 647   </body>
 648 </html>