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 Digital Photography | 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 Digital Photography
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#protection_c
h" target="_blank">
66 The Protection of Children Standard
66 </a>
66 </p>
67 <h3 class="h3">
67 SCOPE OF THIS CHAPTER
67 </h3>
68 <p>
68 This chapter provides procedures for staff on the use of photographic and video images e.g. as
part of activities.
68 </p>
69 <h3 class="h3">
69 RELEVANT GUIDANCE
69 </h3>
70 <p>
70 <a
href="http://www.proceduresonline.com/LimitedCMS_centrally_managed_content/indep_chomes/shared
_files/acpo_images.pdf" target="_blank">
70 ACPO Lead Position on Self Taken Images Guidance
70 </a>
70 </p>
71 <h3 class="h3">
71 RELEVANT CHAPTER
71 </h3>
72 <p>
72 <a href="p_corresp.html">
72 Staying in Touch (including safe use of the internet and Social Media) Procedure
72 </a>
72 </p>
73 </div>
74 <h2 class="h2_underlined">
74 <br />
75 Contents
75 </h2>
76 <ol>
77 <li>
77 <a href="#photo_vid">
77 Photography and Videos
77 </a>
77 </li>
78 <li>
78 <a href="#acc_inapp">
78 Access to Inappropriate Images and Internet Usage
78 </a>
78 </li>
79 </ol>
80 <h2 class="h2_underlined">
80 <br />
81 1.
81 <a name="photo_vid" id="photo_vid">
81 </a>
81 Photography and Videos
81 </h2>
82 <p>
82 Working with children and young people may involve the taking or recording of images. Any such
work should take place with due regard to the law and the need to safeguard the privacy,
dignity, safety and well-being of the children and young people.
82 </p>
83 <p>
83 Informed written consent from the
83 <a href="http://trixresources.proceduresonline.com/nat_key/keywords/placing_authority.html"
target="_blank">
83 Placing Authority
83 </a>
83 , parents or carers and agreement, where possible, from the child or young person, should always
be sought before an image is taken for any purpose.
83 </p>
84 <p>
84 Children may want to take pictures of themselves and each other; digital imaging equipment is
becoming readily available on personal devices and can be highly sophisticated.
84 </p>
85 <p>
85 It is not realistic to assume that restrictions should be placed upon every child and that an
outright ban on photography should be introduced, however a culture of respectful and careful
consideration should be promoted as to how activities involving the taking of images are
organised and undertaken. Care should be taken to ensure that all parties especially children
within the home understand the implications of the image being taken especially if it is to be
used for any publicity purposes or published in the media, or on the internet. There also needs
to be an agreement before images are used and as to whether the images will be destroyed or
retained for further use, where these will be stored and who will have access to them.
85 </p>
86 <p>
86 Staff need to remain sensitive to any children who appear uncomfortable, for whatever reason,
and should recognise the potential for such activities to raise concerns or lead to
misunderstandings.
86 </p>
87 <p>
87 It is not acceptable for staff to take photographs of children for their personal use or using
their personal equipment.
87 </p>
88 <p>
88 This means that staff should:
88 </p>
89 <ul>
90 <li>
90 Be clear about the purpose of the activity and about what will happen to the images when the
activity is concluded;
90 </li>
91 <li>
91 Be able to justify images of children in their possession;
91 </li>
92 <li>
92 Avoid making images in one to one situations or which show a single child with no surrounding
context;
92 </li>
93 <li>
93 Ensure the child/young person understands why the images are being taken and has agreed to the
activity and that they are appropriately dressed;
93 </li>
94 <li>
94 Only use equipment provided or authorised by the company;
94 </li>
95 <li>
95 Report any concerns about any inappropriate or intrusive photographs found to their manager;
95 </li>
96 <li>
96 Always ensure that they have parental permission to take and/or display photographs;
96 </li>
97 <li>
97 Images should only be stored on company equipment; no transfer of images to other devices is
permitted without the strict approval of the Home's manager.
97 </li>
98 </ul>
99 <h2 class="h2_underlined">
99 <br />
100 2.
100 <a name="acc_inapp" id="acc_inapp">
100 </a>
100 Access to Inappropriate Images and Internet Usage
100 </h2>
101 <p>
101 Staff should ensure that children and young people are not exposed to any inappropriate images
or web links. Home's Managers and staff need to ensure that internet equipment used by children
have the appropriate controls with regards to access and site-limitations and that
'firewall' and other safety filters are installed and regularly monitored and maintained.
101 </p>
102 <p>
102 Staff need to talk to the child, agree ground rules and monitor their activities as there are
constantly new ways unwanted material can pass existing security systems. There will also always
be people trying to gain unauthorised access to networks and PCs.
102 </p>
103 <p>
103 There are no circumstances that will justify staff possessing indecent images of children.
103 </p>
104 <p>
104 Staff who access and possess links to such websites will be viewed as a significant and
potential threat to children. Accessing, making and storing indecent images of children on the
internet is illegal. This will lead to criminal investigation and the individual being barred
from working with children and young people, if proven.
104 </p>
105 <p>
105 Staff should not use equipment belonging to their company to access pornography; neither should
personal equipment containing these images or links to them be brought into the workplace. This
will raise serious concerns about the suitability of the adult to continue to work with
children.
105 </p>
106 <p>
106 Where indecent images of children and other unsuitable material are found in staff possession,
they should be confiscated and the Home's Manager should be notified. The Home's Manager should
then notify the relevant social worker(s) and a decision should be reached about the actions
that should follow - which may include consulting, the police and
106 <a
href="http://trixresources.proceduresonline.com/nat_key/keywords/local_authority_desig.html"
target="_blank">
106 Local Authority Designated Officer
106 </a>
106 (LADO) should be immediately informed. Staff should not attempt to investigate the matter or
evaluate the material themselves, as this may lead to evidence being contaminated which in
itself can lead to a criminal prosecution.
106 </p>
107 <p>
107 This means that staff should:
107 </p>
108 <ul>
109 <li>
109 Ensure that children are not exposed to unsuitable material on the internet;
109 </li>
110 <li>
110 Ensure that any films or material shown to children and young people are age appropriate.
110 </li>
111 </ul>
112 <p>
112 Whilst accessing internet, all or any instances of inappropriate images or material which are
not suitable for children and young people must be reported to line manager.
113 </p>
114 <p>
114 <br />
115 <br />
116 </p>
117 </div>
118 </div>
119 </div>
120 </div>
121 <div id="footer-wrap">
122 <div id="footer-container">
122 <div id="footer">
123 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">
124 <tr>
125 <td width="60%" align="left" style="padding-top: 0px;">
125 <a href="http://www.trixonline.co.uk/" target="_blank">
125 <img src="images/trix_logo.gif" width="57" height="22" alt="tri.x logo" border="0"/>
125 </a>
125
125 <span class="darkdivider">
125 |
125 </span>
125 Copyright ©
125 <a href="http://www.trixonline.co.uk/" target="_blank">
125 tri.x
125 </a>
125
125 <span class="darkdivider">
125 |
125 </span>
125
125 </td>
126 <td width="40%" align="right" valign="top" style="padding-top: 0px;">
128 <div class="footer_box">
128 <a href="#">
128 visibility:
128 </a>
128
128 <a href="#" onclick="setActiveStyleSheet('small'); return false;">
128 <img src="images/icons/small_a.gif" alt="View this website with small text" border="0" />
128 </a>
128 <a href="#" onclick="setActiveStyleSheet('medium'); return false;">
128 <img src="images/icons/medium_a.gif" border="0" alt="View this website with medium
text" />
128 </a>
128 <a href="#" onclick="setActiveStyleSheet('large'); return false;">
128 <img src="images/icons/large_a.gif" border="0" alt="View this website with large text" />
128 </a>
128 <a href="#" onclick="setActiveStyleSheet('hivis'); return false;">
128 <img src="images/icons/hivis.gif" border="0" alt="View this website with high
visibility" />
128 </a>
128
128 <span class="darkdivider">
128 |
128 </span>
128
128 </div>
129 <div class="footer_box">
129 <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
129 <img src="images/icons/favourite.gif" alt="Add this page to your favourites" width="18"
height="18" border="0" />
129 </a>
129 <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
129 favourites
129 </a>
129
129 <span class="darkdivider">
129 |
129 </span>
129
129 </div>
130 <div class="footer_box">
130 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"/>
132 <a href="#" onclick="printSpecial()">
132 print
132 </a>
132
132 <span class="darkdivider">
132 |
132 </span>
132
132 </div>
133 </td>
134 </tr>
135 </table>
136 </div>
136 </div>
137 </div>
138 </body>
139 </html>