sIFR and Anchors Can Be Friends! Marc over at the Crossroads blog (basically consisting of only the one post) provides an excellent article on issues affecting link accessibility and how to modify the standard sIFR Javascript and ActionScript to fix it. Great work.
Note, of course, that this pertains to accessibility for links in a sIFR context. One of the great boons of sIFR (aside from eliminating hours of boring Photoshopping) is that ascii text treated with it is 100% accessible. Er, except the link thing, to some extent.
Note: Well, that’s what I get for going off half-cocked. Turns out the anchor hack fails miserably in Firefox 1.5 — the sIFR-ized text has a tendency to disappear entirely (sometimes) in that browser. I’ll investigate further to see if I can jimmy the whosis. But meanwhile, caveat emptor and (always) test thoroughly before going live, kids.
Marc’s contribution makes a fine companion to Marko Dugonjic’s excellent two-color sIFR hack, so’s you can have more than one color in a block of sIFR-ized text. For that you’ll need the first article and the second part, which includes some more standards-compliant optimizations.
Note: A couple drawbacks to the 2-color hack are worth mentioning. Foremost, the second color must be encoded into the Flash file itself (via one of the ActionScript files). Changing your site palette will thus mean re-encoding the sIFR. (I’ve not tried hacking the hack to see if it can be repurposed to, say, a CSS class, tho I’m not optimistic since it relies on dynamically swapping in an olde school FONT COLOR=”foo” tag.) Also, integrating the hack is kinda cumbersome in a couple ways. One, it was created for an earlier version of sIFR, and so the “find this and replace it with that” stuff in many cases no longer explicitly applies — which means putting on your reverse engineering hat. Two, part two of the article is revisions to the previous revisions — which means you gotta reverse engineer the changes twice.
Both of these hacks are officially sanctioned included in the sIFR documentation wikki, but is not officially sanctioned by the creators of sIFR. (See comments, below.) I’m also pleased to report that the wiki appears to have been fixed and will now talk to you even outside of bankers’ hours. Hooray! (Or boo…that means I don’t have any excuses when working late or on the weekend.)
(If you don’t know about sIFR, then get thee to the official sIFR site right quick.)