W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2013


From: James Nurthen <james.nurthen@oracle.com>
Date: Fri, 25 Jan 2013 10:33:05 -0800
Message-ID: <5102CFE1.9090805@oracle.com>
To: Sailesh Panchang <spanchang02@yahoo.com>
CC: "'Joshue O Connor'" <joshue.oconnor@cfit.ie>, "'Steve Faulkner'" <faulkner.steve@gmail.com>, David MacDonald <david100@sympatico.ca>, "'WCAG'" <w3c-wai-gl@w3.org>, w3c-wai-pf@w3.org
There are times when the author of the web application has no idea what 
scripting may be running on the application when it is deployed by the 
customer. Any change to the DOM hierarchy adds extra risk. This extra 
risk may make the change infeasible due to the added cost of regression 
testing the change. Adding a simple attribute to an element does not 
present the same risk so may well be preferred in these situations.
When starting with a clean slate of course using an HTML heading (h1-h6) 
is preferred - but we are not always starting with a clean slate. WCAG 
should allow us to meet the guideline so long as the solution is 
accessibility supported.


On 1/25/2013 10:01 AM, Sailesh Panchang wrote:
> For an image with text  styled like a heading, I'd say wrap an h-tag around it.
> It will work for screen reader users.
> Will aria-header work here then instead of h-tag? No need to adjust margins etc. (needed when an h-tag is inserted into the mix).
> Sailesh Panchang
> --- On Fri, 1/25/13, David MacDonald <david100@sympatico.ca> wrote:
> From: David MacDonald <david100@sympatico.ca>
> To: "'Joshue O Connor'" <joshue.oconnor@cfit.ie>, "'Steve Faulkner'" <faulkner.steve@gmail.com>
> Cc: "'Sailesh Panchang'" <spanchang02@yahoo.com>, "'WCAG'" <w3c-wai-gl@w3.org>, w3c-wai-pf@w3.org
> Date: Friday, January 25, 2013, 10:43 AM
> I suggest adapting the heading description paragraph.
> "There are almost no use cases for the use of the aria-header attribute in
> HTML because its semantics are not as rich as the native html headings.
> However, an example of where it may be useful would be where a complicated
> legacy web application is getting updated for WCAG, and the programming is
> dependent on the root nodes of the DOM, which would break the program if
> changed to a native html heading. Placing an aria-heading on it instead of a
> native html heading it would expose the heading to AT and not change the
> value of the node."
> Cheers
> David MacDonald
> CanAdapt Solutions Inc.
>    Adapting the web to all users
>              Including those with disabilities
> www.Can-Adapt.com
> -----Original Message-----
> From: Joshue O Connor [mailto:joshue.oconnor@cfit.ie]
> Sent: January-25-13 10:22 AM
> To: Steve Faulkner
> Cc: David MacDonald; Sailesh Panchang; WCAG; w3c-wai-pf@w3.org
> Hi Steve,
>> OK I would suggest if such a technique is published it should be with
>> warnings about its use.
> We do try, in a 'User Agent Notes' section in our techniques to document
> bugs/known issues with any of the them at time of writing.
> Cheers
> Josh
Received on Friday, 25 January 2013 18:33:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:10 UTC