E-mail List Archives

Search E-mail List Archives for

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

From: paul.creedy
Date: Mon, Jun 28 2004 4:39PM
Subject: Re: WebAIM Discussion List Digest 25.06.2004.
No previous message | Next message →

I've just started my first attempt at CSS layout with XHTML.  I've also tried to add accesskeys to the common menu items. 
 
It was hard going at first and XHTML gave me loads of errors which I think I've now identified.  Next I want to improve accessibility.
 
I'd welcome any suggestions on improving it's accessibility.
 
The site is here at the moment: http://d476047.r39.rcthosting.com/
 
Paul Creedy
= EMAIL ADDRESS REMOVED = wrote:
WebAIM Discussion List Digest 25.06.2004.------------------------------------------------------------------------From: = EMAIL ADDRESS REMOVED = ject: Re: Intro and questionDate: Thu, 24 Jun 2004 09:22:03 -0600Check out the CSS Zen Garden at www.zengarden.com . There are dozens ofbeautiful and accessible web designs on this site. When you constructyour site using CSS, separating presentation from content, there is noneed for two sites.Katy Whitelaw>>> = EMAIL ADDRESS REMOVED = 6/23/2004 3:03:14 PM >>>Another caution in developing a separate version is that many timestheseparate version is developed for screen reader users. This is not theonlydisability community who use the web. So a separate "accessible" sitemightnot be truly accessible, it could end up just being a screen
readerversion.The site might still be inaccessible for other audiences.A resource which might help, especially if you need to justify yourdecision*not* to maintain two sites, is "Myth: Just Add a Text-Only Version"in"Understanding Web Accessibility" in the book "Constructing AccessibleWebsites.""Constructing Accessible Websites" by Jim Thatcher, Cynthia Waddell,Shawn Henry, Sarah Swierenga, Mark Urban, Michael Burks, Paul Bohman,Publisher: APress; Reprint edition (July 14, 2003), ISBN: 1590591488

From: Chris Price
Date: Mon, Jun 28 2004 6:40PM
Subject: Re: WebAIM Discussion List Digest 25.06.2004.
← Previous message | Next message →

Paul

Providing access keys is not a straightforward accessibility issue.

For one, there is some debate as to whether they are useful or not.

Not all browsers support them and the use of letters can be problematic.
Also, in your guide to access keys your instruction is to press alt+ whereas
on the Mac you press control+.

Is the link in the top left a permanent fixture? If so, its a bit too
prominent. After all, your site is about a community not web accessibility.
Likewise, the heading Navigation makes the page a little mechanic. Why are
NEWS and EVENTS navigation when HOME and LEISURE aren't.

Talking of headings, you haven't got any on the home page. That's an
important accessibility issue as it gives the page structure.

The titles on your 2 topic links are wasting my time telling me something
that's totally obvious. If you want to tell your visitor they're links you
could just underline them.

As well as accessibility, have you considered usability issues such as: when
your in Leisure, the LEISURE button's behaviour changes. Once I'm in
Leisure, there are no clues as to where I am.

Jakob Neilsen's alertbox is excellent for tips on usability.
I found
http://e-government.cabinetoffice.gov.uk/Resources/WebHandbookIndex1Article/
fs/en?CONTENT_ID=4000092&chk=XHiT3L worth looking at re: access keys and
accessibility in general.

If you're serious about XHTML you might want to try building to XHTML strict
if only because it makes you disciplined in your coding.

Good look with the site, its got a good feel about it.

--
Chris Price
Choctaw Media Ltd
Choctaw.co.uk

On 28/6/04 11:35 pm, "paul.creedy" wrote:

> I've just started my first attempt at CSS layout with XHTML. I've also tried
> to add accesskeys to the common menu items.
>
> It was hard going at first and XHTML gave me loads of errors which I think
> I've now identified. Next I want to improve accessibility.
>
> I'd welcome any suggestions on improving it's accessibility.
>
> The site is here at the moment: http://d476047.r39.rcthosting.com/
>
> Paul Creedy

From: Jon Gunderson
Date: Tue, Jun 29 2004 8:07AM
Subject: Re: WebAIM Discussion List Digest 25.06.2004.
← Previous message | Next message →

Here is an example otf a website that supports enabling and
disabling acceskeys.

http://ncpad.rehab.uiuc.edu

Jon


---- Original message ----
>Date: Tue, 29 Jun 2004 01:35:55 +0100
>From: "chris.price"
>Subject: Re: [WebAIM] WebAIM Discussion List Digest 25.06.2004.
>To: "WebAIM Discussion List"
>
>
>Paul
>
>Providing access keys is not a straightforward accessibility
issue.
>
>For one, there is some debate as to whether they are useful
or not.
>
>Not all browsers support them and the use of letters can be
problematic.
>Also, in your guide to access keys your instruction is to
press alt+ whereas
>on the Mac you press control+.
>
>Is the link in the top left a permanent fixture? If so, its a
bit too
>prominent. After all, your site is about a community not web
accessibility.
>Likewise, the heading Navigation makes the page a little
mechanic. Why are
>NEWS and EVENTS navigation when HOME and LEISURE aren't.
>
>Talking of headings, you haven't got any on the home page.
That's an
>important accessibility issue as it gives the page structure.
>
>The titles on your 2 topic links are wasting my time telling
me something
>that's totally obvious. If you want to tell your visitor
they're links you
>could just underline them.
>
>As well as accessibility, have you considered usability
issues such as: when
>your in Leisure, the LEISURE button's behaviour changes. Once
I'm in
>Leisure, there are no clues as to where I am.
>
>Jakob Neilsen's alertbox is excellent for tips on usability.
>I found
>http://e-government.cabinetoffice.gov.uk/Resources/WebHandbookIndex1Article/
>fs/en?CONTENT_ID=4000092&chk=XHiT3L worth looking at re:
access keys and
>accessibility in general.
>
>If you're serious about XHTML you might want to try building
to XHTML strict
>if only because it makes you disciplined in your coding.
>
>Good look with the site, its got a good feel about it.
>
>--
>Chris Price
>Choctaw Media Ltd
>Choctaw.co.uk
>
>On 28/6/04 11:35 pm, "paul.creedy"
wrote:
>
>> I've just started my first attempt at CSS layout with
XHTML. I've also tried
>> to add accesskeys to the common menu items.
>>
>> It was hard going at first and XHTML gave me loads of
errors which I think
>> I've now identified. Next I want to improve accessibility.
>>
>> I'd welcome any suggestions on improving it's accessibility.
>>
>> The site is here at the moment:
http://d476047.r39.rcthosting.com/
>>
>> Paul Creedy
>
>----
>To subscribe or unsubscribe, visit
http://www.webaim.org/discussion/
>


Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
MC-574
College of Applied Life Studies
University of Illinois at Urbana/Champaign
1207 S. Oak Street, Champaign, IL 61820

Voice: (217) 244-5870
Fax: (217) 333-0248

E-mail: = EMAIL ADDRESS REMOVED =

WWW: http://cita.rehab.uiuc.edu/
WWW: http://www.staff.uiuc.edu/~jongund

From: Chris Price
Date: Tue, Jun 29 2004 11:04AM
Subject: Re: WebAIM Discussion List Digest 25.06.2004.
← Previous message | No next message

On 29/6/04 3:03 pm, "jongund 25.06.2004." wrote:

>
> Here is an example otf a website that supports enabling and
> disabling acceskeys.
>
> http://ncpad.rehab.uiuc.edu

Not very pretty is it? Nor is it standards compliant. Nor does it pass
accessibility level 3.

I'd have thought websites dealing with disabilities would be leading the way
but I've seen other such websites that fail badly.

--
Chris Price