Skip to content

change checklist to W3C format #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

change checklist to W3C format #15

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion checklist.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,13 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">

<head>
<title>[DRAFT] FAST Checklist</title>
<script class="remove" src="respec-config.js"></script>
<script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove"></script>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link href="https://www.w3.org/StyleSheets/TR/base" rel="stylesheet" />

<style type="text/css">
@counter-style checklist
{
Expand Down Expand Up @@ -52,6 +56,16 @@
}</style>
</head>
<body>
<section id="abstract">
<p>to be added</p>
</section>
<section id="sotd">
</section>
<section>
<h2>Introduction</h2>
<p>to be added</p>
</section>
<section>
<h1>[DRAFT] <abbr title="Framework for Accessibility in the Specification of Technologies">FAST</abbr> Checklist</h1>
<p>This is a draft checklist to support <a href="./">Framework for Accessibility in the Specification of Technologies (FAST)</a> prepared by the <a href="http://www.w3.org/WAI/APA/">Accessible Platform Architectures Working Group</a>. The goal of <abbr title="Framework for Accessibility in the Specification of Technologies">FAST</abbr> is to describe the features that web technologies should provide to ensure it is possible to create content that is accessible to users with disabilities. The full framework references an analysis of user requirements, describes how technologies, content authoring, and user agents work together to meet these needs, and provides comprehensive guidance to technology developers. This checklist extracts that information at a high level to aid in self-review of technologies. Specification developers can use this to help ensure the technology will address features likely to be raised during horizontal review from accessibility proponents.</p>
<p>Web technologies address a variety of needs, and play a variety of roles in web accessibility. Content languages describe primary content, styling languages impact presentation, APIs enable manipulation and data interchange, and protocols tie it all together. Each of these types of technologies can impact accessibility. </p>
Expand Down Expand Up @@ -516,5 +530,6 @@ <h1>[DRAFT] <abbr title="Framework for Accessibility in the Specification of Tec
</tr>
</tbody>
</table>
</section>
</body>
</html>