[webproducers] Re: creating accessible websites and how it im pacts the project life cycle
- From: kona bordango <filmchicka@xxxxxx>
- To: webproducers@xxxxxxxxxxxxx
- Date: Sat, 8 May 2004 14:47:32 -0700 (PDT)
I agree that starting to think about accessibility now, will create less coding
heartache later.
Also, if we look to the open source kids for inspiration, we might well realize
that this could be a huge opportunity to create and implement a well-thought
out raising of usability standards; we could be creating a standard ourselves.
Let's use blindness as our disability standard to work on-
The visual of the web is not coming across, so let's use another sense; sound
would work.
Now I understand some people enjoy the fact that the web medium doesn't make a
lot of audible noises to make apparent a users movement and choices. But what
if there was an 'opt in for sound' standard eventually built into every
browser, which would cue a page to bring up its audio for the page? Like on a
television you can change the default language to Spanish; in this case we
would be changing the default sense (sight) to another sense (sound).
This would be built into every browser *in the exact same place*, so it would
be easy to find by those who are blind. Perhaps the button would always be in
the top right corner; by scrolling over there a rollover button would trigger
audio to say "turn audio on" or somesuch. Then within every webpage you would
have the choice (except if you were federally funded as formerly stated in
previous posts) to build rollover audio bits to work at least the navigation on
the page- content audio would probably have to start right up upon load. I'm
just brainstorming right now.
But I do think that we have a great opportunity to start thinking of what would
make a good standard, and by taking a cue from open source developers, bat our
ideas around in online forums and come up with a proposal for browsers. (or
unveil at a convention, etc, etc)
-Sharon
Good to know, although unemployed, I can still churn out a thought or two ;)
-----Original Message-----
From: "Greg Glaser"<g_glaser@xxxxxxxxx>
To: webproducers@xxxxxxxxxxxxx
Date: Tue May 04 14:15:02 PDT 2004
Subject: [webproducers] Re: creating accessible websites and how it im pacts
the project life cycle
><Funny anecdote ahead>
>A company I had worked for in the past insisted that web development conform
>to *their* adapataion of the ADA guidelines. This "adapation" was merely a
>copy/paste of the ADA requirements...but they used the ADA, not the 508
>subsection, so our websites were required to be wheelchair accessible. Go
>figure.
></userdefined&
>>
>
>Not to trivialize the question, but the impact to create an accessible site is
>no different than requiring that a site "conform to our company's existing
>style guide." You're just assuming that the style of the site, so to speak, be
>branded and also accessible.
>
>So...if you account for accessibility early--that is, in your requirements and
>design stages (or pick your preferred methodology buzzwords)--the impact is
>minimal, or at least proportional to any other design expectation. It's when
>you try to add it in later that you increase your costs, as you might expect.
>Plan plan plan, then build.
>
>For other reference, you might try the following:
>
>http://www.section508.gov/
>
>http://www.hhs.gov/
>or
>http://www.medicare.gov/ (both good examples of compliance; medicare.gov even
>has a screen-reader option)
>http://bobby.watchfire.com/bobby/html/en/index.jsp (the ubiquitous Bobby
>accessiblity evaluator)
>
>http://www.w3.org/WAI/ (the W3C's web accessibility guidelines and tools)
>
>Greg Glaser, PMP
>Project Manager
>Zen Consulting
>www.zen-consulting.com
>
>
>
>=-=-=-=-=-=-=-=-=
>"Brad B. McCormick" <mccormickb@xxxxxxxxxxxxx> wrote:
>Actually, I believe the websites recieving any kind of FEDERAL FUNDING have
>to be accessible; that is, abide by the 508 standards.
>
>-----Original Message-----
>From: Cortney Sellers [mailto:cortney@xxxxxxxxxxxxxxxxxx]
>Sent: Tuesday, May 04, 2004 4:18 PM
>To: webproducers@xxxxxxxxxxxxx
>Subject: [webproducers] Re: creating accessible websites and how it
>impacts the project life cycle
>
>
>One note here that may be of interest to all....
>
>Website accessibility is required by federal law. While this is the case,
>some precedents are now being set which lay the groundwork for how
>accessible one has to be.
>
>It would be a great additional knowledge base for any web producer to have
>in their toolbox. Many of the things are simple, easy to implement, and
>beneficial in multiple ways.
>
>The trick will be to know that your team has a clear understanding of
>accessibility from each of their tasks: design, development, testing, etc.
>
>Cortney
>
>
>-----Original Message-----
>From: webproducers-bounce@xxxxxxxxxxxxx
>[mailto:webproducers-bounce@xxxxxxxxxxxxx] On Behalf Of tonyzeoli
>Sent: Monday, May 03, 2004 11:04 PM
>To: webproducers@xxxxxxxxxxxxx
>Subject: [webproducers] Re: creating accessible websites and how it impacts
>the project life cycle
>
>I'm assuming that he means what does is cost in extra development time to
>take into consideration accessibility issues, for example making the site
>compliant for the hearing or visibly impaired with either text or audio that
>
>can be accessed automatically when you visit a web site.
>
>I don't have any resources, but I'll look around. I did learn a little about
>
>this in my last semester at NYU.
>
>These types of issues are really relevant to the health care industry or the
>
>government, whose regulations require that web sites need to be accessible
>for the elderdly and the handicapped.
>
>Tony Z.
>> Zahid,
>> is there a chance you can re-phrase your wording.
>>
>> "creating accessible websites impact on the project life cycle" -- quite
>> possible it's me don't understand this.
>> Please elaborate.
>>
>> Sergei
>>
>> ********
>> Can anyone give me some advice on the subject creating accessible websites
>> impact on the project life cycle?
>> > Any useful thoughts, websites, books and resources would be
>appreciated.
>> >
>> > still had no responses hmmmm .......... I wonder why ?
>> >
>> > Many Thanks
>> >
>> > Zahid Hossain
>>
>> __________________________________________________________________________
>> To unsubscribe send a blank message with unsubscribe in the subject
>> to webproducers-request@xxxxxxxxxxxxx
>>
>> To access our webform to subscribe, unsubscribe, and manage your
>> subscription (digest and vacation) visit www.WebProducers.org.
>>
>> The WPO list is a public discussion forum with a public archive at
>> www.WebProducers.org. Be sure to trim your posts and delete personal
>> information such as telephone numbers if you do not want them as
>> part of the archive.
>
>
>Tony Zeoli
>Founder/President
>Netmix.com
>496 Court Street, #3
>Brooklyn, NY 11231
>
>email: tonyzeoli@xxxxxxxxxx
>ph: 718-858-7876
>fax: 718-504-4337
>cel: 917-705-4700
>aim: djtonyz
>__________________________________________________________________________
>To unsubscribe send a blank message with unsubscribe in the subject to
>webproducers-request@xxxxxxxxxxxxx
>
>To access our webform to subscribe, unsubscribe, and manage your
>subscription (digest and vacation) visit www.WebProducers.org.
>
>The WPO list is a public discussion forum with a public archive at
>www.WebProducers.org. Be sure to trim your posts and delete personal
>information such as telephone numbers if you do not want them as part of the
>archive.
>
>
>
>__________________________________________________________________________
>To unsubscribe send a blank message with unsubscribe in the subject to
>webproducers-request@xxxxxxxxxxxxx
>
>To access our webform to subscribe, unsubscribe, and manage your
>subscription (digest and vacation) visit www.WebProducers.org.
>
>The WPO list is a public discussion forum with a public archive at
>www.WebProducers.org. Be sure to trim your posts and delete personal
>information such as telephone numbers if you do not want them as part of the
>archive.
>__________________________________________________________________________
>To unsubscribe send a blank message with unsubscribe in the subject to
>webproducers-request@xxxxxxxxxxxxx
>
>To access our webform to subscribe, unsubscribe, and manage your subscription
>(digest and vacation) visit www.WebProducers.org.
>
>The WPO list is a public discussion forum with a public archive at
>www.WebProducers.org. Be sure to trim your posts and delete personal
>information such as telephone numbers if you do not want them as part of the
>archive.
>
>
>__________________________________________________________________________
>To unsubscribe send a blank message with unsubscribe in the subject to
>webproducers-request@xxxxxxxxxxxxx
>
>To access our webform to subscribe, unsubscribe, and manage your subscription
>(digest and vacation) visit www.WebProducers.org.
>
>The WPO list is a public discussion forum with a public archive at
>www.WebProducers.org. Be sure to trim your posts and delete personal
>information such as telephone numbers if you do not want them as part of the
>archive.
>
___________________________________________________
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com
__________________________________________________________________________
To unsubscribe send a blank message with unsubscribe in the subject to
webproducers-request@xxxxxxxxxxxxx
To access our webform to subscribe, unsubscribe, and manage your subscription
(digest and vacation) visit www.WebProducers.org.
The WPO list is a public discussion forum with a public archive at
www.WebProducers.org. Be sure to trim your posts and delete personal
information such as telephone numbers if you do not want them as part of the
archive.
Other related posts:
