It seems like every day some piece of firmware or svtware needs updating. Whether it’s the operating system on our phones or computers, or an app or program. When that happens, we often hear and ask the million-dollar question. “Should I update, or not?” If I had a dollar for every time I’ve asked this question aloud or to myself, I think I’d be quite rich! For most people, updating isn’t a big deal. There may be changes in how things look, or work, and enhancements and bug fixes, and some bugs. While some bug bites are more severe than others, most of the time, the bug is found and squashed quickly, or, they may only fly around your head and annoy you. So, for the most part, the answer is black-white, and, a little more clear-cut, and, it’s an easy choice for people to make. 

However, for people with disabilities, things can get a little more complex. If our devices got infested with bugs, a bug bite could be at best annoying and easily dealt with and worked around, and, at worst, the effects can be severe. This could range from not being able to use apps or software, or, accessibility features, such as VoiceOver, and support for assistive tech such as braille displays being broken as well. Because of this, we have to use caution, and, oftentimes the word update makes us cringe. Some people might even consider that word to be on the same level as a swear word. So, we typically either don’t update until we’re forced to, or, we watch and wait to see what bugs people are getting bit by. This is the approach is the one I take, along with asking others. For Apple users, the best place to go to track bugs that are and aren’t related to accessibility, is AppleVis. Every year, their team tests beta software, and, they report on the new features and bugs that they got bit by. 

However, because their team is small, they couldn’t test every use case. Then, people can and do comment on the post, and, if they wish, people can subscribe to it, receiving notifications through email. At times, this can become… overwhelming. This is what I do, because it’s the best way for me to keep track of all of it. Plus, reports are scattered throughout the site such as in their forums where people can go to give and receive help. However, AppleVis has pulled the curtain back on something that will hopefully make it easier to make an informed choice. They will be launching a community bug tracking initiative to give the community an opportunity to talk about bugs they have been bitten by.

If you would like to read more about it, you can click the link below:

The initiative is expected to launch in the second week of June, just in time for Apple’s Worldride Developers Conference, where they announce upcoming software releases.

The spicifics are still being worked out, however, they are anticipating it looking as follows:

• The program will be open to anyone using either the IOS. or Mac-OS. betas.

• You will be required to submit reports of any and all bugs that are found to Apple through their Feedback app. This is so that Apple can be made aware of them, which will help make it easier to squash them. When you report a bug through the Feedback app, you will get a Feedback number, which you will provide when reporting a bug. No submissions will be accepted without a feedback number.

• Participants will fill out a form with the following information:

* The issue that was encountered

* The platform the issue was encountered on

* The steps to reproduce the issue

* The Apple feedback number

• The AppleVit team will see if their device(s) are infested with that bug, by attempting to reproduce the issue, and see if they get bitten. If they do, they will report the bug to Apple, and, keep track of it throughout the beta cycle. If the bug is still present in the Golden Master of the beta, which is the version that will be released to the consummers, then AppleVis will include it in its bug report, which lists and details new bugs, and, bugs that have been squashed.

• If they’re unable to reproduce an issue, they will not be able to track it internally, or put it in their bug report. However, people are welcome to post about issues and bugs they’re experiencing in the comments section, as well as in the forum, as has been done previously.

• If a user-submitted bug is included in the report, that user will get mentioned. However, you can remain anonymous if you wish.              

• Program participants will be featured in the final announcement release, however, you can choose to remain anonymous if you wish.

AppleVis has been publishing these bug reports since as least 2012, and, many blind Apple users, including myself, have and still do heavily rely on these to help us make the decision to update or wait. I have directed people to AppleVis in the past whenever they have asked that million-dollar question. However, because they’re an independent editorial organization, they have a small team. This means that testing eferts can only go so far. I will say though, that they have done an amazing job, and, they continue to. In 2022, they evolved their guidelines to allow for posting about beta software in their forums, and, created spaces in their forums for this. This is an excelent way to broaden the scope of testing, tracking and reporting of bugs, and will hopefully give a clearer picture of each release. This will in turn, help us better weigh the pros and cons, and, in general, make a more informed choice. Also, while some people may not either agree with me, or, not think or realize this, being a beta tester, tracking and reporting bugs is a form of advocacy. When you beta test an app or piece of software, as a person with a disability, you are using your assistive tech, such as a braille display, or, accessibility feature(s) such as VoiceOver. This is a very unique perspective that most developers, engineers, etc, don’t get every day, unless they use these features day in and day out. This means that they can track whether the bug is occurring for users of a Focus Braille Display from Vispero, or, a Brailliant BIX. series braille display from HumanWare. You’re educating them on how the disabled community uses their devices every day, and how they help us live our lives. Also, if multiple users are reporting getting bit by the same bug, then, it’s likely that the bug will get fixed. As the saying goes, the squeaky wheel gets the grease. In other words, this is a unique way to make your voice heard.

I hope that this will be expanded to include all of Apple’s softoware releases. Although I’m sure that will happen at some point in the future. I also hope that it gets opened up to users who are not beta testers as well. Because not everyone can be a beta tester for many reasons. For example, some people either don’t have a backup device, or, their device(s) are mission-critical, meaning they’re needed for school, work, or other reasons. I usually don’t beta test Apple software, however, I do and have beta tested several apps. However, this initiative is making me think about jumping in.

I want to hear from you! What are your thoughts on this initiative? Have you ever been a beta tester, and, if so, did you test an app or a software version? Are you still beta testing? If you have an Ios. device or a Mac, are you thinking about being a beta tester, and/or participating in this initiative? If you are a beta tester, what would you want both new beta testers, and people are are considering being beta testers to know either before or when they jump into the deep end of the pool so to speak? Feel free to share these and other thoughts in the comments section of this post!