RE: Template for Accessible Web Page

>A large, possibly the largest, part of accessibility comes down to  
>using the correct markup for the data you have. You can't simply  
>template that.

I agree with that 100%! No mater what, the final coding should be
accessible. But, sometimes it's good to have a base to start from as
long as the developer understands what ultimately needs to happen for
accessibility. 

>> Also, the form elements I have come across that would require label  
>> tags have them.
>> There is the poll which could use a label tag, but employs the
input's
>> "value" attribute instead.
>
>Which results in a tiny target area for clicks. Labels on radio  
>buttons and checkboxes are probably those which most benefit pointing  
>device users.

There isn't always one way to accomplish "accessibility" (<label> tags)
and using this means is still accessible, but possibly lacks the
"usability" that some would prefer. Even WCAG 2.0 suggests the title
attribute as an additional alternate option. 

>> Which sections did you find to be JavaScript dependant?

>Select element as navigation.

I did find the quicklinks select element to be JavaScript dependent and
this should definitely be avoided if not necessary. But, isn't WCAG
moving away from requiring JavaScript to be disabled? I know the United
States' Section 508 Technical Standards has allowed it for years.

Thanks!

Antonio O. HaileSelassie


-----Original Message-----
From: David Dorward [mailto:david@dorward.me.uk] 
Sent: Monday, March 24, 2008 2:37 PM
To: Haileselassie, Antonio O. (HQ-LM020)[InDyne, Inc]
Cc: w3c-wai-ig@w3.org; M. Urban
Subject: Re: Template for Accessible Web Page

On 24 Mar 2008, at 18:30, Haileselassie, Antonio O. (HQ-LM020) 
[InDyne, Inc] wrote:
>
> Which sections did you find to be JavaScript dependant?

Select element as navigation.

> Also, the form elements I have come across that would require label  
> tags have them.
> There is the poll which could use a label tag, but employs the input's
> "value" attribute instead.

Which results in a tiny target area for clicks. Labels on radio  
buttons and checkboxes are probably those which most benefit pointing  
device users.

> Also, do you have alternate suggestions for more accessible templates?

I'd have mentioned them if I did.

A large, possibly the largest, part of accessibility comes down to  
using the correct markup for the data you have. You can't simply  
template that.

-- 
David Dorward
http://dorward.me.uk/
http://blog.dorward.me.uk/

Received on Monday, 24 March 2008 19:07:04 UTC