http://www.lioncourt.com/2009/06/14/safari-4-and-accessibility/ ...extra! extra!... Mon, 17 Oct 2011 16:05:59 +0000 hourly 1 http://wordpress.org/?v=3.1 http://www.lioncourt.com/2009/06/14/safari-4-and-accessibility/comment-page-1/#comment-105 Chris Sun, 21 Jun 2009 02:42:39 +0000 http://www.lioncourt.com/?p=403#comment-105 I have just updated to the latest version of Safari and I'm glad to have had the foresight to read this post before visiting the ITunes store. You didn't specifically mention the ITunes store but your reference to "online store pages" has made me somewhat apprehensive about browsing for new podcasts. I have just updated to the latest version of Safari and I’m glad to have had the foresight to read this post before visiting the ITunes store. You didn’t specifically mention the ITunes store but your reference to “online store pages” has made me somewhat apprehensive about browsing for new podcasts.

]]> http://www.lioncourt.com/2009/06/14/safari-4-and-accessibility/comment-page-1/#comment-104 Jake Mon, 15 Jun 2009 03:36:20 +0000 http://www.lioncourt.com/?p=403#comment-104 Regarding the crash on the Apple Store pages, as well as a few others, Apple has already fixed this in the most recent builds of Webkit, and they should have a fix out for the general release of Safari 4.0 very soon according to their accessibility folks. They definitely realize this is a major problem, and it is obviously a rather serious regression. One would've thought they'd at least use some of their own store pages to test out Voiceover before releasing Safari 4, considering there's some rather complex scriptlets on that page they'd want to make sure were read by Voiceover for their own site in addition to where similar scripts are used on other pages. The good thing is that they're on top of it and have the issue resolved, let's just hope they backport the fix to the system-wide Webkit used by Safari very soon. It is a bit worrying, for those just trying out Safari 4 and Voiceover it will not leave a good impression, and we all know that first impressions carry a great deal of weight when someone is first using any new bit of technology and, coupled with all the misinformation out there... let's just say further testing with Voiceover before release would have been a very good idea. Regarding the crash on the Apple Store pages, as well as a few others, Apple has already fixed this in the most recent builds of Webkit, and they should have a fix out for the general release of Safari 4.0 very soon according to their accessibility folks. They definitely realize this is a major problem, and it is obviously a rather serious regression. One would’ve thought they’d at least use some of their own store pages to test out Voiceover before releasing Safari 4, considering there’s some rather complex scriptlets on that page they’d want to make sure were read by Voiceover for their own site in addition to where similar scripts are used on other pages. The good thing is that they’re on top of it and have the issue resolved, let’s just hope they backport the fix to the system-wide Webkit used by Safari very soon.
It is a bit worrying, for those just trying out Safari 4 and Voiceover it will not leave a good impression, and we all know that first impressions carry a great deal of weight when someone is first using any new bit of technology and, coupled with all the misinformation out there… let’s just say further testing with Voiceover before release would have been a very good idea.

]]>