Not signed in (Sign In)

SkillShare - A place to discuss Web Standards and Web Design topics

Categories

Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.

    • CommentAuthoreingko
    • CommentTimeApr 14th 2006
     permalink

    Three days ago (April 11) Microsoft released an Internet Explorer update in response to the patent battle between Microsoft and Eolas. After installing the update, Internet Explorer (not other browsers, fortunately) users will be required to “activate” embedded objects and plug-ins before they can interact with them. Here’s what sucks, most users will receive this update automatically via Windows Update. Embedded objects and controls affected are:

    Adobe Reader
    Apple QuickTime Player
    Macromedia Flash
    Microsoft Windows Media Player
    Real Networks RealPlayer
    Sun Java Virtual Machine

    In order to activate these objects, users are required to press the space bar, enter key, or use the mouse to click on the item. Anyone that’s tested the Internet Explorer 7 beta will have noticed similar behavior within that browser. According to w3schools browser statistics, over 60% of web users browse using Internet Explorer, meaning within the next few days approximately 60% of visitors to Flash websites, or sites using embedded media will be required to activate the media before being able to use it; because of this, some users may assume that the website is broken.

    Here’s the good news: Microsoft has posted a solution for web developers that would like to avoid their content being blocked. Essentially, in order to avoid this problem all that a web developer needs to do is embed the object via external script files. Those who have opted for Unobtrusive Flash Object placement within their websites will not be affected, because their content is already embedded in this manner.

    What’s ironic about this entire situation is that it actually forces developers to use a more standards compliant approach, go figure.

    More information here:
    http://msdn.microsoft.com/library/default.asp?url=/workshop/author/dhtml/overview/activating_activex.asp
    http://support.microsoft.com/?kbid=912945

    •  
      CommentAuthornifkin
    • CommentTimeApr 14th 2006 edited
     permalink
    Cross-Reference: "Flash insertion that validates, but still..." has some discussion of FlashObject, UFO and the EOLAS lawsuit.
    • CommentAuthorjrodgers
    • CommentTimeApr 15th 2006
     permalink

    If you need a quick and dirty solution to just get your sites working with a simple include there is the ActivateActiveX script.


    I used it to just fix a lot of older sites quickly... and because I am not entirely sure that Unobtrusive Flash Object or FlashObject are accessible even though they are standards friendly - Jaws might choke on it.

  1.  permalink
    re: FlashObject / UFO being accessible.

    they have been tested by macromedia, they both work fine with JAWS and everthing else:

    http://weblogs.macromedia.com/accessibility/archives/2005/08/in_search_of_a.cfm
    • CommentAuthorjrodgers
    • CommentTimeApr 15th 2006
     permalink
    Except in one key area... they require javascript, which you can argue that if someone has js off (who does that now anyway?) the probably aren't interested in Flash unless of course that Flash is used for navigation. Then your site is totally inaccessible. It is an annoying catch 22.

    Personally I prefer UFO/FO techniques. Just the ActivateActiveX was the easiest way for me to update sites quickly. I can go through and apply UFO when I have time.
    • CommentAuthorKanashii
    • CommentTimeApr 15th 2006
     permalink
    Actually if you're using UFO for it to actually be unobtrusive you should have a standard navigation to begin with and then replace it with the flash so even if javascript is disabled the user will still have the standard navigation. So it really depends on how the page is made and takes advantage of progressive enhancement : )
  2.  permalink
    jrodgers: both scripts allow for alternate content, so even if you were using it for a nav, you could put an html version of your nav 'under' the flash, so if js is off, they will just get the alternate version.
    • CommentAuthoreingko
    • CommentTimeApr 17th 2006
     permalink
    I always provide accessible alternate content if I'm using Flash replacement, because it creates mult-tier usability.

    A navigation list where the elements use an image-replacement technique for all elements, which is then overlayed with Flash.

    Users that don't have Flash will still have access to navigation, users that are incompatible with my stylesheets (ie4, netscape4, etc.) will still have a list.

    It's not a new concept, but I've always felt that it was a pretty good way to do things. Anyway...
Add your comments
    Username Password
  • Format comments as (Help)