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

1.2 - terminology not clear

1.2 exceptions needed

1.2.1 not realistic

1.2.2 not realistic

1.4.3 - 5:1 too high

1.4.4 - 200% is too high

2.2.2 - how to handle advertisements

2.4.10 aa instead of aaa

2.4.8 AA instead of AAA

80 characters

80 characters?

[WCAG2 TECHS] i18n comment 1: H34 example source direction

\"Awkward wording

\"Item Number\': Abstract. clarify with commas

\"Webmasters\"

\"well formed\"

\"with disabilities\"

\"with disabilities\", take two

a small usability enhancement to the guidelines document

a voice easy to understand (G 1.1)

abbreviation refers to \"organization\"?

Accessibility supported (lists of Web technologies)

accessibility supported - users\' assistive technologies

activity where moving, blinking...

Add header to first page

add image map example

Add reference to 1.2.1

Add reference to 1.4.1

aligned on both left and right

Allow users to filter out HTML techniques

ambiguous if not clear from context already?

arbitrary values?

assistive technology - stray word

awkward phrasing

Awkward wording

blink vs flash

both cases - awkward

Can \"conforming alternate versions\" be objects on a page?

captions - awkward wording

Change \"accessibility supported\" to \"accessibility-supporting\"

changes of context definition

Clarification of advisory techniques

Clarification of note / awkward phrasing

clarification of the term \'perceivable\'

clarification of the term \'understandable\'

clarify keyboard shortcut

Clarify what \'which is optional\' applies to

Combine \"usable in general\" and \"older individuals\"

Comments from Eric Hansen on the 17 Dec 2007 draft of WCAG 2.0

Concerns about 80 characters width limit

Concerns about text resizing requirements

Conformance and use of accessibility-supported tehcnologies in a non-conforming way

Conformance level too low

conforming alternative version - awkward wording

Consider title change

Consistent Presentation (SC 3.2.3)

contrast algorithm for 1.4.3: Contrast (Minimum)

Contrast ratio (on text edges)

contrast ratio - generalised copy

Criteria to evaluate essential things

dependent on UA?

descriptive labels (SC 2.4.6)

descriptive titles (SC 2.4.2)

EOWG's replies to WCAG WG resolutions of EOWG comments on May 2007 Draft of WCAG 2.0

Example Doc is XHTML, not HTML

extended audio - clarification in note

Failure does not fail in Firefox

Failure F70 Does not Prohibit Duplicate Attributes

flash

flashing dependent on size, but not specified!

flashing dependent on size?

G 3.1 covers perceivability as well as understandability

G14: Does example 2 fail the success criterion?

general flash and red threshold - confusing jargon?

H36: Using alt attributes on images used as submit buttons

Hard to accomplish the examples in 3 seconds

headings and which SC?

How to create the documented lists

HTML Version of Understanding WCAG with semantic classes and IDs

I think I may have answered my own question...

Image map text alternative

immediately?

Introduction, first part, trim wording

Introduction, second part, trim wording

Is \"Prior warning\" really OK here?

It is unclear if this SC is testable.

Language Subtags (Techniques H57 and H58)

Level A for low or no-contrast content

line spacing

Link \'metadata\'

Links ot ARIA out of date

Links to How to Meet SC

List all contributors to WCAG 2.0

meaningful sequence (SC 1.3.2)

Metadata sentence right at the end

Missing full stop

Mouse hover and focus not equivalent

navigated sequentially

Need Bullets for Educational Testing Situations

non w3c techiques have to be named with clear examples

non-text content

Not testable

Optional components and the hint of metadata

programmatically determiend - typo

Programmatically determine the role not explained

programmatically determined / programmatically determinable

Progress Bar

purpose of each link (SC 2.4.4)

real-time event

Remove rationale from Guideine 1.1 text

role

SC 3.1.3: Glossary without Links Should Fail?

SC 3.3.1: Providing client-side validation and adding error text via the DOM (future technique )

section headings (SC 2.4.10)

Sections Headings conformance level

Sequential navigation and meaning

set of Web pages - clarify

set of Web pages - unnecessarily convoluted

Several Success Criteria include specific values

so headings are optional then at anything below AAA?

stray word in accessibility supported

Sufficient techniques seems to contradict other areas and principles.

Suggestions to clarify \"media alternatives to text\"

supplemental content

sweeping generalisation?

synchronised media - awkard

Technique also works in Firefox

Text of Image

Typos in Programmatically determiend

understand the speech (SC 1.4.7)

understand the speech output (SC 1.4.2)

Updated testing to allow Dojo

usable default presentation (G 1.4)

Use of roles with current technologies

User agents\' incorrect behaviour while navigating sequentially

user interface component - missing comma

Version numbers should be added for Firefox

viewport - awkard

Visually customizable text

WCAG 2.0 Comment Submission

WCAG 2.0 should advance to Candidate Recommendation

WCAG 2.0: Accessibility supported technologies

web page example 4

what if it\'s not the author\'s fault?

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