W3C home > Mailing lists > Public > public-wai-eo-badtf@w3.org > April 2006

Re: [Fwd: Testing BAD "after" site]

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Wed, 12 Apr 2006 15:22:40 +0200
Message-ID: <443CFF20.2040007@w3.org>
To: Sylvie Duchateau <sylvie.duchateau@snv.jussieu.fr>
Cc: public-wai-eo-badtf@w3.org

Hi Sylvie,

Thank you for your review, this is indeed very helpful. Please find some comments and questions below:

Sylvie Duchateau wrote:
> In general:
> 1. It is difficult to take apart what is WAI information, and what is a 
> feature that has been implemented by the Web site designer to facilitate 
> the accessibility of the site.

Agreed, the "real" and "demo" content is not easy to distinguish via screen reader, we will rework this and clarify more.

> 2. Selecting another page through the "quick menu" does not seem to 
> work. When you select "facts" in the "quick menu" and click "go", an 
> error page is displayed.

Yes, this is still unfinished, we will fix it.

> The quick menu is also not always the same. On the Home page, you have 
> the choice between the 4 pages. The choice for home has additional 
> information telling the user that Home is the current page. This 
> informatin is not available on the quick menu of the other pages. In the 
> quick menu of the page "news" the menu item "news" has disappeared from 
> the quick menu.

Do you have an opinion which method you favor? (Having all pages in the select field and the one you are currently on marked as such, or rather only the pages you can actually get to)

> * Home Page: <http://www.w3.org/WAI/EO/2005/Demo/after/index>
> In the links to the diferent news: while looking at the code source, I 
> noticed that all of them point to the "info" page. It could be easier to 
> let them point to the beginning of the news, or to the detail of the 
> news. So the user could directly access the story he wants to read.

Not sure about this one. Ideally we would have different pages for every article but that would make the Web site larger than we agreed on. On the other hand, if we jump into the middle of the page it could confuse some users. This is an issue which we will need to rediscuss.

> Page structure: I don't understand the page structure after second 
> heading 1 entitled "elsewhere on the Web". The information belnging to 
> that section talks again about information on the City: "more City 
> Parks", and "free penguins".

Right. "Free Pengiuns" and "More City Parks" are actually part of a side bar but this is not appartent for screen readers.

> * News Article: <http://www.w3.org/WAI/EO/2005/Demo/after/info>
> A heading informing that you are on the news page could be helpful. 
> Which mechanisms have been implemented to help the user find out where 
> he is?

We discussed this in the task force and the conclusion was the title of the document as well as the heading structure give you the context. Why is that not sufficient in your opinion?

> In the datatable summarising the answers to the question on favourite 
> organs a "summary" seems to be missing.

A caption is provided, and the table is pretty simple. What issues are you encountering?

> * Events Page: <http://www.w3.org/WAI/EO/2005/Demo/after/data>
> The second data table is not easy to understand. There should be a 
> description of the way columns and rows interact with each other.

ID, scope, and header attributes have been assigned to all table cells. Do you mean a textual description of the table structure for example in the summary? Isn't this information already provided by the screen reader?

> * Survey Form: <http://www.w3.org/WAI/EO/2005/Demo/after/form>
> It's a good idea to number the categories: general information, habits, 
> traffic perception,....
> It could also be useful to give each question a number: "where do you 
> live?", "how many cars?".
> I'm not sure that the mention (this a required field" should be written 
> each time, as the designer writes, at the beginning of the form, that 
> fields with a * are required fields. It makes the reading of the form 
> with a screen reader much longer.
> Otherwise, I have no remarks on the form.

How about the way in which form and non-form elements are mixed? Do you need to jump back and forth into forms mode? If a novice screen reader user reads the page, do you anticipate any potential problems?

> I don't understand why following information is still on the page: 
> "penguins" and "city park". It may loose the user to have such information.
> As far as page structure is concerned: the headings of the different 
> categories of the form "general information, habits...." are on the same 
> level (level 2) as the headings after the form: "free penguins", "more 
> city parks".

We may need (an invisible) h1 to explain that this is a side bar.

> Other general remark: the pages are full with information. To make them 
> more accessible, there should be less information on the page.

I'm not sure what the exact accessibility issue is. Maybe this will get better when we rework the document headers which would make the pages structurally easier.

Thanks for your review!


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 Wednesday, 12 April 2006 13:22:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:50 UTC