Strict w3c validation allows any data-* attributes, and any class. Directives can be applied to DOM elements with any of: <tag directive-name> <tag data-directive-name> (*) <tag x-directive-name> <tag directive_name> <tag x_directive_name> <tag data_directive_name> At least the data- one is fully W3C compliant (provided you declare HTML5 doctype). So the following code validates (the attribute name, … Read more
“Normative” means that it’s an official formal part of the specification; non-normative means that it’s there to be helpful and aid understanding, but you can’t appeal to it in a court of law (so to speak). I’m afraid that specifications from standard bodies like W3C, just like legal contracts, are written in formal language that … Read more
W3C has a great post on the subject of CSS units. In particular: cm: Not recommended for screen / recommended for print The so-called absolute units (cm, mm, in, pt and pc) mean the same in CSS as everywhere else. A length expressed in any of these will appear as exactly that size (within the … Read more
Update 2023-08-27 AVIF images in Edge Canary 118 seem to have been disabled again. Update 2023-07-17 AVIF images are now showing up in Edge Canary. Tested on: Edge 117.0.1981.0 (Official build) canary (64-bit) Windows 10 22H2 (19045.3208) http://www.amorosity.com/Slingblade/ Update 2023-02-20 @ 22:23 Alex Russell, Microsoft Partner PM on the Edge team and a Blink API … Read more
Leave out the <p> tag unless the content of your table cell is truly a paragraph. It’s certainly possible to have paragraphs in tabular data, and in that case a semantic <p> would be appropriately placed. But for the common table with data in the cells eg. numbers, names, etc., don’t include the <p>.
On this page: http://blogs.msdn.com/b/mike/archive/2008/11/13/time-vs-time-taken-fields-in-iis-logging.aspx it says: The Time field is quite straightforward: it specifies when the log entry was created. Note that this is not always the same as when the log entry actually gets written to the log, as buffering can occur for some request/response scenarios. Therefore, you are correct in thinking that the … Read more
To me, linebreaks should only be used inside paragraphs to indicate a new line. Adding line-breaks between paragraphs was used back in the day, when HTML looked like Chop Suey and the semantics of the HTML document looked like someone from preschool used Dreamweaver. I personally rely on margins and padding for content separation, if … Read more
Semantically correct IMHO would be to keep an empty cell really empty. However, I, too, fill empty cells with s for pragmatic reasons. As for screen readers, I’ll have to make an educated guess: Empty nodes will likely not be read, because HTML consists mostly of whitespace text nodes, which readers ignore, and I assume, … Read more
WCAG 2.0 is divided into three conformance levels (A-AA-AAA) because the success criteria are organised based on the impact they have on design or visual presentation of the pages. The higher the level, the more restraining it becomes on design. For example, let’s take guideline 1.4 (Distinguishable), which is about making it easier for users … Read more
If you are writing a form in a meaningful (read: semantic) way, you will want the flow of text to lead to the element: <form> <p><label for=”firstName”>Please enter your first name:</label><input id=”firstName” type=”text” /></p> </form> An even better way is to treat your form like a mad-libs script: <form> <p>Hello. My <label for=”firstName”>name</label> is <input … Read more