-
Notifications
You must be signed in to change notification settings - Fork 1
/
index.html
42 lines (39 loc) · 1.73 KB
/
index.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 name="viewport" content="width=device-width, minimal-ui">
<meta charset="utf-8">
<link rel="stylesheet" type="text/css" href="style.css">
<title>ta11y: Testing the accessibility of HTML & ARIA samples</title>
</head>
<body>
<!-- Header w/ breadcrumb (Adjust breadcrumb links as needed) -->
<header role="banner">
<nav role="navigation">
<a href="index.html">Home</a>
</nav>
<hr>
</header>
<main role="main">
<h1>ta11y: Testing the accessibility of HTML & ARIA samples</h1>
<!-- Component start -->
<ul>
<li><a href="HTML5/html5.html">HTML 5</a></li>
<li><a href="ARIA/aria.html">ARIA</a></li>
<li><a href="https://github.com/IBMa/ta11y">ta11y repository on GitHub</a></li>
</ul>
<h2>Using These Code Samples</h2>
<p>
These code samples help developers and testers understand how different web components operate with assistive technology (AT) on desktop and mobile devices. They contain sample components along with testing results. When a new OS or AT is released, the data will be updated.
</p>
<p>
The best way to use these samples is to experiment with the component behaviors on different mobile devices or desktop environments. You can then "view source" to copy and modify the code for your own applications.
</p>
<p><b>Note:</b> The look and feel of these code samples is quite simplistic as the goal is to provide the cleanest view of the components being used without clutter.</p>
<!-- Component end -->
</main>
<footer role="contentinfo">
<hr>
</footer>
</body>
</html>