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       Electronic Recording of Meetings and Conversations
  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="Electronic Recording of Meetings and Conversations" />
  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             Electronic Recording of Meetings and Conversations
 282           </h2>
 284         </div>
 287         <div id="scope_box">
 288           <h3>
 288             SCOPE OF THIS CHAPTER
 288           </h3>
 289           <p>
 289             This chapter deals with recording of meetings/conversations by individual service-users, in their
                 capacity as private individuals. Note that the employees of the local authority, acting in their
                 professional capacity, are subject to different legislative requirements, e.g. under the Data
                 Protection Act 2018.
 289           </p>
 290           <p>
 290             This is a developing area, and legal advice
 290             <span class="bold">
 290               must
 290             </span>
 290             be sought as necessary.
 290           </p>
 291           <h3>
 291             AMENDMENT
 291           </h3>
 292           <p>
 292             This guidance was reviewed and updated in October 2018 following the introduction of the General
                 Data Protection Regulations (GDPR) and Data Protection Act 2018.
 292           </p>
 293         </div>
 294         <div id="sections">
 295           <h3>
 295             Contents
 295           </h3>
 296           <ol>
 297             <li>
 297               <a href="#intro">
 297                 Introduction
 297               </a>
 297             </li>
 298             <li>
 298               <a href="#consent">
 298                 Consent
 298               </a>
 298             </li>
 299             <li>
 299               <a href="#recorded">
 299                 Use of Recorded Material
 299               </a>
 299             </li>
 300             <li>
 300               <a href="#practice">
 300                 Good Practice
 300               </a>
 300             </li>
 301             <li>
 301               <a href="#further_info">
 301                 Further Information
 301               </a>
 301             </li>
 302           </ol>
 303           <h3 id="intro">
 303             1. Introduction
 303           </h3>
 304           <p>
 304             Advances in technology (e.g. smartphones) have made the recording of meetings and other
                 conversations with professionals much more easily available to individual service-users. This may
                 be simply because they wish to have a verbatim record of the conversation/meeting to refer back
                 to, or because they have difficulties in following or recalling conversations. They may, however,
                 seek to use the recording for other purposes such as admission into evidence in family court
                 proceedings, or even for wider broadcast.
 304           </p>
 305           <p>
 305             This may arise in the context of private law or public law proceedings, and may involve recording
                 of conversations between parents, between parents and social workers, foster carers, etc, or
                 recording of conversations between parents and children. One parent may be trying to use it, for
                 example, to justify their assertions regarding contact with the other parent.
 305           </p>
 306           <p>
 306             The recording may take place overtly or covertly.
 306           </p>
 307           <h3 id="consent">
 307             2. Consent
 307           </h3>
 308           <p>
 308             There are no specific legal restrictions on the recording of face-to-face conversations, whether
                 this is overt or covert. Thus, whilst good practice would suggest that advance consent should be
                 sought for any planned recording, a blanket ban on recording is unlikely to be lawful.
 308           </p>
 309           <p>
 309             This is not a clear-cut area, and legal advice
 309             <span class="bold">
 309               must
 309             </span>
 309             be sought as appropriate. Practitioners should be mindful that covert recording may be taking
                 place, and should endeavour to ensure that they do not make statements during 'private'
                 conversations which they would not be prepared to hear produced as evidence in court.
 309           </p>
 310           <p>
 310             Cafcass, in its
 310             <a href="files/cafcass_operating_frwork.pdf" target="_blank" rel="noopener">
 310               Operating Framework
 310             </a>
 310             , states:
 310           </p>
 311           <p>
 311             <span class="italic">
 311               'We should have nothing to fear from covert recording. Our attitude should be, &ldquo;I am doing
                   my job and I have nothing to hide. I can explain why I said what I said or why I did what I
                   did.&rdquo; This is within the spirit of transparency in the family courts. We should always be
                   transparent in our work, to meet contemporary expectations, including being able to defend
                   whatever we say or write in a court under cross-examination, because we are working to a
                   professional standard on behalf of a child. In this sense, we should expect that everything we
                   say or write could become public knowledge'.
 311             </span>
 311           </p>
 312           <p>
 312             The fact that the social worker has not given their consent to the conversation being recorded
                 does not, of itself, render the recording unlawful or inadmissible.
 312           </p>
 313           <p>
 313             If the scale or style of recording is excessive, oppressive or disproportionate, then this may
                 cross a threshold. For example, a parent recording their questioning of the child in a manner
                 which is oppressive may in fact be evidence of possible emotional abuse of the child by that
                 parent. Persistent recording of a social worker in such a way as to amount to intimidation may
                 constitute harassment, and it may be possible for the social worker to seek legal redress such as
                 a non-molestation order.
 313           </p>
 314           <h3 id="recorded">
 314             3. Use of Recorded Material
 314           </h3>
 315           <p>
 315             Whilst the recording itself may well be legitimate, there may be restrictions on its use.
 315           </p>
 316           <p>
 316             If a party seeks to admit such material into court proceedings, then it is at the discretion of
                 the court whether to allow this or not. Such evidence will only be admitted if it is relevant to
                 the issues in the case and not, for example, in furtherance of a personal grievance by a parent
                 against a social worker.
 316           </p>
 317           <p>
 317             The Data Protection Act 2018 does not cover processing of personal data by an individual in the
                 course of a purely personal or household activity. The scope of this in the context of recording
                 is not clear. However, Jackson J in M v F (Covert Recording of Children) [2016] EWFC 29 expressed
                 the view that a similar exemption contained in the previous Data Protection Act was intended to
                 protect normal domestic use, and would not cover the covert recording of individuals, and
                 particularly children, for the purpose of evidence-gathering in family proceedings.
 317           </p>
 318           Wider distribution, for example, making such recordings available via the internet, would be in
               contravention of the General Data Protection Regulations and the Data Protection Act 2018. Such
               recordings are likely to contain information (including possible 'sensitive personal
               information') relating to third parties, and the distribution of such information so as to enable
               those third parties to be identified would be in breach of data protection provisions. If the issues
               in question are the subject of ongoing court proceedings, then there is also a possible contempt of
               court.
 319           <h3 id="practice">
 319             4. Good Practice
 319           </h3>
 320           <p>
 320             A clear process should be in place for dealing with requests to record meetings/conversations or
                 for situations where it seems likely that covert recording is taking place or is likely to take
                 place. It is preferable for this to be addressed with all service-users at an early stage, rather
                 than waiting until the situation arises at the start of a meeting. The process should set out how
                 the request should be made, who will consider the request and how far in advance of the meeting
                 the request should be made. It should also make clear to the service-user the limitations upon the
                 use of the recorded material, e.g. that it can only be used in relation to the ongoing family
                 proceedings and cannot be broadcast more widely. The service-user will preferably be invited to
                 sign to indicate their agreement to and understanding of these limitations.
 320           </p>
 321           <p>
 321             It is important that each such request is considered on its own merits. If the decision-maker is
                 minded to refuse the request, then legal advice should be sought.
 321           </p>
 322           <h3 id="further_info">
 322             5. Further Information
 322           </h3>
 323           <p>
 323             Please see
 323             <a
                 href="http://www.transparencyproject.org.uk/press/wp-content/uploads/2016/05/Whymightparentswantto
                 recordmeetingsv2jan16.pdf" target="_blank" rel="noopener">
 323               Parents recording social workers - A guidance note for parents and professionals (The
                   Transparency Project, 2015)
 323             </a>
 323             .
 323           </p>
 324         </div>
 328       </main>
 329     </div>
 332     <footer>
 333       <div class="footer">
 334         <div>
 335           <p>
 335             <a href="privacypolicy.html">
 335               Privacy Policy
 335             </a>
 335             <br>
 336             <span style="font-size:small;">
 337               <span id='desktop_button' tabindex='0'>
 337                 Desktop
 337               </span>
 337               |
 337               <span id='mobile_button' tabindex='0'>
 337                 Mobile
 337               </span>
 337               |
 337               <span id='responsive_button' tabindex='0' style='text-decoration:underline'>
 337                 Responsive
 337               </span>
 337             </span>
 337           </p>
 339           <div id="trix_logo">
 340             <a href="https://www.trixonline.co.uk/" target="_blank" class="imagelink">
 340               <img src="images/trixlogo.png" height="40" alt="Tri.x Logo links to Tri.x homepage"/>
 340             </a>
 341           </div>
 342         </div>
 343       </div>
 345     </footer>
 346     <div id="desktoptest">
 346     </div>
 347     <script>
 474     </script>
 476     <script>
 485     </script>
 487     <script>
 534     </script>
 537     <script>
 539     </script>
 547     <script>
 586     </script>
 587     <script type="text/javascript">
 587     </script>
 589     <script>
 628     </script>
 632     <script type="text/javascript">
 644     </script>
 645   </body>
 646 </html>