E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 5 (In chronological order)

From: Terrill Thompson
Date: Wed, Mar 18 2009 11:55AM
Subject: Accessible NCAA Tournament Bracket 2009
No previous message | Next message →

Hi All,

Please spread the word if anyone is looking for an NCAA tournament bracket
that doesn't require eyesight and a mouse:
http://terrillthompson.com/ncaa

Now in its third year, this has become an annual tradition. Partly it's just
a fun project, but I also see it as a testing ground for making a
challenging interface accessible. My approach at making the bracket
accessible is to break it into smaller components: Each region contains
multiple rounds, and each round is a list of games, where games are lists of
two teams. Level 2 and 3 headings identify each region and round
respectively, which combined with the list structure make it fairly easy to
navigate for screen reader users. I then use CSS to stylize this so it looks
like a bracket for visual folks.

I'm not 100% convinced that this is the best possible approach, but it seems
to work ok for now. If anyone has ideas for an alternative approach, or for
enhancements to this approach, please let me know.

Cheers,
Terry

Terrill Thompson
Technology Accessibility Specialist
DO-IT, Accessible Technology
UW Technology Services
University of Washington
= EMAIL ADDRESS REMOVED =
206/221-4168

From: Simius Puer
Date: Thu, Mar 19 2009 3:35AM
Subject: Re: Accessible NCAA Tournament Bracket 2009
← Previous message | Next message →

Hi Terry

Great to see such accessibility effort going into a not-for-profit project!

A few thoughts:

- The nav with anchors (which are not present btw) needs to be repeated
between regions, or possibly better to have a single instance the user has
some method to jump back to
- The data for each section is quite heavy. I imagine the users with
screen readers may benefit from some additional sub-navigation, say, to jump
between rounds.
- The maximum line length needs to be defined (talking about the
text-pages here which are currently 'liquid') and set according to
best-practice for readability. I know you are focusing on non-sighted users
primarily but overly-long lines reduce the readability for sighted users,
especially those with tunnel-vision (or even if they are just using a
high-res monitor)
- Check for XHTML validation results as you have a couple of minor errors
which might cause issues.

The help page is missing (I realise this is probably a work-in-progress) but
that also highlights the lack of a custom 404 page. Hopefully you'll never
need one but it's always a good idea to have one to assist those that do end
up there as the default one is inherantly inaccessibly and offers poor
usability and user-experience too.

Have a good day.

From: Cliff Tyllick
Date: Thu, Mar 19 2009 6:35AM
Subject: Re: Accessible NCAA Tournament Bracket 2009
← Previous message | Next message →

Andrew Hart (Simius Puer) said:

Hopefully you'll never need one [a custom 404 page] but it's always a good idea to have one to assist those that do end up there as the default one is inherently inaccessible and offers poor usability and user-experience too.

Cliff Tyllick responds:

I have often wondered why 404 pages typically do not do a better job of giving people links to key portions of the site. Most don't even reproduce sitewide navigation. Here's a typical message:

"Page Not Found

You may have typed the address incorrectly or followed a broken link on this or another site. Visit our home page to access the major areas of our Web site. Direct technical questions about our site to [our webmaster's e-mail]."

Why not make it a habit to add a useful set of links to the 404 page? Based on error reports, it's even possible to figure out what information is likely to be most helpful to the majority of folks who have been getting 404 errors recently. Or you could explain recent major changes and accommodate customers affected by them:

"Oops! The page you are looking for, [bad url], does not exist.

If you are looking for [content recently moved], try [new url of a key page]. We have recently reorganized that section of our site.

You may also use these links to return to our site:

[list links to main navigational pages here]"

Doesn't that make sense?

Cliff Tyllick
Web development coordinator
Agency Communications Division
Texas Commission on Environmental Quality
512/239-4516
= EMAIL ADDRESS REMOVED =
>>> Simius Puer < = EMAIL ADDRESS REMOVED = > 03/19/09 4:31 AM >>>
Hi Terry

Great to see such accessibility effort going into a not-for-profit project!

A few thoughts:

- The nav with anchors (which are not present btw) needs to be repeated
between regions, or possibly better to have a single instance the user has
some method to jump back to
- The data for each section is quite heavy. I imagine the users with
screen readers may benefit from some additional sub-navigation, say, to jump
between rounds.
- The maximum line length needs to be defined (talking about the
text-pages here which are currently 'liquid') and set according to
best-practice for readability. I know you are focusing on non-sighted users
primarily but overly-long lines reduce the readability for sighted users,
especially those with tunnel-vision (or even if they are just using a
high-res monitor)
- Check for XHTML validation results as you have a couple of minor errors
which might cause issues.

The help page is missing (I realise this is probably a work-in-progress) but
that also highlights the lack of a custom 404 page. Hopefully you'll never
need one but it's always a good idea to have one to assist those that do end
up there as the default one is inherantly inaccessibly and offers poor
usability and user-experience too.

Have a good day.

From: ben morrison
Date: Thu, Mar 19 2009 6:40AM
Subject: Re: Accessible NCAA Tournament Bracket 2009
← Previous message | Next message →

On Thu, Mar 19, 2009 at 12:33 PM, Cliff Tyllick
< = EMAIL ADDRESS REMOVED = >wrote:

> Andrew Hart (Simius Puer) said:
>
> Hopefully you'll never need one [a custom 404 page] but it's always a good
> idea to have one to assist those that do end up there as the default one is
> inherently inaccessible and offers poor usability and user-experience too.


some 404 info...

http://www.plinko.net/404/default.asp

--
Ben Morrison

From: Simius Puer
Date: Thu, Mar 19 2009 7:05AM
Subject: Re: Accessible NCAA Tournament Bracket 2009
← Previous message | No next message

Hi Cliff

It does make perfect sense to improve on the standard response...and lets
not blame the server here, the 404 is simply a generic error response. Many
developers overlook these and many clients don't know to ask for one so they
fall through the cracks.

I'd recommend reading "The Perfect 404" by Ian Lloyd over on AListApart. [
http://www.alistapart.com/articles/perfect404]. How complex you get depends
on the website you manage but this covers everything from the basics though
to some advanced techniques.