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 Access to Records | 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 Access to Records
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 <h3 class="h3">
67 RELATED CHAPTERS
67 </h3>
68 <p>
68 <a href="p_case_record.html">
68 Case Recording Procedure
68 </a>
68 </p>
69 <p>
69 <a href="p_care_plac.html">
69 Care and Placement Plans Guidance
69 </a>
69 </p>
70 <h3 class="h3">
70 RELEVANT GUIDANCE
70 </h3>
71 <p>
71 <a href="http://www.legislation.gov.uk/ukpga/2018/12/contents/enacted" target="_blank">
71 The Data Protection Act 2018
71 </a>
71 </p>
72 </div>
73 <h2 class="h2_underlined">
73 <br />
74 Contents
74 </h2>
75 <ol>
76 <li>
76 <a href="#rights">
76 Right of Access by the Data Subject
76 </a>
76 </li>
77 <li>
77 <a href="#exemptions">
77 Exemptions to the Right of Access
77 </a>
77 </li>
78 <li>
78 <a href="#child_gain">
78 Children Gaining Access to their Files/Records
78 </a>
78 </li>
79 <li>
79 <a href="#change_record">
79 Changing a Record
79 </a>
79 </li>
80 </ol>
81 <h2 class="h2_underlined">
81 <br />
82 1.
82 <a name="rights" id="rights">
82 </a>
82 Right of Access by the Data Subject
82 </h2>
83 <p>
83 The right of a
83 <a href="http://www.proceduresonline.com/resources/glossary-cs/" target="_blank">
83 Data Subject
83 </a>
83 to request access to personal information or records held on them by the home are set out in
data protection legislation (namely the General Data Protection Regulations (GDPR) and the Data
Protection Act 2018). Under this data protection legislation, those in respect of whom personal
information is held in any form have a right of access to the information, unless one of the
exemptions set out in
83 <a href="#exemptions">
83 Section 2, Exemptions to the Right of Access
83 </a>
83 applies.
83 </p>
84 <h2 class="h2_underlined">
84 <br />
85 2.
85 <a id="exemptions" name="exemptions">
85 </a>
85 Exemptions to the Right of Access
85 </h2>
86 <p>
86 The Data Protection Act 2018 (Schedule 3) contains exemptions to the rights of access set out in
Article 15 of the GDPR for health, social work, education and child abuse data. The data
subject's right of access to view their records is restricted in the following circumstances:
86 </p>
87 <ul>
88 <li>
88 Where the right of access would prejudice the carrying out of social work because access to
the information would be likely to cause serious harm to the physical or mental health of the
data subject or some other individual;
88 </li>
89 <li>
89 Where the records contain child abuse data; there is an exemption if access to the record
would not be in the best interests of the data subject. ("Child abuse data" is
defined in the Data Protection Act as personal data consisting of information as to whether
the data subject is or has been the subject of, or may be at risk of, child abuse. For this
purpose, "child abuse" includes physical injury (other than accidental injury) to,
and physical and emotional neglect, ill-treatment and sexual abuse of, an individual aged
under 18);
89 </li>
90 <li>
90 Where the person is incapable of managing their affairs;
90 </li>
91 <li>
91 Where complying with the right of access would mean disclosing information which was given by
the data subject in the expectation that it would not be disclosed or is information which the
data subject expressly indicated should not be disclosed;
91 </li>
92 </ul>
93 <p>
93 Access can also be refused if:
93 </p>
94 <ul>
95 <li>
95 Disclosing information to the data subject would involve disclosing information relating to a
third party who can be identified from the information. Unless (a) the other individual has
consented to the disclosure of the information to the data subject, or (b) it is reasonable to
disclose the information to the data subject without the consent of the other individual;
95 </li>
96 <li>
96 Where disclosure may prevent the detection or investigation of a crime or jeopardise public or
national security.
96 </li>
97 </ul>
98 <p>
98 Access requests can also be refused if they are 'manifestly unfounded or excessive', for example
if an identical or similar request has been received from the same person and already been
complied with.
98 </p>
99 <p>
99 These exemptions do not justify the total withholding of information but only those records /
parts of records covered by the exemptions. The remainder of the case records should be made
available to the data subject. Before a copy of the case record is provided to a child / young
person, care leaver or former service user, all of the information should be checked and any
which falls within the exemptions listed above redacted or removed from the copy of the case
record provided to the data subject. The data subject should be offered support and the
opportunity to ask questions when they are give n their case record.
99 </p>
100 <p>
100 The exemptions do not apply where disclosure is required by a court order or is necessary for
the purpose of or in connection with any legal proceedings.
100 </p>
101 <h2 class="h2_underlined">
101 <br />
102 3.
102 <a id="child_gain" name="child_gain">
102 </a>
102 Children Gaining Access to their Files/Records
102 </h2>
103 <p>
103 Children living in the home should be actively encouraged to take an interest in their case
record, and routinely given the opportunity to read and comment on them. They should be helped
to understand what personal information is contained in their case record, how it is used, how
long it is kept for and who it may be shared with.
103 </p>
104 <p>
104 Before case records are shown to children, consideration should be given to the likely effect of
sharing the information. All information contained should normally be shared, unless it falls
within the exemptions outlined in
104 <a href="#exemptions">
104 Section 2, Exemptions to the Right of Access
104 </a>
104 . If in doubt or if there are concerns about the likely effect on the child, the child's social
worker and the home's manager must be consulted.
104 </p>
105 <p>
105 Should staff need to share information provided by previous carers or third parties they should:
105 </p>
106 <ul>
108 <li>
108 Read the records/reports beforehand;
108 </li>
109 <li>
109 Speak to the authors if possible and obtain their consent to the sharing of information.
109 </li>
110 </ul>
111 <p>
111 Before the young person is shown their case file staff should:
111 </p>
112 <ul>
113 <li>
113 Collate the records in chronological order and check they use plain, easy to understand
language;
113 </li>
114 <li>
114 Give thought to what questions the young person may ask;
114 </li>
115 <li>
115 Offer appropriate support to the child / young person;
115 </li>
116 <li>
116 A note should be placed on the Daily Record each time a child has access to records or their
file.
116 </li>
117 </ul>
118 <h2 class="h2_underlined">
118 <br />
119 4.
119 <a id="change_record" name="change_record">
119 </a>
119 Changing a Record
119 </h2>
120 <p>
120 If a child claims that information contained in the record/file is inaccurate, incorrect or
misleading they may ask for it to be corrected or changed. A response to such a request should
be provided in 1 month, and the home's manager (or other member of staff) should take reasonable
steps to establish if the data is accurate and rectify the record if necessary.
120 </p>
121 <p>
121 If there is disagreement between the originator and the child, the home's manager should make a
decision on whether or how the record should be amended.
121 </p>
122 <p>
122 This may result in the original record remaining the same and an additional record of the
child's views being made.
122 </p>
123 <p>
123 <br />
124 <br />
125 </p>
126 </div>
127 </div>
128 </div>
129 </div>
130 <div id="footer-wrap">
131 <div id="footer-container">
131 <div id="footer">
132 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">
133 <tr>
134 <td width="60%" align="left" style="padding-top: 0px;">
134 <a href="http://www.trixonline.co.uk/" target="_blank">
134 <img src="images/trix_logo.gif" width="57" height="22" alt="tri.x logo" border="0"/>
134 </a>
134
134 <span class="darkdivider">
134 |
134 </span>
134 Copyright ©
134 <a href="http://www.trixonline.co.uk/" target="_blank">
134 tri.x
134 </a>
134
134 <span class="darkdivider">
134 |
134 </span>
134
134 </td>
135 <td width="40%" align="right" valign="top" style="padding-top: 0px;">
137 <div class="footer_box">
137 <a href="#">
137 visibility:
137 </a>
137
137 <a href="#" onclick="setActiveStyleSheet('small'); return false;">
137 <img src="images/icons/small_a.gif" alt="View this website with small text" border="0" />
137 </a>
137 <a href="#" onclick="setActiveStyleSheet('medium'); return false;">
137 <img src="images/icons/medium_a.gif" border="0" alt="View this website with medium
text" />
137 </a>
137 <a href="#" onclick="setActiveStyleSheet('large'); return false;">
137 <img src="images/icons/large_a.gif" border="0" alt="View this website with large text" />
137 </a>
137 <a href="#" onclick="setActiveStyleSheet('hivis'); return false;">
137 <img src="images/icons/hivis.gif" border="0" alt="View this website with high
visibility" />
137 </a>
137
137 <span class="darkdivider">
137 |
137 </span>
137
137 </div>
138 <div class="footer_box">
138 <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
138 <img src="images/icons/favourite.gif" alt="Add this page to your favourites" width="18"
height="18" border="0" />
138 </a>
138 <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
138 favourites
138 </a>
138
138 <span class="darkdivider">
138 |
138 </span>
138
138 </div>
139 <div class="footer_box">
139 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"/>
141 <a href="#" onclick="printSpecial()">
141 print
141 </a>
141
141 <span class="darkdivider">
141 |
141 </span>
141
141 </div>
142 </td>
143 </tr>
144 </table>
145 </div>
145 </div>
146 </div>
147 </body>
148 </html>