FAQ and Tags Update

Oct 04, 2009 15:28

Heya, it's your friendly neighborhood mod here. Two notes:
  1. As many of you have noticed, we've been battling the tag limit for a while, but we haven't gotten the new tagging scheme up and running yet. Right now, I'm working on easing things up a bit by porting author tags over to delicious. Eventually all author tags will be over there, but for some intermediate period we'll have a situation where some author tags are here and some are there. If you can't find an author tag that you're sure ought to exist (or if some of the posts for that tag seem to be missing from the tag), pop over to delicious and look under the "authors" tag bundle. It should be over there. (Also, the (delicious) tag that some of you may have noticed? The intent is for it to be used during the transition, to help us keep track of what we're doing -- when we finish, we'll get rid of it. Please don't add or remove that tag to posts, unless you are working on the tag-portage project.)

    And yes, as soon as we get the details sorted out, we will be asking for help in porting things over. Believe me, I am already very much looking forward to the extra hands.

  2. I'm going to modify the spoiler-code listed in the FAQ so that it has better accessibility for people who use screenreaders. The idea and execution is described here, but the basic idea is to bridge the spoiler with a "skip this spoiler" hyperlink. Like so:
    ( skip spoiler)
    This should be skippable even when one is using a screenreader. If it's a long spoiler you'll get one border around the entire block of text, instead of overlapping borders around each individual line of text. Dunno about you, but that had been bugging me.
    If this doesn't render properly on your browser, let me know, and I'll see what I can do to fix it.

    If you want to try it out in the comments, here's the spoiler code:

    ( skip spoiler)

    SPOILER TEXT GOES HERE


    If you have more than one spoiler, just change "skip.firstspoiler" to "skip.secondspoiler" (change both instances!) as appropriate.

    Also, because I know that big block of code can be unpleasant for some, I'll add instructions to the FAQ for rot-13. (Unless anyone has a good reason to not use rot-13?) V zlfrys unir n sbaqarff sbe byq-fxbby zrgubqf; ohg gura, V'z yvxr gung. (Gung gbgnyyl jnfa'g jbegu hapvcurevat, jnf vg? Fbeel.)

    ETA: It appears that using rot-13 well with screen-readers should have similar "jump past this spoiler" HTML around it, which doesn't make it much/any simpler to implement.

tags, mod posts, faq update

Previous post Next post
Up