So you're wondering what I look like right? (No? - Oh. Well anyway...)

Left, Simon Peg. Right, me (a tiny bit drunk)

Voter aphethy? Not on my watch!

Sign the petition, or the kitty gets it!

http://petitions.pm.gov.uk/govaccessibility/

Sorry!

What?

There will be a cessation of verbal violence, whilst I try to get on top of some code upgrade related work.

What with all the browser upgrades and whatnot, there's no rest for this wicked soul. :(


Back with more opinionated rubbish as soon as the warm, brown and smelly sea I stand in subsides to a level below my snorkel once more.

New Phishing bug found in IE7?

Looks like it. I don't know how I did it, but I got the address bar showing my previous address, and the the current page to stay put. This was a random accident, and I'm still trying to reproduce, but it did happen...

The page was fully functional, and according to the browser, fully loaded.

Screen shot:



Obviously I could mock up anything in photoshop, But if you believe me (and its true) you can see that I didn't just type in the google address, as its got its icon next to it...

Hmmm.

Sort it out M$

Duvet day...

So I'm feeling a bit grim. Flu. Or a 'Man Cold', as the wife would say. Anyway I've spotted an assortment of handy links today.

I don't have the mental energy to say much about them, but they all interested me....:

http://justaddwater.dk/2006/10/23/captcha-usability-humane-alternative-to-captcha/

Have just seen some nasty spam over on the Accessify forum, and then came across this a couple of minutes later, I thought this is the kind of thing they need to be implementing. Yes there's a problem if you have js switched off. But in which case I think you could force the user to go through a little, convoluted email verification process (IF they had no JS)...

Then on a pet subject of mine, browser zooming, AlistaireC as a great, in brief, comparison of the major browsers:

http://alastairc.ac/2006/11/browser-zoom-comparison/

After winging at length about the IE7 zoom being bug ridden, my issues with it seem to have been fixed now. i.e. it now evaluates hit areas of elements correctly during mouseover events when the page is zoomed. Well done M$. Don't say I don't thank you when you get things right. Eventually.

I'm off to whimper some more....

Kapp Notes: Gadgets, Games and Gizmos: Talking Web Sites

Kapp Notes: Gadgets, Games and Gizmos: Talking Web Sites


Here's another intresting take on uses for Talklets

There have been several inventive suggestions as to what it could be useful for: tesing site for accessibility, increasing "stickability" (as I can testify to), creating alternative format versions of publications,...

All good stuff.

Response to comment on "Is the AJAX accessibility problem, really a problem?"

Well I got a great full fat response to my brief take on the screen reading
problem with AJAX. I'll start by mindlessly reiterating my initial stance,
filling it in a bit, and then reply to each major point in turn, and see
if I come to any conclusions... First I should point out that I agree with virtually everything said in said response. So this is a subjective positioning, more than a denial of what was said.

IMO (never a good start to a sentance...) trying to say 'The Web"
must restrict its methods to accomodate old versions of screen readers is
unreaslistic, and impractical. Yes the notion is moot, even
stipulated by many regulations and guidelines, but we live in a real world,
and sometimes guidelines are inaccurate, or become so as the world around them
evolves. AJAX is here. It will only increase from now on. Yes making it
accessible is great, but some are saying it can not be accessible at all
(because it relies on users upgrading their screen readers, and that
is 'inaccessible'), therefore it is bad... My point is, all the accessiblity
guildines, and regulation litigation in the world can not hold back
inovation on the web. We (screen reader developers, webmasters and developers,
web 2.0 content creators - i.e. users) simply have to keep up. Winging
won't help (at the risk of offending, I hope I don't, it's not intended to).

TV came first. Then subtitles, and now, many decades after TV became
near ubiquitous within the home, we're starting to see commentary services for
VI viewers (previous to this, TV was less accessible than most AJAX
sites). TV media outlets are not forced and are barely encouraged to
offer their content in audio only and visual only
formats. This would be analgous, to me, to the
imposition on Web 2.0 to be backward compatible with old screen
readers, OR (as it is impossible is some cases) offer all content in a format
that is. No, we (those previously mentioned) must demand and/or
create new services for minority users, to make the new tech accessible,
and expect that to involve the development of new thech.

I know this is tantermount to blasphemy in the field I work. But it is not an
absolute. There should be encouragement to do what we can, where
possible and practical, right now. But there should not be laws mandating
this. IMO. Looking at my stance, it seems rather right-wing, 'let the
minorities get their goodies, when someone can be bothered the help them'.
This is far from the case. I'm a developer AND user of scren reader tech.
So I'm putting the onus on me. But how silly would it be to put all the
legal onus on the screen reader companies. Why not make it law that
Freedom Scientific make their upgrade free, in order to make the latest web
standards and feautres/techniques compatible with their stuff (inc
javascript and AJAX)? Because it wouldn't be fair, or practical...

Should we this all as a problem was my question. Note the question
mark in the title. No I don't think its a problem, I think its an exciting
future for screen reader users, as our screen reading tech improves and
evolves to make use of web 2.0. 

</rant>

 Problem 1: You can upgrade up to two consecutive versions of JAWS if
you're already covered by a Software Maintenance Agreement. But buying such an
agreement is expensive, to the tune of
$180
for JAWS Standard and $260 for JAWS Professional.

There are OSS solutions being developed. And JAWS chageing too much is hardly
a reason to impose laws on billions of web users and hundreds of millions of
web developers. This should raise questions though. Like, should the
government be offering larger allowences to VI workers and students?

Problem 2: Upgrading to a version of JAWS released before Vista
entered the Release Candidate stage and that is
not
optimized for Internet Explorer 7 is not going to be terribly
appealing even to those who can afford it.

This seems very tenuous. Yes its a real life pain, but Vista is to all of
us... Not just those of us useing AT. 

 Problem 3: What about other screen reading and voice browsing software?
Virgo? Window-Eyes? Home Page Reader? HAL? Edbrowse? Orca? Gnopernicus?
ZoomText? Opera? VoiceOver? Thunder? This isn't just a JAWS issue. Screen
readers are extremely complex software
(ever
tried one?) and asking someone to switch to a different screen
reader is not dissimilar to asking someone to use a new operating system. Oh
yeah, and if you go for a commercial screen reader, switching can be even more
expensive than upgrading. JAWS Standard will set you back $895.

Same applies to all of them. If I bought JAWS version 1 and expected all of
todays software and online content to be accessible via it, I'd be sadly
disapointed, and naive (again at the risk of offending, which I'm not trying
to -  its just MHO). And again, the rest of the world should not be
hounded for the cost one company sets for their product, no matter they cater
to. Plus, as you point out yourself, they're not the only solution. As
for have I tried one, I have made two, and am useing one now.

Problem 5: W3C's
Web
Content Accessibility Guidelines explicitly request that we attempt
to accommodate those users who "have an early version of a browser, a different
browser entirely, a voice browser, or a different operating system". Obviously,
even good principles should rarely be taken to extremes. But from an ethical
perspective, surely the limit of our compromises on behalf of outdated user
agents ought to be what we might reasonably expect users to do (for example,
continuing to use the expensive screen reader of their choice), not what will
make us the most money (for example, going out of our way to support Internet
Explorer 6)?

But reasonably, they HAVE to expect to update their software, if the menas of
creating a displaying content evolves beyond the capabilities of their current
technology. This is far from 'nice', but is practical.

Liked your list of links.

I may come back to this when I have more time.

Cheers 

Is the AJAX accessibility problem, really a problem?

I've been looking at the issue of AJAX and dynamic content updating, with regards to screen reader users. And my conclusion is, if there is a problem its this: You've got an old version of JAWS? Then upgrade...

End of.

I've heard from many folk reporting to be in the know regarding this issue that "there's no way for the user to know if the content is updated" with panic in their eyes. Well actually it turns out that the issue was with JAWS using a buffer to store the DOM, which only updated after page refreshes and loads. Well that wasn't the best way of doing things, and so they've changed that.

I have good sight, but poor reading skills due to abnormal neurological morphology. My brains a funny shape. Not drastically so, but enough to make reading a pain. Its called dyslexia, and I'm far from alone. 10%+ of the population are effected. I realized something today. I had been missing bits of info updating magically on the screen, through new funky use of newly famed AJAX trickery. But something struck me. I soon learned to look for it. Yes I know many screen reader users can't "look" for it exactly, but the can use their tech to scan for it. And they, like I, will soon learn to do this...

So if the problem is solved, as long as JAWS users upgrade, and users continue to learn to use the evolving tech they're confronted by, then there really isn't such a problem is there?

Or is there?

Please do comment. I'm looking for answers still...