WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Value and prioritization of large-scale things a web site can do for improved accessibility

for

From: Dave Merrill
Date: Apr 17, 2013 12:19PM

Steve, are you saying that ARIA landmarks on static content aren't useful
in general, or just that it's not necessary to link a heading to the parent
container whose content it describes? I assume the second, just making sure
I'm not misinterpreting you.

I hear you about dynamic content. Our customers have to prioritize whizbang
vs accessibility to some degree, and how they do that is really out of our
hands. In the future, it would be great if we could include a set of
styleable and accessible widgets they could use, but for now I need to
focus on page structure tools, as I've said. In any case, many sites value
supposed uniqueness so highly that they'll find some shiny new toys to
sprinkle around anyway.


On Wed, Apr 17, 2013 at 1:59 PM, Steve Green < <EMAIL REMOVED>
> wrote:

> Those survey results correspond with our experience of user testing but I
> would add one more category of blocker, which is dynamic content
> (hide/reveal, tabbed interfaces, lightboxes, carousels etc). ARIA markup
> could help with that, but it is usually going to be specific to widgets
> rather than being in a template.
>
> I don't think that your example of adding ARIA markup to static content is
> going to help anyone.
>
> Steve
>
>