If you鈥檙e not using ARIA Landmarks and they鈥檙e not required, then how are you making the <div id="footer"> determinable to AT users? #a11y
1
1
.@sinabahram You put a heading in the Footer? What does it say "This is the Footer"? Serious question because I鈥檝e 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鈥檇 like to see if not able to share I understand :)
2
.@sinabahram footer region identification tells the screen reader user when they enter/focus the region, heading does not tell them that.
4
@pauljadam @SinaBahram why else create new semantics if they don't provide better reach into the features and languages we require?
3
1
@mholzschlag @pauljadam The problem is a classic one in computer science. Search VS Insertion.
1
Replying to @SinaBahram
@SinaBahram @pauljadam exactly my point. It's a classic problem@ We should have classic answers to look too at least for inspiration yes?馃槂

Apr 3, 2016 路 4:04 PM UTC

4
Replying to @mholzschlag
@mholzschlag @pauljadam A complete re-rendering of the interface based on user intent is required with lossless semantic transformation
1
1
@SinaBahram @pauljadam now you're hitting on something really interesting. Not responsive design. Responsive user agents.
1
Replying to @mholzschlag
@mholzschlag @pauljadam Well, if you nat to get into it. Yes, we do. It's called complete reformatting of the interface on the fly.
1
Replying to @mholzschlag
@mholzschlag @pauljadam It's what we do with datastructures. Hashes rock insertions, but suck at discovery. Lists rock discovery.
1
Replying to @mholzschlag
@mholzschlag @pauljadam We don't apply these optimizations of intent to UX. personalization doesn't even scratch the surface.
1