1.4.5 wording can use some improvement
- WCAG 2.0 Comment Form (Thursday, 31 January)
20 hour exception is too long for secure sessions dealing with identification and financial information and services
- WCAG 2.0 Comment Form (Thursday, 31 January)
200% seems too ambitious
- WCAG 2.0 Comment Form (Thursday, 31 January)
5 is too much and miss of exceptions
- WCAG 2.0 Comment Form (Saturday, 5 January)
About unique link names
- Sailesh Panchang (Monday, 28 January)
Absence of a success criterion that covers the absence of support for scripting or programmatic objects
- WCAG 2.0 Comment Form (Monday, 28 January)
Absence of mention of XHTML whenever HTML is used for referring to Web page markup
- WCAG 2.0 Comment Form (Monday, 28 January)
Absence of success criterion for deprecated and obsolete features
- WCAG 2.0 Comment Form (Monday, 28 January)
Absence of success criterion for markup/properties that prevent configuring pages/interfaces to meet accessibility needs
- WCAG 2.0 Comment Form (Monday, 28 January)
accessibility of social networking site content
- WCAG 2.0 Comment Form (Monday, 21 January)
accessibility supported definition and concept is confusing
- WCAG 2.0 Comment Form (Wednesday, 30 January)
achieving all or one ?
- WCAG 2.0 Comment Form (Saturday, 12 January)
Additional failure technique needed
- WCAG 2.0 Comment Form (Wednesday, 30 January)
- WCAG 2.0 Comment Form (Wednesday, 30 January)
Additional requirement for contrast controls
- WCAG 2.0 Comment Form (Wednesday, 30 January)
alternative to text with external text ?
- WCAG 2.0 Comment Form (Saturday, 12 January)
block sizing with absolute unit and text sizing with relative unit
- WCAG 2.0 Comment Form (Saturday, 5 January)
Bypass Blocks confusing
- WCAG 2.0 Comment Form (Wednesday, 30 January)
Change SC level for flashing content
- WCAG 2.0 Comment Form (Tuesday, 22 January)
Changing SC for re-authentication after time limit expiration
- WCAG 2.0 Comment Form (Tuesday, 22 January)
color and pattern for background-image too ?
- WCAG 2.0 Comment Form (Saturday, 5 January)
Components do not have \"sensory\" characteristics but just attributes or characteristics.
- WCAG 2.0 Comment Form (Wednesday, 30 January)
Concern about providing an alt version of readable content
- WCAG 2.0 Comment Form (Wednesday, 30 January)
Conformance Level wrong
- WCAG 2.0 Comment Form (Wednesday, 30 January)
- WCAG 2.0 Comment Form (Wednesday, 30 January)
contrast control available on or from the page
- WCAG 2.0 Comment Form (Saturday, 5 January)
Cross reference for SC of different conformance level
- WCAG 2.0 Comment Form (Thursday, 31 January)
Currently not addressed: Background images disappear with user-specific colors
- WCAG 2.0 Comment Form (Thursday, 31 January)
double negative in the essential exception
- WCAG 2.0 Comment Form (Saturday, 26 January)
Drafting of SC does not convey intent. Not clear.
- WCAG 2.0 Comment Form (Wednesday, 30 January)
EOWG's replies to WCAG WG resolutions of EOWG comments on May 2007 Draft of WCAG 2.0
- Shawn Henry (Friday, 11 January)
Essential Exception
- WCAG 2.0 Comment Form (Tuesday, 22 January)
Example \"A help dialog ...\"
- WCAG 2.0 Comment Form (Thursday, 31 January)
Geberal Advice is listed as a failure
- WCAG 2.0 Comment Form (Wednesday, 30 January)
How to decide wether it is \"large scale text\" or not
- WCAG 2.0 Comment Form (Thursday, 31 January)
HTML Version of Understanding WCAG with semantic classes and IDs
- WCAG 2.0 Comment Form (Thursday, 31 January)
Information on current location conformance level change
- WCAG 2.0 Comment Form (Thursday, 31 January)
Is it proven that the new algorithm for calculating brightness is superior to the old one?
- WCAG 2.0 Comment Form (Thursday, 31 January)
labels and headings definition not sufficient
- WCAG 2.0 Comment Form (Tuesday, 22 January)
lists for accessibility supported technologies
- WCAG 2.0 Comment Form (Thursday, 31 January)
Making links visually distinct
- WCAG 2.0 Comment Form (Thursday, 31 January)
meaning of accessibility supported unclear
- WCAG 2.0 Comment Form (Tuesday, 22 January)
meaningful and logical sequence
- WCAG 2.0 Comment Form (Tuesday, 22 January)
Media exemption to 1.1.1
- WCAG 2.0 Comment Form (Tuesday, 22 January)
Minimum contrast needed for default layout in case 1.4.3 is met via a contrast control
- WCAG 2.0 Comment Form (Thursday, 31 January)
missing situation
- WCAG 2.0 Comment Form (Saturday, 5 January)
Missing Success Criteria - Acronyms
- WCAG 2.0 Comment Form (Wednesday, 30 January)
paragraph spacing is larger than line spacing
- WCAG 2.0 Comment Form (Thursday, 31 January)
Potential consequences of success criterion 3.2.5 are too severe for \"AAA\"
- WCAG 2.0 Comment Form (Monday, 28 January)
problem with example of change of context
- WCAG 2.0 Comment Form (Saturday, 12 January)
Provide a quick reference for web designer
- WCAG 2.0 Comment Form (Thursday, 31 January)
provide greater support for people with cognitive, language or reading difficulties
- WCAG 2.0 Comment Form (Tuesday, 22 January)
Provide no keyboard trap information in context
- WCAG 2.0 Comment Form (Tuesday, 22 January)
Reference to \"users with disabilities\" in appropriate
- WCAG 2.0 Comment Form (Wednesday, 30 January)
Refering to \"users\" vs. \"users with disabilities\"
- WCAG 2.0 Comment Form (Thursday, 31 January)
- WCAG 2.0 Comment Form (Thursday, 31 January)
SC 1.4.5 unclear
- Sailesh Panchang (Tuesday, 29 January)
scaling of line-height and containers-heights
- WCAG 2.0 Comment Form (Thursday, 31 January)
Space missing in \"visuallycustomized\" of the \"Customizable\" list item.
- WCAG 2.0 Comment Form (Monday, 28 January)
Step backwards from WCAG 1.0?
- WCAG 2.0 Comment Form (Thursday, 31 January)
technical terms definition and example
- WCAG 2.0 Comment Form (Saturday, 12 January)
Technique G142 Insufficient
- WCAG 2.0 Comment Form (Wednesday, 30 January)
Test
- WCAG 2.0 Comment Form (Thursday, 3 January)
The subject here does not affect an content author.
- WCAG 2.0 Comment Form (Thursday, 31 January)
Unclear wording of Sufficient Technique H73
- WCAG 2.0 Comment Form (Wednesday, 30 January)
Unnecessary extra Principle 4
- WCAG 2.0 Comment Form (Thursday, 31 January)
Use of \"disability\" instead of \"impairment\".
- WCAG 2.0 Comment Form (Thursday, 31 January)
very similar in color to the body text condition
- WCAG 2.0 Comment Form (Saturday, 5 January)
WCAG 2.0 Comment Submission
- WCAG 2.0 Comment Form (Monday, 21 January)
- WCAG 2.0 Comment Form (Saturday, 5 January)
When is a change of content a change of context
- WCAG 2.0 Comment Form (Thursday, 31 January)
Why do contrast requirements not apply to lines in diagrams and such?
- WCAG 2.0 Comment Form (Thursday, 31 January)
Why the exception for proper names and technical terms?
- WCAG 2.0 Comment Form (Thursday, 31 January)
Word \"Essential\" is confusing
- WCAG 2.0 Comment Form (Wednesday, 30 January)
Word \"limited\" is confusing
- WCAG 2.0 Comment Form (Wednesday, 30 January)
Last message date: Thursday, 31 January 2008 21:50:14 UTC