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