- From: Tom Wright <developer@tomwright.me.uk>
- Date: Thu, 21 Apr 2005 14:44:03 +0100
- To: Isofarro <lists@isofarro.uklinux.net>
- CC: WCAG <w3c-wai-gl@w3.org>, Becky_Gibson@notesdev.ibm.com
Isofarro wrote: > >> I've got a working example of this I've devised on my own using >> internal anchors as a basis. If its okay, I'd like to make it >> available for discussion in this group (or WAI-IG if that's a more >> appropriate venue). > > <url:http://sandbox.isolani.co.uk/demo/integratedHelp/> A nice technique Mike. One suggestion. IMO might it be better for the help content to be placed at the bottom of the document - like a footnote. Then in a non script-enabled environment (visual or speech) the user would not have to work through the help content before reaching each field if they do not need the help. While the internal links would allow them to jump to the relevant /help/ note (with a corresponding 'back to field' internal link). Perhaps the link-text for each help link could be numbered (as per footnotes) to provide a visual clue to the relationships (ie for a page with all content above the fold). Otherwise, the internal help links seem a little redundant with scripts disabled, so they might be better built by the DOM. The above would also minimise the potential 'flashing content problem' when the help content is hidden, on load, by shifting this content to the bottom of the page. As a technique I would favour being a little more unobtrusive with removing the content, using the technique of declaring styles at the head of the script file - synchronise accessibility and aesthetics :). But this might not meet with approval. Cheers, Tom PS I amended the subject to include [script-techs] so this thread can be filtered accordingly if it raises further discussion. Hope that is not bad practice. -- --------------------------------------------------------- Tom Wright, devloper@tomwright.me.uk http://www.severnsolutions.co.uk
Received on Thursday, 21 April 2005 13:44:22 UTC