-
Notifications
You must be signed in to change notification settings - Fork 0
/
2-1-6.html
42 lines (35 loc) · 1.64 KB
/
2-1-6.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<link rel="stylesheet" type="text/css" href="main.css">
<title>2.1.6 Describing access issues that need taking into account</title>
</head>
<body class="backgroundMixDesk shadow1">
<div class="flex-container">
<h1 class="logo"><a href="index.html">Jody Richardson</a></h1>
<ul class="navigation">
<li><a href="index.html">Home</a></li>
<li><a href="1-1-0.html">About</a></li>
<li><a href="sitemap.html">site map</a></li>
<li><a href="contact.html">Contact</a></li>
</ul>
</div>
<h2 class="centreText">Unit 2 - 1.6 Describing access issues that need taking into account</h2>
<p class="mainPara">
When designing any digital project we must take into account the fact that there will be different accessibility
requirements depending on the end user.
A person with sight impairment may need to be able to access a braille encoded, high contrast or audio described
version of the product.
Any audio related content would need to be provided in text form if the user is hard of hearing or deaf.
People whose first language is not English will need to have the page translated for them to use it comfortably.
There are tools that are provided free of charge by companies such as Google that can help resolve these issues
using the cloud, without the need for specific code to be written.
</p>
<div class="navbarL">
<a href="2-1-5.html">PREV</a>
</div>
<div class="navbarR">
<a href="2-1-7.html">NEXT</a>
</body>
</html>