On 21/06/2022 02:06, Juan Manuel Macías wrote:
Max Nikulin writes:
I would like to stress that styles can not be a rescue in some
important cases. Let's leave aside ad hoc final tuning of formatting.
In the case of HTML export there are still <img alt="Description"> and
<a href="..." title="Description"> attributes that are namely
per-object, not part of style.
You are right, but my question is: Could there be a similar use case
within inline special blocks? Keep in mind that this (for now,
hypothetical) element type would be intended only for very short
segments of text within the paragraph. I don't find a scenario where
it's worth overloading that with options and attributes, IMHO.
Juan Manuel, your answer is not clear for me. Direct formatting is
another issue. There are cases when attributes are part of *content*,
not formatting. If alternative text for images and description of links
are not convincing, there is e.g.
Org document may be exported as
<abbr title="HyperText Markup Language">HTML</abbr> file.
Do you consider inline special blocks solely for formatting and only for
the kind of it that may be expressed through styles? Then attributes for
inline objects should be another feature with its own syntax.
in html:
<name>contents></name>
Concerning <name> vs. <span class="name">, is it the same for
assistive technologies like screen readers to add
<strong>text</strong> (or <b>text</b>) and <span
class="strong">text</span> with "font-weight: bolder;" in CSS?
"<name>contents></name>": it was my confusion, sorry. I already explained
it here: https://list.orgmode.org/8735g0tnoh....@posteo.net/
I am unsure that <name>content</name> should not be supported at all.
However I admit that difference of the following code may be
insignificant in reality:
<strong class="alert">Do not do it!</strong>
vs.
<span role="strong" class="alert">Do not do it!</span>
