Logs and Screen Readers

[Connie]

Just wondering if there is anyway to tell if someone using a screen reader is accessing a site from the raw server logs?

[WebSavvy]

Not that I'm aware of there isn't. I have PleaseRead and Jaws, and whenever I use them and visit my own site and then review the log files later, I've never been able to pinpoint a screen reader as anything other than a normal browser user.

There might be something in the referrer tail that I'm not aware of. You might ask this over at Anthony's too, Connie. Vinnie is really involved in WAI so he might know.

[Connie]

Thanks Deb. I have been scouring my raw log the last few days, and the question just poped into my mind.

I will ask at Anthony's.

[g1smd]

The UA details should be visible in the logs.

[Connie]

Originally posted by g1smd
The UA details should be visible in the logs.
I suppose you mean user agent. From what I have found a screen reader will use the default browser, so I don't think UA is the answer. In fact I don't think there is anyway to tell.

[WebSavvy]

That's correct, Connie. A screen reader uses whatever the default browser is on that particular computer.

That's why it's next to impossible to know how many of your site's visitors are using screen readers.

There was some talk a while back about defining a specific user-agent assigned to screen readers ... but, screen readers are dependent upon the browser that's installed on the local machine.

Most screen readers are not stand-alone browsers that would have a specific user-agent.

[Connie]

Never having to use a screen readier I had no Idea about how they worked. I do now.

I think it would be helpful to webmasters is there was someway to identify a screen reader. I guess that would go back to the browser manufacture. If thats the case probably will not happen. At least in my life time.

[WebSavvy]

Some screen readers are better than others. There are some where all you need to do is hover the mouse over the text areas and it will read it to you out loud.

There are others that you must copy and paste the text areas into the screen reader for it to read it to you.

[grungee]

Roughly whats involved in making a site accessable to sight impaired people?

[WebSavvy]

OK, ... roughly ... you need to add ALT text to all images.

Skip links must be added to make the page keyboard accessible for those that are unable to use a mouse or have limited hand mobility (applies to wheelchair bound persons as well).

Links on the page must use tabindex to allow for easy navigation within the page content.

Forms on the page must be web accessible.

Images that flicker must be removed.

Images that convey content must also use the long description attribute.

All tables must use the table summary tag.

Links in a page that open in a new window must warn they open in a new window.

Links in a page must have unique anchor text (words cannot be used twice for two different links pointing to two different URLs).

Abbreviated words must use the acronym tag.

Links must be separated by more than whitespace. They must either have a single pipeline | at the end of the link, or a closing </p> or closing </i>

There's lots more, Tony. You'd have to run your page through Bobby or Cynthia, to find out what your problem areas are.

I spent several months going through my entire site and bringing all of my code up to meet section 508, and AAA Bobby ratings.

The new pages will be up shortly, and you'll be able to see them. I'm excited to get them up, of course ... but we have to make sure everything's been done prior to releasing it.

:)

[grungee]

Does that mean spacer gifs also have to have an alt tag? not just ""

Not sure what a skip link is though?

Is seems to be similar to w3 validation just with some extra work. Its not like coding for phones where its a completely different page, its the same page but with more thorough validation is that right?

[WebSavvy]

Yep, spacer.gifs need to have ALT text too ... not just ""

Proper ALT tags for spacer.gifs would be alt="*"

A skip link is a link that uses a name attribute.

Example, let's say that at the top of the page next to the logo we put in a skip link that says: "Skip to navigation"

The link would be coded as:

<a href="#navigation"></a>

Then, at the beginning of the navigation, you'd have:

<a id="#navigation"></a>

Skip link target areas are the following areas in all web pages:

#navigation
#menu
#content area
#seealso (additional information)
#footer

Yes, it's similar to W3C validation, but with more than "a little extra work" ... it's more like a lot of extra work.

Once you start getting into it, and seeing how many warnings and flags you have -- it'll give you a better idea of what you need to clear.

[Blue]

The technically correct term for a skip link is "named anchor."

[WebSavvy]

Yep, it is that, Blue. :D

Lots of folks just call them "skip links" as do I. When you use "named anchor" you get a big "HUH?" out of most people.

Just like most don't know what an anchor title is either. Then you have to show them ... it's this:

<a href="" title="This is the anchor title">This is the anchor text</a>