W3C home > Mailing lists > Public > public-html-a11y@w3.org > December 2009

Involving Users for Better Accessibility. Summary Eval Wiki Page Update (was CHANGE PROPOSAL: Table Summary)

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Wed, 9 Dec 2009 10:58:08 -0600
Message-ID: <1c8dbcaa0912090858gf458f5eo39a3cfd1bff22209@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Cc: Matt Morgan-May <mattmay@adobe.com>, John Foliot <jfoliot@stanford.edu>, Ian Hickson <ian@hixie.ch>, Roger Johansson <roger@456bereastreet.com>, Leif Halvard Silli <lhs@malform.no>, Janina Sajka <janina@rednote.net>, "Michael(tm) Smith" <mike@w3.org>
Hello Everyone,

Just in case you missed it, the document: "Involving Users in Web
Projects for Better, Easier Accessibility" was recently published [1].
It mentions "Web technologies and technical specifications, such as
HTML".

I’ve added that link to the reference section of our "Brainstorming
Table Summary Usability Evaluations" Wiki page [2] and made a few
other minor updates.

Again, if I missed anything or if I got anything wrong on the Wiki
page, please correct it or let me know and I will. If anyone has
additions please do contribute to the document. Or chime in here.

Thanks.

Best Regards,
Laura

[1] http://www.w3.org/WAI/users/involving.html
[2] http://www.w3.org/WAI/PF/HTML/wiki/Brainstorming_Table_Summary_Usability_Evaluation

On 12/8/09, Laura Carlson <laura.lee.carlson@gmail.com> wrote:
> Hello Everyone,
>
> I wrote:
>> Did I get any of this wrong? Are there additions or corrections? Are
>> there other concerns? I can start a brainstorming page to track
>> this in the Wiki.
>
> Here is a start of a Wiki page to gather concerns (general and
> specific) that may be relevant to any usability evaluation that this
> task force may possibly undertake to investigate and resolve HTML
> Issue 32.
> http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Brainstorming_Table_Summary_Usability_Evaluation
>
> If I missed anything or got anything wrong, please correct it or let
> me know and I will.
>
> If anyone else has additions please contribute to the document. Or
> chime in here.
>
> Thanks.
>
> Best Regards,
> Laura


On 12/8/09, Laura Carlson <laura.lee.carlson@gmail.com> wrote:
> Hello Everyone,
>
> I went back through the public-html-a11y email on table summary thread
> trying to extract concerns (general and specific) [1] that may be
> relevant to any usability evaluation goals [2]. So far I've found:
>
> Matt's concerns [3] [4]:
> * Will a table summary replacement that defaults to visible not be
> used because it's presented visually?
> * What is the best way to reconcile aesthetics and data with one another?
> * If people are taught to write _good_ @summary values will they
> write _bad_ summary values?
> * Will people think to add a summary paragraph if they are they're not
> prompted to do so by a tool?
> * How can study data be fairly analyzed by humans who are frustratingly
> analog?
>
> John's concerns [5]:
> * Are facts based on public available data?
> * What evidence is there that @summary causes *harm* to users?
> * Is  meta-data better than no data?
>
> Ian's concerns [6] [7]:
> * Would a visible table summary help accessibility?
> * Does a hidden table summary (summary attribute) harm accessibility?
> * Does a hidden table summary (summary attribute) help accessibility?
>
> Roger's concerns and criteria [8]:
> * Do AT users  who use shortcuts to jump straight to the table miss
> any information if the table summary information is provided in
> paragraphs not explicitly associated with a table?
> * What is the best way for authors to satisfy stakeholders aesthetics
> of not having a table table summary information visible and still
> making a table accessible?
>
> Leif's concerns [9]:
> * What kind of extra table summary information is needed for accessibility?
> * What is the best way to add that information?
> * What is the feasibility of a the task force doing test? Do we have
> the needed resources?
> * Can we include authors as well as participants in studies?
> * Can goals be specified so everyone agrees upon them?
> * How do we fairly interpretable outcomes?
>
> Did I get any of this wrong? Are there additions or corrections? Are
> there any other concerns? I can start a brainstorming page to track
> this in the Wiki.
>
> My concerns are similar to those above. The biggest one is:
> * How can table summary be *improved*?
>
> If it is decided we want to pursue this avenue, I have some 2002
> usability testing planning documents on line which may be useful. They
> include planning materials for usability testing goals, tasks,
> scenarios, measures, participants, timelines, materials etc.
> http://www.d.umn.edu/~lcarlson/testing/planning/
>
> Best Regards,
> Laura
>
> [1] A concern is a question about usability.
> [2] A goal is a declarative statement resulting from a question of
> concern. A goal establishes an objective to measure.
> [3] http://lists.w3.org/Archives/Public/public-html-a11y/2009Dec/0003.html
> [4] http://lists.w3.org/Archives/Public/public-html-a11y/2009Dec/0008.html
> [5] http://lists.w3.org/Archives/Public/public-html-a11y/2009Dec/0004.html
> [6] http://lists.w3.org/Archives/Public/public-html-a11y/2009Dec/0002.html
> [7] http://lists.w3.org/Archives/Public/public-html-a11y/2009Dec/0045.html
> [8] http://lists.w3.org/Archives/Public/public-html-a11y/2009Dec/0042.html
> [9] http://lists.w3.org/Archives/Public/public-html-a11y/2009Dec/0043.html

-- 
Laura L. Carlson
Received on Wednesday, 9 December 2009 16:58:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:41:57 GMT