Hi Jeremy. Thank you for your reply. I do appreciate it. Your tw code renders an html code like
<label>This is my label<select><option value="one">one</option><option (...) </option></select></label> This fails https://www.w3.org/WAI/WCAG21/Techniques/html/H44 because of lack of "id" tag. https://www.w3.org/WAI/WCAG21/Techniques/html/H65 provides an alternative with the "title" tag but neither edit-text widget nor button widget provide a way to get a title tag. This solution would be a little out of touch (aka not very acceptable) if you provide a label element that fails only because of a lack of "id" tag. on the contrary we are clearly within the wrong as shown in https://www.w3.org/WAI/WCAG21/Techniques/failures/F68 If we can't get WCAG conformity witg tiddlywiki, this mean the law will forbid any application in tw technology to be used as a web app for any major public (the public, corporate app, etc). This would really be a shame. Is there really no way to properly handle id tags? Could we imagine a blue sky effort to imagine potential solutions? Where and how could interested parties be technically briefed and reports their own works about it afterwards? regards. -- Jean-Pierre Le mercredi 21 avril 2021 à 22:27:39 UTC+2, [email protected] a écrit : > Hi Jean-Pierre > > Using HTML IDs is awkward in TiddlyWiki because of the way that fragments > of HTML can be displayed more than once. But it is also possible to nest > the select element inside the label element: > > > https://developer.mozilla.org/en-US/docs/Web/HTML/Element/select#advanced_select_with_multiple_features > > For example: > > <label> > This is the label > <$select tiddler=<<qualify 'select-demo'>> default='HelloThere'> > <$list filter='[all[shadows+tiddlers]tags[]sort[title]]'> > <option value=<<currentTiddler>>><$view field='title'/></option> > </$list> > </$select> > </label> > > Best wishes > > Jeremy > > -- > Jeremy Ruston > [email protected] > https://jermolene.com > > On 21 Apr 2021, at 11:04, Jean-Pierre Rivière <[email protected]> > wrote: > > As far as WCAG 2.1 is concerned, a "select" elements should better have > an "id" tag in order that a "label" element could point to it witg its > "for" tag. Alternatives are a "title" tag or WAI-ARIA roles for the > "select" element. > > > Alas, none of this is possible with the current "select" widget. > > The "button" widget can have aria labels but sill cannot get an "id" tag. > > Neither can have a "name" tag which can also be helpful in this respect > (as a poor man's workaround). > > I think it would be time to address this a11y issues that prevents to make > a fully accessible document or site with tiddlywiki. > > I propose to help in this endeavour in listing the accessibility problems > with forms widgets. And propose some fixes (if I'm successfull). > > My interest in the quest: I am using tiddliwiki to build a tool for > recording scores and minutes at accessibility tests for web sites. It would > also be better if the tool was as WCAG compliant as it could be. > > Regards. > > -- > Jean-Pierre > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/ed0a3873-8007-4e15-932d-b99811308884n%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/ed0a3873-8007-4e15-932d-b99811308884n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/cd8c9c6e-39d9-4b8b-9b31-d448cc7b5d03n%40googlegroups.com.
