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 Social Worker Visits | 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 Social Worker Visits
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#care_plannin
g" target="_blank">
66 The Care Planning Standard
66 </a>
66 </p>
67 <p>
67 <a
href="http://qualitystandards.proceduresonline.com/homes/p_quality_standards.html#ch_views
" target="_blank">
67 The Children's Views, Wishes and Feelings Standard
67 </a>
67 </p>
68 </div>
69 <h2 class="h2_underlined">
69 <br />
70 Contents
70 </h2>
71 <ol>
72 <li>
72 <a href="#normal">
72 Normal Frequency
72 </a>
72 </li>
73 <li>
73 <a href="#who_should">
73 Who Should Be Seen
73 </a>
73 </li>
74 <li>
74 <a href="#purpose">
74 Purpose
74 </a>
74 </li>
75 <li>
75 <a href="#record">
75 Recording
75 </a>
75 </li>
76 </ol>
77 <h2 class="h2_underlined">
77 <br />
78 <a id="normal" name="normal">
78 </a>
78 1. Normal Frequency
78 </h2>
79 <p>
79 Social workers have a statutory obligation to visit child at the following intervals, subject to
the conditions below:
79 </p>
80 <ul>
81 <li>
81 Within one week of the placement;
81 </li>
82 <li>
82 Then at intervals of no more than six weeks during the first year of the placement;
82 </li>
83 <li>
83 In subsequent years, the child should be visited every six weeks (if the placement is intended
to last until the child is 18).
83 </li>
84 </ul>
85 <p>
85 This applies to all placements, even where a child has moved from one placement to another.
These are minimum requirements and may take place more frequently or in line with the child's
Care Plan. The social worker should endeavour to visit whenever reasonably requested to do so by
the child. Visits during the first weeks of placement are particularly important to ensure
arrangements are in place and to develop the relationship between the child and the social
worker.
85 </p>
86 <p>
86 Some visits should be unannounced.
86 </p>
87 <h2 class="h2_underlined">
87 <br />
88 2.
88 <a id="who_should" name="who_should">
88 </a>
88 Who Should Be Seen
88 </h2>
89 <p>
89 Wherever possible, the child must be seen in private and alone (unless the child of sufficient
age and maturity and refuses). If this is not possible, a further visit must be made at
short notice in order that the child can be seen alone and observed with the staff.
89 </p>
90 <p>
90 The social worker should also meet the Manager of the home and staff, on occasions.
90 </p>
91 <p>
91 The social worker should be aware of who else lives in the home and they should know about
changes in structure and composition as well as the relationships within the home.
91 </p>
92 <p>
92 For children who are not able to verbally communicate their views, the social worker should
ensure that observations of the child are made in the home and also in other settings, for
example, school.
92 </p>
93 <p>
93 Issues raised by staff can be discussed when a child is not present for example when they are at
school.
93 </p>
94 <p>
94 Social workers should provide feedback to staff regarding their visit.
94 </p>
95 <h2 class="h2_underlined">
95 <br />
96 3.
96 <a id="purpose" name="purpose">
96 </a>
96 Purpose
96 </h2>
97 <p>
97 The purpose of the visit is to ensure the placement continues to promote the child's welfare and
in particular:
97 </p>
98 <ol>
99 <li type="a">
99 To give the child the opportunity to express his or her wishes, feelings and views and offer
reassurance if the child feels isolated or vulnerable while away from family and friends;
99 </li>
100 <li type="a">
100 To advise, assist and befriend the child;
100 </li>
101 <li type="a">
101 To monitor the standard of care offered by the placement;
101 </li>
102 <li type="a">
102 To monitor how the contact arrangements are working;
102 </li>
103 <li type="a">
103 To provide support to the placement;
103 </li>
104 <li type="a">
104 To identify any areas where additional support is required;
104 </li>
105 <li type="a">
105 To evaluate whether the placement is helping to achieve the objectives and actions of the
105 <a href="http://trixresources.proceduresonline.com/nat_key/keywords/care_plan.html"
target="_blank">
105 Care Plan
105 </a>
105 .
105 </li>
106 </ol>
107 <p>
107 <a href="http://trixresources.proceduresonline.com/nat_key/keywords/place_plan_meeting.html"
target="_blank">
107 Placement Planning Meetings
107 </a>
107 can be undertaken during social workers visits.
107 </p>
108 <p>
108 See
108 <a href="p_place_plan.html">
108 Placement Planning Meetings Procedure
108 </a>
108 .
108 </p>
109 <h2 class="h2_underlined">
109 <br />
110 4.
110 <a id="record" name="record">
110 </a>
110 Recording
110 </h2>
111 <p>
111 Home's staff should record visits in the Daily Log and on children's Daily Records. The social
worker should discuss with the child, subject to the age and understanding what information
should be shared with who and why.
111 </p>
112 <p>
112 A written report on each visit must be made by the social worker and kept in the child's file
stating clearly:
112 </p>
113 <ol>
114 <li type="a">
114 Who was seen;
114 </li>
115 <li type="a">
115 Whether the child was seen and if not why not;
115 </li>
116 <li type="a">
116 Whether the child was seen alone;
116 </li>
117 <li type="a">
117 Any comments made by the child or the staff/parents;
117 </li>
118 <li type="a">
118 Any developments or progress;
118 </li>
119 <li type="a">
119 Any matters of concern or difficulties.
119 </li>
120 </ol>
121 <p>
121 <br />
122 <br />
123 </p>
124 </div>
125 </div>
126 </div>
127 </div>
128 <div id="footer-wrap">
129 <div id="footer-container">
129 <div id="footer">
130 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">
131 <tr>
132 <td width="60%" align="left" style="padding-top: 0px;">
132 <a href="http://www.trixonline.co.uk/" target="_blank">
132 <img src="images/trix_logo.gif" width="57" height="22" alt="tri.x logo" border="0"/>
132 </a>
132
132 <span class="darkdivider">
132 |
132 </span>
132 Copyright ©
132 <a href="http://www.trixonline.co.uk/" target="_blank">
132 tri.x
132 </a>
132
132 <span class="darkdivider">
132 |
132 </span>
132
132 </td>
133 <td width="40%" align="right" valign="top" style="padding-top: 0px;">
135 <div class="footer_box">
135 <a href="#">
135 visibility:
135 </a>
135
135 <a href="#" onclick="setActiveStyleSheet('small'); return false;">
135 <img src="images/icons/small_a.gif" alt="View this website with small text" border="0" />
135 </a>
135 <a href="#" onclick="setActiveStyleSheet('medium'); return false;">
135 <img src="images/icons/medium_a.gif" border="0" alt="View this website with medium
text" />
135 </a>
135 <a href="#" onclick="setActiveStyleSheet('large'); return false;">
135 <img src="images/icons/large_a.gif" border="0" alt="View this website with large text" />
135 </a>
135 <a href="#" onclick="setActiveStyleSheet('hivis'); return false;">
135 <img src="images/icons/hivis.gif" border="0" alt="View this website with high
visibility" />
135 </a>
135
135 <span class="darkdivider">
135 |
135 </span>
135
135 </div>
136 <div class="footer_box">
136 <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
136 <img src="images/icons/favourite.gif" alt="Add this page to your favourites" width="18"
height="18" border="0" />
136 </a>
136 <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
136 favourites
136 </a>
136
136 <span class="darkdivider">
136 |
136 </span>
136
136 </div>
137 <div class="footer_box">
137 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"/>
139 <a href="#" onclick="printSpecial()">
139 print
139 </a>
139
139 <span class="darkdivider">
139 |
139 </span>
139
139 </div>
140 </td>
141 </tr>
142 </table>
143 </div>
143 </div>
144 </div>
145 </body>
146 </html>