W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2012

Re: Concerns with ARIA only indicators for structural elements

From: Sailesh Panchang <sailesh.panchang@deque.com>
Date: Sat, 10 Nov 2012 19:40:10 -0500
Message-ID: <CAJi9Cqqxwa5fKNBO-fFp0AqPuzMi3uEr+a4MuOM0eUU9MzO72Q@mail.gmail.com>
To: Jonathan Avila <jon.avila@ssbbartgroup.com>
Cc: w3c-wai-ig@w3.org
Hello Jonathan,
Many do not know or forget that ARIA should only be used in
circumstances where native HTML markup  is not available.
Sailesh


On 11/9/12, Jonathan Avila <jon.avila@ssbbartgroup.com> wrote:
> With more people embracing the use of ARIA, I am concerned that reliance on
> ARIA only to convey structure will be a problem.
>
>
>
> For example, the ARIA role of heading can be used with the level attribute
> to specify headings on any element.  When a page is viewed without style
> sheets or with a custom style sheet all heading levels would likely appear
> the same  without a change of size that you would normally get from using
> HTML heading structural elements h1, h2, h3, etc..
>
>
>
> I believe this could violate WCAG 2 SC 1.3.1 Information and Relationships
> as there is no differentiation of headings unless a custom style sheet with
> CSS for the heading and level roles was implemented.
>
>
>
> Do people see this as a user agent issue or a WCAG 2 violation?
>
>
>
> Jonathan
>
Received on Sunday, 11 November 2012 00:40:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 11 November 2012 00:40:37 GMT