From: David Arnold <darnold@northcoast.com>
Subject: Accessibility
Date: Fri, 2 Sep 2005 22:03:48 -0700 [thread overview]
Message-ID: <1CC553DC-1C38-11DA-A65D-001124338712@northcoast.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1959 bytes --]
All,
We got the note below from our college president today. What does
anyone know about making context and pdf accessible to student with
vision problems?
Dear Colleagues:
We have an obligation and a commitment to full accessibility to our
courses and programs for students with disabilities.
By sending this memo, I want to inform you that effective immediately,
and in adherence to College of the Redwoods Board of Trustees Policy
No. 809 Administrative Regulation 809.07, specifically Part III of the
Policy Statement "Access to Electronic and Information Technology"
http://www.redwoods.edu/district/board/policies/ar/AR80907.Htm , all
instructional web pages and Blackboard postings must meet Level 1
accessibility standards as defined by the World Wide Web Consortium
(W3C) and Section 508 of the Rehabilitation Act Part 1194.22. These
standards are primarily concerned with the construction of electronic
documents including web pages and the readability of those documents by
assistive technology used by students with disabilities including
students who are low vision or blind.
In designing online instructional documents for your courses, please
ensure that they meet the specific requirements for accessibility
compliance found in both of the following:
W3C Checklist http://www.w3.org/TR/WAI-WEBCONTENT/full-checklist.html
and
Section 508 Checklist http://www.webaim.org/standards/508/checklist
Faculty web page authors may also access the staff of the Center for
Teaching Excellence for guidance and assistance in web page and
Blackboard development. Additional online information can also be found
by visiting the
http://hightech.redwoods/accessibility/
Using these resources, each of us can ensure the accessibility of our
course materials. Thank you so much for your attention to this
important matter-
Casey
[-- Attachment #1.2: Type: text/enriched, Size: 2920 bytes --]
All,
We got the note below from our college president today. What does
anyone know about making context and pdf accessible to student with
vision problems?
<fontfamily><param>Arial</param><x-tad-smaller>Dear Colleagues:
We have an obligation and a commitment to full accessibility to our
courses and programs for students with disabilities.
By sending this memo, I want to inform you that effective immediately,
and in adherence to College of the Redwoods Board of Trustees Policy
No. 809 Administrative Regulation 809.07, specifically Part III of the
Policy Statement "Access to Electronic and Information Technology"
</x-tad-smaller></fontfamily><fontfamily><param>Arial</param><color><param>0000,0000,FFFF</param><bigger>http://www.redwoods.edu/district/board/policies/ar/AR80907.Htm</bigger></color><x-tad-smaller>
, all instructional web pages and Blackboard postings must meet Level
1 accessibility standards as defined by the World Wide Web Consortium
(W3C) and Section 508 of the Rehabilitation Act Part
</x-tad-smaller></fontfamily><fontfamily><param>Arial</param><bigger>1194.22</bigger><x-tad-smaller>.
These standards are primarily concerned with the construction of
electronic documents including web pages and the readability of those
documents by assistive technology used by students with disabilities
including students who are low vision or blind.
In designing online instructional documents for your courses, please
ensure that they meet the specific requirements for accessibility
compliance found in both of the following:
W3C Checklist
</x-tad-smaller></fontfamily><fontfamily><param>Arial</param><color><param>0000,0000,FFFF</param><bigger>http://www.w3.org/TR/WAI-WEBCONTENT/full-checklist.html</bigger></color><x-tad-smaller>
and
Section 508 Checklist
</x-tad-smaller></fontfamily><fontfamily><param>Arial</param><color><param>0000,0000,FFFF</param><bigger>http://www.webaim.org/standards/508/checklist</bigger></color><x-tad-smaller>
Faculty web page authors may also access the staff of the Center for
Teaching Excellence for guidance and assistance in web page and
Blackboard development. Additional online information can also be
found by visiting the
</x-tad-smaller></fontfamily><fontfamily><param>Arial</param><color><param>0000,0000,FFFF</param><bigger>http://hightech.redwoods/accessibility/</bigger></color><x-tad-smaller>
</x-tad-smaller></fontfamily><fontfamily><param>Times New Roman</param><bigger>
</bigger></fontfamily><fontfamily><param>Arial</param><x-tad-smaller>Using
these resources, each of us can ensure the accessibility of our course
materials. Thank you so much for your attention to this important
matter-
Casey
</x-tad-smaller></fontfamily><fontfamily><param>Arial</param><x-tad-bigger> </x-tad-bigger></fontfamily>
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next reply other threads:[~2005-09-03 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-03 5:03 David Arnold [this message]
2005-09-03 5:11 ` Accessibility Brooks Moses
2014-08-04 14:43 Accessibility D.K.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1CC553DC-1C38-11DA-A65D-001124338712@northcoast.com \
--to=darnold@northcoast.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).