There is an art to testing software. As software testers, testing desktops, websites, mobile testing and enterprise software projects, in Functionality testing, Exploratory testing, Accessibility testing, WCAG2.2, Section 508 and Automation, including Automated Regression testing, we can often walk a fine line when developers tell a mutual client that they can test the application without software testers.

Of course, we don't agree as our job is quite different than that of a developer. As independent software testers, we provide clients with comprehensive software testing so that as many bugs can be found and fixed before the client signs off on a project, releasing the developers and signing off on the project.

This happened recently, and the client decided to use our services before signing off. We found 14 high-priority bugs, which had to be pulled into a new development sprint.

It took an additional two weeks for the apps to be fixed and once completed,we completed V&V-Verification and Validation testing-to ensure all the bugs were fixed before the app is released to the client. Our client was thrilled that she was not left to deal with these bugs after the release of the three apps.

There is also an art to testing when you are testing for the Library of Congress, National Library Service for the for the Blind and Print Disabled (NLS), Library of Congress, and BARD website using an Android phone or tablet. To be successful, YouTube is sensitive to the fact that many individuals who are blind believe all testing should be done by the blindforthe “pure blind experience.”

As accessibility testers, we understand and want to be sensitive to this point, but blindness is not absolute. We test for low vision, no vision, and color blindness. We also test for hearing impairments and deafness, motor and developmental disabilities and light-induced epilepsy. Individuals who have visual impairments often have a secondary disability so testing for only one thing is not comprehensive.

What To Consider When Designing for People Who Are Blind

We do believe in having User Test panels that provide valuable information as to how a person who is blind would use an app differently than a sighted person and incorporate User Test panels into our testing process.

We also learned about blind etiquette, being sensitive to the language we use, and taking another person's perspective. Below, I have attached several links about blind etiquette that we found helpful.

• https://nfb-in.org/about-blind...
• https://www.perkins.org/how-to...

Our testing was not only on the BARD Mobile, currently in development, but included testing concurrently with a braille refreshable display like the ones by Freedom Scientificand Humanware and using JAWS, and ZoomText.

BARD Mobilewas not designed and easily supported but Google has now added Braille Back to Android phones and should be more easily supported.

• https://www.freedomscientific....
• https://www.freedomscientific....
• https://www.freedomscientific....
• https://www.humanware.com/en-u...

Android Accessibility Questions and Answers

• https://support.google.com/acc...

The art of software testing is a complex and ever-changing field. As technology advances, so too do the methods and tools used to test software applications. At its core, the goal of testing remains the same: to ensure that software works as intended and meets the needs of its users.

Relevant Resources:

• What is Software Quality Assurance?
• What Is Accessibility Testing?