Summary of BAD TF teleconference on Tuesday 14 February, 2006

Hi,

Today's discussion covered the following topics:
* Resolving issues list
* Plan for future work
* Date of next meeting


RESOLVING ISSUES LIST:

#1) Images of top stories as CSS (Panda, Violin, Brains)
- These images usually do convey some content that is related to the article. To demonstrate best practice in images and descriptions, we will do the following:
 * Images in the (right) side bar will be assumed as purely decorative and hence will remain as CSS images with no descriptions.
 * Images in the center top-stories section (Panda, Violin, Brains) will be assumed informative and will be placed into the HTML with short descriptions.


#2) Bad foreground/background color contrast for several links
- These will be fixed to demonstrate best practice (easy fix).


#3) PDF leaflet needs an accessible version (or alternative)
- This will be removed from the before and after page.


#4) Need explicitly associated label for the quick menu
- An invisible <label> to describe the purpose of the quick menu should be implemented as best practice. More over, the contents of the menu should reflect the themes rather than repeat the left navigation bar (e.g. "articles", "tickets", etc). This will be changed on both the before and after pages because it is not really an accessibility issue.


#5) Document structure should start with <H1> level heading
- An invisible <h1> with information such as "Citylights Home Page" should be implemented. This heading should be the same as the document title too.


#6) CSS validation errors ("display: inline-block") and warnings  
- Seems like inline-block is a valid CSS 2.1 element. Shadi will look into this.

#7) Screen reader directions and options
- Invisible list at the top of the page that describes the skip links to screen reader users does not show in JAWS. The reason is the usage of CSS "display: none". Need to implement this by left positioning out of the view port. Also, these direction should come after the warning which should always be the first element.


PLAN FOR FUTURE WORK

Most of the remaining issues (listed above) are to be resolved during the next day or two (mainly Shadi and Liam). After that, the template will be sent out to BAD TF participants for them to put their after pages in to (Steve for "News" and "Data", and Pasquale for "Survey"). At the same time, volunteers from EOWG will be testing the template on different environments and with assistive technologies etc for additional outstanding issues (I hope only small tweaks will be necessary if at all).


DATE OF NEXT MEETING

Tuesday 21 February, 2006 at 11am CET (10am UK, 9pm EST).


Regards,
  Shadi


-- 
Shadi Abou-Zahra     Web Accessibility Specialist for Europe | 
Chair & Staff Contact for the Evaluation and Repair Tools WG | 
World Wide Web Consortium (W3C)           http://www.w3.org/ | 
Web Accessibility Initiative (WAI),   http://www.w3.org/WAI/ | 
WAI-TIES Project,                http://www.w3.org/WAI/TIES/ | 
Evaluation and Repair Tools WG,    http://www.w3.org/WAI/ER/ | 
2004, Route des Lucioles - 06560,  Sophia-Antipolis - France | 
Voice: +33(0)4 92 38 50 64          Fax: +33(0)4 92 38 78 22 |

Received on Tuesday, 14 February 2006 12:20:15 UTC