<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Lemon, Gez</title>	<link>http://tc.eserver.org/authors/Lemon,_Gez</link>
	<description>A bibliography of works by Lemon, Gez in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Lemon, Gez</title>
		<link>http://tc.eserver.org/dir/Lemon,_Gez</link>
	</image>
	<item>
		<title>The HTML Scope/Headers Debate</title>
		<link>http://tc.eserver.org/35390.html</link>
		<guid>http://tc.eserver.org/35390.html</guid>
		<description>The HTML working group have decided not to include the headers attribute in the HTML 5.0 working draft, as they believe the scope attribute is sufficient for associating header cells with data cells. With simple and most complex tables, this is a reasonable assertion, but doesn&apos;t work with overlaid and irregular tables, where the associated headers aren&apos;t in the same column or row.</description>
	</item>
	<item>
		<title>Introduction to WAI ARIA</title>
		<link>http://tc.eserver.org/32516.html</link>
		<guid>http://tc.eserver.org/32516.html</guid>
		<description>This article is for those who are new to ARIA. You need an understanding of HTML and the potential difficulties that people with disabilities can face using the Web. It is useful to be familiar with some Rich Internet Applications from a user&apos;s perspectiveAfter reading this article, you&apos;ll understand what ARIA is for, how to integrate it into your sites, and how you can use it now to make even the simplest of sites more accessible.</description>
	</item>
	<item>
		<title>The AxsJAX Framework for ARIA</title>
		<link>http://tc.eserver.org/30471.html</link>
		<guid>http://tc.eserver.org/30471.html</guid>
		<description>Charles L. Chen  and T. V Raman have developed a common JavaScript framework to enhance the accessibility of AJAX-based applications. The framework is called AxsJAX, pronounced, &apos;Access JAX.&apos;</description>
	</item>
	<item>
		<title>E-Shop Accessibility: From Theory to Reality</title>
		<link>http://tc.eserver.org/30473.html</link>
		<guid>http://tc.eserver.org/30473.html</guid>
		<description>This article will explain how it is possible to apply WCAG 1.0 (and also how to comply with the future WCAG 2.0  and ISO 9241-151) to create an accessible e-shop shopping-cart and backend management system, analyzing the problems and the proposed solutions.</description>
	</item>
	<item>
		<title>Fieldsets, Legends and Screen Readers</title>
		<link>http://tc.eserver.org/30475.html</link>
		<guid>http://tc.eserver.org/30475.html</guid>
		<description>The grouping and labelling of thematically related controls within a form is an important aspect of providing semantic information so users can understand and complete a form successfully. Differences in quality and implementation of support across user agents can hamper some users&apos; ability to benefit from this information. This must not be taken as disincentive to developers, as the benefits of using these elements outweighs the negatives. But it is clear that some assistive technology vendors need to improve implementation of HTML features that enhance accessibility, so their users can gain the most benefit.</description>
	</item>
	<item>
		<title>The HTML 5 Image Element</title>
		<link>http://tc.eserver.org/30470.html</link>
		<guid>http://tc.eserver.org/30470.html</guid>
		<description>One of the great things about the current HTML 5 draft is that they give plenty of examples of how to specify alternate text for images, although a few of them are misguided. Alternate text should be concise, and a longer description provided with a longdesc attribute if necessary.</description>
	</item>
	<item>
		<title>Providing Context for Ambiguous Link Phrases</title>
		<link>http://tc.eserver.org/30474.html</link>
		<guid>http://tc.eserver.org/30474.html</guid>
		<description>This article demonstrates a technique that allows ambiguous link phrases to be rendered visually in a page, whilst making sense to screen readers, and other non-graphical devices, that might render the links out of context.</description>
	</item>
	<item>
		<title>Screen Readers and &apos;display:none&apos;</title>
		<link>http://tc.eserver.org/30472.html</link>
		<guid>http://tc.eserver.org/30472.html</guid>
		<description>When an element is hidden with display: none, the browser doesn&apos;t generate a box for the element; the element is not visible on the screen, and the layout of the page isn&apos;t effected by the element. As screen readers are supposed to read the screen, it makes sense that they do not announce content that is hidden with display: none.</description>
	</item>
	<item>
		<title>Improving Ajax Applications for JAWS users</title>
		<link>http://tc.eserver.org/28515.html</link>
		<guid>http://tc.eserver.org/28515.html</guid>
		<description>Popular screen readers use a virtual buffer to allow users to interact with web content, whereby the virtual buffer provides a mechanism for screen reader users to interact with web content. This article uncovers undocumented behaviour in JAWS 7.1 and later, which allows web developers to build Ajax applications that update the virtual buffer without any interaction from the user.</description>
	</item>
	<item>
		<title>Making Ajax Work with Screen Readers</title>
		<link>http://tc.eserver.org/27670.html</link>
		<guid>http://tc.eserver.org/27670.html</guid>
		<description>The accessibility community is understandably concerned about the accessibility of client-side scripting, in particular using Asynchronous JavaScript and XML (Ajax) to produce Rich Internet Applications. Steve Faulkner of Vision Australia  and founder member of the Web Accessibility Tools Consortium  (WAT-C) and myself on behalf of The Paciello Group (TPG)  have collaborated in an effort to come up with techniques to make Ajax and other client-side scripting techniques accessible to assistive technology.</description>
	</item>
	<item>
		<title>The DOM And Screen Readers</title>
		<link>http://tc.eserver.org/27417.html</link>
		<guid>http://tc.eserver.org/27417.html</guid>
		<description>This article investigates a method of providing client-side form validation through the DOM, and ensures that it works as expected with screen readers. Modern screen readers work relatively well with scripting, but it&apos;s the extra steps required to inform screen reader users that the content has changed that needs addressing.</description>
	</item>
	<item>
		<title>Greasemonkey Form Help</title>
		<link>http://tc.eserver.org/27418.html</link>
		<guid>http://tc.eserver.org/27418.html</guid>
		<description>Two relatively common usability problems with web forms are textareas that are too small, and dropdown lists being clumsy to use for some people. This Greasemonkey user script automatically assigns links above each textarea so that it can be resized, and automatically expands dropdown lists. The script is easily configurable, so you can choose not to expand dropdown lists, or determine the maximum number of items you want displayed in a dropdown list, or have graphic or text links for resizing textarea form controls.</description>
	</item>
	<item>
		<title>Photosensitive Epilepsy</title>
		<link>http://tc.eserver.org/27419.html</link>
		<guid>http://tc.eserver.org/27419.html</guid>
		<description>Photosensitive epilepsy is a form of epilepsy that is triggered by visual stimuli, such as flickering or high contrast oscillating patterns, and it&apos;s believed that around 3% to 5% of people with epilepsy are susceptible to photosensitive material. Photosensitive epilepsy is usually triggered where the flicker rate is between 16Hz to 25Hz, although it&apos;s not uncommon for seizures to be triggered by flicker rates between 3Hz to 60Hz. The condition most commonly effects children, and is usually developed between the ages of 9 and 15 years, and most prevalent in females.</description>
	</item>
	<item>
		<title>Required Elements, and Required Tags</title>
		<link>http://tc.eserver.org/27421.html</link>
		<guid>http://tc.eserver.org/27421.html</guid>
		<description>The difference between required elements and required tags has received a fair amount of attention recently, but the difference between the two is rarely (if ever) explained in detail.</description>
	</item>
	<item>
		<title>User-Defined Access Keys</title>
		<link>http://tc.eserver.org/27420.html</link>
		<guid>http://tc.eserver.org/27420.html</guid>
		<description>Access keys are a contentious area of accessibility, as they can sometimes clash with the shortcut keys used by user agents. One method to get around this problem is to allow users to define their own access keys. This post suggests a PHP class that allows users to define their own access keys.</description>
	</item>
	<item>
		<title>WCAG 2.0 Baseline Concept</title>
		<link>http://tc.eserver.org/27423.html</link>
		<guid>http://tc.eserver.org/27423.html</guid>
		<description>In order to encourage vendors of non-W3C technologies to include accessibility features in their technologies, and in recognition of emerging technologies that are beneficial for the Web, WCAG 2.0 is technology neutral. Rather than list each technology that the guidelines cover, WCAG 2.0 introduces the concept of a baseline. This post attempts to explain what is meant by this baseline concept.</description>
	</item>
	<item>
		<title>Writing a Good Accessibility Statement</title>
		<link>http://tc.eserver.org/27422.html</link>
		<guid>http://tc.eserver.org/27422.html</guid>
		<description>&#xD;Accessibility statements are an ideal place to empower visitors to your website. Most accessibility statements are too technical, and don&apos;t necessarily address the needs of the visitor. Those that do address the needs of visitors often have the information lost in a myriad of other information that is unlikely to be understood by the average visitor to the website. What should and shouldn&apos;t be included in an accessibility statement?</description>
	</item>
	<item>
		<title>Apache HTTP Status Codes</title>
		<link>http://tc.eserver.org/25691.html</link>
		<guid>http://tc.eserver.org/25691.html</guid>
		<description>Those familiar with Apache will be used to the luxury of being able to specify redirects on the fly, without having to write programs to catch errors, and ensure they return the correct HTTP status codes. Being new to Apache, I was amazed at just how easy it is. The following provides an overview of the Apache Redirect directive.</description>
	</item>
	<item>
		<title>Div Mania</title>
		<link>http://tc.eserver.org/25690.html</link>
		<guid>http://tc.eserver.org/25690.html</guid>
		<description>More and more web documents are appearing that consist of nothing more than a collection of div elements. In most cases, better use of CSS selectors could be used to avoid overusing the div element.</description>
	</item>
	<item>
		<title>Accessibility Tutorial</title>
		<link>http://tc.eserver.org/22327.html</link>
		<guid>http://tc.eserver.org/22327.html</guid>
		<description>Developers put a lot of effort into ensuring their sites can be viewed in outdated browsers, but all too often ignore newer browsers, or worse still, a whole range of visitors. Accessibility means access to information for all. Information to all, regardless of the device used to view the document, or abilities of the visitor. You&apos;re extremely proud of your latest masterpiece. The choice of colours is striking, the layout fits perfectly on your screen, but how does it look on a Personal Digital Assistant (PDA)? How does it look to a colour-blind visitor? Does it read correctly using assistive technologies, such as screen reading software? Can a visitor navigate the site without the use of a mouse? Is the site usable when JavaScript and images are switched off in the browser?</description>
	</item>
	<item>
		<title>Active Server Page (ASP) Tutorial</title>
		<link>http://tc.eserver.org/22328.html</link>
		<guid>http://tc.eserver.org/22328.html</guid>
		<description>Introduced in 1996, Active Server Pages (ASP) are just like normal x/html pages except they are processed on the server before being sent to the client&apos;s machine. ASP itself is not a programming language, but a platform on which any scripting language that your web-server understands can run. The most popular languages used with ASP are VBScript (a subset of Visual Basic), JScript (Microsoft&apos;s version of JavaScript) and Perl Script. This tutorial only covers VBScript.</description>
	</item>
	<item>
		<title>Cascading Style Sheets (CSS) Tutorial</title>
		<link>http://tc.eserver.org/22336.html</link>
		<guid>http://tc.eserver.org/22336.html</guid>
		<description>Cascading Style Sheets (CSS) were introduced by the World Wide Web Consortium to help determine the layout of an HTML document. Removing the formatting from the HTML document allows you to quickly apply a style to a whole site, rather than going through each document and changing the tags that represent the style. It also means that the content of the HTML document isn&apos;t bloated by extra information about how data is to be presented. The current specification for using style sheets, Cascading Style Sheets, level 2, may be found at the World Wide Web Consortium&apos;s site. Cascading Style Sheets, level 3 is currently available in its draft version.</description>
	</item>
	<item>
		<title>The Extensible HyperText Markup Language (XHTML) Tutorial</title>
		<link>http://tc.eserver.org/22334.html</link>
		<guid>http://tc.eserver.org/22334.html</guid>
		<description>The Extensible HyperText Markup Language (XHTML) is intended to be a replacement for HTML. XHTML has a stricter syntax than HTML and is the official recommendation. of the W3C. XHTML was required due to the poor standard of some HTML documents due to the forgiving nature of browsers. This tutorial discusses the issues in making your documents XHTML compliant.</description>
	</item>
	<item>
		<title>Extensible Markup Language (XML) Tutorial</title>
		<link>http://tc.eserver.org/22335.html</link>
		<guid>http://tc.eserver.org/22335.html</guid>
		<description>The Extensible Markup Language (XML) is a subset of the Standard Generalised Markup Language (SGML), the standard for creating markup documents. Unlike HTML, another markup language based on SGML, XML allows you to describe data and its structure rather than display it. XML is not a replacement for HTML, but compliments it by allowing the author to describe their own tags. XML is extensible as the author can create an unlimited number of tags. There are no predefined tags in XML.</description>
	</item>
	<item>
		<title>HyperText Markup Language (HTML) Tutorial</title>
		<link>http://tc.eserver.org/22329.html</link>
		<guid>http://tc.eserver.org/22329.html</guid>
		<description>The HyperText Markup Language (HTML) is the standard language for developing documents on the World Wide Web. This tutorial concentrates on HTML 4.01, the latest version of HTML as specified by the World Wide Web Consortium (W3C). See the Extensible HyperText Markup Language (XHTML) tutorial for guidelines on making the pages XHTML compliant. An HTML document consists of elements (sometimes referred to as tags), that are handled by a user agent (such as a browser) to render the document.</description>
	</item>
	<item>
		<title>Java Tutorial</title>
		<link>http://tc.eserver.org/22331.html</link>
		<guid>http://tc.eserver.org/22331.html</guid>
		<description>Java may be used to develop stand-alone applications, servlets (an application that runs on the server), or applets (an application that runs inside a Java-capable browser). Applets appear in web-pages in the same way as an image, but because they are essentially embedded applications, are dynamic and interactive.</description>
	</item>
	<item>
		<title>MySQL Tutorial</title>
		<link>http://tc.eserver.org/22330.html</link>
		<guid>http://tc.eserver.org/22330.html</guid>
		<description>Released in January 1998, MySQL is an open source relational database management system (RDBMS). It&apos;s based around the Structured Query Language (SQL), and is best for managing the content of the database as opposed to transactions, as MySQL does not support COMMIT or ROLLBACK. One of the biggest drawbacks of MySQL is it&apos;s lack of support for referential integrity, no stored procedures, no triggers, and no sub-queries. MySQL is free, and may be downloaded from download section at MySQL.</description>
	</item>
	<item>
		<title>PHP Server-Side Scripting Tutorial</title>
		<link>http://tc.eserver.org/22332.html</link>
		<guid>http://tc.eserver.org/22332.html</guid>
		<description>PHP is a server-side scripting language and interpreter that is available on a wide range of platforms, including some versions of Apache, and Microsoft&apos;s Internet Information Server (IIS). The PHP script is embedded in the Web page, and interpreted on the server before being sent to the client who requested the page.</description>
	</item>
	<item>
		<title>Wireless Markup Language (WML) Tutorial: Getting User Input</title>
		<link>http://tc.eserver.org/22333.html</link>
		<guid>http://tc.eserver.org/22333.html</guid>
		<description>The Wireless Markup Language (WML) is the markup language used to make sites suitable for viewing using a WAP (Wireless Application Protocol) device. If you don&apos;t have a WAP device to view the pages, you can get a simulator by downloading the Wireless Companion from YourWAP.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Lemon,_Gez.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>