If you’re not using ARIA Landmarks and they’re not required, then how are you making the <div id="footer"> determinable to AT users? #a11y
1
1
@pauljadam with a heading.
1
.@sinabahram You put a heading in the Footer? What does it say "This is the Footer"? Serious question because I’ve never seen one before.
4
@pauljadam It also is a graceful fallback even with role=contentinfo, which is why I always have clients still do it.
1
@sinabahram if you can send me an example I’d like to see if not able to share I understand :)
2
@pauljadam mcachicago.org/Home
2
.@sinabahram footer region identification tells the screen reader user when they enter/focus the region, heading does not tell them that.
4
Replying to @pauljadam
@pauljadam @SinaBahram I don't even see it as #a11y at this point. It is quality of craft. We must aim higher wider greater more inclusive.

Apr 3, 2016 · 4:02 PM UTC

2
Replying to @mholzschlag
@mholzschlag @pauljadam I also agree RE not being #a11y, but I will argue AT still hs a huge responsibility here.
1
1
@SinaBahram @pauljadam I passionately agree that AT (which is us) has significant responsibility and yes, it goes beyond WCAG.
Replying to @mholzschlag
@mholzschlag @pauljadam No other group is so shackled with their entire interaction being mediated through so many layers.
2
1
@SinaBahram we do face very intense challenges. And that is part of the evolutionary and frankly, sexy part of the web to me! 😛 @pauljadam
1
1
more replies