That's right, Amelie has a job. :D Nothing exciting, just a little bit of temporary work over Christmas to help with present funding. But yeah, I start tomorrow (it would have been today, but I have lectures on Mondays so I can't work then). ARGH TOMORROW. I have no idea what I'll be doing, who I should report to and where... This whole job was organised in a rush on Thursday and I had a very brief induction on Saturday. I'm in at the deep end tomorrow morning at 9am sharp. O_O EEP!

In other news, I met Jem, her partner Karl and Katy yesterday :D Decided at the last minute that while Katy was there admiring their new flat, I might as well go down and see what all the fuss was about (and meet everyone all at once, woo) as well. Dragged the boyfriend with me, since I can't drive and navigate at the same time, and he ended up driving. We then got lost because Jem lives in the middle of nowhere the directions we got off some travel site shoved us down a tiny narrow road that was closed instead of down the much easier (and more open) main road. Heh. Anyway, that was fun. :)

Now I can go back to fretting about jobliness tomorrow. ARGH I START IN 12 HOURS AND 20 MINUTES ARGH

...you dream about your script getting its own LiveJournal community. >.<

In case you haven't noticed, I've tried to make this site more accessible since the revamp last week. I had got everything to AAA/priority 3 standards about a year ago, but I got lazy and started using silly things like "click here" as link text and forgetting my accesskeys.

So, I put the accesskeys back in for this layout. When I went to test them, nothing happened. I know they work, since I was able to use them in IE, but in Firefox and Opera every time I tried the key combinations, a menu would popup, an extension shortcut would get activated, etc. etc. etc. (or in the case of Opera, nothing happened. Eh?) Of course, a solution to this is to do what many others have done and use numbers as accesskeys - but I disagree with doing this. Why? Because it's not symbolic enough (to me, at least), and ... I don't know, I just don't like it. I prefer to use letters if at all possible. Besides, the number thing doesn't solve the shortcut problem - I like to use accesskeys on others' sites because I'm lazy and prefer to use keyboard shortcuts than the mouse, but when I went to press ALT + 0 to go back home (or whatever it was), I was once again presented with some options for an extension. Hmph. Seeing as I never use the keyboard shortcuts for those extensions, I tried disabling them, but apparently that's not possible.

Having said that, the site should conform to priority 3/AAA accessibility levels now. The automatic checker at WebXact doesn't seem to like my previous/next page links though, and tells me they don't make sense out of context... I think they do, but I tried changing them to such things as "View more blog posts" and even more detailed sentences but it didn't like those either. I've manually checked everything else and to me it seems fine, but of course many of the accessibility checkpoints are to do with personal preference and/or opinion. I may think those links make sense out of context (they don't have a context anyway... They're pretty much standalone as it is) but that doesn't mean everyone will.

Just a small layout note: I know about the slow/jerky scrolling - this is caused by the transparent PNG background. I will try and change that, but when I tried a solid background, it didn't really work :\ Likewise, I also know about the fact that this centre column looks odd in high resolution/widescreen monitors, since it is fixed width and the rest of the layout is not. Again, I'll try and fix this when I have a moment.