See also: IRC log
shadi: are we missing anything from WCAG
2.0?
... specifically the after pages.
<shadi> http://www.w3.org/WAI/EO/2005/Demo/after/
shadi: we need an evaluation of it
Tom: what does it need to cover: sufficient techniques or all success criteria?
<shadi> ACTION: Tom to evaluate after pages against WCAG 2.0 by 24 November [recorded in http://www.w3.org/2008/11/12-badtf-minutes.html#action01]
shadi: Eris' conclusion: markup needs optimisation
Michael: after code should be best possible
... visual layout should be the same
Tom: nervous about demonstrating bad practice
Maik: change of design is a lot of work
<shadi> ACTION: Eric to provide a sample after page with optimized code [recorded in http://www.w3.org/2008/11/12-badtf-minutes.html#action02]
<shadi> http://www.w3.org/WAI/EO/2005/Demo/before/info
shadi: should Broken CSS on Articles Page be dropped?
Michael: maybe too unrealistic as it is now
Eric: is the link between bad CSS + markup and broken CSS communicated?
<shadi> Reading order is distorted without style sheets - see Page Structure in the Evaluation Report different format
Michael: problem with reading order usually appears in headers and floating boxes
shadi: after pages has priority
<shadi> ACTION: Eric to implement incorrect reading order (but without it breaking on most browsers) on the before "Articles Page" [recorded in http://www.w3.org/2008/11/12-badtf-minutes.html#action03]
<Michael> http://www.wienfluss.net/BAD/BAD.png
<shadi> http://lists.w3.org/Archives/Public/public-wai-eo-badtf/2008Nov/0004.html
Tom: are the tabs just visual?
Micheal: maybe ARIA, but keep it simple - markup
<shadi> ACTION: Michael to implement a prototype of the proposed navigation by 24 November [recorded in http://www.w3.org/2008/11/12-badtf-minutes.html#action04]
shadi: both accessible and inaccessible annotation pages?
Jan Sjoerd: where should the icons be placed?
Jan Sjoerd: would be images within a link, and with CSS and Javascript text boxes would pup-up
Jan Sjoerd: ...bottom of the page would have a list with the information about the problem
shadi: need to code now, the content will come later
Michael: had some discussion, might summarize on the list
shadi: Different icons for different
problems
... before: one for real issues, one for warnings; after: one is
sufficient
Eric: after: two icons: information and error corrected
<shadi> ACTION: shadi to recruit somebody to help out with the JavaScript [recorded in http://www.w3.org/2008/11/12-badtf-minutes.html#action05]
<shadi> ACTION: jan sjoerd to provide an update for the icon/markup annotation [recorded in http://www.w3.org/2008/11/12-badtf-minutes.html#action06]
Jan Sjoerd: should we provide a verbosity setting? like show only A or AA etc.
<shadi> ACTION: shadi to chase liam on his action item [recorded in http://www.w3.org/2008/11/12-badtf-minutes.html#action07]
shadi: next meeting on 26th of november 2008