W3C home > Mailing lists > Public > public-wcag2ict-tf@w3.org > July 2012

Re: User Interface Context

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Fri, 13 Jul 2012 02:24:04 +0200
To: "Hoffman, Allen" <Allen.Hoffman@HQ.DHS.GOV>
Cc: "Bailey, Bruce" <Bailey@Access-Board.gov>, Andi Snow-Weaver <andisnow@us.ibm.com>, "public-wcag2ict-tf@w3.org" <public-wcag2ict-tf@w3.org>
Message-id: <D1F23E05-260D-4C48-9D4F-FB9AF35C55A3@trace.wisc.edu>
Good catch

Actually they don't contradict. But I can see how the way they are worded may sound that way. 


When you open a non-modal dialog the User Interface Context gets new parts or grows.  So it "changes".  You aren't leaving the old UIC but the old UIC changes. 

But the way it is written it clearly sounds like a contradiction.

I have rewritten #5  from
> "5.In software user interfaces, the user interface context would change when a non-modal dialog box is opened because additional information and user interface elements are just added to the previously existing context. 
to
"5.In software user interfaces, the user interface context be modified but you would not change to a new UIC when a non-modal dialog box is opened because additional information and user interface elements are just added to the previously existing context. 





Gregg
--------------------------------------------------------
Gregg Vanderheiden Ph.D.
Director Trace R&D Center
Professor Industrial & Systems Engineering
and Biomedical Engineering
University of Wisconsin-Madison

Co-Director, Raising the Floor - International
and the Global Public Inclusive Infrastructure Project
http://Raisingthefloor.org   ---   http://GPII.net








On Jul 12, 2012, at 6:14 PM, Hoffman, Allen wrote:

> Unless we've progressed past this:
> 
> In thinking on this, I am thinking that note five contradicts with Note seven.
> 
> "5.In software user interfaces, the user interface context would change when a non-modal dialog box is opened because additional information and user interface elements are just added to the previously existing context. 
> 7.Standard menus are not themselves user interface contexts because the user can navigate to and from them using standard focus navigation commands.   The same applies to standard ribbons."
> 
> -----Original Message-----
> From: Bailey, Bruce [mailto:Bailey@Access-Board.gov] 
> Sent: Thursday, July 12, 2012 12:12 PM
> To: Gregg Vanderheiden
> Cc: Hoffman, Allen; Andi Snow-Weaver; public-wcag2ict-tf@w3.org
> Subject: RE: User Interface Context
> 
> I think I am comfortable with:
>> User Interface Context == set of user interface elements and the presented information that can be accessed using only navigation commands
> 
> I can also appreciate that "product" was meant as an example of a "set of User Interface Contexts" rather than as a definition.
> 
> But that still leaves:
>> User Interface Context (by one author) == set of user interface elements and the presented information, within a product, that can be accessed using only navigation commands
> 
> That if it is not circular, it is at least ambiguous without a definition of "product" (that does not use our new UIC term).  I am not clear why we need to define "User Interface Context (by one author)".  Where do we use that phrase?
> 
> 




Received on Friday, 13 July 2012 00:24:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 13 July 2012 00:24:33 GMT