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 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 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 </p>
67 </div>
68 <h2 class="h2_underlined">
68 <br />
69 Contents
69 </h2>
70 <ol>
71 <li>
71 <a href="#bedroom">
71 Bedroom Furniture, Facilities, Equipment and Decoration
71 </a>
71 </li>
72 <li>
72 <a href="#security">
72 Bedroom Security and Keys
72 </a>
72 </li>
73 <li>
73 <a href="#staff">
73 Staff/Carers Presence in Bedrooms
73 </a>
73 </li>
74 <li>
74 <a href="#visiting">
74 Visiting and Sharing Rooms
74 </a>
74 </li>
75 <li>
75 <a href="#alarms">
75 Alarms and Monitoring Devices
75 </a>
75 </li>
76 </ol>
77 <h2 class="h2_underlined">
77 <br />
78 1.
78 <a name="bedroom" id="bedroom">
78 </a>
78 Bedroom Furniture, Facilities, Equipment and Decoration
78 </h2>
79 <p>
79 Children's bedrooms should be pleasantly furnished, equipped and decorated in a manner
appropriate to their individual needs, interests and choices.
79 </p>
80 <p>
80 Children should be encouraged to personalise their bedrooms, with posters, pictures and personal
items of their choice.
80 </p>
81 <p>
81 Children of an appropriate age and level of understanding should be encouraged and supported to
purchase furniture, equipment or decorations; preferably as part of a plan to prepare the child
for independence.
81 </p>
82 <h2 class="h2_underlined">
82 <br />
83 2.
83 <a name="security" id="security">
83 </a>
83 Bedroom Security and Keys
83 </h2>
84 <p>
84 Children should have adequate, safe, storage for their belongings and medicines, if permitted to
administer their own.
84 </p>
85 <p>
85 If it is necessary to do so, to protect children or their belongings or to develop their sense
of independence, bedrooms may be fitted with locks or other forms of security. If locks are
fitted, keys may be made available to children.
85 </p>
86 <h2 class="h2_underlined">
86 <br />
87 3.
87 <a name="staff" id="staff">
87 </a>
87 Staff/Carers Presence in Bedrooms
87 </h2>
88 <p>
88 Children's privacy should be respected.
88 </p>
89 <p>
89 Unless there are exceptional circumstances, staff should knock the door before entering
children's bedrooms; and then only enter with their permission.
89 </p>
90 <p>
90 The exceptional circumstances where staff may have to enter a child's bedroom without knocking
or asking permission are as follow:
90 </p>
91 <ul>
92 <li>
92 To wake a heavy sleeper, undertake cleaning, return or remove soiled clothing; though, in
these circumstances, the child should have been told/warned that this may be necessary;
92 </li>
93 <li>
93 To take necessary action, including forcing entry, to protect the child or others from injury
or to prevent likely damage to property. The taking of such action is a form of Physical
Intervention.
93 </li>
94 </ul>
95 <p>
95 See the following procedures:
95 </p>
96 <p>
96 <a href="p_searching_rooms.html">
96 Searching Children/Bedrooms Procedure
96 </a>
96 </p>
97 <p>
97 <a href="p_phys_inter.html">
97 Use of Restraint and Physical Intervention Procedure
97 </a>
97 </p>
98 <h2 class="h2_underlined">
98 <br />
99 4.
99 <a name="visiting" id="visiting">
99 </a>
99 Visiting and Sharing Rooms
99 </h2>
100 <p>
100 Children placed on an emergency basis may not share bedrooms (other than with siblings) until an
assessment has been carried out to ascertain their views and the views of those who already
sleep in the bedroom. Apart from this, a request to change or share a bedroom will be given
serious consideration by the Home's Manager.
100 </p>
101 <p>
101 However, not more than two children may share a bedroom and children may not share bedrooms
unless the child(ren) freely agree to the arrangement, they are of the same gender and similar
age (other than siblings). Before coming to a decision, the Home's Manager will undertake an
assessment to ascertain the wishes and views of the child who already occupies the bedroom and
will consult relevant social workers.
101 </p>
102 <p>
102 Children may not receive visitors in their bedrooms unless has been agreed by the social worker,
the children's views and wishes have been obtained, considered and the arrangements are outlined
in the relevant Placement Plan.
102 </p>
103 <h2 class="h2_underlined">
103 <br />
104 5.
104 <a name="alarms" id="alarms">
104 </a>
104 Alarms and Monitoring Devices
104 </h2>
105 <p>
105 To ensure the safety of the young person or others, it may be appropriate to monitor exit and
entry from a child's bedroom outside of normal waking hours with the use of a silent alarm that
is triggered when a door is opened.
105 </p>
106 <p>
106 Such devices may only be used if outlined in the Home's Statement of Purpose and the
arrangements set out in relevant Children's Placement Plans.
106 </p>
107 <p>
107 If used, every effort must be made to ensure the child's privacy, dignity and rights whilst the
system is in use:
107 </p>
108 <ul>
109 <li>
109 The use of these alarms is outlined fully in the homes statement of purpose;
109 </li>
110 <li>
110 Their use is assessed on an individual basis and agreed to in the care plan by a social
worker;
110 </li>
111 <li>
111 The child is made fully aware of their use and the reasons why the decision is made;
111 </li>
112 <li>
112 The use of the door alarms is reviewed regularly as to their appropriateness of use.
112 </li>
112 </ul>
113 <p>
113 <br />
114 <br />
115 </p>
116 </div>
117 </div>
118 </div>
119 </div>
120 <div id="footer-wrap">
121 <div id="footer-container">
121 <div id="footer">
122 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">
123 <tr>
124 <td width="60%" align="left" style="padding-top: 0px;">
124 <a href="http://www.trixonline.co.uk/" target="_blank">
124 <img src="images/trix_logo.gif" width="57" height="22" alt="tri.x logo" border="0"/>
124 </a>
124
124 <span class="darkdivider">
124 |
124 </span>
124 Copyright ©
124 <a href="http://www.trixonline.co.uk/" target="_blank">
124 tri.x
124 </a>
124
124 <span class="darkdivider">
124 |
124 </span>
124
124 </td>
125 <td width="40%" align="right" valign="top" style="padding-top: 0px;">
127 <div class="footer_box">
127 <a href="#">
127 visibility:
127 </a>
127
127 <a href="#" onclick="setActiveStyleSheet('small'); return false;">
127 <img src="images/icons/small_a.gif" alt="View this website with small text" border="0" />
127 </a>
127 <a href="#" onclick="setActiveStyleSheet('medium'); return false;">
127 <img src="images/icons/medium_a.gif" border="0" alt="View this website with medium
text" />
127 </a>
127 <a href="#" onclick="setActiveStyleSheet('large'); return false;">
127 <img src="images/icons/large_a.gif" border="0" alt="View this website with large text" />
127 </a>
127 <a href="#" onclick="setActiveStyleSheet('hivis'); return false;">
127 <img src="images/icons/hivis.gif" border="0" alt="View this website with high
visibility" />
127 </a>
127
127 <span class="darkdivider">
127 |
127 </span>
127
127 </div>
128 <div class="footer_box">
128 <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
128 <img src="images/icons/favourite.gif" alt="Add this page to your favourites" width="18"
height="18" border="0" />
128 </a>
128 <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
128 favourites
128 </a>
128
128 <span class="darkdivider">
128 |
128 </span>
128
128 </div>
129 <div class="footer_box">
129 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"/>
131 <a href="#" onclick="printSpecial()">
131 print
131 </a>
131
131 <span class="darkdivider">
131 |
131 </span>
131
131 </div>
132 </td>
133 </tr>
134 </table>
135 </div>
135 </div>
136 </div>
137 </body>
138 </html>