Re: Adding ARIA role="presentation" to a table based CMS

Hi Gez,

The technique works for most of the sites I've seen. Generally if a form 
is lined up by using a <table>, each form control has its own <tr>. 
Threfore the contents will be exposed to ATs in the correct order.

- Aaron



From:
"Gez Lemon" <gez.lemon@gmail.com>
To:
joshue.oconnor@cfit.ie
Cc:
Richard Schwerdtfeger/Austin/IBM@IBMUS, "w3c-wai-pf@w3.org PF" 
<w3c-wai-pf@w3.org>, "W3C WAI-XTECH" <wai-xtech@w3.org>
Date:
11/05/2008 04:53 AM
Subject:
Re: Adding ARIA role="presentation" to a table based CMS




Hi Josh,

2008/11/5 Joshue O Connor <joshue.oconnor@cfit.ie>:
>
> Hi Rich,
>
>> That is the intent of aria-presentation and it is much easier than 
trying
>> to reproduce the desired behavior with style sheets for existing
>> implementations.
>
> Yes. I think this would be *very* useful for organisations who are
> locked into using a CMS solution that outputs its content or mods into
> tables (for the whatever reason). Rather than is codifying poor practice
> I think it will improve the user experience in this case.

I can see how role="presentation" will be useful in ensuring that
presentational information isn't mapped to an accessibility API, but
it's important to remember that it doesn't stop the issues associated
with using markup incorrectly. For example, the biggest issue of using
tables for layout is when they don't linearise, and adding a role of
presentation isn't going to help reorder the content so that it does
linearise correctly.

Cheers,

Gez


-- 
_____________________________
Supplement your vitamins
http://juicystudio.com