I know, I realized that after I asked the question. I'm feeling a little stupid now. LOL!
Chris. ----- Original Message ----- From: Andrew Lamanche To: [email protected] Sent: Thursday, June 11, 2015 2:00 AM Subject: Re: Major frustrations and a big predicament Hi, You can assign a shortcut key combination to switch between DOM and group navigation in keyboard commander in VoiceOver utility. On 10 Jun 2015, at 23:17, Christopher-Mark Gilland <[email protected]> wrote: Is there a quick way to do this, or will I have to do it each time back and forth within the Voiceover Utility. Chris. ----- Original Message ----- From: Barry Hadder To: [email protected] Sent: Wednesday, June 10, 2015 6:09 PM Subject: Re: Major frustrations and a big predicament Hi Chris, Just switch to groups mode and it will work with voiceover. The rest of the form works fine with dom navigation. On Jun 10, 2015, at 5:01 PM, Christopher-Mark Gilland <[email protected]> wrote: So, guys, I never like writing e-mails like this, and I know some of you are going to write me and scream at me for being over dramatic, or for waisting your time etc. Most of you on this list who're civil have seen the patterns, therefore I don't think it's either necessary nor appropriate for me to quote names, as you all probably know the folks I'm referring to. Here is the situation though. I'm obviously going to keep this fairly general, but I have to at least be detailed enough for you all to understand where I'm coming from, so though this may be borderline, I don't think it's quite at the point of violating anything. So, this morning, I installed the beta of I O S 9 on my IPhone 5S. I'm not at liberty to state the specifics, but I found a bug which is quite severe and could really effect accessibility in one aspect. Though it's not anything that would render the device useless, it definitely is severe enough it needs to be fixed. Again, I'm not at a position to elaborate on this, but my point is, I logged into the Apple developer web site, and proceeded to the bug reporter. I should add that I tried this both with Capitan and with Yosemite. Both have the same results. Once I clicked the button for a new bug report, it popped up asking what type of bug I'm filing. Under the "Other" heading, I chose accessibility. This opened up a window to create a new accessibility report. I hit vo+Right arrow, and got down to classification. Once I hit vo+space on the item that says select classification clickable, nothing at all happened. Absolutely nothing. So, I cannot accessibly continue the process, as at this point, I get totally stuck. I tried routing my mouse pointer with vo+command+F5, then vo+shift+space, I tried hitting spacebar, return, clicking the literal trackpad, interacting, vo+shift+M, ctrl+clicking the trackpad, absolutely nothing! is working. I tried with Safari, and with Chrome both on Yosemite, and on Capitan with the same results. I tried on Windows with Windows 8.1 in both IE 11, and in Firefox. Both were tested with JAWS 16, and with NVDA 2015.2. Once I clicked the new button for a new report, I tried hitting enter on the accessibility button, and absolutely nothing happened. In JAWS, I did an insert+escape to refresh the screen, no good. I re-initialized Aria, just in case that was what it was using, no good. I tried routing my jaws cursor to my virtual PC cursor then clicking. No good. In NVDA, I routed my mouse pointer with NVDA+numpad slash, then left clicked with num pad slash. No good. I even tried with Window-Eyes, routing the mouse with insert+num pad plus, then doing a left click. Again, no good. Nothing happened. When I called Apple developer support to let them know about this, and that the accessibility of the bug tracker was broken, they didn't exactly blow me off, but they didn't seem really all that concerned either. They basically told me they'd file it with apple.com/feedback When I told them that I don't know how long that would take but it probably wouldn't get solved very soon that method, most likely, the guy got a little bit defensive with me. He told me that in his words, they don't support the Bug tracker in his department, therefore he doesn't have a way to open a ticket with the engineers to get this fixed. When I told him that I just spent the very last 99 dollars I had for this program, he got snovvy and said, then you better start developing your apps so you can get paid back. I told him I don't program, I don't write applications. The reason I joined was to report bugs, and help them with making sure things were accessible. I told him if I can't do that and report bugs in the first place, then what is the point therefore of me being a dev. I told him I'd paid 99 dollars for this, and therefore feel it's my right to be able to have this looked into quickly, or to get a refund. He told me unfortunately, he doesn't have the tools to push the feedback up to the bug reporter engineers. That might be true, I don't know if it is or not, but if it is, then, that's frankly, ridiculous! Especially considerring he was a senior advisor in the developer department. When I asked him for a refund, he told me that their policy is no refunds no matter what. He said, plus, even if they did! refund me, they've changed the way they deploy I O S 9 to devices. Technically, I'm not probably supposed to tell you all this, but I feel it's in you all's best interest to know, so you don't totally ruin your devices. If you upgrade to I O S 9, it even says right there on the web site, you cannot downgrade back to I O S 8. Not even apparently with D F U mode. So, if I did! get a refund, and they disabled my dev account, that would unenroll my devices, therefore renderring them forever permanently useless unless they were re-enrolled, which there policy is, I couldn't do for 12 months after disabling them. Frankly, Apple needs to get their shit together. That's all I'm gonna say. You may not like hearing it, but this has me a little disturbed. If we blind people can't report bugs, then how the hell do they expect us to help them with that side of things? Chris. -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout. Barry Hadder [email protected] -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout.
