Re: [Bulk] Re: [Mac-cessibility News] Twitterific for Mac 4.0 Is Released Sans VoiceOver Accessibility

2011-02-16 Thread Josh de Lioncourt
On Feb 16, 2011, at 11:52 AM, Michael Thurman wrote: just post t he text if you want to post stuff here these stes are rediculous anywayif you can't copy and paste the text into the E mail why bother these sites take forever and are almost universally porly written 1. These messages

Re: [Bulk] Re: [Bulk] Re: [Mac-cessibility News] Twitterific for Mac 4.0 Is Released Sans VoiceOver Accessibility

2011-02-16 Thread Ray Foret Jr
For my part, I'm going only to say this. I suspect that what we're dealing with here is a fundamental misunderstanding. Seems to me to be the case that, if we had this explanation earlier, (perhaps at the point of first criticism), it would never have gone to this level. I myself have found

Re: [Bulk] Re: [Mac-cessibility News] Twitterific for Mac 4.0 Is Released Sans VoiceOver Accessibility

2011-02-16 Thread Søren Jensen
Hi Josh. The only thing most of us don't like is that the server only send a part of the articles instead the whole articles. Personally I like the website and really like the way you write the articles and explains how things works, but the way the news is being sended to the lists is very

Re: [Bulk] Re: [Mac-cessibility News] Twitterific for Mac 4.0 Is Released Sans VoiceOver Accessibility

2011-02-16 Thread Laura M
I guess my problem whenever this topic comes up--and it comes up kind of a lot--is that Josh and the other mods don't owe us anything. If they feel their services aren't appreciated enough, they're perfectly within their rights to stop providing them. If we feel we aren't getting enough out of

Re: [Bulk] Re: [Mac-cessibility News] Twitterific for Mac 4.0 Is Released Sans VoiceOver Accessibility

2011-02-16 Thread Ricardo Walker
Please. Can we all spend a few seconds to proof read and spell check our messages before sending them off? Especially when you are attacking someone for poorly written content. lol. The irony is dripping all over this. An no. I'm not a list mod. I just like to be able to get through a 2

Re: [Mac-cessibility News] Twitterific for Mac 4.0 Is Released Sans VoiceOver Accessibility

2011-02-14 Thread Søren Jensen
I'm tired of reading 95% of the news and then click the link to open the website to read the last 10 words. I don't know if this is the limit of the blogging system, but I don't have time . to open up a website just to read the whole news when receiving more than 200 mails each day. Best

Re: [Mac-cessibility News] Twitterific for Mac 4.0 Is Released Sans VoiceOver Accessibility

2011-02-14 Thread Chris Moore
I must admit, I totally agree with this. What is the point in directing us to only read a few extra words? This seems to happen with the majority of these postings. Why not just paste the entire article in here? On 14 Feb 2011, at 09:51, Søren Jensen wrote: I'm tired of reading

Re: [Bulk] Re: [Mac-cessibility News] Twitterific for Mac 4.0 Is Released Sans VoiceOver Accessibility

2011-02-14 Thread Ray Foret Jr
Quite correct. IF you ask me, this is getting just plain f. IF the intention is to encourage us to visit the site for the story, why not just post the blasted link and be done with it for goodness sake. I'm also growing very weary of this infantile stupid practice of making us go to the

[Mac-cessibility News] Twitterific for Mac 4.0 Is Released Sans VoiceOver Accessibility

2011-02-11 Thread Maccessibility
Twitterific for Mac 4.0 Is Released Sans VoiceOver Accessibility The IconFactory has released the much anticipated Twitterific 4.0 for Mac OS X. Though Twitterific was one of the first OS X Twitter clients to incorporate accessibility, the application has taken a huge step backward with this

Re: [Mac-cessibility News] Twitterific for Mac 4.0 Is Released Sans VoiceOver Accessibility

2011-02-11 Thread Chris Snyder
Man, why does this continue to happen. I don't understand how or why breaking accessibility happens. I thought that if the programmers coded the app incorporating Apple's accessibility guidelines, it would simply work. For that matter, I thought that if the programmer simply used Cocoa as the