Re: [techs] EXTENDED Techniques Teleconference 17 November 2004

Late regrets, but I have a few pieces of feedback on the latest Script 
Techs draft.
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-SCRIPT-TECHS-20041116>

----------------------------------------------------------------------
Regarding 2.1 javascript: URIs (Example)

<a href="register.php" target="registerwindow"
  onclick="window.open('',this.target);">register here</a>

Perhaps could be:

<a href="register.php" target="registerwindow"
  onclick="window.open(this.href,this.target); return 
false;">registration</a>

Better yet, the return value should be determined by the pop-up 
function, so that certain pop-up blcokers don't deny access.


----------------------------------------------------------------------
Regarding 2.2 Dynamic content generation

I would suggest a little more visible structure in the variable naming 
conventions, though of course this is personal preference for best 
practices rather than anything based on an accessibility 
recommendation.

function fillContent(oContainer) {
   // oContainer is an element in the DOM and passed in as a function 
parameter
   var oHeading = document.createElement("h1");
   oHeading.insertText("Heading Text");
   var oParagraph = document.createElement("p");
   oParagraph.insertText("Paragraph Text.");
   var oList = document.createElement("ul");
   var oItem = document.createElement("li");
   var oAnchor = document.createElement("a");
   oAnchor.setAttribute("href","destination.html");
   oAnchor.insertText("link text");
   oList.appendChild(oItem);
   oContainer.appendChild(oHeading);
   oContainer.appendChild(oParagraph);
   oContainer.appendChild(oList);
}


----------------------------------------------------------------------
2.6 Dynamic HTML menus

Typo: This task [wille] describe an accessible...


----------------------------------------------------------------------


Cheers,
James Craig

-- 
http://cookiecrook.com/

Received on Saturday, 20 November 2004 07:15:39 UTC