[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Rationale for <alt> inside <image>
(copying this to data-lightweight as it also affects that standard) That may explain why there is an <alt> instead of @alt, not why <alt> is inside <image> and can itself contain a <ph> which can contain an <image> etc. If <alt> would be part of <fig>, there would not have been any problem with any rendering system, just like there is no problem with <title> at the top of the <fig>, where lots of PDF renderings move the <title> to a caption below the image. To add to the problem, LwDITA is copying the same situation, with <alt> inside <image>. With <image> essentially being an inline element and <alt> a block element, this implies that mixed content makes its way into a standard that tries to do away with it altogether. Also, there is an irrational mismatch between the semantic markup of <image> and its modern multi-media counterparts <video> and <audio>: those elements have separate child elements for setting various parameters (track, controls, source, loop, etc - none of which have translatable content), where <image> has attributes for all such configuration data plus <alt> as a child element. A consistent semantic markup for multi-media items would use similar items for similar meanings. If <video>, <audio> and <image> are all seen as part of <fig>, they should all have a similar internal structure and markup. My suggestion would be: <element name=“fig”> <optional> <element name=“title”/> </optional> <optional> <element name=“alt”/> </optional> <choice> <element name=“image”> <attribute name=“href”/> <attribute name=“height”/> <attribute name=“width”/> <attribute name=“scale”/> </element> <element name=“video”> <attribute name=“source”/> <attribute name=“height”/> <attribute name=“width”/> <attribute name=“scale”/> <attribute name=“controls”/> <attribute name=“autoplay”/> <attribute name=“muted”/> <attribute name=“track”/> <attribute name=“poster”/> </element> <element name=“audio”> <attribute name=“source”/> <attribute name=“controls”/> <attribute name=“autoplay”/> <attribute name=“muted”/> <attribute name=“track”/> <attribute name=“poster”/> </element> </choice> </element> To comply with various accessibility standards, the <alt> would be made mandatory and would, obviously be required for video and audio as well. Jang F.M. Graat Smart Information Design Amsterdam, Netherlands
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]