Top of Page Marker.

Boinkin Chipmunks – About Application Testing and Its Usefulness.

This is a Primary Content Page with two columns.

Skip to the Main Content.

If using some assisted technologies to view the web content, it may be best to disable style sheets within the browswer. Additionally, user selectable style sheets are available from within the Web site content.

The Keyboard Shortcut Information Notice.

If you need to visit our list of Keyboard Shortcuts, use the keyboard shortcut key of Zero.

End of Keyboard Shortcut Information Notice.

The Page Header Information: The Boinkin Chipmunk Logo, Contact and Location.

e-mail that guy:
office location:
1 baie orientale.
97150 saint martin, fwi.
 

Accessible Theme Preference: Theme Menu and Selection is Under Development. [UD].

About Accessible Themes.

Menu to the Site's Most Frequently Viewed Content Pages.

 
Warm beaches are everywhere.

About Application Testing Main Content.

Breadcrumb Page Navigation.

Home >> Application Testing

Purpose of Application Testing and Its Usefulness.

use the nasa philosophy.

Whenever content is built, sufficient planning should go into its structure prior to the content's construction. This Web site is an exception, primarily because it is a testing site and was built without a defining purpose in its content or structure.

Without getting into all of the variables, explanations of those variables and implementation of the same as indicated within the first sentence, this content page is about the need of thorough testing of any technology and its addition to the Web content.

Test technology using the NASA principal. Test as though thousands of pounds of thrust are strapped to your butt and that the content and technology has to work. Failure is not an option. To place that into perspective, a NASA engineer will average six tenths [0.60] lines of code per hour, an average of five lines of code per day.

The Issue.

I required a method to display content segments that wouldn't require a page refresh to display the segmented content. I required greater flexibility and ease of implementation than what a similar solution could be accomplished with AJAX. The solution would have to parse across any DTD and MIME content type for those DTDs. The solution must be able to parse in application/xhtml+xml. It had to function within a .NET framework environment. It had to meet accessibility and search engine optimization requirements. In short, it had to meet all of the requirements for best practices and do it in the most straightforward manner, e.g. without hacks.

The Solution – Project Seven's Glide Panel Magic.

Listed below, within the widget's menu tabs, are a few of the adjustments that were able to be made within the Glide Panel Magic widget's use to accommodate this Web site. That is one of the primary benefits behind this widget, — the widget is highly configurable.

The Glide Panel Magic used on this site is a beta release. In this beta release, the JavaScript has been changed to allow the widget's use within Web content that is delivered as true XML. In my tests, the widget performs flawlessly in any Web standard's based HTML or XML environment.

As with most widgets, the PVII widget is no exception, the primary function of the widget is to provide a sound basis in its function. With the PVII widget, it accomplishes that. The PVII Glide Panel Magic widget is highly configurable for the novice. For the experienced developer, the widget's structure, CSS and code can be adjusted to meet just about any scenario or use.

 


The Glide Panel Magic Widget Analysis.

The JavaScript and the Glide Panel Magic Widget.

Prior to this Beta version of the widget, its JavaScript used the document.write method and as such could not be parsed by the Web browser as XML.

Additional changes were made to the script so that required portions of the widget would be treated as nodes rather than as text within the Web browser's DOM.

Such changes within the widget's JavaScript are what now allow for the widget's use within any XHTML Web content that is parsed as XML.

The Widget's JavaScript, Search Engines and Accessibility.

Another very functional use of the widget's JavaScript is that all content controlled by the widget will be rendered and available to any Web browser that does not include a script engine or wherein scripts have been disabled by the user. As a result, all content is exposed to search engines and to some accessibility technology user agents.

The JavaScript and noscript Element.

Since the widget's content usability is not dependent upon its JavaScript, technically, the use of the noscript element to provide alternate content is not necessary.

However, if the targeted audience of the Web content is for a broad audience, it may be advisable to use the noscript element for notifying any user whenever they may have JavaScript disabled.

Not all accessibility user agents will have the entire contents and its segments exposed to the user agent. This is particularly true of a user agent that is rendering content delivered to it by a browser that has JavaScript enabled. Consideration should be given to proper identification of the widget's menu and its menu buttons. Include title attributes where and deemed necessary to aid in comprehension by the user.

The CSS and the Glide Panel Magic Widget.

The CSS of the widget can be customized to adapt to a particular desing and layout. Caution should be used when modifying the CSS, however.

The Glide Panel Magic depends upon the CSS style rules of display:none and display:visible for hiding and exposing the content segments of the widget.

The Print Function and Effect of the Glide Panel Magic Widget.

Browsers will print only the content of the Web page that is exposed to the browser at the time of printing. Since this widget folds content that is only exposed through the widget's menu selection, the entire content of the page will not print unless a print CSS style sheet is used that includes the proper CSS rules to instruct the browser to expose the folds to the printer.

The Print Style Rules.

The print style rules should mimic the effect upon the widget as though its JavaScript function were disabled. The following rules are used:

.p7GP01 .sidecontent{display:none}
The above rule prevents any sidebar content, if present, within the widget from printing as a sidebar.
.p7GPcontentwrapper,.p7GPsidebar{display:block
!important}
This rule forces the sidebar content and the folded content to be displayed to the printer.
.p7GPW{overflow:visible !important}
This rule ensures that all content is exposed.
Print of Background Colors.

A print style sheet should be cognizant of the ink consumption that occurs during any print function. The following rules make adjustment to disable any background colors or background images that may have been specified within the widget's CSS for device display.

.p7GP01 .p7GPinnerwrapper{background-color:#fff
!important}
The above rule specifies the color of white to be sent to the printer. White, to a printer, is equivalent to no color.
.p7GP01 .p7GPtwrapper{background-color:#fff
!important}
This rule ensures a white background, also.
Print of Widget's Menu.

Dependent upon how the designer/developer has coded the CSS styles, consideration should be given to preventing the widget's menu backgrounds and images from printing.

ul.gpm-links a{background-color:#fff !important;
background-image:none !important}
In the case of this site's content and on how the CSS rules have been written, in conjunction with the HTML code, the above print rule is used to prevent the widget's menu images and backgrounds from printing.

Another option to the designer would be to prevent the printing of the widget's menu, altogether.

ul.gpm-links a{display:none !important}
The above rule, if it had been used for this Web content, would have prevented the printing of the widget's menu.

For a first hand look at how these rules affect the print output, use your browser's print preview function to view this specific Web page's print output and appearance.

The SEO Structure and the Glide Panel Magic Widget.

The Glide Panel Magic Widget can be placed anywhere within a content page with the menu for widget separate from the widget's content.

When this is done, as with any HTML, logical order should be built and maintained. This should include the proper use of the h1 through h6 header elements. The entire document should be structured with the header elements as if the document were being built from a formal outline. In fact, when only the header elements are displayed, the content should be a formal outline.

Even though the widget uses JavaScript to expose and hide the content within the Glide Panel Magic system, all of the content is exposed to search engines. Search engines do not apply JavaScript.

Exposure to Search Engines versus Usability.

Content exposure to search engines and usability of that content through search engine results are two different things.

When a user of a search engine finds content listed within the search engine results page that is part of hidden content, such as that of this specific widget for example, the search engine link requires a click through that will take the user to that content. However, with hidden content and without special consideration given to that, the user will be taken to the content page without having that content exposed to them.

Search Engine Results Usability.

Several methods can be used that will give the user a click through or inform the user where the results of the content search are located within the Web document.

If header elements are used within the content of the widget, assign a unique id value to the uppermost header element within that content segment. Internal links can reference these id values as needed.

One method would be to include descriptive links within or immediately adjacent to the exposed content of the widget's first panel.

Creation of Appropriate Links.

The widget panels are automatically assigned a component and a panel number for each Glide Panel Magic segment. This is assigned as an id value to the corresponding div or table element.

For example, this specific content section has been assigned an id value of p7GPc1_4. The component panel identifier is 1 and the content panel identifier is 4.

To create a proper click through link that will automatically expand the correct content panel, use the URL parameter for the content segment and the anchor method that identifies the appropriate header element.

For this panel segment the URL parameter within the href attribute would be:

general.aspx?gpm=1_4#panel1
A proper URL parameter.

For this Web site, I have included the various content segments within the site map of the various Glide Panel Magic widgets used. The site map provides a brief description of each of the widget's content panels and provides a link that will reference the content and expose it. The site map content page is then referenced as an upper level within a search engine site reference xml file. This reference file is used by search engines for determining what content pages should be indexed and at what frequency indexing should occur. In short, this method exposes the widgets' content that includes appropriate click through links.

Summary.

Various other methods could be used to accomplish click through exposure including some complex ASP.NET code behind URI methods, perhaps.

Whatever method is used just be sure to include a link that will expose the hidden content, when necessary, and provide a click through for the user to access the content.

Miscellaneous Points and the Glide Panel Magic Widget.

During testing and development of these widgets, a few miscellaneous observations were made and some suggestions may be of use.

Top of Menu Links.

Consideration within certain uses of the widget, particularly when large segments of content are included, should be given to use a link at the bottom of the content segment that takes the user back to the widget's menu.

Keep in mind, such a link is extremely helpful for users who do not enable the use of JavaScript within their browser. Such a link is almost mandatory whenever the widget's menu falls out of the viewport when the entire content segment of the widget is viewed.

It allows the user to conveniently go back to the menu and select other content areas of the widget for viewing.

Character Encodings.

When using the XHTML Strict DTDs be sure to change any character encoding from the friendly equivalent to the character equivalent. For example when using the non-breaking space, reference its numeric equivalent of   rather than the friendly equivalent of &#nbsp;.

 

The Various Glide Panel Widget Test Pages.

Results of the Tests.

These tests results demonstrate that the widget is parsed by any modern browser based upon the DTD and its MIME content type. In short, the widget will parse as text/html or as application/xhtml+xml dependent upon use of the correct DTD and the browser's ability to recognize and parse XML.

General Information.

All of the test links will open into a new browser window.

The last link is an example of how the widget renders when JavaScript is disabled. All content within the widget displays and is available for search engines and any browser or user agent that does not support JavaScript.

The Test Page Links.
The XHTML Test Page and application/xhtml+xml MIME type.

XHTML Web content pages, when the correct DTD and associated namespace are used, are served with a MIME type of application/xhtml+xml to modern browsers provided that the browser supports the application/xhtml+xml MIME and that the file ends with an xhtml extension. Certain frameworks, such as the .NET framework, have the ability to configure content negotiation so that the correct MIME content–type can be delivered to specific Web browsers that support xml and deliver it to the remaining browsers as text/html.

In the case of these tests, ASP.NET Web pages, those pages that use the aspx extension, will deliver application/xhtml+xml content to browsers that support it. Since Microsoft Internet Explorer versions 7.0 and below do not support application/xhtml+xml, the .NET framework delivers these pages to Internet Explorer with a MIME type of text/html.

Presentation of a true XHTML test on a public external server is problematic. Many hosting companies have disabled the xhtml file extension and its proper MIME type, altogether. This is done, even though, default installation of Microsoft's IIS includes the xhtml and its correct MIME type for Web content delivery.

The logic of the hosting company is that since the browser with the largest market share, Microsoft's Internet Explorer, does not support xhtml then it should be disabled on the hosting servers. The logic continues with the rational that it is to preclude problems with the largest Web content creators, the hobbyist and do–it–yourself individual.

Point blank, this market segment doesn't know XHTML from that of doughnuts nor do, generally, the applications they use to create Web content know the difference. They have no basis to ever, even inadvertently, specify a content page as XHTML nor use the extension of xhtml.

The hosting company's solution for the customer who needs the ability to deliver standards compliant XHTML content is to add within IIS the xhtml file extension and deliver it. more often than not, with a MIME type of application/octet-stream. This specific MIME type is a generic binary content type that basically tells the browser or application that the content is unknown and the browser and/or application should try to figure out what to do with it.

The use of application/octet-stream to deliver XHTML is worse than the delivery of XHTML as text/html. It defeats one of the primary functions of XHTML. That function is to remove ambiguity for user agents and browsers in parsing and rendering of the Web content.

Fortunately, the hosting company for Boinkin Chipmunks, Go Daddy, decided to provide use for true XHTML content delivery upon request. Therefore, a viable method for an external test of the widget's ability to render within a fully standard's based non–framework Web environment is available.

Thanks, Bob, for the hosting server adjustment! And, thank you, Gerry, for making your Glide Panel Magic widget even better by enabling support of true application/xhtml+xml and thus the ability of your product's use within the .NET framework!

The XHTML Test Page Link.
The XHTML Generated DOM Source Code.

The generated source code for the XHTML Test is available for review via the following links:

 

Project Seven.

Project Seven creates and develops superb products for Web development. Their products are delivered as Adobe Dreamweaver extensions. Though I don't use Dreamweaver, their products can be hand-coded or Dreamweaver can be used, simply, to insert and adjust the product when necessary. Project Seven's support is excellent, some of the best of any computer technical business. Worth a look and damn well worth the money for any of their products.

If you have any questions regarding any issues or questions concerning application testing, please e-Mail that boinkin guy.Mail to Image.

End of the Application Testing Main Content.

The Right Sidebar Column Content.

Evening Wear.

Proud and smiling.

Style speaks much. Some things are spoken remarkably well.


Keyboard Navigation and Web Content Usability.

Keyboard navigation of Web content is becoming of greater importance as more content is accessed by mobile devices. It is not, solely, an accessibility solution for those with disabilities. Proper structure of content should allow for site navigation that is not limited to any specific hardware or device, for example, mouse technologies.

Part of successful keyboard navigation is dependent upon the tab key and being able to tab through links, form controls and, even, content segments. Successful implementation of tab control through content cannot depend upon any browser or user agent to successfully and automatically assign proper tab order throughout any rendered content.

Designers and developers should assign tabindex values to all necessary elements. Tab key values should follow the linear order of the content. Linear order of the value should only be superseded by the logical order of tab order, when necessary.


Keyboard Shortcuts and Navigation.

Another critical function of keyboard navigation is the use of shortcut keys for important links and for major content segments. This requires effective use of the accesskey value. This site uses a modified version of the United Kingdom Standard of Keyboard Shortcuts.

More thorough information about the use of the United Kingdom Standard is available on this Web site's Keyboard ShortcutAdjacent link will open into a new window. content page.

Keyboard Shortcut List.

Shortcut Key, s.
Skip to the Main Content.
Shortcut Key, One.
The Home Page.
Shortcut Key, Two.
About the Site.
Shortcut Key, Three.
The Site Map.
Shortcut Key, Four.
The Accessibility Policy.
Shortcut Key, Five.
The Copyright Notice.
Shortcut Key, Six.
The Safety Policy.
Shortcut Key, Seven.
The Privacy Policy.
Shortcut Key, Eight.
The Terms of Use.
Shortcut Key, Nine.
The Contact Page.
Shortcut Key, Zero.
The Keyboard Shortcut Links Table.
Shortcut Key, t.
The Top of the Page.
Shortcut Key, c.
The Main Content Column.
Shortcut Key, r.
The Right Sidebar Column.
Shortcut Key, g.
The General Page Menu.
 

The End of Boinkin Chipmunks – About Application Testing.