As a former user of Apple products, it saddens me very greatly to see the road which it appears that Apple has taken lately in regards to accessibility. Though it seems that some efforts are being made to correct prior error, let's address a few critical things. Realize that these comments stand not just for us blind individuals, but more the bigger picture in a whole.
First of all, there is the situation with all of the bugs which were released with the first-coming release of I O S 8.0. Again, I stress that most issues have been fixed, especially within the new I O S 8.1.1 which was just recently distributed to all users. Unfortunately, due to prior bad judgement on behalf of Apple by means of releasing faulty OS firmware which included many accessibility problems for both blind and visually impaired people, the faith ratio in Apple's reliability has decreased quite significantly in many respects.
Along with the problems which were encountered within I O S, there were also many issues within the new OSX Yosemite 10.10 for the Macintosh platform. Speaking not only as a personal user, but also from an academic level, I myself am a student attending certain college online courses and certification classes. For me, my studies require me to use a mac computer to carry out certain tasks. Part of this involves internet research. In Yosemite, a convenient feature was introduced to low vision and blind individuals who use the Voiceover screen reader to read what is on the screen. Apple introduced a new way by means of simply depressing any of the four arrow keys by themselves to interact with the web content. This applies to any html area regardless the application at hand. The problem however is that if a user decides to switch back and forth between arrow navigation and the traditional Voiceover navigation methods, they will find themselves in quite a mess. More specifically, the Voiceover focus does not track with the arrow key navigation, even if the Voiceover screen reader is set to follow the keyboard focus within the Voiceover preferences. This becomes very aggravating to most users as this means one cannot reliably jump by certain html elements such as headings, tables, form controls, etc. whilst still maintaining use of the new arrow key navigation. For this reason, the new feature is made impractical in many situations.
Another thing which has been reported to Apple multiple times which I do not see fixed, not even in the new 10.10.1 update released on November seventeenth, 2014 is the confusing message spoken by Voiceover when a character is inserted into a text area while in an html area. Voiceover will speak the message "New line selected." For advanced Voiceover users as myself, this is simply a major annoyance, however for beginner users who might not be at all familiar with the Mac, or with Voiceover in a whole, this is confusing, not to mention very misleading. If an individual was unaware that this was simply a bug, they may actually think that they have indeed done just that... selected a new line of text. By the time that they realize this is not the case, they have been pulling their hair out trying to figure out what is occurring. Again, I reiterate that this issue has been brought up to Apple many many times. Even in the new 10.10.1 update, this still seems to be an ongoing problem.
Further, there is an issue with a friend of mine's macbook 13 inch mid 2010 polycarbon system which was just updated to the new 10.10.1 O S X distribution. It appears that when running 10.10, his system ran fine. On the contrary, when he updated, his system became sluggish, and took a significantly long time to finish performing the update. (More so than usual.) In Apple's defense, this could be a result of him having only 2GB of ram, which I did advise him to try upgrading at some point, if at all possible.
In conclusion, my ultimate goal in this article is to bring awareness to the fact that Apple still seems to have a long ways to go to fix the problems which they have created most recently. I would like to say that I have complete faith that they will be fixed, however, though I haven't lost total hope, I am a bit skeptical, I will confess. If Apple Accessibility happens to read this, I very kindly ask that they take into consideration these issues, and diligently work to perform the necessary processes to insure they are dealt with in a timely and prompt manor.