Ben Caldwell
Christophe Strobbe (on behalf of BenToWeb)
Hansen, Eric
Loretta Guarino Reid
Michael Stenitzer
Patrick H. Lauke
Patrick Lauke
Shadi Abou-Zahra
Wayne Dick
WCAG 2.0 Comment Form
- Need Bullets for Educational Testing Situations (Friday, 29 February)
- Progress Bar (Friday, 15 February)
- Is \"Prior warning\" really OK here? (Wednesday, 6 February)
- Programmatically determine the role not explained (Monday, 4 February)
- Failure does not fail in Firefox (Monday, 4 February)
- Technique also works in Firefox (Monday, 4 February)
- Version numbers should be added for Firefox (Monday, 4 February)
- Hard to accomplish the examples in 3 seconds (Monday, 4 February)
- Mouse hover and focus not equivalent (Monday, 4 February)
- Links ot ARIA out of date (Monday, 4 February)
- Example Doc is XHTML, not HTML (Monday, 4 February)
- Updated testing to allow Dojo (Monday, 4 February)
- Links to How to Meet SC (Monday, 4 February)
- Not testable (Monday, 4 February)
- Change \"accessibility supported\" to \"accessibility-supporting\" (Saturday, 2 February)
- Add header to first page (Saturday, 2 February)
- Add header to first page (Saturday, 2 February)
- \"Item Number\': Abstract. clarify with commas (Saturday, 2 February)
- Link \'metadata\' (Saturday, 2 February)
- Remove rationale from Guideine 1.1 text (Saturday, 2 February)
- Clarify what \'which is optional\' applies to (Saturday, 2 February)
- changes of context definition (Saturday, 2 February)
- Typos in Programmatically determiend (Saturday, 2 February)
- List all contributors to WCAG 2.0 (Saturday, 2 February)
- Consider title change (Saturday, 2 February)
- Allow users to filter out HTML techniques (Saturday, 2 February)
- Introduction, second part, trim wording (Saturday, 2 February)
- Introduction, first part, trim wording (Saturday, 2 February)
- web page example 4 (Saturday, 2 February)
- user interface component - missing comma (Saturday, 2 February)
- viewport - awkard (Saturday, 2 February)
- synchronised media - awkard (Saturday, 2 February)
- supplemental content (Saturday, 2 February)
- set of Web pages - unnecessarily convoluted (Saturday, 2 February)
- set of Web pages - clarify (Saturday, 2 February)
- role (Saturday, 2 February)
- real-time event (Saturday, 2 February)
- programmatically determiend - typo (Saturday, 2 February)
- programmatically determined / programmatically determinable (Saturday, 2 February)
- non-text content (Saturday, 2 February)
- non-text content (Saturday, 2 February)
- navigated sequentially (Saturday, 2 February)
- general flash and red threshold - confusing jargon? (Saturday, 2 February)
- flash (Saturday, 2 February)
- extended audio - clarification in note (Saturday, 2 February)
- contrast ratio - generalised copy (Saturday, 2 February)
- How to create the documented lists (Saturday, 2 February)
- 80 characters (Saturday, 2 February)
- Text of Image (Saturday, 2 February)
- Visually customizable text (Saturday, 2 February)
- WCAG 2.0 should advance to Candidate Recommendation (Saturday, 2 February)
- I think I may have answered my own question... (Friday, 1 February)
- Can \"conforming alternate versions\" be objects on a page? (Friday, 1 February)
- Suggestions to clarify \"media alternatives to text\" (Friday, 1 February)
- Consistent Presentation (SC 3.2.3) (Friday, 1 February)
- G 3.1 covers perceivability as well as understandability (Friday, 1 February)
- section headings (SC 2.4.10) (Friday, 1 February)
- descriptive labels (SC 2.4.6) (Friday, 1 February)
- purpose of each link (SC 2.4.4) (Friday, 1 February)
- descriptive titles (SC 2.4.2) (Friday, 1 February)
- understand the speech (SC 1.4.7) (Friday, 1 February)
- understand the speech output (SC 1.4.2) (Friday, 1 February)
- usable default presentation (G 1.4) (Friday, 1 February)
- meaningful sequence (SC 1.3.2) (Friday, 1 February)
- a voice easy to understand (G 1.1) (Friday, 1 February)
- clarification of the term \'understandable\' (Friday, 1 February)
- clarification of the term \'perceivable\' (Friday, 1 February)
- conforming alternative version - awkward wording (Friday, 1 February)
- captions - awkward wording (Friday, 1 February)
- blink vs flash (Friday, 1 February)
- assistive technology - stray word (Friday, 1 February)
- activity where moving, blinking... (Friday, 1 February)
- accessibility supported - users\' assistive technologies (Friday, 1 February)
- stray word in accessibility supported (Friday, 1 February)
- immediately? (Friday, 1 February)
- both cases - awkward (Friday, 1 February)
- abbreviation refers to \"organization\"? (Friday, 1 February)
- awkward phrasing (Friday, 1 February)
- Contrast ratio (on text edges) (Friday, 1 February)
- Accessibility supported (lists of Web technologies) (Friday, 1 February)
- WCAG 2.0 Comment Submission (Friday, 1 February)
- Conformance and use of accessibility-supported tehcnologies in a non-conforming way (Friday, 1 February)
- Use of roles with current technologies (Friday, 1 February)
- Sections Headings conformance level (Friday, 1 February)
- Sequential navigation and meaning (Friday, 1 February)
- User agents\' incorrect behaviour while navigating sequentially (Friday, 1 February)
- Criteria to evaluate essential things (Friday, 1 February)
- Concerns about text resizing requirements (Friday, 1 February)
- Conformance level too low (Friday, 1 February)
- Concerns about 80 characters width limit (Friday, 1 February)
- non w3c techiques have to be named with clear examples (Friday, 1 February)
- non w3c techiques have to be named with clear examples (Friday, 1 February)
- 2.4.10 aa instead of aaa (Friday, 1 February)
- 2.4.8 AA instead of AAA (Friday, 1 February)
- 2.2.2 - how to handle advertisements (Friday, 1 February)
- 1.4.4 - 200% is too high (Friday, 1 February)
- 1.4.3 - 5:1 too high (Friday, 1 February)
- 1.2 exceptions needed (Friday, 1 February)
- 1.2 - terminology not clear (Friday, 1 February)
- 1.2.2 not realistic (Friday, 1 February)
- 1.2.1 not realistic (Friday, 1 February)
- It is unclear if this SC is testable. (Friday, 1 February)
- Several Success Criteria include specific values (Friday, 1 February)
- clarify keyboard shortcut (Friday, 1 February)
- add image map example (Friday, 1 February)
- Add image map example (Friday, 1 February)
- Image map text alternative (Friday, 1 February)
- Add image map example (Friday, 1 February)
- Level A for low or no-contrast content (Friday, 1 February)
- Optional components and the hint of metadata (Friday, 1 February)
- \"Awkward wording (Friday, 1 February)
- Sufficient techniques seems to contradict other areas and principles. (Friday, 1 February)
- \"well formed\" (Friday, 1 February)
- ambiguous if not clear from context already? (Friday, 1 February)
- so headings are optional then at anything below AAA? (Friday, 1 February)
- dependent on UA? (Friday, 1 February)
- sweeping generalisation? (Friday, 1 February)
- flashing dependent on size? (Friday, 1 February)
- flashing dependent on size, but not specified! (Friday, 1 February)
- arbitrary values? (Friday, 1 February)
- \"with disabilities\", take two (Friday, 1 February)
- \"with disabilities\" (Friday, 1 February)
- what if it\'s not the author\'s fault? (Friday, 1 February)
- line spacing (Friday, 1 February)
- aligned on both left and right (Friday, 1 February)
- 80 characters? (Friday, 1 February)
- Clarification of advisory techniques (Friday, 1 February)
- Clarification of note / awkward phrasing (Friday, 1 February)
- Awkward wording (Friday, 1 February)
- Add reference to 1.4.1 (Friday, 1 February)
- Add reference to 1.2.1 (Friday, 1 February)
- Missing full stop (Friday, 1 February)
- Missing full stop (Friday, 1 February)
- Metadata sentence right at the end (Friday, 1 February)
- \"Webmasters\" (Friday, 1 February)
- Combine \"usable in general\" and \"older individuals\" (Friday, 1 February)
Last message date: Friday, 29 February 2008 22:22:59 UTC