public-comments-wcag20@w3.org from February 2008 by thread

Need Bullets for Educational Testing Situations WCAG 2.0 Comment Form (Friday, 29 February)

a small usability enhancement to the guidelines document Patrick H. Lauke (Tuesday, 19 February)

Progress Bar WCAG 2.0 Comment Form (Friday, 15 February)

Re: EOWG's replies to WCAG WG resolutions of EOWG comments on May 2007 Draft of WCAG 2.0 Loretta Guarino Reid (Thursday, 7 February)

Re: [WCAG2 TECHS] i18n comment 1: H34 example source direction Loretta Guarino Reid (Thursday, 7 February)

Is \"Prior warning\" really OK here? WCAG 2.0 Comment Form (Wednesday, 6 February)

Re: HTML Version of Understanding WCAG with semantic classes and IDs Ben Caldwell (Tuesday, 5 February)

Programmatically determine the role not explained WCAG 2.0 Comment Form (Monday, 4 February)

Failure does not fail in Firefox WCAG 2.0 Comment Form (Monday, 4 February)

Technique also works in Firefox WCAG 2.0 Comment Form (Monday, 4 February)

Version numbers should be added for Firefox WCAG 2.0 Comment Form (Monday, 4 February)

Hard to accomplish the examples in 3 seconds WCAG 2.0 Comment Form (Monday, 4 February)

Mouse hover and focus not equivalent WCAG 2.0 Comment Form (Monday, 4 February)

Links ot ARIA out of date WCAG 2.0 Comment Form (Monday, 4 February)

Example Doc is XHTML, not HTML WCAG 2.0 Comment Form (Monday, 4 February)

Updated testing to allow Dojo WCAG 2.0 Comment Form (Monday, 4 February)

Links to How to Meet SC WCAG 2.0 Comment Form (Monday, 4 February)

Re: WCAG 2.0: Accessibility supported technologies Shadi Abou-Zahra (Monday, 4 February)

Not testable WCAG 2.0 Comment Form (Monday, 4 February)

RE: headings and which SC? Patrick Lauke (Monday, 4 February)

Change \"accessibility supported\" to \"accessibility-supporting\" WCAG 2.0 Comment Form (Saturday, 2 February)

Add header to first page WCAG 2.0 Comment Form (Saturday, 2 February)

Add header to first page WCAG 2.0 Comment Form (Saturday, 2 February)

\"Item Number\': Abstract. clarify with commas WCAG 2.0 Comment Form (Saturday, 2 February)

Link \'metadata\' WCAG 2.0 Comment Form (Saturday, 2 February)

Remove rationale from Guideine 1.1 text WCAG 2.0 Comment Form (Saturday, 2 February)

Clarify what \'which is optional\' applies to WCAG 2.0 Comment Form (Saturday, 2 February)

changes of context definition WCAG 2.0 Comment Form (Saturday, 2 February)

Typos in Programmatically determiend WCAG 2.0 Comment Form (Saturday, 2 February)

List all contributors to WCAG 2.0 WCAG 2.0 Comment Form (Saturday, 2 February)

Consider title change WCAG 2.0 Comment Form (Saturday, 2 February)

Allow users to filter out HTML techniques WCAG 2.0 Comment Form (Saturday, 2 February)

Introduction, second part, trim wording WCAG 2.0 Comment Form (Saturday, 2 February)

Introduction, first part, trim wording WCAG 2.0 Comment Form (Saturday, 2 February)

web page example 4 WCAG 2.0 Comment Form (Saturday, 2 February)

user interface component - missing comma WCAG 2.0 Comment Form (Saturday, 2 February)

viewport - awkard WCAG 2.0 Comment Form (Saturday, 2 February)

synchronised media - awkard WCAG 2.0 Comment Form (Saturday, 2 February)

supplemental content WCAG 2.0 Comment Form (Saturday, 2 February)

set of Web pages - unnecessarily convoluted WCAG 2.0 Comment Form (Saturday, 2 February)

set of Web pages - clarify WCAG 2.0 Comment Form (Saturday, 2 February)

role WCAG 2.0 Comment Form (Saturday, 2 February)

real-time event WCAG 2.0 Comment Form (Saturday, 2 February)

programmatically determiend - typo WCAG 2.0 Comment Form (Saturday, 2 February)

programmatically determined / programmatically determinable WCAG 2.0 Comment Form (Saturday, 2 February)

non-text content WCAG 2.0 Comment Form (Saturday, 2 February)

non-text content WCAG 2.0 Comment Form (Saturday, 2 February)

navigated sequentially WCAG 2.0 Comment Form (Saturday, 2 February)

general flash and red threshold - confusing jargon? WCAG 2.0 Comment Form (Saturday, 2 February)

flash WCAG 2.0 Comment Form (Saturday, 2 February)

extended audio - clarification in note WCAG 2.0 Comment Form (Saturday, 2 February)

contrast ratio - generalised copy WCAG 2.0 Comment Form (Saturday, 2 February)

How to create the documented lists WCAG 2.0 Comment Form (Saturday, 2 February)

80 characters WCAG 2.0 Comment Form (Saturday, 2 February)

Text of Image WCAG 2.0 Comment Form (Saturday, 2 February)

Visually customizable text WCAG 2.0 Comment Form (Saturday, 2 February)

WCAG 2.0 should advance to Candidate Recommendation WCAG 2.0 Comment Form (Saturday, 2 February)

I think I may have answered my own question... WCAG 2.0 Comment Form (Friday, 1 February)

Can \"conforming alternate versions\" be objects on a page? WCAG 2.0 Comment Form (Friday, 1 February)

Suggestions to clarify \"media alternatives to text\" WCAG 2.0 Comment Form (Friday, 1 February)

Comments from Eric Hansen on the 17 Dec 2007 draft of WCAG 2.0 Hansen, Eric (Friday, 1 February)

Failure F70 Does not Prohibit Duplicate Attributes Christophe Strobbe (on behalf of BenToWeb) (Friday, 1 February)

SC 3.3.1: Providing client-side validation and adding error text via the DOM (future technique ) Christophe Strobbe (on behalf of BenToWeb) (Friday, 1 February)

SC 3.1.3: Glossary without Links Should Fail? Christophe Strobbe (on behalf of BenToWeb) (Friday, 1 February)

Language Subtags (Techniques H57 and H58) Christophe Strobbe (on behalf of BenToWeb) (Friday, 1 February)

contrast algorithm for 1.4.3: Contrast (Minimum) Christophe Strobbe (on behalf of BenToWeb) (Friday, 1 February)

G14: Does example 2 fail the success criterion? Christophe Strobbe (on behalf of BenToWeb) (Friday, 1 February)

H36: Using alt attributes on images used as submit buttons Christophe Strobbe (on behalf of BenToWeb) (Friday, 1 February)

Consistent Presentation (SC 3.2.3) WCAG 2.0 Comment Form (Friday, 1 February)

G 3.1 covers perceivability as well as understandability WCAG 2.0 Comment Form (Friday, 1 February)

section headings (SC 2.4.10) WCAG 2.0 Comment Form (Friday, 1 February)

descriptive labels (SC 2.4.6) WCAG 2.0 Comment Form (Friday, 1 February)

purpose of each link (SC 2.4.4) WCAG 2.0 Comment Form (Friday, 1 February)

descriptive titles (SC 2.4.2) WCAG 2.0 Comment Form (Friday, 1 February)

understand the speech (SC 1.4.7) WCAG 2.0 Comment Form (Friday, 1 February)

understand the speech output (SC 1.4.2) WCAG 2.0 Comment Form (Friday, 1 February)

usable default presentation (G 1.4) WCAG 2.0 Comment Form (Friday, 1 February)

meaningful sequence (SC 1.3.2) WCAG 2.0 Comment Form (Friday, 1 February)

a voice easy to understand (G 1.1) WCAG 2.0 Comment Form (Friday, 1 February)

clarification of the term \'understandable\' WCAG 2.0 Comment Form (Friday, 1 February)

clarification of the term \'perceivable\' WCAG 2.0 Comment Form (Friday, 1 February)

conforming alternative version - awkward wording WCAG 2.0 Comment Form (Friday, 1 February)

captions - awkward wording WCAG 2.0 Comment Form (Friday, 1 February)

blink vs flash WCAG 2.0 Comment Form (Friday, 1 February)

assistive technology - stray word WCAG 2.0 Comment Form (Friday, 1 February)

activity where moving, blinking... WCAG 2.0 Comment Form (Friday, 1 February)

accessibility supported - users\' assistive technologies WCAG 2.0 Comment Form (Friday, 1 February)

stray word in accessibility supported WCAG 2.0 Comment Form (Friday, 1 February)

immediately? WCAG 2.0 Comment Form (Friday, 1 February)

both cases - awkward WCAG 2.0 Comment Form (Friday, 1 February)

abbreviation refers to \"organization\"? WCAG 2.0 Comment Form (Friday, 1 February)

awkward phrasing WCAG 2.0 Comment Form (Friday, 1 February)

Contrast ratio (on text edges) WCAG 2.0 Comment Form (Friday, 1 February)

Accessibility supported (lists of Web technologies) WCAG 2.0 Comment Form (Friday, 1 February)

WCAG 2.0 Comment Submission WCAG 2.0 Comment Form (Friday, 1 February)

Conformance and use of accessibility-supported tehcnologies in a non-conforming way WCAG 2.0 Comment Form (Friday, 1 February)

Use of roles with current technologies WCAG 2.0 Comment Form (Friday, 1 February)

Sections Headings conformance level WCAG 2.0 Comment Form (Friday, 1 February)

Sequential navigation and meaning WCAG 2.0 Comment Form (Friday, 1 February)

User agents\' incorrect behaviour while navigating sequentially WCAG 2.0 Comment Form (Friday, 1 February)

Criteria to evaluate essential things WCAG 2.0 Comment Form (Friday, 1 February)

Concerns about text resizing requirements WCAG 2.0 Comment Form (Friday, 1 February)

Conformance level too low WCAG 2.0 Comment Form (Friday, 1 February)

Concerns about 80 characters width limit WCAG 2.0 Comment Form (Friday, 1 February)

non w3c techiques have to be named with clear examples WCAG 2.0 Comment Form (Friday, 1 February)

non w3c techiques have to be named with clear examples WCAG 2.0 Comment Form (Friday, 1 February)

2.4.10 aa instead of aaa WCAG 2.0 Comment Form (Friday, 1 February)

2.4.8 AA instead of AAA WCAG 2.0 Comment Form (Friday, 1 February)

2.2.2 - how to handle advertisements WCAG 2.0 Comment Form (Friday, 1 February)

1.4.4 - 200% is too high WCAG 2.0 Comment Form (Friday, 1 February)

1.4.3 - 5:1 too high WCAG 2.0 Comment Form (Friday, 1 February)

1.2 exceptions needed WCAG 2.0 Comment Form (Friday, 1 February)

1.2 - terminology not clear WCAG 2.0 Comment Form (Friday, 1 February)

1.2.2 not realistic WCAG 2.0 Comment Form (Friday, 1 February)

1.2.1 not realistic WCAG 2.0 Comment Form (Friday, 1 February)

It is unclear if this SC is testable. WCAG 2.0 Comment Form (Friday, 1 February)

Several Success Criteria include specific values WCAG 2.0 Comment Form (Friday, 1 February)

clarify keyboard shortcut WCAG 2.0 Comment Form (Friday, 1 February)

add image map example WCAG 2.0 Comment Form (Friday, 1 February)

Add image map example WCAG 2.0 Comment Form (Friday, 1 February)

Image map text alternative WCAG 2.0 Comment Form (Friday, 1 February)

Add image map example WCAG 2.0 Comment Form (Friday, 1 February)

Level A for low or no-contrast content WCAG 2.0 Comment Form (Friday, 1 February)

Optional components and the hint of metadata WCAG 2.0 Comment Form (Friday, 1 February)

\"Awkward wording WCAG 2.0 Comment Form (Friday, 1 February)

Sufficient techniques seems to contradict other areas and principles. WCAG 2.0 Comment Form (Friday, 1 February)

\"well formed\" WCAG 2.0 Comment Form (Friday, 1 February)

ambiguous if not clear from context already? WCAG 2.0 Comment Form (Friday, 1 February)

so headings are optional then at anything below AAA? WCAG 2.0 Comment Form (Friday, 1 February)

dependent on UA? WCAG 2.0 Comment Form (Friday, 1 February)

sweeping generalisation? WCAG 2.0 Comment Form (Friday, 1 February)

flashing dependent on size? WCAG 2.0 Comment Form (Friday, 1 February)

flashing dependent on size, but not specified! WCAG 2.0 Comment Form (Friday, 1 February)

arbitrary values? WCAG 2.0 Comment Form (Friday, 1 February)

\"with disabilities\", take two WCAG 2.0 Comment Form (Friday, 1 February)

\"with disabilities\" WCAG 2.0 Comment Form (Friday, 1 February)

what if it\'s not the author\'s fault? WCAG 2.0 Comment Form (Friday, 1 February)

line spacing WCAG 2.0 Comment Form (Friday, 1 February)

aligned on both left and right WCAG 2.0 Comment Form (Friday, 1 February)

80 characters? WCAG 2.0 Comment Form (Friday, 1 February)

Clarification of advisory techniques WCAG 2.0 Comment Form (Friday, 1 February)

Clarification of note / awkward phrasing WCAG 2.0 Comment Form (Friday, 1 February)

Awkward wording WCAG 2.0 Comment Form (Friday, 1 February)

Add reference to 1.4.1 WCAG 2.0 Comment Form (Friday, 1 February)

Add reference to 1.2.1 WCAG 2.0 Comment Form (Friday, 1 February)

Missing full stop WCAG 2.0 Comment Form (Friday, 1 February)

Missing full stop WCAG 2.0 Comment Form (Friday, 1 February)

Metadata sentence right at the end WCAG 2.0 Comment Form (Friday, 1 February)

\"Webmasters\" WCAG 2.0 Comment Form (Friday, 1 February)

Combine \"usable in general\" and \"older individuals\" WCAG 2.0 Comment Form (Friday, 1 February)

Last message date: Friday, 29 February 2008 22:22:59 UTC