That being the case, a further reading section at the end of the short document with those links and whatever other useful resources you have to hand would be useful. Even more useful would be an introduction stating document's purpose and limitations. A paragraph describing some of the extra stuff that will be possible if the developer does the extra reading will also be useful. Kind of like a trail of breadcrumbs.


On Fri, 8 Feb 2008, Ricky Buchanan wrote:

Jude,

Yes, I know there's a ton of information on apple.com about this - that's the problem, it's a TON of information. Too much for most developers to be bothered with reading. Two of the links that Apple sent in that email were from chapter five of a longer document!

I am looking at putting together a very short document about getting started with Accessibility in programming, something that a dev can read in 10 minutes and will let them make most applications at least somewhat accessible. Hopefully after that, they will be more motivated and interested to read the long documents.

Regards,
Ricky

On 08/02/2008, at 8:48 AM, Jude DaShiell wrote:





---------- Forwarded message ----------
Date: Wed, 6 Feb 2008 13:42:15 -0800
From: Accessibility <[EMAIL PROTECTED]>
To: Jude DaShiell <[EMAIL PROTECTED]>
Subject: Re: Sighted Developers and VO (fwd)

Hi Jude:

There's a ton of information about tools for testing applications on
Apple's developer web pages  developer.apple.com

(Kinda makes me wonder if anyone bothered to check. Just type
"accessibility" into the search field on the main page).

On a PC, the hardest part of QA testing is getting the testers a
screen reader (they're expensive and hard to learn!) but on the Mac,
it's easy and it's included.  Plus, there's a screen curtain feature
that blanks out the screen so sighted testers can't "cheat" by
looking.  And, for testers that don't want to learn VO, Apple offers
two other tools, the Accessibility Inspector and Accessibility
Verifier that can help uncover obvious mistakes in accessibility
without using VO.

To get you started, here are some key links:

Start page for developers on accessibility
http://developer.apple.com/referencelibrary/GettingStarted/GS_Accessibility/

Accessibility Inspector
http://developer.apple.com/documentation/Accessibility/Conceptual/AccessibilityMacOSX/OSXAXTesting/chapter_5_section_2.html

Accessibility Verifier
http://developer.apple.com/documentation/Accessibility/Conceptual/AccessibilityMacOSX/OSXAXTesting/chapter_5_section_3.html




On Feb 3, 2008, at 4:57 AM, Jude DaShiell wrote:

> > > > > ---------- Forwarded message ----------
> Date: Sun, 3 Feb 2008 22:52:43 +1100
> From: Ricky Buchanan <[EMAIL PROTECTED]>
> Reply-To: General discussions on all topics relating to the use of
> Mac OS X by
>   the blind <[email protected]>
> To: General discussions on all topics relating to the use of Mac OS
> X by the
>   blind <[email protected]>
> Subject: Sighted Developers and VO
> > > On 22/01/2008, at 4:44 PM, Justin Harford wrote:
> > You know any developer could just set vo to read what's under the
> > mouse. That way they could move the mouse over the buttons and see
> > for themselves what doesn't read without having to learn vo.
> > Has anybody actually written a short guide for sighted program
> developers about how to set up VO for basic use to test their app,
> or other ways to test the accessibility of their program? Jush wrote
> that a dev could just set up VO to read what's under the mouse but I
> doubt most sighted developers even know they can do that, much less
> *how* to do it. I would be thrilled to put any document on ATMac.org
> about how to make sure your app is accessible, and I'm sure Josh at
> Lioncourt.com would be also thrilled about it. As a sighted person
> myself, I don't think I'm qualified to write it though - although
> since I know practically nothing about VO I'd be happy to test a
> document like that to see how much it makes sense to a non-VO user!
> > Ricky Buchanan
> --
> Ricky Buchanan * [EMAIL PROTECTED] * http://notdoneliving.net/
> The people of the machine not only reduce everything to mathematics,
> but they also leave important sums out of the equations. -- DJN


r
--
Ricky Buchanan * [EMAIL PROTECTED] * http://notdoneliving.net/
The people of the machine not only reduce everything to mathematics,
but they also leave important sums out of the equations. -- DJN


Reply via email to