Page reportSummary
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:
1 
W874 [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 P967 [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 W605 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 W605 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 Searching Children/Bedrooms | 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 W605 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 W605 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 W609 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>
39 </head>
40 <body onload="highlight();">
41 <div class="banner">
42 </div>
43 <div id="buttons">
43 <div id="menu">
44 <ul>
45 <li>
45 <a href="index.html">
45 Home
45 </a>
45 </li>
46 <li>
46 <a href="contents.html">
46 Contents
46 </a>
46 </li>
47 <li>
47 <a href="local_resources.html">
47 Local Resources
47 </a>
47 </li>
48 </ul>
49 </div>
49 <div id="search">
50 <form action="search/search.html" id="cse-search-box" style="margin: 0px;">
51 I899 [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">
52 <tr>
53 <td>
53 E885 [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;" />
53 </td>
54 <td>
54 <input type="submit" value="Go"/>
54 </td>
55 </tr>
56 </table>
57 </form>
57 </div>
57 </div>
58 <div id="topper">
58 </div>
60 <div id="printReady">
61 <div id="container">
62 <div id="content_frame_overflow">
62 <div class="content_text">
63 <h1 class="h1">
63 Searching Children/Bedrooms
63 </h1>
64 <div class="scope_box" style="padding-bottom: 0px; padding-top: 15px;">
65 <h2 class="h3">
65 REGULATIONS AND STANDARDS
65 </h2>
66 <p>
66 <a
href="http://qualitystandards.proceduresonline.com/homes/p_quality_standards.html#qual_purpose
" target="_blank">
66 The Quality and Purpose of Care Standard
66 </a>
66 <br />
67 Regulation 6
67 </p>
68 <h3 class="h3">
68 RELATED CHAPTERS
68 </h3>
69 <p>
69 <a href="p_phys_inter.html">
69 Use of Restraint and Physical Intervention Procedure
69 </a>
69 </p>
70 <p>
70 <a href="p_police.html">
70 Offending and Anti-Social Behaviour – Guidance on when to Involve the Police
70 </a>
70 </p>
71 </div>
72 <h2 class="h2_underlined">
72 <br />
73 Contents
73 </h2>
74 <ol>
75 <li>
75 <a href="#searching">
75 Searching
75 </a>
75 </li>
76 <li>
76 <a href="#confiscating">
76 Confiscating Items
76 </a>
76 </li>
77 <li>
77 <a href="#review">
77 Notifications and Management Review
77 </a>
77 </li>
78 <li>
78 <a href="#recording">
78 Recording
78 </a>
78 </li>
79 </ol>
80 <h2 class="h2_underlined">
80 <br />
81 1.
81 <a name="searching" id="searching">
81 </a>
81 Searching
81 </h2>
82 <p>
82 Bedrooms should not be generally entered without the child's permission. Where it may be
necessary to conduct a room search, this should take place after the child has been informed or
permission given.
82 </p>
83 It may be appropriate to conduct an immediate search of a child or a child's belongings, including
the searching of a child's bedroom, if there is reasonable cause to believe that the child has
concealed weapons, illegal drugs other items, which may place the child or others at risk of
injury; this may include mobile phones if they are being used in a way that places the child or
others at risk of Significant harm e.g. as a form of Cyberbullying or places them or others at
risk of exploitation.
84 <h3 class="h3">
84 1.1 Searches with Co-operation
84 </h3>
85 <p>
85 If there is a suspicion that such items are concealed, staff should try to obtain them with the
child's co-operation.
85 </p>
86 <p>
86 If the child does not co-operate, or is unlikely to, it may be appropriate to conduct a search
of the child or his/her belongings/room.
86 </p>
87 <p>
87 Before conducting such a search, staff should consult their own supervisor/manager and the
child's social worker. Two staff should be present during the search, one of which should be the
same gender as the child, and the child should be present.
87 </p>
88 <p>
88 The power to search without consent enables a 'personal search', involving removal of outer
garments and searching of pockets, but not an intimate search going further than that; which
only a person with more extensive powers e.g. a Police Officer, can do.
88 </p>
89 <p>
89 When conducting searches, reasonable precautions must be taken to protect against possible sharp
or dangerous objects that may be concealed.
89 </p>
90 If weapons or any dangerous or offensive items are found, they must be seized and passed to the
Manager, see
90 <a href="#confiscating">
90 Section 2, Confiscating Items
90 </a>
90 .
91 <h3 class="h3">
91 1.2 Searches without Co-operation or without the knowledge of the child
91 </h3>
92 <p>
92 If the child does not co-operate, or is likely not to, a search may be undertaken without the
child's co-operation or knowledge.
92 </p>
93 <p>
93 Unless there are exceptional circumstances, the Manager and child's social worker must be
consulted and come to a decision about the actions that may be taken. It may be appropriate to
consult relevant Line Managers.
93 </p>
94 <p>
94 When coming to a decision on the actions that will be taken, the managers/social worker(s) must
take account of the following:
94 </p>
95 <ul>
96 <li>
96 Two staff must be present, one of whom must be the same gender as the child, and the child if
possible;
96 </li>
97 <li>
97 If there is a risk that the searching of the child may escalate the situation e.g. lead to
violence or injury to the child, staff or others, staff should contain the situation as best
they can and consult the Home's Manager or a supervisor before proceeding; and consideration
given to asking for Police assistance;
97 </li>
98 <li>
98 The power to search without consent enables a 'personal search', involving removal of outer
garments and searching of pockets, but not an intimate search going further than that; which
only a person with more extensive powers e.g. a Police Officer, can do;
98 </li>
99 <li>
99 When conducting searches, reasonable precautions must be taken to protect against possible
sharp or dangerous objects that may be concealed;
99 </li>
100 <li>
100 If weapons or any dangerous or offensive items are found, they must be seized and passed to
the Manager, see
100 <a href="#confiscating">
100 Section 2, Confiscating Items
100 </a>
100 .
100 <br />
101 <br />
102 </li>
103 </ul>
104 <table title="Exceptional Circumstances" width="95%" border="1" cellspacing="0" cellpadding="5">
105 <tr class="table_row_lightblue">
106 <td class="table_row_even">
106 <p class="bold">
106 Exceptional Circumstances
106 </p>
107 <p>
107 If there is an immediate risk of Injury or Damage to Property, staff may take what actions
they deem to be appropriate to protect themselves or others. As a Last Resort, this can
include the use of
107 <a
href="http://trixresources.proceduresonline.com/nat_key/keywords/phys_intervention.html
" target="_blank">
107 Physical Intervention
107 </a>
107 in order to search a child, and the entering of a child's bedroom without their knowledge.
However, staff must only take such actions if it is safe to do so and their actions comply
with the provisions/procedures set out in
107 <a href="p_phys_inter.html">
107 Use of Restraint and Physical Intervention Procedure
107 </a>
107 . If there is a risk that an offence may be committed, the Police must be called (see
107 <a href="p_police.html">
107 Offending and Anti-Social Behaviour – Guidance on when to Involve the Police
107 </a>
107 ).
107 </p>
107 </td>
108 </tr>
109 </table>
110 <h2 class="h2_underlined">
110 <br />
110 2.
110 <a name="confiscating" id="confiscating">
110 </a>
110 Confiscating Items
110 </h2>
111 <p>
111 Any items that are seized or removed by staff passed to the Home's Manager, even if they are
owned by children. The Home's Manager should record the matter and, if items are confiscated,
they must be kept securely until the child leaves or the Manager considers that they should be
returned to the child e.g. where a child demonstrates s/he is able to use a mobile phone safely.
The Manager must provide the child with a receipt for the confiscated item(s).
111 </p>
112 <p>
112 If the items are thought to be a weapon, they should be passed to the Police. Where staff find
controlled drugs, the Home's Manager should consider passing them to the Police; other
substances not believed to be controlled drugs e.g. so called 'legal highs', should be
confiscated, passed to the Home's Manager, recorded and destroyed. If items are thought to be
stolen they must be delivered to the police unless there is a good reason not to do so (see
below) – in which case the stolen item should be returned to the owner. These stolen items may
be retained or disposed of if returning them to their owner is not practicable.
112 </p>
113 <p>
113 Re passing weapons or other items to the Police: Home's managers should have a good reason not
to pass items to the Police and should take account of the following:
113 </p>
114 <ul>
115 <li>
115 Where the manager is unsure as to the legal status of a substance and has reason to believe it
may be a controlled drug they should treat it as such;
115 </li>
116 <li>
116 With regard to stolen items, it would not be reasonable or desirable to involve the police in
dealing with low value items. However, the manager may judge it appropriate to contact the
police if the items are valuable (iPods/laptops) or illegal (alcohol/fireworks);
116 </li>
117 <li>
117 Disposing of alcohol does not include returning it to the child. It should be poured down the
sink.
117 </li>
118 </ul>
119 <h2 class="h2_underlined">
119 <br />
120 3.
120 <a name="review" id="review">
120 </a>
120 Notifications and Management Review
120 </h2>
121 <p>
121 There are different notifications procedures for searches concluded with and without
children's co-operation.
121 </p>
122 <h3 class="h3">
122 3.1 With Children's Co-operation
122 </h3>
123 <p>
123 Searches undertaken with the child's co-operation, where no force is used, must be notified to
the Manager at the first opportunity; the manager will decide whether to inform the relevant
social worker.
123 </p>
124 <h3 class="h3">
124 3.2 Without Children's Co-operation
124 </h3>
125 <p>
125 Searches conducted without the child's co-operation, where a level of force has been used, is an
Incident and must be notified to the Manager and relevant within 24 hours or as soon as
practicable thereafter.
125 </p>
126 <p>
126 The social worker should decide whether to inform the child's parent(s) and, if so, who should
do so.
126 </p>
127 <p>
127 Depending on the seriousness of the Incident, other people/agencies may have to be notified, see
127 <a href="p_notif_events.html">
127 Notification of Serious Events Procedure
127 </a>
127 .
127 </p>
128 <h2 class="h2_underlined">
128 <br />
129 4.
129 <a name="recording" id="recording">
129 </a>
129 Recording
129 </h2>
130 <p>
130 Searches should be noted in the home's Daily Log, relevant child's Daily Record, with details as
listed below:
130 </p>
131 <ol type="a">
132 <li>
132 The time and date of the search;
132 </li>
133 <li>
133 The reason or suspicions which led to the need to conduct the search;
133 </li>
134 <li>
134 Who conducted the search and whether the child or others were present;
134 </li>
135 <li>
135 Whether the child cooperated;
135 </li>
136 <li>
136 What was found, and whether items found were retained/confiscated;
136 </li>
137 <li>
137 If items were retained/confiscated, where they were stored.
138 </li>
139 </ol>
141 <p>
141 <br />
142 <br />
143 </p>
144 </div>
145 </div>
146 </div>
147 </div>
148 <div id="footer-wrap">
149 <div id="footer-container">
149 <div id="footer">
150 I899 [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">
151 <tr>
152 <td width="60%" align="left" style="padding-top: 0px;">
152 <a href="http://www.trixonline.co.uk/" target="_blank">
152 <img src="images/trix_logo.gif" width="57" height="22" alt="tri.x logo" border="0"/>
152 </a>
152
152 <span class="darkdivider">
152 |
152 </span>
152 Copyright ©
152 <a href="http://www.trixonline.co.uk/" target="_blank">
152 tri.x
152 </a>
152
152 <span class="darkdivider">
152 |
152 </span>
152
152 </td>
153 <td width="40%" align="right" valign="top" style="padding-top: 0px;">
155 <div class="footer_box">
155 <a href="#">
155 visibility:
155 </a>
155
155 <a href="#" onclick="setActiveStyleSheet('small'); return false;">
155 <img src="images/icons/small_a.gif" alt="View this website with small text" border="0" />
155 </a>
155 <a href="#" onclick="setActiveStyleSheet('medium'); return false;">
155 <img src="images/icons/medium_a.gif" border="0" alt="View this website with medium
text" />
155 </a>
155 <a href="#" onclick="setActiveStyleSheet('large'); return false;">
155 <img src="images/icons/large_a.gif" border="0" alt="View this website with large text" />
155 </a>
155 <a href="#" onclick="setActiveStyleSheet('hivis'); return false;">
155 <img src="images/icons/hivis.gif" border="0" alt="View this website with high
visibility" />
155 </a>
155
155 <span class="darkdivider">
155 |
155 </span>
155
155 </div>
156 <div class="footer_box">
156 <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
156 <img src="images/icons/favourite.gif" alt="Add this page to your favourites" width="18"
height="18" border="0" />
156 </a>
156 <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
156 favourites
156 </a>
156
156 <span class="darkdivider">
156 |
156 </span>
156
156 </div>
157 <div class="footer_box">
157 W884 [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"/>
159 <a href="#" onclick="printSpecial()">
159 print
159 </a>
159
159 <span class="darkdivider">
159 |
159 </span>
159
159 </div>
160 </td>
161 </tr>
162 </table>
163 </div>
163 </div>
164 </div>
165 </body>
166 </html>