- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Sun, 15 Jan 2017 00:20:30 +0000
- To: Wayne Dick <wayneedick@gmail.com>
- CC: GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
> Why is it worth asking authors to make alt text and it is not important to ask authors to supply semantic markup so that assistive technologies can use to identify points of need for visual assistance. Alt text is there or not, the structure of HTML & CSS comes in all sorts of shapes and sizes. There's nothing wrong with the code on the W3C wiki page, it is somewhat complex but that heading has two things within it, so having elements nested inside is appropriate. There are far more complex frameworks, check the HTML on Gmail for *real* nesting. Companies are not going to replace millions of dollars of frameworks because they nest elements more than we like. I've been thinking about methods for over-riding styles, and a few things stand out: - Over-riding CSS is not strong or nuanced enough, for example, you can't make things display linearly without showing everything that should be hidden. - You can't predict across websites how nested their HTML is or how specific their styles are. - Applying an external stylesheet (e.g. with a bookmarklet) will fail completely when people use CSP headers [1] to block external styles (as Github does). I think the way forward is to use a browser extension to override styles with JavaScript, or extract the content for re-display. (Or some combination of both.) That enables you to apply inline styling (with !important if needed), choose elements more carefully, and turn on/off certain features. It is interesting reading through the code of an open source extension [2] that does a similar job to Safari's reader mode. It checks for articles by finding the element with the most direct children that are paragraphs... probably a good heuristic! There is work to do to establish what sites should be responsible for (at the technique level), but it is worth considering what the user-agent end can do first. Kind regards, -Alastair 1] https://content-security-policy.com/ 2] https://github.com/ZachSaucier/Just-Read/blob/master/content_script.js
Received on Sunday, 15 January 2017 00:21:06 UTC