From MAILER-DAEMON Wed Dec  1 12:16:34 2010
Date: 01 Dec 2010 12:16:34 -0500
From: Mail System Internal Data <MAILER-DAEMON@turing.acm.org>
Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
X-IMAP: 1291223794 0000000000
Status: RO

This text is part of the internal format of your mail folder, and is not
a real message.  It is created automatically by the mail system software.
If deleted, important folder data will be lost, and it will be re-created
with the data reset to initial values.

From perlman@turing.acm.org Thu Dec  2 09:32:18 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Thu, 2 Dec 2010 09:32:17 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: HCI Webliography <apache@turing.acm.org>
cc: director@hcibib.org, kontakt@semseolab.de
Subject: Re: !SUGGEST_a_LINK! hci-sites:companies: Agency for SEO and SEM -
 website-optimization for friendly usability for human and searchengines
In-Reply-To: <201012021106.oB2B6vE4029583@turing.acm.org>
Message-ID: <Pine.LNX.4.64.1012020932080.7801@turing.acm.org>
References: <201012021106.oB2B6vE4029583@turing.acm.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

I am sorry, but the site below does not have specific HCI
content and will not be included in the HCI Bibliography.
 	http://hcibib.org/faq.html#Data-5

Gary Perlman, Director, HCI Bibliography Project
mailto:director@hcibib.org  http://hcibib.org/

On Thu, 2 Dec 2010, HCI Webliography wrote:

> Reply-To: director@hcibib.org
>
> This data is being sent to director@hcibib.org
> to be considered for inclusion in the HCI Bibliography
>
> %M U.agentur-sem-seo.de   79.195.80.106
> %0 INTERNET
> %D 2010-12-02
> %K hci-sites:companies hci-sites:consultants
> %A Mike Sch&ouml;nfelder
> %C germany, hamburg, hamburg - rostock
> %I semseolab
> %K seo agency, sem, search engine optimization, search engine marketing, website-optimization
> %T Agency for SEO and SEM - website-optimization for friendly usability for human and searchengines
> %U kontakt@semseolab.de
> %W http://www.agentur-sem-seo.de
>
> Information from this tool may also be used for your entry:
> http://hcibib.org/accessibility/chaccess.cgi?url=http://www.agentur-sem-seo.de
>

From perlman@turing.acm.org Sat Dec  4 18:25:03 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Sat, 4 Dec 2010 18:25:02 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: Richard Onley <samarobrin@gmail.com>
Subject: Re: Registration for Herbie page
In-Reply-To: <AANLkTi=wV7mB=eAAXPGhNiu0mHEoBiXovJ02B5zQwMnG@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1012041814300.1681@turing.acm.org>
References: <AANLkTi=wV7mB=eAAXPGhNiu0mHEoBiXovJ02B5zQwMnG@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

I don't think it's legal for me to make them available.
Scans are someimes available on usenet.

I see the complete set posted on July 28 by noemail@hereorthere.org (cw-poster)
to alt.binaries.comics.

cw-vintage [064/155] "Herbie in Forbidden Worlds.cbr" yEnc (001/118) [H]  28.08 MB 
cw-vintage [09/31] "Herbie The Return of Herbie.cbr" yEnc (01/29) [H]  6.86 MB 
cw-vintage [10/31] "Herbie the Fat Fury 01.cbr" yEnc (01/48) [H]  11.35 MB 
cw-vintage [11/31] "Herbie the Fat Fury 02.cbr" yEnc (01/42) [H]  9.92 MB 
cw-vintage [12/31] "Herbie the Fat Fury 03.cbr" yEnc (01/33) [H]  7.78 MB 
cw-vintage [13/31] "Herbie the Fat Fury 04.cbr" yEnc (01/40) [H]  9.29 MB 
cw-vintage [14/31] "Herbie the Fat Fury 05.cbr" yEnc (01/40) [H]  9.42 MB 
cw-vintage [15/31] "Herbie the Fat Fury 06.cbr" yEnc (01/36) [H]  8.35 MB 
cw-vintage [16/31] "Herbie the Fat Fury 07.cbr" yEnc (01/39) [H]  9.22 MB 
cw-vintage [17/31] "Herbie the Fat Fury 08.cbr" yEnc (01/38) [H]  8.98 MB 
cw-vintage [18/31] "Herbie the Fat Fury 09.cbr" yEnc (01/38) [H]  8.83 MB 
cw-vintage [19/31] "Herbie the Fat Fury 10.cbr" yEnc (01/39) [H]  9.11 MB 
cw-vintage [20/31] "Herbie the Fat Fury 12.cbr" yEnc (01/38) [H]  8.92 MB 
cw-vintage [21/31] "Herbie the Fat Fury 13.cbr" yEnc (01/38) [H]  8.92 MB 
cw-vintage [22/31] "Herbie the Fat Fury 14.cbr" yEnc (01/20) [H]  4.56 MB 
cw-vintage [23/31] "Herbie the Fat Fury 15.cbr" yEnc (01/37) [H]  8.77 MB 
cw-vintage [24/31] "Herbie the Fat Fury 16.cbr" yEnc (01/38) [H]  8.83 MB 
cw-vintage [25/31] "Herbie the Fat Fury 17.cbr" yEnc (01/37) [H]  8.69 MB 
cw-vintage [26/31] "Herbie the Fat Fury 18.cbr" yEnc (01/38) [H]  8.97 MB 
cw-vintage [27/31] "Herbie the Fat Fury 19.cbr" yEnc (01/40) [H]  9.31 MB 
cw-vintage [28/31] "Herbie the Fat Fury 20.cbr" yEnc (01/40) [H]  9.49 MB 
cw-vintage [29/31] "Herbie the Fat Fury 21.cbr" yEnc (01/46) [H]  10.91 MB 
cw-vintage [30/31] "Herbie the Fat Fury 22.cbr" yEnc (01/42) [H]  9.90 MB 
cw-vintage [31/31] "Herbie the Fat Fury 23.cbr" yEnc (01/41) [H]  9.56 MB

They are CBR archives (rar format) for which there is a nice reader.
See http://en.wikipedia.org/wiki/Comic_Book_Archive_file

Anyway, who would believe you? He's just a little fat nothing!

Good luck

Gary

On Sat, 4 Dec 2010, Richard Onley wrote:

> How do I register to get to the PDFs on your page about Herbie?  I want to
> show them to some friends.  I've tried to tell them about him, but no one
> believes me!  --"SAR"
>

From perlman@turing.acm.org Sun Dec  5 21:11:51 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Sun, 5 Dec 2010 21:11:51 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: Gary perlman <perlman@turing.acm.org>
Subject: wcag 2 for wc.org
Message-ID: <Pine.LNX.4.64.1012052111340.10276@turing.acm.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

Listing of files in this pack:
   wcag2.cgi
   wcag2.db
   wc.db
fpack:!@#$%^&*(): wcag2.cgi
#! /bin/ksh

# make a table of WCAG 2.0 guidelines in wcag2.db

# todo: add a button to show all/hide all, or always show for print

title="WCAG 2.0 Web Content Accessibility Guidelines"
more="More..."
echo "Content-type: text/html

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>"

echo "<html lang='en'>
<head>
<meta name='robots' content='index,nofollow' />
<meta name='description' content='Web Content Accessibility Guidelines WCAG 2.0, 2008-12-11 in a form to help document issues and/or conformance with the guidelines.' />
<meta name='keywords' content='accessibility, accessible, access, disability, disabilities, disabled, handicap, physically handicapped, assistive, universal usability, special needs, impaired, impairment, blind, usability, user interface software, human-computer interaction, WCAG, WAI, web accessibility initiative, web content accessibility guidelines' />
<title>$title</title>
<style type='text/css'>
 	BODY {font-family: sans-serif; }
     .depth1 {background: #DDD; font-size: 125%; }
     .depth2 {background: #EEE; }
     .depth3 {font:weight: 200; }
     .levelA { background: #EFE; }
     .levelAA { background: #EFF }
     .levelAAA { background: #EEF; }
 	.NA { background: #EEE; }
 	.FC { background: #EFE; }
 	.PC { background: #FFE; }
 	.NC { background: #FEE; }
 	.hidden {display: none; }
 	th { font-family: sans-serif; background: #CCC; }
 	h2 {font-size: 100%; margin: 0; padding: 0; display: inline;}
 	h3 {font-size: 100%; margin: 0; padding: 0; display: inline;}
 	a { white-space: nowrap; }
     .button {background: white; border: solid thin blue; color: blue; }
</style>
<script type='text/javascript' language='JavaScript'>
     function show(ident) { document.getElementById(ident).style.display = 'block'; }
     function hide(ident) { document.getElementById(ident).style.display = 'none'; }
</script>
</head>
<body>
<h1>$title</h1>
<p>
<a href='http://www.w3.org/TR/WCAG20/'>WCAG 2.0</a>
was approved as a <a href='http://www.w3.org/'>W3C</a>
recommendation 2008-12-11.
It differs in many ways from 
<a href='http://www.w3.org/TR/WCAG10/'>WCAG 1.0 (1999)</a>.
There are 4 principles
(systems must be
<a href='#a1'>Perceivable</a>,
<a href='#a2'>Operable</a>,
<a href='#a3'>Understandable</a>,
and
<a href='#a4'>Robust</a>)
divided into 12 guidelines and 61 Success Criteria (corresponding to checkpoints in WCAG 1.0).
</p>
<p>
In the table on this page, all principles, guidelines, and success criteria are presented
along with their priority level:
</p>
<ul>
 	<li><span class='levelA'>level A</span>: the most important</li>
 	<li><span class='levelAA'>AA or double-A</span>: of intermediate importance</li>
 	<li><span class='levelAAA'>AAA or triple-A</span>: the least important</li>
</ul>
<p>
and links to documentation provided with WCAG 2.0:
</p>
<ul>
 	<li><strong>Details</strong>: a link to the principle, guideline, or success criteria.</li>
 	<li><strong>Understanding</strong>: a link to an explanation of the guideline or success criteria.</li>
 	<li><strong>How-to</strong>: a link to information about how to achieve the success criteria.
 		More information is available in
 		<a target='new' href='http://www.w3.org/TR/WCAG20-TECHS/'>Techniques for WCAG 2.0</a>
 		</li>
</ul>
<p>
Some success criteria have more text than fits on a couple of lines, and for those,
there is a <span class='button' title='Sorry, nothing more here'>$more</span> button that will show more lines;
to make the lines disappear, click the lines anywhere, and the <span class='button' title='Sorry, nothing more here, either'>$more</span> button will reappear.
</p>
<p>
Notes can begin with 2-character codes that color the cell containing the notes:
</p>
<ul>
 	<li><strong class='NA'>NA</strong>:&nbsp; Not Applicable</li>
 	<li><strong class='FC'>FC</strong>:&nbsp; Fully Compliant</li>
 	<li><strong class='PC'>PC</strong>:&nbsp; Partially Compliant</li>
 	<li><strong class='NC'>NC</strong>:&nbsp; Not Compliant</li>
</ul>
"

wcag2=wcag2.db
data=wc.db
url="http://www.w3.org/TR/WCAG20"                       # append #%tag
understand="http://www.w3.org/TR/UNDERSTANDING-WCAG20"  # append /%tag.html
quickref="http://www.w3.org/WAI/WCAG20/quickref"        # append /#qr-%tag

# todo: more "button" is not accessible with keyboard

t="<tr id='a%number' valign='top' class='depth%depth'>
     <th align='left' scope='row'>
         %number
     </th>
     <td class='level%level'>
             <xyzzy>%title</xyzzy><!-- depth=%depth -->: %text
             <div id='extra%number' class='hidden' onclick='hide(\"extra%number\"); show(\"more%number\");' title='Click to hide this expanded text on %number'>%extra</div> <!-- extra=%1.1extra| -->
             <span id='more%number' onclick='show(\"extra%number\"); hide(\"more%number\");' class='button' title='Expand to show more text on %number right here'>$more</span> <!-- extra=%1.1extra| -->
     </td>
     <td class='level%level' align='center'>
         %level&nbsp;
     </td>
 	<td class='%.2notes'>
 		%notes&nbsp;
 	</td>
     <td>
         <a target='new' title='Details for %number' href='$url/#%tag'>%number details</a>
         | <a target='new' title='How to meet %number' href='$quickref/#qr-%tag'>%number how-to</a><!-- depth=%depth -->
         | <a target='new' title='Understanding %number' href='$understand/%tag.html'>%number understanding</a><!-- depth=%depth -->

     </td>
</tr>"

header="<tr>
     <th scope='col'>Number</th>
     <th scope='col' align='left'>Principle / Guideline / Success Criteria</th>
     <th scope='col'>Level</th>
     <th scope='col' align='left'>Notes</th>
     <th scope='col' align='left'>Links</th>
</tr>"

summary="Table of principles, guidelines, and success criteria for WCAG 2.0.
Each row includes a hierarchical number, title and details, priority level (for criteria), optional notes,
and liks to documents with more information."

echo "<table border='1' cellpadding='2' cellspacing='0' summary='$summary'>"
echo "$header"

ssformat=./ssformat
ssmerge=./ssmerge
ssadd=./ssadd

$ssadd -f ident -et "I%number@I" $data | tr -d @ |
 	./ssmerge -fident $wcag2 |
 		./ssformat -t "$t" |
 			sed '
 					/understanding.*depth=1/d
 					/quickref.*depth=[12]/d
 					/: *$/s///
 					/-- extra= |/d
 					/depth=1/s/xyzzy/h2/g
 					/depth=2/s/xyzzy/h3/g
 					/depth=3/s/xyzzy/strong/g
 				'

echo "$header"
echo "</table>
</body>
</html>"
fpack:!@#$%^&*(): wcag2.db
%number 1
%depth 1
%tag perceivable
%title Perceivable
%text Information and user interface components must be presentable to users in ways they can perceive.
%ident I1I

%number 1.1
%depth 2
%tag text-equiv
%title Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
%ident I1.1I

%number 1.1.1
%depth 3
%level A
%tag text-equiv-all
%title Non-text Content
%text All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below.
%extra <ul>
<li><strong>Controls, Input</strong>: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.) </li>
<li><strong>Time-Based Media</strong>: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.) </li>
<li><strong>Test</strong>: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content. </li>
<li><strong>Sensory</strong>: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content. </li>
<li><strong>CAPTCHA</strong>: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.</li>
<li><strong>Decoration, Formatting, Invisible</strong>: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.</li>
</ul>
%ident I1.1.1I

%number 1.2
%depth 2
%tag media-equiv
%title Provide alternatives for time-based media.
%ident I1.2I

%number 1.2.1
%depth 3
%level A
%tag media-equiv-av-only
%title Audio-only and Video-only (Prerecorded)
%text For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:&nbsp;
%extra <ul>
<li><strong>Prerecorded Audio-only</strong>: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.</li>
<li><strong>Prerecorded Video-only</strong>: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.</li>
</ul>
%ident I1.2.1I

%number 1.2.2
%depth 3
%level A
%tag media-equiv-captions
%title Captions (Prerecorded)
%text Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
%ident I1.2.2I

%number 1.2.3
%depth 3
%level A
%tag media-equiv-audio-desc
%title Audio Description or Media Alternative (Prerecorded)
%text An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
%ident I1.2.3I

%number 1.2.4
%depth 3
%level AA
%tag media-equiv-real-time-captions
%title Captions (Live)
%text Captions are provided for all live audio content in synchronized media.
%ident I1.2.4I

%number 1.2.5
%depth 3
%level AA
%tag media-equiv-audio-desc-only
%title Audio Description (Prerecorded)
%text Audio description is provided for all prerecorded video content in synchronized media.
%ident I1.2.5I

%number 1.2.6
%depth 3
%level AAA
%tag media-equiv-sign
%title Sign Language (Prerecorded)
%text Sign language interpretation is provided for all prerecorded audio content in synchronized media.
%ident I1.2.6I

%number 1.2.7
%depth 3
%level AAA
%tag media-equiv-extended-ad
%title Extended Audio Description (Prerecorded)
%text Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media.
%ident I1.2.7I

%number 1.2.8
%depth 3
%level AAA
%tag media-equiv-text-doc
%title Media Alternative (Prerecorded)
%text An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media.
%ident I1.2.8I

%number 1.2.9
%depth 3
%level AAA
%tag media-equiv-live-audio-only
%title Audio-only (Live)
%text An alternative for time-based media that presents equivalent information for live audio-only content is provided.
%ident I1.2.9I

%number 1.3
%depth 2
%tag content-structure-separation
%title Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
%ident I1.3I

%number 1.3.1
%depth 3
%level A
%tag content-structure-separation-programmatic
%title Info and Relationships
%text Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
%ident I1.3.1I

%number 1.3.2
%depth 3
%level A
%tag content-structure-separation-sequence
%title Meaningful Sequence
%text When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
%ident I1.3.2I

%number 1.3.3
%depth 3
%level A
%tag content-structure-separation-understanding
%title Sensory Characteristics
%text Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.
%ident I1.3.3I

%number 1.4
%depth 2
%tag visual-audio-contrast
%title Make it easier for users to see and hear content including separating foreground from background.
%ident I1.4I

%number 1.4.1
%depth 3
%level A
%tag visual-audio-contrast-without-color
%title Use of Color
%text Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
%ident I1.4.1I

%number 1.4.2
%depth 3
%level A
%tag visual-audio-contrast-dis-audio
%title Audio Control
%text If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.
%ident I1.4.2I

%number 1.4.3
%depth 3
%level AA
%tag visual-audio-contrast-contrast
%title Contrast (Minimum)
%text The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:&nbsp;
%extra <ul>
       <li><strong>Large Text</strong>: Large-scale text and images of large-scale text have a contrast ratio of at least 4.5:1;</li>
       <li><strong>Incidental</strong>: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.</li>
       <li><strong>Logotypes</strong>: Text that is part of a logo or brand name has no minimum contrast requirement.</li>
</ul>
%ident I1.4.3I

%number 1.4.4
%depth 3
%level AA
%tag visual-audio-contrast-scale
%title Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
%ident I1.4.4I

%number 1.4.5
%depth 3
%level AA
%tag visual-audio-contrast-text-presentation
%title Images of Text
%text If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following:&nbsp;
%extra <ul>
 	<li><strong>Customizable</strong>: The image of text can be visually customized to the user's requirements;</li>
 	<li><strong>Essential</strong>: A particular presentation of text is essential to the information being conveyed.</li>
</ul>
%ident I1.4.5I

%number 1.4.6
%depth 3
%level AAA
%tag visual-audio-contrast7
%title Contrast (Enhanced)
%text The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following:&nbsp;
%extra <ul>
 	<li><strong>Large Text</strong>: Large-scale text and images of large-scale text have a contrast ratio of at least 4.5:1;</li>
 	<li><strong>Incidental</strong>: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.</li>
 	<li><strong>Logotypes</strong>: Text that is part of a logo or brand name has no minimum contrast requirement.</li>
</ul>
%ident I1.4.6I

%number 1.4.7
%depth 3
%level AAA
%tag visual-audio-contrast-noaudio
%title Low or No Background Audio
%text For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true:&nbsp;
%extra <ul>
 	<li><strong>No Background</strong>: The audio does not contain background sounds.</li>
 	<li><strong>Turn Off</strong>: The background sounds can be turned off.</li>
 	<li><strong>20 dB</strong>: The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds.</li>
</ul>
%ident I1.4.7I

%number 1.4.8
%depth 3
%level AAA
%tag visual-audio-contrast-visual-presentation
%title Visual Presentation
%text For the visual presentation of blocks of text, a mechanism is available to achieve the following:&nbsp;
%extra <ol>
 	<li>Foreground and background colors can be selected by the user.</li>
 	<li>Width is no more than 80 characters or glyphs (40 if CJK).</li>
 	<li>Text is not justified (aligned to both the left and the right margins).</li>
 	<li>Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing.</li>
 	<li>Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window.</li>
</ol>
%ident I1.4.8I

%number 1.4.9
%depth 3
%level AAA
%tag visual-audio-contrast-text-images
%title Images of Text (No Exception)
%text Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.
%ident I1.4.9I

%number 2
%depth 1
%tag operable
%title Operable
%text User interface components and navigation must be operable.
%ident I2I

%number 2.1
%depth 2
%tag keyboard-operation
%title Make all functionality available from a keyboard.
%ident I2.1I

%number 2.1.1
%depth 3
%level A
%tag keyboard-operation-keyboard-operable
%title Keyboard
%text All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.
%ident I2.1.1I

%number 2.1.2
%depth 3
%level A
%tag keyboard-operation-trapping
%title No Keyboard Trap
%text If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.
%ident I2.1.2I

%number 2.1.3
%depth 3
%level AAA
%tag keyboard-operation-all-funcs
%title Keyboard (No Exception)
%text All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
%ident I2.1.3I

%number 2.2
%depth 2
%tag time-limits
%title Provide users enough time to read and use content.
%ident I2.2I

%number 2.2.1
%depth 3
%level A
%tag time-limits-required-behaviors
%title Timing Adjustable
%text For each time limit that is set by the content, at least one of the following is true:&nbsp;
%extra <ul>
 	<li><strong>Turn off</strong>: The user is allowed to turn off the time limit before encountering it; or </li>
 	<li><strong>Adjust</strong>: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or</li>
 	<li><strong>Extend</strong>: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or</li>
 	<li><strong>Real-time Exception</strong>: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or</li>
 	<li><strong>Essential Exception</strong>: The time limit is essential and extending it would invalidate the activity; or </li>
 	<li><strong>20 Hour Exception</strong>: The time limit is longer than 20 hours. </li>
</ul>
%ident I2.2.1I

%number 2.2.2
%depth 3
%level A
%tag time-limits-pause
%title Pause, Stop, Hide
%text For moving, blinking, scrolling, or auto-updating information, all of the following are true:&nbsp;
%extra <ul>
 	<li><strong>Moving, blinking, scrolling</strong>: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and</li>
 	<li><strong>Auto-updating</strong>: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.</li>
</ul>
%ident I2.2.2I

%number 2.2.3
%depth 3
%level AAA
%tag time-limits-no-exceptions
%title No Timing
%text Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events.
%ident I2.2.3I

%number 2.2.4
%depth 3
%level AAA
%tag time-limits-postponed
%title Interruptions
%text Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.
%ident I2.2.4I

%number 2.2.5
%depth 3
%level AAA
%tag time-limits-server-timeout
%title Re-authenticating
%text When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.
%ident I2.2.5I

%number 2.3
%depth 2
%tag seizure
%title Do not design content in a way that is known to cause seizures.
%ident I2.3I

%number 2.3.1
%depth 3
%level A
%tag seizure-does-not-violate
%title Three Flashes or Below Threshold
%text Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.
%ident I2.3.1I

%number 2.3.2
%depth 3
%level AAA
%tag seizure-three-times
%title Three Flashes
%text Web pages do not contain anything that flashes more than three times in any one second period.
%ident I2.3.2I

%number 2.4
%depth 2
%tag navigation-mechanisms
%title Provide ways to help users navigate, find content, and determine where they are.
%ident I2.4I

%number 2.4.1
%depth 3
%level A
%tag navigation-mechanisms-skip
%title Bypass Blocks
%text A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
%ident I2.4.1I

%number 2.4.2
%depth 3
%level A
%tag navigation-mechanisms-title
%title Page Titled
%text Web pages have titles that describe topic or purpose.
%ident I2.4.2I

%number 2.4.3
%depth 3
%level A
%tag navigation-mechanisms-focus-order
%title Focus Order
%text If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
%ident I2.4.3I

%number 2.4.4
%depth 3
%level A
%tag navigation-mechanisms-refs
%title Link Purpose (In Context)
%text The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.
%ident I2.4.4I

%number 2.4.5
%depth 3
%level AA
%tag navigation-mechanisms-mult-loc
%title Multiple Ways
%text More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.
%ident I2.4.5I

%number 2.4.6
%depth 3
%level AA
%tag navigation-mechanisms-descriptive
%title Headings and Labels
%text Headings and labels describe topic or purpose.
%ident I2.4.6I

%number 2.4.7
%depth 3
%level AA
%tag navigation-mechanisms-focus-visible
%title Focus Visible
%text Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
%ident I2.4.7I

%number 2.4.8
%depth 3
%level AAA
%tag navigation-mechanisms-location
%title Location
%text Information about the user's location within a set of Web pages is available.
%ident I2.4.8I

%number 2.4.9
%depth 3
%level AAA
%tag navigation-mechanisms-link
%title Link Purpose (Link Only)
%text A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.
%ident I2.4.9I

%number 2.4.10
%depth 3
%level AAA
%tag navigation-mechanisms-headings
%title Section Headings
%text Section headings are used to organize the content.
%ident I2.4.10I

%number 3
%depth 1
%tag understandable
%title Understandable
%text Information and the operation of user interface must be understandable.
%ident I3I

%number 3.1
%depth 2
%tag meaning
%title Make text content readable and understandable.
%ident I3.1I

%number 3.1.1
%depth 3
%level A
%tag meaning-doc-lang-id
%title Language of Page
%text The default human language of each Web page can be programmatically determined.
%ident I3.1.1I

%number 3.1.2
%depth 3
%level AA
%tag meaning-other-lang-id
%title Language of Parts
%text The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.
%ident I3.1.2I

%number 3.1.3
%depth 3
%level AAA
%tag meaning-idioms
%title Unusual Words
%text A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.
%ident I3.1.3I

%number 3.1.4
%depth 3
%level AAA
%tag meaning-located
%title Abbreviations
%text A mechanism for identifying the expanded form or meaning of abbreviations is available.
%ident I3.1.4I

%number 3.1.5
%depth 3
%level AAA
%tag meaning-supplements
%title Reading Level
%text When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available.
%ident I3.1.5I

%number 3.1.6
%depth 3
%level AAA
%tag meaning-pronunciation
%title Pronunciation
%text A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.
%ident I3.1.6I

%number 3.2
%depth 2
%tag consistent-behavior
%title Make Web pages appear and operate in predictable ways.
%ident I3.2I

%number 3.2.1
%depth 3
%level A
%tag consistent-behavior-receive-focus
%title On Focus
%text When any component receives focus, it does not initiate a change of context.
%ident I3.2.1I

%number 3.2.2
%depth 3
%level A
%tag consistent-behavior-unpredictable-change
%title On Input
%text Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.
%ident I3.2.2I

%number 3.2.3
%depth 3
%level AA
%tag consistent-behavior-consistent-locations
%title Consistent Navigation
%text Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.
%ident I3.2.3I

%number 3.2.4
%depth 3
%level AA
%tag consistent-behavior-consistent-functionality
%title Consistent Identification
%text Components that have the same functionality within a set of Web pages are identified consistently.
%ident I3.2.4I

%number 3.2.5
%depth 3
%level AAA
%tag consistent-behavior-no-extreme-changes-context
%title Change on Request
%text Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
%ident I3.2.5I

%number 3.3
%depth 2
%tag minimize-error
%title Help users avoid and correct mistakes.
%ident I3.3I

%number 3.3.1
%depth 3
%level A
%tag minimize-error-identified
%title Error Identification
%text If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.
%ident I3.3.1I

%number 3.3.2
%depth 3
%level A
%tag minimize-error-cues
%title Labels or Instructions
%text Labels or instructions are provided when content requires user input.
%ident I3.3.2I

%number 3.3.3
%depth 3
%depth 3
%level AA
%tag minimize-error-suggestions
%title Error Suggestion
%text If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.
%ident I3.3.3I

%number 3.3.4
%depth 3
%level AA
%tag minimize-error-reversible
%title Error Prevention (Legal, Financial, Data)
%text For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:&nbsp;
%extra <ol>
 	<li><strong>Reversible</strong>: Submissions are reversible.</li>
 	<li><strong>Checked</strong>: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.</li>
 	<li><strong>Confirmed</strong>: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.</li>
</ol>
%ident I3.3.4I

%number 3.3.5
%depth 3
%level AAA
%tag minimize-error-context-help
%title Help
%text Context-sensitive help is available.
%ident I3.3.5I

%number 3.3.6
%depth 3
%level AAA
%tag minimize-error-reversible-all
%title Error Prevention (All)
%text For Web pages that require the user to submit information, at least one of the following is true:&nbsp;
%extra <ol>
 	<li><strong>Reversible</strong>: Submissions are reversible.</li>
 	<li><strong>Checked</strong>: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.</li>
 	<li><strong>Confirmed</strong>: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.</li>
</ol>
%ident I3.3.6I

%number 4
%depth 1
%tag robust
%title Robust
%text Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
%ident I4I

%number 4.1
%depth 2
%tag ensure-compat
%title Maximize compatibility with current and future user agents, including assistive technologies.
%ident I4.1I

%number 4.1.1
%depth 3
%level A
%tag ensure-compat-parses
%title Parsing
%text In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.
%ident I4.1.1I

%number 4.1.2
%depth 3
%level A
%tag ensure-compat-rsv
%title Name, Role, Value
%text For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
%extra <p>
Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.
</p>
%ident I4.1.2I

fpack:!@#$%^&*(): wc.db
%number 1.1.1
%level A
%tag text-equiv-all
%title Non-text Content
%notes PC alt-text

%number 1.2.1
%level A
%tag media-equiv-av-only
%title Audio-only and Video-only (Prerecorded)
%notes NA

%number 1.2.2
%level A
%tag media-equiv-captions
%title Captions (Prerecorded)
%notes NA

%number 1.2.3
%level A
%tag media-equiv-audio-desc
%title Audio Description or Media Alternative (Prerecorded)
%notes NA

%number 1.2.4
%level AA
%tag media-equiv-real-time-captions
%title Captions (Live)
%notes NA

%number 1.2.5
%level AA
%tag media-equiv-audio-desc-only
%title Audio Description (Prerecorded)
%notes NA

%number 1.2.6
%level AAA
%tag media-equiv-sign
%title Sign Language (Prerecorded)
%notes NA

%number 1.2.7
%level AAA
%tag media-equiv-extended-ad
%title Extended Audio Description (Prerecorded)
%notes NA

%number 1.2.8
%level AAA
%tag media-equiv-text-doc
%title Media Alternative (Prerecorded)
%notes NA

%number 1.2.9
%level AAA
%tag media-equiv-live-audio-only
%title Audio-only (Live)
%notes NA

%number 1.3.1
%level A
%tag content-structure-separation-programmatic
%title Info and Relationships
%notes PC

%number 1.3.2
%level A
%tag content-structure-separation-sequence
%title Meaningful Sequence
%notes FC?

%number 1.3.3
%level A
%tag content-structure-separation-understanding
%title Sensory Characteristics
%notes PC graphic design
/ some text refers to top, next, ...

%number 1.4.1
%level A
%tag visual-audio-contrast-without-color
%title Use of Color
%notes FC graphic design

%number 1.4.2
%level A
%tag visual-audio-contrast-dis-audio
%title Audio Control
%notes NA

%number 1.4.3
%level AA
%tag visual-audio-contrast-contrast
%title Contrast (Minimum)
%notes graphic design

%number 1.4.4
%level AA
%tag visual-audio-contrast-scale
%title Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
%notes FC graphic design

%number 1.4.5
%level AA
%tag visual-audio-contrast-text-presentation
%title Images of Text
%notes NA graphic design - images of text are not used in wc.org; logos in WCl are allowed

%number 1.4.6
%level AAA
%tag visual-audio-contrast7
%title Contrast (Enhanced)
%notes graphic design

%number 1.4.7
%level AAA
%tag visual-audio-contrast-noaudio
%title Low or No Background Audio
%notes NA

%number 1.4.8
%level AAA
%tag visual-audio-contrast-visual-presentation
%title Visual Presentation
%notes NC graphic design - Several options not available.

%number 1.4.9
%level AAA
%tag visual-audio-contrast-text-images
%title Images of Text (No Exception)
%notes FC graphic design

%number 2.1.1
%level A
%tag keyboard-operation-keyboard-operable
%title Keyboard
%notes FC

%number 2.1.2
%level A
%tag keyboard-operation-trapping
%title No Keyboard Trap
%notes NA

%number 2.1.3
%level AAA
%tag keyboard-operation-all-funcs
%title Keyboard (No Exception)
%notes FC

%number 2.2.1
%level A
%tag time-limits-required-behaviors
%title Timing Adjustable
%notes PC timing

%number 2.2.2
%level A
%tag time-limits-pause
%title Pause, Stop, Hide
%notes NA

%number 2.2.3
%level AAA
%tag time-limits-no-exceptions
%title No Timing
%notes NA

%number 2.2.4
%level AAA
%tag time-limits-postponed
%title Interruptions
%notes NA

%number 2.2.5
%level AAA
%tag time-limits-server-timeout
%title Re-authenticating
%notes PC timing

%number 2.3.1
%level A
%tag seizure-does-not-violate
%title Three Flashes or Below Threshold
%notes NA

%number 2.3.2
%level AAA
%tag seizure-three-times
%title Three Flashes
%notes NA

%number 2.4.1
%level A
%tag navigation-mechanisms-skip
%title Bypass Blocks
%notes FC?

%number 2.4.2
%level A
%tag navigation-mechanisms-title
%title Page Titled
%notes FC

%number 2.4.3
%level A
%tag navigation-mechanisms-focus-order
%title Focus Order
%notes FC

%number 2.4.4
%level A
%tag navigation-mechanisms-refs
%title Link Purpose (In Context)
%notes

%number 2.4.5
%level AA
%tag navigation-mechanisms-mult-loc
%title Multiple Ways
%notes FC

%number 2.4.6
%level AA
%tag navigation-mechanisms-descriptive
%title Headings and Labels
%notes PC h# and label

%number 2.4.7
%level AA
%tag navigation-mechanisms-focus-visible
%title Focus Visible
%notes PC Look into setting the focus on search results and detailed record to the search box.

%number 2.4.8
%level AAA
%tag navigation-mechanisms-location
%title Location
%notes

%number 2.4.9
%level AAA
%tag navigation-mechanisms-link
%title Link Purpose (Link Only)
%notes

%number 2.4.10
%level AAA
%tag navigation-mechanisms-headings
%title Section Headings
%notes

%number 3.1.1
%level A
%tag meaning-doc-lang-id
%title Language of Page
%notes FC wc.org already lists the UI language on each page.

%number 3.1.2
%level AA
%tag meaning-other-lang-id
%title Language of Parts
%notes PC This is complicated in WorldCat.
The only parts of a record for which we can confidently identify the language are
subject headings and marc 880 non-Latin script.
It is not clear what to do for the millions of records that have fields that may not be in English.
<ul>
 	<li><strong>Language of the item</strong>:&nbsp;
 		There is a good chance that various fields match the language of the item,
 		but it is not assured. Titles might be in English and the other language.
 		Abstracts are usually only in English. Publication locations are usually in English (e.g., Vienna, not Wien)</li>
 	<li><strong>Other languages</strong>:&nbsp;
 		Websites and DVDs often come in multiple languages,
 		and these languages can appear in the catalg data.</li>
 	<li><strong>Language of cataloging</strong>:&nbsp;
 		When the cataloging language is not English,
 		one would expect that most of the data is not English,
 		but the utility of this information has been disappointing.
 		Perhaps we can identify some cataloging agencies that reliably catalog in a specific language.</li>
 	<li><strong>Subject headings</strong>:&nbsp;
 		One of our best sources of language is in subject headings because
 		each comes with a cataloging agency and each agency implies a specific language.
 		This information has been used for a few years in wc.org.</li>
 	<li><strong>Non-Latin script</strong>:&nbsp;
 		The marc 880 script sometimes, by itself, implies a language, but there are sometimes ambiguity
 		(e.g., Hebrew vs. Yiddish, Traditional versus Simplified Chinese vs. Japanese).
 		If only one language is mentioned in the language of the item or the language of cataloging,
 		then the identification of the language of the 880 data in a record is reliable.
 		Sometimes, more than one language is mentioned, which introduces ambiguity.</li>
 	<li><strong>Uniform titles</strong>:&nbsp;
 		Uniform titles are always in the language of the original work, so the uniform title (marc 240 or 130) of
 		"20,000 Leagues Under the Sea" is "Vingt Mille Lieues sous les Mers" (French).</li>
 	<li><strong>Proper names</strong>:&nbsp;
 		We have no markup in WorldCat to indicate the language of names,
 		but it might be possible to consult the name authority file to get this information.</li>
 	<li><strong>Links</strong>:&nbsp;
 		<a href="http://www.w3.org/International/articles/language-tags/Overview.en.php">W3C language tags</a>
 		| <a href="http://www.w3.org/TR/i18n-html-tech-lang/">W3C lang spec</a></li>
</ul>

%number 3.1.3
%level AAA
%tag meaning-idioms
%title Unusual Words
%notes NA?

%number 3.1.4
%level AAA
%tag meaning-located
%title Abbreviations
%notes NA?

%number 3.1.5
%level AAA
%tag meaning-supplements
%title Reading Level
%notes NA?

%number 3.1.6
%level AAA
%tag meaning-pronunciation
%title Pronunciation
%notes NA

%number 3.2.1
%level A
%tag consistent-behavior-receive-focus
%title On Focus
%notes

%number 3.2.2
%level A
%tag consistent-behavior-unpredictable-change
%title On Input
%notes NC Checkboxes and menus that immediately make changes should have title text indicating the behavior of the component.

%number 3.2.3
%level AA
%tag consistent-behavior-consistent-locations
%title Consistent Navigation
%notes FC

%number 3.2.4
%level AA
%tag consistent-behavior-consistent-functionality
%title Consistent Identification
%notes FC

%number 3.2.5
%level AAA
%tag consistent-behavior-no-extreme-changes-context
%title Change on Request
%notes

%number 3.3.1
%level A
%tag minimize-error-identified
%title Error Identification
%notes FC

%number 3.3.2
%level A
%tag minimize-error-cues
%title Labels or Instructions
%notes FC

%number 3.3.3
%level AA
%tag minimize-error-suggestions
%title Error Suggestion
%notes FC

%number 3.3.4
%level AA
%tag minimize-error-reversible
%title Error Prevention (Legal, Financial, Data)
%notes FC? WMS fines?

%number 3.3.5
%level AAA
%tag minimize-error-context-help
%title Help
%notes NC wc.org help is not context sensitive

%number 3.3.6
%level AAA
%tag minimize-error-reversible-all
%title Error Prevention (All)
%notes FC?

%number 4.1.1
%level A
%tag ensure-compat-parses
%title Parsing
%notes NC wc.org does not parse to any grammar.

%number 4.1.2
%level A
%tag ensure-compat-rsv
%title Name, Role, Value
%notes PC? TinyMCE editor used in social (optionally swap out for a textarea)?
<a target='new' title='few changes since approval of WCAG 2.0' href='http://wiki.moxiecode.com/index.php/TinyMCE:Accessibility'>TinyMCE Accessibility</a>

fpack:!@#$%^&*():

From perlman@turing.acm.org Thu Dec  9 11:18:58 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Thu, 9 Dec 2010 11:18:58 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: HCI Webliography <apache@turing.acm.org>
cc: director@hcibib.org, info@jab-design.de
Subject: Re: !SUGGEST_a_LINK! hci-sites:companies: Webdesign Hamburg
 Designexperts
In-Reply-To: <201012091424.oB9EObIX013046@turing.acm.org>
Message-ID: <Pine.LNX.4.64.1012091118500.20256@turing.acm.org>
References: <201012091424.oB9EObIX013046@turing.acm.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

I am sorry, but the site below does not have specific HCI
content and will not be included in the HCI Bibliography.
 	http://hcibib.org/faq.html#Data-5

Gary Perlman, Director, HCI Bibliography Project
mailto:director@hcibib.org  http://hcibib.org/

On Thu, 9 Dec 2010, HCI Webliography wrote:

> Reply-To: director@hcibib.org
>
> This data is being sent to director@hcibib.org
> to be considered for inclusion in the HCI Bibliography
>
> %M U.jab-design.de   85.177.167.53
> %0 INTERNET
> %D 2010-12-09
> %K hci-sites:companies
> %A Joska Moeller
> %C Germany, Hamburg, Hamburg
> %I JAB-Designexperts
> %K webdesign, printdesign, logodesign, magazines, brochures
> %L German, English
> %T Webdesign Hamburg Designexperts
> %U info@jab-design.de
> %W http://www.jab-design.de
> %X Webdesign and media design company with over 20 years of experience in the media branch
>
> Information from this tool may also be used for your entry:
> http://hcibib.org/accessibility/chaccess.cgi?url=http://www.jab-design.de
>

From perlman@turing.acm.org Sat Dec 11 13:18:59 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Sat, 11 Dec 2010 13:18:59 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: Gary perlman <perlman@turing.acm.org>
Subject: !contrast ratio formulay
Message-ID: <Pine.LNX.4.64.1012111318290.22848@turing.acm.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

http://www.w3.org/TR/2007/WD-WCAG20-TECHS-20070517/Overview.html#G18

From perlman@turing.acm.org Sat Dec 11 18:05:46 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Sat, 11 Dec 2010 18:05:45 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: Gary Perlman at OCLC <perlman@oclc.org>
Subject: vision formulas
Message-ID: <Pine.LNX.4.64.1012111805030.9186@turing.acm.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

http://www.visionaustralia.org/info.aspx?page=628

It is a tool for checking foreground & background colour combinations to determine if they provide good colour visibility. Determining "colour visibility" is based on algorithms suggested by the World Wide Web Consortium (W3C):

"Two colours are considered to provide good colour visibility if the brightness difference and the colour difference between the two colours are greater than a set range." The range suggested by the W3C is > 125 for colour brightness and > 500 for colour difference.

Note: Hewlett Packard (HP) provide an online colour contrast verification tool that uses the W3C algorithms, but sets the Colour Difference range at > 400, which results in a greater range of foreground & background colour combinations being deemed acceptable.

Colour Brightness Formula
Colour brightness is determined by the following formula:

((Red value X 299) + (Green value X 587) + (Blue value X 114)) / 1000

The difference between the background brightness, and the foreground brightness should be greater than 125.

Note: This algorithm is taken from a formula for converting RGB values to YIQ values. This brightness value gives a perceived brightness for a colour.

Colour Difference Formula
Colour difference is determined by the following formula:

(maximum (Red value 1, Red value 2) - minimum (Red value 1, Red value 2)) + (maximum (Green value 1, Green value 2) - minimum (Green value 1, Green value 2)) + (maximum (Blue value 1, Blue value 2) - minimum (Blue value 1, Blue value 2))

The difference between the background colour and the foreground colour should be greater than 500.




From perlman@turing.acm.org Mon Dec 13 11:56:16 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Mon, 13 Dec 2010 11:56:16 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: HCI Webliography <apache@turing.acm.org>
cc: director@hcibib.org, joshuasturgeon@gmail.com
Subject: Re: !SUGGEST_a_LINK! intercultural:translation: Translation Boston
 MA
In-Reply-To: <201012130624.oBD6OZQS011382@turing.acm.org>
Message-ID: <Pine.LNX.4.64.1012131155490.7698@turing.acm.org>
References: <201012130624.oBD6OZQS011382@turing.acm.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

I am sorry, but the site below does not have specific HCI
content and will not be included in the HCI Bibliography.
 	http://hcibib.org/faq.html#Data-5

Gary Perlman, Director, HCI Bibliography Project
mailto:director@hcibib.org  http://hcibib.org/

On Mon, 13 Dec 2010, HCI Webliography wrote:

> Reply-To: director@hcibib.org
>
> This data is being sent to director@hcibib.org
> to be considered for inclusion in the HCI Bibliography
>
> %M U.citygateinterpreters.com   98.217.217.11
> %0 INTERNET
> %D 2010-12-13
> %K intercultural:translation intercultural:companies
> %A Josh
> %C United States, Massachusetts, Boston
> %I City Gate Interpreters
> %K City Gate Interpreters & Translation offers certified language services to to a variety of clients who are looking to bridge the gaps in their communication.
> %L English
> %T Translation Boston MA
> %U joshuasturgeon@gmail.com
> %W http://www.citygateinterpreters.com
> %X Online translation for important documents or marketing materials and live interpretation (consecutive or simultaneous).
>
> Information from this tool may also be used for your entry:
> http://hcibib.org/accessibility/chaccess.cgi?url=http://www.citygateinterpreters.com
>

From perlman@turing.acm.org Fri Dec 17 23:37:26 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Fri, 17 Dec 2010 23:37:24 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: Guillermo G <guillermog@trusted-directory.com>
cc: Webmaster <director@hcibib.org>
Subject: Re: Link Exchange Request
In-Reply-To: <7470368.1175.1292530939538.JavaMail.guillermog@VirtualPC035>
Message-ID: <Pine.LNX.4.64.1012172331390.15693@turing.acm.org>
References: <7470368.1175.1292530939538.JavaMail.guillermog@VirtualPC035>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

Hi,

We do not do link exchanges.

We have 4 links to trustedtranslations.com.

If you want to link to hcibib.org, the information you want is in our metadata:

http://hcibib.org/accessibility/chaccess.cgi?url=hcibib.org&links=checked

This page is probably the most relevant to you:
 	http://hcibib.org/intercultural/
which has different metadata:
 	http://hcibib.org/accessibility/chaccess.cgi?url=hcibib%2Eorg%2Fintercultural

Gary Perlman, Director, HCI Bibliography Project
mailto:director@hcibib.org  http://hcibib.org/

On Thu, 16 Dec 2010, Guillermo G wrote:

> Dear Webmaster,
>
> I'm the webmaster of http://www.trustedtranslations.com
> I'm contacting you again because I am not sure you received my
> previous email about exchanging links with your site.
>
> I believe that a link to your site will benefit you.
> If you are interested in the offer, please use the information below
> to add our link to your webpage:
>
> Title: Spanish Translation
>
> URL: http://www.trustedtranslations.com
>
> Description: Translation company leader in Spanish translation and
> language translations. Free quote or consultation. Quality at the best rates.
> Expert Translator teams.
>
> Our HTML code is: <a href="http://www.trustedtranslations.com"
> target="_blank">Spanish Translation</a> - Translation company leader in
> Spanish translation and language translations. Free quote or consultation.
> Quality at the best rates. Expert Translator teams.
>
>
> If you are interested in exchanging links, please send me the
> following information:
> URL:
> Title:
> Description:
>
> I manage different pages so it would be more practical that you let
> me know where you would post our link so that I post your link on a
> similar page.
>
> Looking forward to your response!
>
> Regards,
>
> Guillermo G
> guillermog@trusted-directory.com

From perlman@turing.acm.org Fri Dec 17 23:38:47 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Fri, 17 Dec 2010 23:38:47 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: oliang@u.washington.edu
Subject: Re: need location of |STAT
In-Reply-To: <alpine.LRH.2.01.1012161549210.9819@hymn33.u.washington.edu>
Message-ID: <Pine.LNX.4.64.1012172338350.15693@turing.acm.org>
References: <alpine.LRH.2.01.1012161549210.9819@hymn33.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

Thank you for your interest in |STAT data manipulation and analysis software.

UNIX |STAT for is now (only) available via Web browsers at a secret location.
 	http://www.hcibib.org/stat/xyzzy/

To obtain UNIX |STAT files, please follow the instructions at:
 	http://www.acm.org/perlman/stat/#access
There are installation notes (e.g., for Mac OS X and Linux) at:
 	http://www.acm.org/perlman/stat/installation.txt

DOS |STAT executables and documentation are available as a WinZip file:
 	http://www.acm.org/perlman/stat/DOS-STAT.ZIP

HTML documentation is available from the |STAT home page:
 	http://www.acm.org/perlman/stat/

On Thu, 16 Dec 2010, oliang@u.washington.edu wrote:

> I AGREE TO ADHERE TO THE CONDITIONS OF USING |STAT.
>   I AGREE NOT TO SHARE THE |STAT LOCATION WITH OTHERS.
>
> Olivia Liang
> UW IBIC Core Neuroimaging
> 206-685-6709
> oliang@u.washington.edu
>
>

From perlman@turing.acm.org Tue Dec 21 21:27:51 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Tue, 21 Dec 2010 21:27:50 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: Allen Delaney <allen@ourlastresort.net>
Subject: Re: |STAT request
In-Reply-To: <55AD40B0-70B8-4134-8C7C-002DFD97ECEF@ourlastresort.net>
Message-ID: <Pine.LNX.4.64.1012212127220.17275@turing.acm.org>
References: <55AD40B0-70B8-4134-8C7C-002DFD97ECEF@ourlastresort.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

Thank you for your interest in |STAT data manipulation and analysis software.

UNIX |STAT for is now (only) available via Web browsers at a secret location.
 	http://www.hcibib.org/stat/xyzzy/

To obtain UNIX |STAT files, please follow the instructions at:
 	http://www.acm.org/perlman/stat/#access
There are installation notes (e.g., for Mac OS X and Linux) at:
 	http://www.acm.org/perlman/stat/installation.txt

DOS |STAT executables and documentation are available as a WinZip file:
 	http://www.acm.org/perlman/stat/DOS-STAT.ZIP

HTML documentation is available from the |STAT home page:
 	http://www.acm.org/perlman/stat/

On Tue, 21 Dec 2010, Allen Delaney wrote:

>
> I've been using your package for a couple of decades, but I've lost the source archive. (Must be getting old).
>
> Can you let me know the web location and any required passwords?
>
> Thanks
>
>   I AGREE TO ADHERE TO THE CONDITIONS OF USING |STAT.
>   I AGREE NOT TO SHARE THE |STAT LOCATION WITH OTHERS.
>
> Allen Delaney
>
>

From perlman@turing.acm.org Wed Dec 22 17:42:26 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Wed, 22 Dec 2010 17:42:25 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: Valentina Budici <editor@polilingua.com>
cc: director@hcibib.org
Subject: Re: Link to your site
In-Reply-To: <AANLkTikW-0bEurCuDAgJsz5_sT+N2efEYtJF8V959ma3@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1012221737220.14943@turing.acm.org>
References: <AANLkTikW-0bEurCuDAgJsz5_sT+N2efEYtJF8V959ma3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

Please see: http://hcibib.org/faq.html#Data-5

I suggest this form: http://www.hcibib.org/suggest.cgi?category=intercultural:translation

The language field should contain en, ru, ro, and de

Here is an analysis of the accessibility of your page:
 	http://hcibib.org/accessibility/chaccess.cgi?url=http%3A%2F%2Fwww.polilingua.com%2F&links=checked&warn=checked&labels=checked

Gary Perlman, Director, HCI Bibliography Project
mailto:director@hcibib.org  http://hcibib.org/

On Wed, 22 Dec 2010, Valentina Budici wrote:

> Hi!
>
> I am the editor at PoliLingua.com, I?ve found your site:
> http://www.hcibib.org/intercultural/
>
> I am interested in exchanging links with you. If interested too, please read
> on...
> I suppose you know that links pointing to your site help improve your
> position in search engines and could significantly increase the number of
> visitors to your website.  In order to benefit to the maximum I propose to
> use cross link exchange. We can offer you a link on any of the pages here:
> http://www.website-translate.com/resources
>
> This is the information about our website we would like to do link exchange:
> Url: http://www.polilingua.com
> Title: Translation services
> Description: PoliLingua delivers translation, localization and managed
> language solutions for clients large and small; in the corporate, government
> and personal sectors.
>
> Please let me know if you are interested.
> Thanks for your time!
> ---
> Best regards,
> Valentina Budici,
> www.PoliLingua.com
> Email : editor@polilingua.com
>

From perlman@turing.acm.org Wed Dec 22 17:47:08 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Wed, 22 Dec 2010 17:47:07 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: HCI Webliography <apache@turing.acm.org>
cc: director@hcibib.org, yao@YaoMandarinSchool.com
Subject: Re: !SUGGEST_a_LINK! intercultural:resources: Learn Pinyin
In-Reply-To: <201012190940.oBJ9e85K001188@turing.acm.org>
Message-ID: <Pine.LNX.4.64.1012221746590.14943@turing.acm.org>
References: <201012190940.oBJ9e85K001188@turing.acm.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

I am sorry, but the site below does not have specific HCI
content and will not be included in the HCI Bibliography.
 	http://hcibib.org/faq.html#Data-5

Gary Perlman, Director, HCI Bibliography Project
mailto:director@hcibib.org  http://hcibib.org/

On Sun, 19 Dec 2010, HCI Webliography wrote:

> Reply-To: director@hcibib.org
> From: yao@YaoMandarinSchool.com (Yao Zhang)
> Sender: yao@YaoMandarinSchool.com
>
> This data is being sent to director@hcibib.org
> to be considered for inclusion in the HCI Bibliography
>
> %M U.quickmandarin.com yao@YaoMandarinSchool.com Yao Zhang 96.49.81.218
> %0 INTERNET
> %D 2010-12-19
> %K intercultural:resources
> %A Yao Zhang
> %K learn Chinese, Quick Mandarin, chinese school, chinese textbook, characters, pinyin
> %L Chinese
> %T Learn Pinyin
> %U yao@YaoMandarinSchool.com
> %W http://www.quickmandarin.com/
> %X Learning Chinese is fun and challenging.  The objective of Quick Mandarin is to help you to Learn Chinese the most efficient way.  Quick Mandarin offers Learn Chinese textbooks and programs at beginner Chinese level, Intermediate and advanced Chinese level. Learn Chinese the efficient way.
>
> Information from this tool may also be used for your entry:
> http://hcibib.org/accessibility/chaccess.cgi?url=http://www.quickmandarin.com/
>

From perlman@turing.acm.org Wed Dec 22 17:51:48 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Wed, 22 Dec 2010 17:51:46 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: HCI Webliography <apache@turing.acm.org>
cc: director@hcibib.org, joannnacorvino@gmail.com, order@KTranslation.com
Subject: Re: !SUGGEST_a_LINK! intercultural:translation: Korean Translation
In-Reply-To: <201012190932.oBJ9Wll9022737@turing.acm.org>
Message-ID: <Pine.LNX.4.64.1012221751060.14943@turing.acm.org>
References: <201012190932.oBJ9Wll9022737@turing.acm.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

I have processed this as a minor update to your existing entry.

Gary Perlman, Director, HCI Bibliography Project
mailto:director@hcibib.org  http://hcibib.org/

On Sun, 19 Dec 2010, HCI Webliography wrote:

> Reply-To: director@hcibib.org
> From: joannnacorvino@gmail.com (joanna corvino)
> Sender: joannnacorvino@gmail.com
>
> This data is being sent to director@hcibib.org
> to be considered for inclusion in the HCI Bibliography
>
> %M U.ktranslation.com joannnacorvino@gmail.com joanna corvino 96.49.81.218
> %0 INTERNET
> %D 2010-12-19
> %K intercultural:translation
> %A Yao Zhang
> %K Korean translation, Korean translate, document certified translation,cheap
> %L Korean to English, English to Korean
> %T Korean Translation
> %U order@KTranslation.com
> %W http://www.ktranslation.com/
> %X KTranslation, Korean translation is the premium Korean English translation service provider, we translate all kinds of documents. We  provide Certified Korean translation.
>
> Information from this tool may also be used for your entry:
> http://hcibib.org/accessibility/chaccess.cgi?url=http://www.ktranslation.com/
>

From perlman@turing.acm.org Wed Dec 22 17:55:54 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Wed, 22 Dec 2010 17:55:53 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: HCI Webliography <apache@turing.acm.org>
cc: director@hcibib.org, joannnacorvino@gmail.com, 
    order@ChineseTranslationPro.com
Subject: Re: !SUGGEST_a_LINK! intercultural:translation: Chinese Translation
In-Reply-To: <201012190930.oBJ9UPwj018922@turing.acm.org>
Message-ID: <Pine.LNX.4.64.1012221755220.14943@turing.acm.org>
References: <201012190930.oBJ9UPwj018922@turing.acm.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

I have processed this submission as an update to your existing entry.

Gary Perlman, Director, HCI Bibliography Project
mailto:director@hcibib.org  http://hcibib.org/

On Sun, 19 Dec 2010, HCI Webliography wrote:

> Reply-To: director@hcibib.org
> From: joannnacorvino@gmail.com (joanna corvino)
> Sender: joannnacorvino@gmail.com
>
> This data is being sent to director@hcibib.org
> to be considered for inclusion in the HCI Bibliography
>
> %M U.chinesetranslationpro.com joannnacorvino@gmail.com joanna corvino 96.49.81.218
> %0 INTERNET
> %D 2010-12-19
> %K intercultural:translation
> %A Yao Zhang
> %K Chinese Translation, Chinese translate, document certified translation, business translator
> %L Chinese to English, English to Chinese Translation
> %T Chinese Translation
> %U order@ChineseTranslationPro.com
> %W http://www.chinesetranslationpro.com/
> %X Chinese Translation Pro is Chinese English translation specialist which you can afford, we can translate all kinds of documents including manuals, websites, legal and business documents. We provide Certified Chinese Translation
>
> Information from this tool may also be used for your entry:
> http://hcibib.org/accessibility/chaccess.cgi?url=http://www.chinesetranslationpro.com/
>

From perlman@turing.acm.org Thu Dec 23 11:18:18 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Thu, 23 Dec 2010 11:18:18 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: Valentina Budici <editor@polilingua.com>
Subject: Re: Link to your site
In-Reply-To: <AANLkTinVwjqYKSFeunjoMT39VH5L2fZUw+Smsruin9ay@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1012231114060.4679@turing.acm.org>
References: <AANLkTikW-0bEurCuDAgJsz5_sT+N2efEYtJF8V959ma3@mail.gmail.com>
 <Pine.LNX.4.64.1012221737220.14943@turing.acm.org>
 <AANLkTinVwjqYKSFeunjoMT39VH5L2fZUw+Smsruin9ay@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

Next, you appear on the page: http://hcibib.org/intercultural/
Finally, send updates if you have them.

Merry Christmas to you and yours.

Gary Perlman, Director, HCI Bibliography Project
mailto:director@hcibib.org  http://hcibib.org/

On Thu, 23 Dec 2010, Valentina Budici wrote:

> Hi!
>
> I've filled in the form.
> Please let me know what happens next.
>
> Thank you and have a merry christmas.
>
> On Thu, Dec 23, 2010 at 12:42 AM, Gary PERLMAN <perlman@turing.acm.org>wrote:
>
>> Please see: http://hcibib.org/faq.html#Data-5
>>
>> I suggest this form:
>> http://www.hcibib.org/suggest.cgi?category=intercultural:translation
>>
>> The language field should contain en, ru, ro, and de
>>
>> Here is an analysis of the accessibility of your page:
>>
>> http://hcibib.org/accessibility/chaccess.cgi?url=http%3A%2F%2Fwww.polilingua.com%2F&links=checked&warn=checked&labels=checked
>>
>> Gary Perlman, Director, HCI Bibliography Project
>> mailto:director@hcibib.org  http://hcibib.org/
>>
>>
>> On Wed, 22 Dec 2010, Valentina Budici wrote:
>>
>>  Hi!
>>>
>>> I am the editor at PoliLingua.com, I?ve found your site:
>>> http://www.hcibib.org/intercultural/
>>>
>>> I am interested in exchanging links with you. If interested too, please
>>> read
>>> on...
>>> I suppose you know that links pointing to your site help improve your
>>> position in search engines and could significantly increase the number of
>>> visitors to your website.  In order to benefit to the maximum I propose to
>>> use cross link exchange. We can offer you a link on any of the pages here:
>>> http://www.website-translate.com/resources
>>>
>>> This is the information about our website we would like to do link
>>> exchange:
>>> Url: http://www.polilingua.com
>>> Title: Translation services
>>> Description: PoliLingua delivers translation, localization and managed
>>> language solutions for clients large and small; in the corporate,
>>> government
>>> and personal sectors.
>>>
>>> Please let me know if you are interested.
>>> Thanks for your time!
>>> ---
>>> Best regards,
>>> Valentina Budici,
>>> www.PoliLingua.com
>>> Email : editor@polilingua.com
>>>
>>>
>
>
>

From perlman@turing.acm.org Thu Dec 30 21:37:27 2010 -0500
Status: 
X-Status: 
X-Keywords:
Date: Thu, 30 Dec 2010 21:37:26 -0500 (EST)
From: Gary PERLMAN <perlman@turing.acm.org>
To: Michael Casale <mbcasale@gmail.com>
Subject: Re: |STAT
In-Reply-To: <AANLkTin0Ws+gggTHg2SywKGeTTs3vqKKddOuOJ-dTqkY@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1012302137230.18169@turing.acm.org>
References: <AANLkTin0Ws+gggTHg2SywKGeTTs3vqKKddOuOJ-dTqkY@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

Thank you for your interest in |STAT data manipulation and analysis software.

UNIX |STAT for is now (only) available via Web browsers at a secret location.
 	http://www.hcibib.org/stat/xyzzy/

To obtain UNIX |STAT files, please follow the instructions at:
 	http://www.acm.org/perlman/stat/#access
There are installation notes (e.g., for Mac OS X and Linux) at:
 	http://www.acm.org/perlman/stat/installation.txt

DOS |STAT executables and documentation are available as a WinZip file:
 	http://www.acm.org/perlman/stat/DOS-STAT.ZIP

HTML documentation is available from the |STAT home page:
 	http://www.acm.org/perlman/stat/

On Mon, 27 Dec 2010, Michael Casale wrote:

> I AGREE TO ADHERE TO THE CONDITIONS OF USING |STAT.
> I AGREE NOT TO SHARE THE |STAT LOCATION WITH OTHERS.
>
> mike
>

