Perhaps this one will get through this time. If you wish to read my views on
the matter, I've
included my prior undelivered messages from this weekend below, which are
direct replies to the messages from Jared and Tyler. . Btw, there is no
petition, I simply created a fan page to gage the level of interest in the
feature; I am also unaware of any ranting taking place anywhere, so I don't
understand on what basis these references are being made.
----- Original Message -----
From: "Bryan Garaventa" <bgaraventa11@xxxxxxxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Sunday, April 18, 2010 10:12 AM
Subject: Fw: Make Facebook's live chat accessible to blind screen reader users?
> Thank you Michael for your views, I agree totally. If the knowledge and
> technology are available, I see no reason why they can't be adopted in a
> friendly manner that benefits all. I wrote the email below that details my
> views more clearly, I'm not sure why it never arrived on the list. I'll keep
> this as my last message on the topic as I wrote below.
>
>
> ----- Original Message -----
> From: Bryan Garaventa
> To: programmingblind@xxxxxxxxxxxxx
> Sent: Saturday, April 17, 2010 12:14 AM
> Subject: Re: Make Facebook's live chat accessible to blind screen reader
> users?
>
>
> That's quite alright, everyone has an opinion.
>
> I would recommend however, that you read the information that is being
> referred to before recommending solutions that are already being offered.
>
> The solution that I've proposed uses a simple WCAG 2.0 standards compliant
> method for making the current implementation of Facebook chat use ARIA to
> allow automatic announcement of incoming messages within both JAWS and NVDA.
> This is a simple solution for any developer to accomplish, and I see no
> reason why something that works imperfectly can't be enhanced to accomplish
> a more standards compliant user experience for all those involved.
>
> As a developer myself, I am always open to new ideas and techniques, which
> is how I learn better and more valuable skills as time goes on. Rather than
> get stuck in old ideas that promote the notion that work arounds are the
> only solution, it is sometimes good to explore the possibilities that new
> technologies offer, which is why they were created in the first place. For
> example, HTML5 and ARIA.
>
> I am quite familiar with all of the accessibility best practices of both
> Section 508 and WCAG 1 and 2. This will be my last post on this subject,
> since it is likely off topic.
>
> If you do not agree with the implementation of more standards compliant and
> accessibility enhanced products and services using the new technologies for
> which they were developed, that is your choice. I choose instead to use
> these new standards compliant technologies, and to recommend solutions that
> not only enhance people's experiences, but also create an equal playing
> field for all those who wish to participate. The nice thing about the latest
> trends in accessible development techniques, is that they are very easy to
> implement, and offer a wide range of automatically accessible features that
> enrich dynamic applications to the fullest extent possible for all user
> types.
>
> Again, if you see a problem with this view point, that is your choice; It is
> not mine.
>
> Good day,
> Bryan Garaventa