Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The <code>&lt;aside&gt;</code> element is not supported by IE 8 and older. This means that any styles you set on it are lost in those browsers. You can partially work around this by using JavaScript code that “teaches” the element to them, but is this all worth the gain? What exactly is the expected gain?</p> <p>Logically, the use described does not match the HTML5 semantics. The descriptions there are vague, but I don’t think an error message can be characterized as <em>tangential</em> when it is displayed and relevant; it’s really the key content then. It is not <em>separate</em> from the rest of the content; instead, it expresses vital information about it.</p> <p>An advertisement would be a candidate for <code>&lt;aside&gt;</code>, and so would an anecdote, or a history note, or generally content that is not necessarily by any means but has some connection with the main content.</p> <p>I have not seen any evidence of any software such as search engines or browsers or browser add-ons actually making use of <code>&lt;aside&gt;</code> markup. Just speculation about what might be done.</p> <p>I think there’s a fundamental flaw in the overall design, making the question about element semantics even more theoretical. What happens when CSS <em>or</em> JavaScript is disabled? Right, the user always sees the error message, even when he has not entered input at all or the input is all correct.</p> <p>A better approach, assuming that this is about errors detected in <em>client-side</em> code, is to keep the error message texts just in JavaScript strings. When an error has been detected, a new element is added, or existing element content is modified, to make an error message available; and it would then be wiped out when the error has been corrected. (No need to rely on CSS here.)</p> <p>This way, the error message could be placed before the field, on the right of it, or below it. It would not matter much which elements you use for it (search engines won’t see it, and browsers are hardly expected to do anything special with it on their own), but <code>&lt;div&gt;&lt;strong&gt;...&lt;/strong&gt;&lt;/div&gt;</code> would probably a good choice.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload