#32517
Accessible Context-Sensitive Help with Unobtrusive DOM Scripting
This article demonstrates two methods of calling context-sensitive help in a web form: the Field Help Method and Form Help Method, in which unobtrusive DOM/JavaScript is employed to achieve the desired result. It also serves to illustrate the separation of the Structure and Behavior layers of a web page. Graceful degradation is employed to make sure that the help information is accessible if JavaScript is disabled or not available in a user agent.
Palinkas, Frank M. Opera (2008). Articles>Web Design>Standards>Help
#32518
Building Accessible Static Navigation with CSS
When building a navigation menu for a web site, steps should be taken to ensure that it is accessible, and degrades gracefully in older browsers with lesser CSS support. In this article we will explore one such implementation. The navigation menu you see in this example is built with valid, semantic HTML and CSS - no JavaScript is involved, as I felt this was unnecessary. The static (non-expanding/collapsing) nature of the example suits a web site comprised of twenty or less target pages.
Palinkas, Frank M. Opera (2008). Articles>Web Design>Accessibility>CSS
#32519
Replacing NOSCRIPT with Accessible, Unobtrusive DOM/JavaScript
Modern user agents with JavaScript enabled will hide content contained within NOSCRIPT, and reveal it when JavaScript is disabled. User agents that do not support JavaScript will display the content within it. User agents with partial/antiquated JavaScript capabilities however interpret the element correctly and do not show the content, but when JavaScript is disabled also do not show the content - it never gets seen. This has an impact on the accessibility of the content. If your writing is targeted at modern, standards-based, compliant, and fully capable JavaScript user agents, employing the NOSCRIPT element is no problem. If the user agents among your audience are unpredictable, however, replacing the NOSCRIPT element with another mechanism becomes significant. This article looks at one such solution.
Palinkas, Frank M. Opera (2008). Articles>Web Design>Accessibility>JavaScript
#32520
Creating Accessible Data Tables
This article demonstrates how to code accessible data tables in (X)HTML, enabling visually impaired users who employ assistive technologies to interpret the table data. Two views of a tabular data table are presented and discussed.
Palinkas, Frank M. Opera (2008). Articles>Web Design>Accessibility>Standards
#35188
Creating Accessible Tabular Data Tables: A Help Authoring Guide
This Fast Track tutorial demonstrates and employs web standards and accessibility methods for tabular data table creation. It is presented free of charge to the community as a help authoring, technical writing and web design guide.
Palinkas, Frank M. helpware.net (2009). Articles>Web Design>Accessibility>Help
#35189
This Fast Track tutorial demonstrates how to create automatic line numbering in a code block.
Palinkas, Frank M. helpware.net (2009). Articles>Documentation>CSS>Help
#35190
Calling Accessible Context-Sensitive Help with Unobtrusive DOM/JavaScript: A Help Authoring Guide
This Fast Track tutorial demonstrates two methods to call Context-Sensitive Help in a Web Form. We'll discover how Unobtrusive DOM/JavaScript achieves the desired result in calling Context-Sensitive help, and demonstrate how to keep the Structure, Presentation, and Behavior layers of a web page completely separate from one another ensuring good practice with current web standards and accessibility rules.
Palinkas, Frank M. helpware.net (2009). Articles>Web Design>Documentation>Help
#35191
There are times when we need to build a navigation tree stucture to accomodate a small document collection. There is no need to have this nav list expand or contract, so employing a Behavior layer (unobtrusive DOM/JavaScript) is not appropriate.
Palinkas, Frank M. helpware.net (2009). Articles>Web Design>CSS>Help
