ISSUE-35
information overload/underload -- no oneSizeFitsAll (public comment)
- State:
- CLOSED
- Product:
- All
- Raised by:
- Bill Doyle
- Opened on:
- 2007-04-13
- Description:
- From public comments
raised by: Al Gilman Alfred.S.Gilman@ieee.org
http://lists.w3.org/Archives/Public/public-usable-
authentication/2007Apr/0000.html
information overload/underload -- no oneSizeFitsAll
where it says, in 2.2 Relevance of security information
The Working Group will analyze common use cases to determine what
security information a user requires to proceed safely and recommend
security information that should, or should not, be presented in
each case.
please consider
While GUI users rarely perturb the presentation decisions of the web author,
Screen reader users commonly do use verbosity settings in their user
environment. So the presumption must be that the good practice this Working
Group decides on as to \"how much to say when\" is in fact only competent for
user interface modes and conditions similar to the predominant delivery
context of web users. It\'s not universal. Yes, it\'s good to get more
consistency in following this good practice where it fits, but recognize the
limits of the goodness of this practice and don\'t think that this goodness
extrapolates across all Web delivery contexts. For that reason, the
function/performance model of the security aspect needs to be articulated
separately and independently from the good practice binding for presentation
of those functions with the desired comprehension and annoyance performance
characteristics in the nominal delivery context. In particular,
10.1.8 \"Provide explanations ...\" shows you realize that the information needs
to be there in support of a mixed-initiative, variable-level-of-detail user
experience. All the available information should be considered \'conditonal
content\' of the dialog state as contemplated by UAAG 1.0, Guideline 2. So
while the WSC deliverables may well not discuss *how* to present all this
information, *some* way to access all this information is a requirement of the
UAAG guideline.
- Related Actions Items:
- No related actions
- Related emails:
- Re: ISSUE-35: information overload/underload -- no oneSizeFitsAll (public comment) (from Mary_Ellen_Zurko@notesdev.ibm.com on 2007-04-17)
- ISSUE-35: information overload/underload -- no oneSizeFitsAll (public comment) (from dean+cgi@w3.org on 2007-04-13)
Related notes:
No additional notes.
Display change log
