[TYPO3-project-formidable] FORMIdable & XHTML

[Jerome Schneider]

BTW, for testing purposes, you can change the _getHtmlId() method of 
class mainrenderer

http://doc-formidable.ameos.com/0.7.71/class_8mainrenderer_8php-source.html#l00324

to generate either

	"_" . $sName . "_"
OR
	"_" . $sName

suffixes

Regards,
Jerome


Jerome Schneider a écrit :
> Hello Manuel, Luc and Oliver
> 
> Do you think that the trailing _ is needed in the id when subtituting 
> brackets by underscores ?
> 
> tx_myformid[myrdtname]
> 
> becomes: 2 options:
> 
> 1) tx_myformid_myrdtname_
> 2) tx_myformid_myrdtname
> 
> Jerome
> 
> 
> 
> Oliver Klee a écrit :
>> Hi,
>>
>> Luc Muller schrieb:
>>> I'm not sure if I'm right... but... this calendar do not resepct 
>>> accessibility standards... to have an accessible date you should use 
>>> a text field where user inputs himself the date.
>>
>> Well, the date field already offers a text field which is perfectly
>> accessible. If a screenreader is used, the alt attribute for the date
>> picker is needed so that the screenreader can output something other
>> than the file name - even if the alt attribute contains only a hint that
>> this is a link to a JavaScript-based date picker that cannot be used for
>> screen readers. In addition, the alt attribute would remove another
>> validation error.
>>
>> About the name and id attributes: For name attributes (which are needed
>> for naming the form data), [ and ] are perfectly valid. For the IDs
>> (which are needed for CSS selectors and for getElementById and for
>> providing targets for label tags), [ and ] are not valid and in some of
>> my tests created actual problems when trying to use them in CSS ID
>> selectors. Luckily, the name and id attribute can be different. As
>> manual proposed, replacing [ and ] by _ in the id attributes (but not
>> the name attributes) to me sounds like the way to go.
>>
>> About validation: I often use a HTML validator to check the validity of
>> my extension HTML templates. When there is lots of noise in the
>> validator output (eg. missing alt attributes or [] in id attributes),
>> this makes it harder for me to spot the actual errors. When there is no
>> validation noise, I can just rely on the green check mark of the HTML
>> validator extension in Firefox - which is a lot faster than always
>> having to open the validator output and sift through the messages.
>>
>> Manuel, maybe you can post a patch that fixes the ID attributes?
>>
>> If I can be of any help, please just ask.
>>
>> Best regards,
>>
>>
>> Oliver