Re: Headings and ARIA substitutes

Hi,
I did read Stephen's comment, and realize that those were extremely complex
headings. That is why I did not include this in the COGA thread.

I really just wanted to remind the community that for visual users that
don't see wai-aria roles, states and properties, headings are important and
really the only thing we have.  UA's don't give us heading navigation, but
clear visible heading can really help.

There has been a discussion as to whether you need to use headings if you
already use landmarks. Screen reader users often want one or the other to
reduce chatter. So it is a problem for everyone.

If we could just display and navigate wai-aria roles, states and properties
at the UA level this could be addressed.

That is all.

Wayne

On Thu, Jun 16, 2016 at 9:10 AM, Repsher, Stephen J <
stephen.j.repsher@boeing.com> wrote:

> Hi Wayne,
>
>
>
> I’m confused as to what your email below is in response to…. Could you
> please clarify or point me to the originating discussion?  I ask because I
> too would strongly oppose any downplay in the need for heading navigation.
>
>
>
> Thanks,
>
> Steve
>
>
>
> *From:* Wayne Dick [mailto:wayneedick@gmail.com]
> *Sent:* Wednesday, June 15, 2016 5:22 PM
> *To:* GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
> *Subject:* Headings and ARIA substitutes
>
>
>
> I really depend on headings. It is not my experience that ARIA attributes
> display visibly. I have even tried [aria-label]::before {content:
> attr(aria-label);}. Maybe when user agents start showing ARIA accessible
> names on request, I would be comfortable dropping heading navigation. Until
> then I need headings. This is no debate.
>
> Wayne
>
> Note: Please don't tell me that there is some magic AT that will fix this
> for me. I've probably tried many more ATs than you.
>