- From: Alan Chuter <achuter@technosite.es>
- Date: Mon, 22 Sep 2008 11:45:21 +0200
- To: MWI BPWG Public <public-bpwg@w3.org>
Here are some comments on different sections of the document (not all of it). 3.5.1 Offer A Consistent View Across Multiple Devices At first reading, from the section heading, I expected this to be about the "Thematic Consistency" BP. I think it would be easier to grasp the idea if the example came first, like "A user may own different mobile devices or may access the same application from both mobile and desktop devices." Then move the "credentials" bit to the next sentence, like "If an application can identify the user from different devices, the experience should be consistent." 3.6.1 Consider Different Device Interaction Methods 3.6.1.1 What it means I think that "there is 4-way navigation" should say "there is 4-way navigation control" and "control the flow" means "move focus." Under touch-based: "There is no concept of a pointer or focus." Surely there is focus, just that it is changed by touching the screen. Perhaps "There is no concept of a pointer or keypad navigation." 3.6.1.2 How to do it Generally in this section I think it use "should" rather than "can". "content requires multiple links" perhaps "interaction requires multiple links" "the user's interaction with links is designed to give them feedback" I don't understand what is intended here. Under focus: "Selectable elements can be widely spaced *so that* the user can select them easily." Under pointer: "The location of the user can be easily determined using as link elements will be in focus" delete "using"? That's the only way I can understand this. Perhaps add "location of the user *on the page*" (it's not about geographical location). Under Touch: "*spaced wide apart* *so that* the user can select..." 3.6.2 Use Scripting for User Interface I think that "re-rendering the page" means "re-rendering the whole page" (even Ajax dynamic pages re-render parts of the page). Perhaps it is really also about "reloading" across the network as well as just rendering it. For "this greatly improves application usability" please add "can" like "this can greatly improve application usability." It isn't the case for all users, for some people the effect can be the opposite. "Script on the client can update specified parts of the page, identified either by the ID tag, the css classname, or from the document structure." Is it necessary to expplain this? If people are reading it we can assume they know how it works in a general way. "ID tag" should be "ID attribute." I don't think it's possible to say this in a useful way in a single sentence. It would be better to talk about the when and why, like "Consider the inter-page interaction. Does the whole page content change? Might it be beneficial to update only part of the current page. Look for islands of dynamic information in a page." I think that this is surely dealt with in great detail elsewhere, it might be useful to link to some article about identifying when to use dynamic page updates. regards, -- Alan Chuter Senior Web Accessibility Consultant, Technosite Researcher, Inredis Project (www.inredis.es/) achuter@technosite.es http://www.technosite.es
Received on Monday, 22 September 2008 09:46:53 UTC