public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Juan Hernandez" <juan@netplus1.com>
To: <speakup@braille.uwo.ca>
Subject: Accessibility university course proposal
Date: Tue, 10 Oct 2006 22:08:37 -0700	[thread overview]
Message-ID: <000e01c6ecf3$4ee69460$0700a8c0@eric> (raw)

Hello everyone,

I am in the process of compiling a proposal to my university.  This proposal
will be directed at the computer science department of my university.  The
information is below.  

When referring to computers and software, accessibility is a very important
topic.  If a web site, software program, or a device is not usable by
someone that has a disability, this may make the person's experience very
bad, and even jeopardize their ability to work, and in some cases make them
loose their job entirely.

I am building an academic guide line and course requirement request for my
university.  I am finishing my Bachelor of Science in computer science at my
school, and will be entering their Master of Science program in the same
field of study next year.  I am hoping to get this requirement accepted by
my school, and even teach it while I am a graduate student.  I will propose
to the Computer Science Department that I would like to see a course
developed that instructs students in the different facets of Accessibility
in terms of software design and development.

The criteria that I have come up with are as follows:

Web accessibility

Interface design and development

Documentation availability

Accessibility considerations when updating software
(I.E. breaking something that worked in previous versions to make something
else work in a new version)
 
This is only a rough outline, and I hope to get more criteria to consider
for my proposal.  Please give me any input, criticism, ideas, opinions, what
ever you feel about this.

Examples of bad and good accessibility implementations, problems people
encounter when making something accessible, and what ever else.

I feel that students do not understand the importance of accessibility, and
that they should be aware, from the beginning of their education about
accessibility. 

For those that are not blind or visually impaired please give me input, I do
not know much about other accessibility needs then those of the blind and
visually impaired.

Please right me off list if you want at:  juanh@cox.neIf you would like to
discuss more about this, we can skype or talk on the phone.

Please let me know what you all thing, remember no needs/wants are stupid,
everything will be considered, and will be compiled into a proposal to my
university.  If I am successful with this, I would like to approach other
universities about this.

Thank You.

Juan Hernandez
San Diego State University
E-mail:  juanh@cox.net
  




             reply	other threads:[~ UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Juan Hernandez [this message]
 ` Chris Norman
   ` Robin Williams
   ` Michael Whapples

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='000e01c6ecf3$4ee69460$0700a8c0@eric' \
    --to=juan@netplus1.com \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).