Discussion: do not set font size!!

<scribe> ACTION: Wayne - create a project page (eg http://www.w3.org/WAI/EO/changelogs/cl-eval-ut) and come back with an interpretation of our requirements (eg a functional &/or technical spec) for review. Then draft the two CSS files. [recorded in http://www.w3.org/2005/12/13-eo-minutes.html#action01]

Note: thanks to Wayne's CECS406 class for print style sheet samples

Wrapper for pages not in nav

EG: http://www.w3.org/WAI/EO/2005/12/f2f-agenda
... http://www.w3.org/WAI/eval/ack#users
... http://www.w3.org/WAI/EO/changelogs/cl-eval-ut

Discussion: Decided that working document pages have minimal LHS navigation - eg W3C/WAI/parent-page(s)

Shawn: for example: http://www.w3.org/WAI/EO/2005/12/f2f-agenda

<scribe> ACTION: Shawn - document the decision, provide for EO email review, implement on appropriate pages [recorded in http://www.w3.org/2005/12/13-eo-minutes.html#action02]

Translations

Shawn: Template (wrapper) for translated pages - e.g. ...

<shawn-MEL> e.g., translation of components: http://www.w3c.es/Traducciones/es/WAI/intro/components

<scribe> ACTION: shawn - check with Ivan & Richard about disclaimer regarding the English version being the 'normative' version and linking to it [recorded in http://www.w3.org/2005/12/13-eo-minutes.html#action03]

Discussion: suggesting using a minimal wrapper (LHS nav) - "W3C Home - WAI Home - English parent page"
... disclaimer - have it styled (e.g. status style) and placed immediately below the document title

<hbj> ACTION: Helle wording on disclaimer for translations (non-normative documents) and pointer to WAI translation page [recorded in http://www.w3.org/2005/12/13-eo-minutes.html#action04]

Helle: need to link to all the XX language translations

Discussion: ideal - link to a page of WAI translations in XX language from each WAI page in that languauge (can be generated from a W3C database)
... also, a list in WAI design of each WAI doc with a subliost of the translations available
... add a LHS link "Other WAI documents in XX language" in XX language
... in LHS the nav links are in English (except "home"); links in the document text should be in the translated language first and linked if available, followed by the English text in square brackets and always linked
... translate the control bar & tag line

<shawn-MEL> e.g.: Componentes esenciales de Accesibilidad Web [Essential Components of Web Accessibility]

Discussion: should encourage translations of the "WAI Resources" page and other intro pages

<scribe> ACTION: Shawn - add "WAI Resources" page to the translation priorities list as a Top Priority [recorded in http://www.w3.org/2005/12/13-eo-minutes.html#action05]

Discussion: for later discuission, translation of the home page (or Highlights Archive)

<shawn-MEL> lunch (finally!)

test

<shawn-MEL> back for a bit

Discussion: options - a) "translations of this page" at the top that links to the anchor on the translations page; b) have a "translations" link in the Page Contents area that links to a list at the bottom of the page
... options c) drop down at the top
... pros - b: printed with the doc; cons - not printed for a & c
... important to have it up nthe top and visible - c does this
... challenge with 'c' is the label. Also, do we have them on the translated page? NO

<scribe> ACTION: CHANGELOG draft a drop-down for available translations and seek feedback and discussion [recorded in http://www.w3.org/2005/12/13-eo-minutes.html#action06]

Discussion: suggested position for drop down is below page title, immediately above (outside) "page contents" DIV

Break: tour of vision australia

Retrofitting document

Discussion: brainstorm - list of accessibility issues

<shawn-MEL> skip links

<shawn-MEL> labels on forms

<shawn-MEL> text in images without alternatives

<shawn-MEL> alt text for important images

<shawn-MEL> tables linearize properly

<shawn-MEL> [easy] div linearization

<shawn-MEL> links to nonHTML files are clearly labeled

<shawn-MEL> [hard] accessible alternatives to non-accessible content (e.g., old

<shawn-MEL> PDF)

<shawn-MEL> basic keyboard access (e.g., not get stopped in Flash, scripted

<shawn-MEL> links & drop-downs (w/o Go button), @@)

<shawn-MEL> device-independence (e.g., hover & focus)

<shawn-MEL> [easy] fix link text

<shawn-MEL> colour contrast

<shawn-MEL> [infrequent] frame names & titles

<shawn-MEL> [infrequent] redundant colour

Discusison: linking to WCAG 1.0 techniques is not a solution as they are often no longer best practice

a/Discusison/Discussion

Discussion: not viable (too problematic) to link to external resources
... may be able to link to WCAG 2.0 techniques down the track
... Q? is it useful to provide a brief description of these common issues without providing techniques?

?

Discussion: YES - far from perfect, but an improvement on the current situation

<scribe> ACTION: CHANGELOG it is effective to publish the general guidance without the list of issues (or techniques) [recorded in http://www.w3.org/2005/12/13-eo-minutes.html#action07]

Glossary

See: http://www.w3.org/WAI/EO/Drafts/glossary/glossary-2005-12-12 & http://www.w3.org/WAI/EO/Drafts/glossary/2005-12-13

Discussion: parameters we used are "clarity" & "simplicity" rather than technical acurate and complete

Activity: addressed 12 definitions with issues

Result: made changes to suggested definition; added notes (if required) about changes; for many, the status is "ready for review"

See: http://www.w3.org/WAI/EO/Drafts/glossary/2005-12-13

<scribe> ACTION: CHANGELOG - consider "web content" for second release [recorded in http://www.w3.org/2005/12/13-eo-minutes.html#action08]

<shawn-MEL> close: "no worries"

This is scribe.perl Revision: 1.127  of Date: 2005/08/16 15:12:03  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/English paraent page(s)/English parent page/
Succeeded: s/Discussion: better to link to a WAI anchor//
Succeeded: s/Discussion: better to link to a WAI anchor//
Succeeded: s/Discussion: in LHS the nav links are in English;/Discussion: in LHS the nav links are in English (except "home");/
Succeeded: s/links in the document text should be translated with a language indicator/links in the document text should be in the translated language first and linked if available, followed by the English text in square brackets and always linked/
Succeeded: s/Also, do we have them on the translated page?/Also, do we have them on the translated page? NO/
Succeeded: s/suggedted/suggested/
Succeeded: s/Discussion: Q? is it useful to provide a brief description of these common issues /Discussion: Q? is it useful to provide a brief description of these common issues without providing techniques?/
No ScribeNick specified.  Guessing ScribeNick: Andrew
Inferring Scribes: Andrew

WARNING: No "Present: ... " found!
Possibly Present: Activity Break Discusison Discussion EG Helle Note Result See Shawn close hbj shawn-MEL
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

Guessing minutes URL: http://www.w3.org/2005/12/13-eo-minutes.html
People with action items: - add changelog helle page resources shawn wai wayne

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)