w3c-wai-gl@w3.org from April to June 2005 by subject

"Accessibility features"

♦Re: Should validity be P1 or P2? (was RE: summary of resolutions from last 2 days)

(1.3) Validation and semantics recap

(very minor) addition to 25 May 2005 WCAG TTF minutes?

* Can we Start 1 hour early for Thursday call????

06/30 call

1.4 background sound

2 levels or 3

2.3 Guideline revisions proposal

3.1 comments

3.1 Issue summary

3.1 REQUIRING NON-TEXT ALTERNATES TO TEXT

3.1: Action item re foreign passages

3.1: Another update

3.1: Another update to the proposal

3.1: Proposal with links to Guide docs

3.1: Proposal with several updated SC

3.1: Proposal with updates from 26 May call

3.2 Proposal version 2

4.2 notes/proposals

9 June 2005 Agenda [=================================

[1.1] Proposal for new example

[1.3] Alternative proposal for guideline text

[2.1] Guideline summary and new proposal

[2.4] Issue summary

[2.4] New proposal for guideline 2.4

[2.4] Proposal for guideline 2.4

[2.4] Proposals for 2.4

[2.4] Summary of issues for guideline 2.4

[4.1] Article on when to create custom DTD's (and when not to)

[Fwd: Re: Possible Scripting Techniques to help with baseline evaluation]

[Fwd: RE: WARNING: Yet another virus sent by 'Wendy']

[minutes] 13 April 2005 TTF telecon

[minutes] 19 May 2005 WCAG WG telecon

[minutes] 2 June 2005 telecon

[minutes] 21 April 2005 telecon

[minutes] 23 june 2005 telecon

[minutes] 26 May 2005 telecon

[minutes] 27 April Techniques Task Force of the WCAG WG telecon

[minutes] 28 April 2005 WCAG WG telecon

[minutes] 31 March 2005 telecon

[script-techs] Possible Scripting Techniques to help with baseline evaluation

[tech] 4.2 Summary

[tech] re: regrets Wed (will have 4.2 by tommorrow)

[techlunch] JAWS 6.10 Free Update for 6.0 Users Released

[Techs-scripting]FW: setting focus on a form field using javascript

[techs] [Fwd: ACCESSKEY heats up]

[techs] Changes in requirements doc

[Techs] Definition of "Reliably human testable"

[Techs] Divide Techniques docs into chapters?

[TECHS] draft introduction to client side scripting techniques

[techs] examples for techniques requirements document

[Techs] JAWS info for matrix

[Techs] Kurzweil 3000 and WYNN zebra strips

[techs] Minutes for 01 June Techniques teleconference

[techs] minutes from April 20 telecon

[techs] Minutes of 11 May 2005 Techniques teleconference

[TECHS] Object tag test files.

[techs] Please review issue summaries

[TECHS] Possible Scripting Techniques with Guideline Mappings

[Techs] proposed definitions re: my May 11 WCAG TTF Action Item

[Techs] Regrets for Wednesday

[techs] regrets for Wednesday's WCAG TTF call

[techs] requirements updated

[TECHS] Review of SC with respect to Scripting and baseline issues.

[techs] Review of techniques issues for Guideline 2.4

[TECHS] Sample Scripting Techniques with baseline information

[techs] Techniques for Guideline 1.1

[techs] Techniques for Guideline 1.3

[techs] Techniques for Guideline 2.4

[techs] Techniques for Guideline 4.2

[TECHS] Techniques Issues for Guideline 1.3 - plain text version

[TECHS] Techniques issues summary for Guideline 2.5

[techs] Techniques Teleconference 01 June 2005

[techs] Techniques Teleconference 04 May 2005

[techs] Techniques Teleconference 06 April 2005

[techs] Techniques Teleconference 08 June 2005

[techs] Techniques Teleconference 11 May 2005

[techs] Techniques Teleconference 13 April 2005

[techs] Techniques Teleconference 18 May 2005

[techs] Techniques Teleconference 20 April 2005

[techs] Techniques Teleconference 22 June 2005

[techs] Techniques Teleconference 25 May 2005

[techs] Techniques Teleconference 27 April 2005

[techs] Updated requirements for techniques and checklists

[Techs]Kurzweil 3000 and WYNN zebra strips

[Techs]Window-Eyes info for matrix

[w3c-wai-gl] <none>

_Tech] Release date for Mac screen reader

a note on voluntary standards and policy related standards

about semantical use of markup

About test 13 (client side image-maps)

About tests 37-41 (headers)

Accessible quotation style in email (was Re: HTML messages)

Action item: Rewriting 1.3, "Ensure that information, functionality, and structure are separable from presentation"

addition proposal, GL 4.2

Agenda (updated) for Thursday 21 April

Agenda + [2.4] CORRECT version of 2.4 proposal

Agenda + Announcement: 19 May 2005

Agenda 6/30/05 - partial regrets

Agenda 6/30/05 =======================

Agenda addendum: link to proposed SC for GL 1.3

Agenda correction: Today's call starts same time as always

Agenda for Techniques portion of Face to Face, 15 - 16 June 2005

AGENDA for Thursday 7 April 2005

Agenda update: 12 May 2005

Agenda Update: 2 June 2005

Agenda with updated links: 5 May 2005

Agenda: 12 May 2005

Agenda: 13-16 June meeting in Brussels

Agenda: 2 June 2005

Agenda: 21 April 2005

Agenda: 23 June Telecon

Agenda: 23 June Telecon - partial regrets

Agenda: 26 May 2005 (with corrected guideline 2.2 survey link)

Agenda: 26 May 2005 =========================

Agenda: 28 April 2005

Agenda: 5 May 2005

Agenda: Thursday 14 April

Analysis, impact of externalized baseline decision on techniques

Another resource re: testability of WCAG2.0 guidelines and success criteria

Another update to the proposal

Background audio (was: Impact of not setting baseline and writing SC as functional outcomes)

Bare-bones proposal for 1.3, "Ensure that information,

Bare-bones proposal for 1.3, "Ensure that information, functionality, and structure are separable from presentation" (re-send)

Baseline definition

Bugzilla down?

Changes..

changing state and value programmatically

checklist prototype

CLOSED: Issue #1225

CLOSED: Issue #1259

CLOSED: Issue #1355

CLOSED: Issue #1422

CLOSED: Issue #1457

CLOSED: Issue #1500

CLOSED: Issue #1501

CLOSED: Issue #180

CLOSED: Issue #478

CLOSED: Issue #503

CLOSED: Issue #659

CLOSED: Issue #777

CLOSED: Issue #802

CLOSED: Issue #965

Conformance Claims - W3C Logo Use

Conformance claims, 4.2, and techniques

Conformance Issues

Conformance Requirements proposal

content arranged in a sequence that affects meaning

Correction (Re: Issues and proposals: conformance claims)

Declaring educational level

Definition of "baseline"

Definition of "semantics"

Definition of "testable" (was: Re: summary of resolutions from last 2 days)

Definition of information (was RE: non-text content)

Done - Revisited

double regrets

Draft Introduction to WCAG 2.0

Dublin Core Accessibility element

Early Regrets - April 28th

Example of baseline information included in HTML Technique 12.4

Example of Baseline information included in HTML Technique 5.11

F2F Proposed Resolutions Draft Updates

Freedom of speech (Was RE: Another update to the proposal)

Further articles documenting the sense of "semantics"

Fwd: [Proposed Recommendation] QA Specification Guidelines

Fwd: [PUBLICATION] QA Specification

Fwd: Re: [TECHS] Sample Scripting Techniques with baseline information (fwd)

Fwd: Re: Proposal for 4.2, Ensure that user interfaces are accessible

Fwd: Test Development FAQ released

GL 1.3 issue summary against June 30 draft

GL 2.2 issue summary (close/clarify/not addressed)

GL 2.2 proposals and issue summary

GL 2.2: new benefit (low computer literacy)

GL 2.2: updated proposals

GL 2.5 Issues Summary and Proposal

GL 2.5 Remaining 3 issues

GL 3.2 proposal and summary

GL 4.2 Issues Summary

GL 4.2: Revised modification to the conformance section

Graceful degradation (was: Re: Issues summary, GL 4.2)

Guide doc: Drafts to discuss on Thursday

Guide doc: resend of Wendy's HTML-Techs mockup

Guideline 1.3 and user interface changes

Guideline 1.3 SC

Guideline 4.1 (use-spec) Issue Summary

Guideline 4.2 Subgroup Report

Hello

HTML messages (was: Re: Please comment on issue summaries)

HTML Techniques16.1, 10.6 baseline Discussion

HTML/XHTML, mime-types, Strict & Transitional [was Re: Semantics]

Ill-defined terms in WCAG 2

Impact Analysis for Guideline 4.2

Impact of not setting baseline and writing SC as functional outcomes

Implications of proposed baseline definitions

imporved accessibility metadata paper

Input for F2F on Guide and general techniques

Introduction: Updated version

IRC log isn't what we're talking about

issue 1214. 2.4: 1194.22-like SC should be level 1 [21]

Issue Summary 1.4

Issue summary for 1.3: "Ensure that information, functionality, and structure are separable from presentation"

ISSUE SuMMARY for 2.3 Avoiding Content that provokes siezures

Issue summary for the guidelines document in general

Issues and proposals: conformance claims

Issues summary, GL 4.2

Items to keep in mind for Principle 3: "Content and controls must be understandable"

JavaScript action example

June 1 Draft

Late regrets for 28 April 2005 call

late regrets:

Late Regrets: 9 June 2005 Agenda [=================================

Late regrets: Agenda for Thursday 21 April

late Regrets: Agenda update: 12 May 2005

Late regrets: Agenda: 12 May 2005

Level 3

List of HTML Techniques not affected by baseline and list of affected

Loretta's analysis of UAAG Guideline 9

More info about new JAWS 6.10 features

move proposed SC to GL 1.3?

Multiple definitions for "baseline"

Need 1.1 L1 SC basic requirement to provide text alternative

Need for exemptions for teaching materials, samples, multilingual documents

NEW: Issue #1486

NEW: Issue #1487

NEW: Issue #1488

NEW: Issue #1489

NEW: Issue #1490

NEW: Issue #1491

NEW: Issue #1492

NEW: Issue #1493

NEW: Issue #1494

NEW: Issue #1495

NEW: Issue #1496

NEW: Issue #1497

NEW: Issue #1498

NEW: Issue #1499

NEW: Issue #1500

NEW: Issue #1501

NEW: Issue #1502

NEW: Issue #1503

NEW: Issue #1504

NEW: Issue #1505

NEW: Issue #1506

NEW: Issue #1507

NEW: Issue #1508

NEW: Issue #1509

NEW: Issue #1510

NEW: Issue #1511

NEW: Issue #1512

NEW: Issue #1513

NEW: Issue #1514

NEW: Issue #1515

NEW: Issue #1516

NEW: Issue #1517

NEW: Issue #1518

NEW: Issue #1519

NEW: Issue #1520

NEW: Issue #1521

NEW: Issue #1522

NEW: Issue #1523

NEW: Issue #1524

NEW: Issue #1525

NEW: Issue #1526

NEW: Issue #1528

NEW: Issue #1529

NEW: Issue #1530

NEW: Issue #1531

NEW: Issue #1533

NEW: Issue #1534

non-text content

Not over til its over - hang in there whatever your view(s).

One model for validation of JavaScript (vaguely related to 1.3, "Ensure that information, functionality, and structure are separable from presentation")

Outside expert opinion on Web standards and WCAG (especially GL 1.3)

Over

Overview of "baseline" (was re: Definition of baseline)def of baseline

overview of 3.1: Proposal with links to Guide docs

Parsing and extracting information (valid or not)

perhaps remove the requirement for validity completely!

Please comment on issue summaries

points to Ponder

possible regrets for Thursday plus suggestion?

Possible Scripting Techniques to help with baseline evaluation

Probable regrets (RE: Agenda 6/30/05 =======================)

programmatically determined

Proposal for 1.3, "Ensure that information, functionality, and structure are separable from presentation"

Proposal for 4.2, Ensure that user interfaces are accessible

Proposal for Guideline 1.1

Proposal for Guideline 1.1 (ASCII art)

Proposal for Guideline 1.1 (Definition of content)

Proposal for Guideline 1.1 (Definition of functionality)

Proposal for Guideline 1.1 (Example 7)

Proposal for Guideline 1.1 (Example 8)

Proposal for Guideline 1.1 (Functional text content)

Proposal for Guideline 1.1 (specifcally about L1 SC4)

Proposal for Guideline 1.1 [definition of text]

Proposal with updates from 26 May call

Proposals from June 13 Face to Face

Proposed ednote to clarify captions and transcript

Proposed planning framework

Protected message

Provide Feedback on Straw poll forms

R: R: R: Re : Influence of valid code on screen readers

R: R: Re : Influence of valid code on screen readers

R: Re : Influence of valid code on screen readers

R: Re-post: Influence of valid code on screen readers

R: Should validity be P1 or P2? (was RE: summary of resolutions from last 2 days)

RE 3.1 proposal - first half

RE 3.1 proposal - first half 2

Re : Influence of valid code (generically)

Re : Influence of valid code on screen readers

Re-post: Influence of valid code on screen readers

Reasons to move validity back to P1

regrets

Regrets (RE: Agenda update: 12 May 2005)

Regrets (RE: Agenda: 23 June Telecon)

Regrets for 12 May 2005 call

Regrets for 27 & 28 April telecons

regrets for 4/20 call

regrets for 5 May telecon

Regrets for next week

Regrets for next week for me also

Regrets for Techniques Teleconference 20 April 2005

Regrets for this evening

Regrets for this evening (R. Scano and L. Mascaro)

Regrets for this week

Regrets for Thursday 7 April 2005 conference

regrets for today's call

Regrets for today's call (05/19)

regrets for today's call (06/23)

regrets, Agenda 6/30/05

regrets, June 2

Regrets: 9 June 2005 Agenda (for Luca Mascaro)

Regrets: 9 June 2005 Agenda [=================================

Regrets: Agenda (updated) for Thursday 21 April

Regrets: Agenda 19 May 2005

Regrets: Agenda 6/30/05

Regrets: Agenda 6/30/05 =======================

Regrets: AGENDA for Thursday 7 April 2005

regrets: Agenda Thursday 14 April

regrets: Agenda with updated links: 5 May 2005

Regrets: Agenda: 12 May 2005

Regrets: Agenda: 2 June 2005

Regrets: Agenda: 23 June Telecon

Regrets: Agenda: 26 May 2005

Regrets: Agenda: 26 May 2005 =========================

regrets: Agenda: 28 April 2005

Regrets: Agenda: Thursday 14 April

Reminder: Call starts early today

Reminder: straw poll for 2.4

remove validity completely?

Requiring ATAG conformance

Resend of planning example

Responses to comments on GL 3.1 proposal

Revised Proposal, GL 4.2

Screen Reader Supported Languages

Semantics [was: Re: Well-formed (was: Re: F2F Proposed Resolutions Draft Updates)]

Should validity be P1 or P2?

Should validity be P1 or P2? (was Re : Influence of valid code on screen readers)

Should validity be P1 or P2? (was RE: summary of resolutions from last 2 days)

Sign language video

Sorry about double posting

Start time of WCAG telecon (was:Re: Agenda 6/30/05)

Stevie Wonder does music video with audio description

Strange behavior of mail archive?

summary of resolutions from last 2 days

Summing up the debate about validity at Priority 1 or 2

test

Test files review, #75, 76, 77, 78¸ 79, 27, 128, 129, 183

testing (no need to respond, still testing archives)

testing (no need to respond, testing archives)

Text being imperceptible (allegedly)

The next WCAG WG face-to-face will be in Brussels 13-16 June

Thinking aloud...Definitions (pre-Guideline 1.1 summary)

Triple Regrets: Agenda (updated) for Thursday 21 April

UAAG Priority 1 checkpoint analysis summary

Unicode encodings

Unifying ATAG and UAAG in 4.2 (or surrogate)

Updated mapping of WCAG 1.0 checkpoints to WCAG 2.0 success criteria

Updated proposal for GL 1.3 L1 SC2

Updated proposal for Guideline 1.1

Updated Survey for 4.1

Updated survey for Guideline 2.5

Updated survey for guideline 3.1

Updated: 9 June 2005 Agenda

Usability issues in Ajax/Web applications (with implications for accessibility)

User agent assumptions - vs - baseline

Validation as test for basic accessibility

Validation: what criteria in L1, L2 or L3?...

Validity and Well-formedness

WAI CSS and WCAG conformance pages (was: W3C style sheet fix (needed for WCAG conformance pages))

WARNING: Yet another virus sent by 'Wendy'

WCAG formalization (rewriting WCAG HTML techniques as automatable rules)

Web Standards Project Accessibility Task Force

Well-formed (was: Re: F2F Proposed Resolutions Draft Updates)

Wendy's analysis of UAAG Guideline 6

Wendy's analysis of web applications vs user agents

Why 2GL .4 isn't on the agenda this week

Why is important require well-formed, validity and richness in XHTML by examples

working definition of baseline

XHTML 1.1 as text/html (was Re: Should validity be P1 or P2?)

YOUR PASSWORD HAS BEEN SUCCESSFULLY UPDATED

{TECHS] Techniques Issues for Guideline 1.3

《EC商务周刊-资讯版》(2005年第22期 总第54期)

Last message date: Thursday, 30 June 2005 20:45:43 UTC