Re: .Net Framework Documentation
- From: Kerneels Roos <kerneels@xxxxxxxxx>
- To: programmingblind@xxxxxxxxxxxxx
- Date: Sat, 7 Aug 2010 11:23:25 +0200
Hi everyone,
I was just wondering how other people experienced working with the Microsoft
document explorer, and if people had some tips and tricks they were using to
make browsing the docs more economic and a more productive process. What I'm
saying is I -- for one -- was not blaming MS at all or complaining about it,
just looking for advice :-).
It's really getting old this thing that blind people complain about how
inaccesseble this or that piece of software is, as if we have this special
right to things being super easy for us. Well, we don't and it's a privilege
rather than a right if companies go to the expense of trying to make their
stuf more accessible. They have little or next to nothing to gain from
spending money on accessibility, yet they still do it, and try to do it well
even.
If you look at the "Help on Help" section in the MS document explorer for
example, you'll see that there are many accessibility features of that
program, like configurable keystrokes for example and everythin can be done
with a keystroke. This does not necessarily mean that the particular program
is easy to use if you can't click everywhere like fully sighted people does,
but it does mean that MS tried to make it workable if you can't see the
screen properly.
Wouldn't it be great if the blind programmer community could get known for
being super cooperative with companies in their drive to make their software
accessible by being nice, giving constructive critisism and each member of
the community going the extra mile themselves before opening their mounths
to complain? Wouldn't such a character prompt vendors to try harder and
harder to make their products inclusive?
And if company X produce very inaccessible software and efforts to make them
try a bit fails it should be seen as an opportunity for company Y to create
competing software that are in fact better and more accessible-- company Y
could add value.
I'm really impressed with many folks on this list that generously offer
their opinions and advice for free to even the silly questions. Let's all
try ask smarter questions and do our homework first. And if one happen to
ask a silly question, be ready to accept a silly response, and let's not
moan and complain -- life's too short.
OK, enough complaining about complaining!
Enjoy the adventure of programming!
On Fri, Aug 6, 2010 at 8:58 PM, Katherine Moss
<plymouthroamer285@xxxxxxxxx>wrote:
> I’m on 11.0.
>
>
>
> *From:* programmingblind-bounce@xxxxxxxxxxxxx [mailto:
> programmingblind-bounce@xxxxxxxxxxxxx] *On Behalf Of *Littlefield, Tyler
> *Sent:* Friday, August 06, 2010 1:19 PM
> *To:* programmingblind@xxxxxxxxxxxxx
> *Subject:* Re: .Net Framework Documentation
>
>
>
> They seem to work fine for me, what jaws are you both running? Rather than
> blame microsoft right off, lets look a bit closer to home first.
>
> ----- Original Message -----
>
> *From:* Katherine Moss <plymouthroamer285@xxxxxxxxx>
>
> *To:* programmingblind@xxxxxxxxxxxxx
>
> *Sent:* Friday, August 06, 2010 11:14 AM
>
> *Subject:* RE: .Net Framework Documentation
>
>
>
> I’ll tell you,
>
> I have had the exact same issue with all of the .net rreferences stuff.
> Even the new SDK docs aren’t even accessible via document explorer. I don’t
> understand why Microsoft doesn’t implement their own classes they have
> provided for accessibility in their own software!
>
>
>
> *From:* programmingblind-bounce@xxxxxxxxxxxxx [mailto:
> programmingblind-bounce@xxxxxxxxxxxxx] *On Behalf Of *Kerneels Roos
> *Sent:* Friday, August 06, 2010 3:51 AM
> *To:* programmingblind
> *Subject:* .Net Framework Documentation
>
>
>
> Hi List,
>
> Don't know about you guys, but I don't find the Microsoft .Net Framework
> documentation browser, or the Microsoft Document Explorer that ships with
> Visual Studio 2008 very accessible via JAWS. Yes, one can get at the
> information, but it's not a smooth and simple process like with the older
> style CHM files that works great with JAWS.
>
> Does anyone know if all of that documentation, or at least just the .Net
> Class Library reference is available in the old style CHM format? I've
> searched a bit but could not get a conclusive, authoritive download as of
> yet.
>
> Maybe I'm missing something, but the current means by which I manage to
> navigate it is not eficient at all. Much tabbing, moving around with the
> JAWS cursor and so on...
>
>
> If anyone is using the default help system any tips would be most welcome!
>
> Regards
>
>
> --
> Kerneels Roos
> Cell/SMS: +27 (0)82 309 1998
> Skype: cornelis.roos
>
> The early bird may get the worm, but the second mouse gets the cheese!
>
>
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 5345 (20100805) __________
>
>
>
> The message was checked by ESET NOD32 Antivirus.
>
>
>
> http://www.eset.com
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 5345 (20100805) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 5347 (20100806) __________
>
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 5347 (20100806) __________
>
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
--
Kerneels Roos
Cell/SMS: +27 (0)82 309 1998
Skype: cornelis.roos
The early bird may get the worm, but the second mouse gets the cheese!
Other related posts:
