4 ms·
Well, yes (build for people) and no (stuff should be technically correct, as well). For instance, the WGAC 2.0 guidelines require that HTML be valid, and if a
by stevejalim 14y ago
Well, yes (build for people) and no (stuff should be technically correct, as well).
For instance, the WGAC 2.0 guidelines require that HTML be valid, and if a client wants WGAC 2.0 compliance (even A level, not AA), the site's gotta validate [1].
[1] http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-parses.html http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-pars...
- zalew 14y agounless you are doing it for bureaucracy's sake (public sector, etc.), do what works, not what some ink on paper from half a decade ago says, otherwise it's CYAE[1]. http://www.alistapart.com/articles/tohellwithwcag2 http://www.alistapart.com/articles/tohellwithwcag2 "To Hell with WCAG 2" (2006) [1] cover your ass engineering
- DanBC 14y ago> do what works Too many people build something that works for them; on their browser version, at their screen size, on their OS. That's especially harmful for accessible sites.