- From: Marc Haunschild <haunschild@mhis.onmicrosoft.de>
- Date: Sat, 18 Jul 2020 22:38:50 +0000
- CC: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
It does not always have to be static texts. Quite often details and summary does the job of hiding and revealing information. I like to give a short hint for experienced users in the summary and reveal in depth help in the hidden part of the details element. But: Everything depends on the particular problem you want to solve. There is not one “right” solution for every use case. And yes: sometimes just static text might be the best choice. In som cases you might should use the deque tool tips and sometimes a picture tells more than a thousand words (of course it will be interesting to write the alternative text for such an image) ;-) So if it has to be a tool tip, you know now how to make them accessible. But be open for other design patterns, too. -- Mit freundlichen Grüßen Marc Haunschild www.mhis.de > On 18. Jul 2020, at 02:27, Ajay Sharma <ajaysharma89003@gmail.com> wrote: > > Thanks all for your inputs, to conclude, tool tips do not provide best > experience to all the users, it is better to convey critical > information as static text. I am not too much inclined towards using > custom tool tips until it is very necessary as it gets hard to > maintain over time, it would be great if it is possible to get > accessible native title tool tips out of the box, that would make > life much easier. > > Cheers, > Ajay > >> On 7/17/20, Sailesh Panchang <sailesh.panchang@deque.com> wrote: >> Note the third statement from Understanding SC 3.3.2: >> "The intent of this Success Criterion is to have content authors >> present instructions or labels that identify the controls in a form so >> that users know what input data is expected. Instructions or labels >> may also specify data formats for fields especially if they are out of >> the customary formats or if there are specific rules for correct >> input. Content authors may also choose to make such instructions >> available to users only when the individual control has focus >> especially when instructions are long and verbose". >> >> So the title attribute does have a role to play in some situations. >> Alas it is not supported via keyboard by most browsers which is a >> long standing serious browser limitation. >> Thanks, >> Sailesh >> >> >> >>> On 7/17/20, Patrick H. Lauke <redux@splintered.co.uk> wrote: >>> On 16/07/2020 22:23, Ajay Sharma wrote: >>>> Hello there, >>>> >>>> I have a question regarding native HTML title attribute, , which is >>>> one of the easy way to add tool tip to a control, but tool tips >>>> generated in this way do not persist while trying to hover with mouse >>>> pointer, which fails SC 1.3.13 Content on hover or focus. >>> >>> Technically, those title tooltips do pass, because they're exempted: >>> >>> "Exception: The visual presentation of the additional content is >>> controlled by the user agent and is not modified by the author." >>> >>> But, as others have noted, I'd actually reconsider the need >>> for/use/reliance on tooltips altogether. >>> >>> P >>> -- >>> Patrick H. Lauke >>> >>> https://www.splintered.co.uk/ | https://github.com/patrickhlauke >>> https://flickr.com/photos/redux/ | https://www.deviantart.com/redux >>> twitter: @patrick_h_lauke | skype: patrick_h_lauke >>> >>> >> >> >> -- >> Sailesh Panchang >> Principal Accessibility Consultant >> Deque Systems Inc >> 381 Elden Street, Suite 2000, Herndon, VA 20170 >> Mobile: 571-344-1765 >> >> >
Received on Saturday, 18 July 2020 22:39:07 UTC