I know a lot of blind QA people. Most testing actually does not involve the look and feel but, rather, exercising as many code paths that can be executed throughout the software. If one has a screen reader they can do this kind of testing with their eyes closed.
On Apr 6, 2009, at 8:49 PM, Sina Bahram wrote:
Having seen QA engineers work ... It is a heavily visual intensive field.A great deal of QA involves visual aspects such as clicking on appropriate areas, clicking on inappropriate areas, identifying color choices that arenot uniform throughout the application, asking why certain buttons areplaced far to any given direction, complaining that a particular button is inactive, even though it still shows on the screen, complaining about lag of things being painted or drawn, explaining that a particular mouse over isn't working, querying the developers about why the application uses such a small font in the most used area of the screen, trying to do things that mightlock up the application, and so on.Also, automated QA, which is hopefully what this position would entail,would involve using many tools that are themselves not accessible.Regarding accessibility ... I'm sure the various members of this list can present multimillion dollar investment pieces of software that have passedthe most stringent of QA testing over multiple years, and are not evenremotely accessible, much less usable by someone who is blind; for example.I don't believe it's appropriate ever to tell someone not to do something, if they want to do so, but by the same token, do realize that the level of accessibility that is potentially possible in something like a programming position is orders of magnitude more than that available in a QA position.Take care, Sina -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of James PanesSent: Monday, April 06, 2009 5:39 PM To: programmingblind@xxxxxxxxxxxxx Subject: Re: Quality Assurance testing bbie,The fact is that accessibility is part of QA. If the application is notaccessible, it fails. Go for it! Regards, James jimpanes@xxxxxxxxx jimpanes@xxxxxxxxxxxx "Everything is easy when you know how." ----- Original Message ----- From: "Robbie Miller" <Robbie@xxxxxxxxxxxxxxxxxxx> To: "Blind Programming" <programmingblind@xxxxxxxxxxxxx> Sent: Monday, April 06, 2009 3:57 PM Subject: Quality Assurance testingListers, I'm being offered the oppertunity to do Quality Assurance testing(QA testing). Has anyone on this list done this kind of work before? Are the testing tools accessible? Any advice on this matter would be greatly appreciated. Robbie millerrobbie@xxxxxxxxxxx __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind
__________View the list's information and change your settings at //www.freelists.org/list/programmingblind
