CMPT 480 / 840 Accessible Computing

Critiques


Purposes of a Critique

Critiques get you thinking about the important parts of what is contained in a paper, by getting you to go beyond what it contains.
NOTE: Critiques are not book reports or summaries of an article.

Critiques are very important for our class, since they will form the basis of some of our discussion of the topics.

Critiques are worth 20% of your mark in the course.

Submitting your Critique

All students are required to e-mail the instructor their critiques (containing the content discussed below) of selected readings (listed below) by 12 noon on the Friday prior to the week where they are to be discussed.

The subject of the e-mail should be "480/840 Critique for week xx - your name", where week xx is the number of the week the critique is for (not the number of the week in which it is to be handed in) and where you insert your own name in the subject line.

It is preferred (but not required) that students use the critique template for formatting their critiques.

It would be appreciated if you would follow the following convention for the files you send for your weekly critique
where nn is the number of the week that the critique is for (e.g. the first critique is for week 02 even though it is due at the end of week 01)


Contents of a Critique

Do a critique of the readings assigned for next week's class by identifying and discussing at least five major challenges and/or opportunities.

Each discussion of a challenge or opportunity should:

Each critique is marked out of 10.

Examples of strong critique items from another course include (each of these items would be worth 2 marks so 5 items of this quality would get the full 10 marks available):

1. Example of an Opportunity:

Identification
Type: Opportunity
Name: Interviewing Techniques
Discussion:  This section discusses gathering information from users via interviews or questionnaires.  What recommendations are there for constructing the questionnaire and/or interview?
Location: Ch 4.4.3, page 35

Significance:
Interviewing is a technique talked about the book which is used by Usability Engineers in order to obtain information from users prior to building the system.  It would be helpful to provide insight regarding interviews and questionnaires because these tools can be the key to obtaining a good analysis of the system.
Suggestion:
[a weak suggestion (for a 1 point critique) would be] Items such as questionnaire/interview length, question format (open ended, closed ended, multiple choice, etc), question order should be discussed.
[a strong suggestion (for a 2 point critique) would be to suggest a means of satisfying the opportunity] http://www.usabilitynet.org/tools/methods.htm provides a good discussion of various uasbility methods.

2. Example of a Challenge:

Identification
Type: Challenge
Name: Wisdom
Discussion: At the beginning of this section, it is pointed out that Data, information, knowledge, and perhaps even wisdom make up the contents of our Web pages.
Location: 6.1.5 Facts and Opinions, page 8
Significance:
I think is impossible to do what this is asking us.
Suggestion:
Based on the definition of “wisdom” in last section and my personal understanding, I don’t think wisdom can be represented in web pages as content. The reason is that wisdom is human being’s ability to use mastered knowledge to evaluate decision and make decision in the unknown area. It is hard to show this kind of abstract concept. Maybe web site can provide a scenario to help users develop their wisdom.

(I expect that the above can be answered in 2 - 3 printed pages)

Please remember: it is not acceptable to  criticize the authors and tell them that they should change their paper. Good critique items are intended to take us beyond the paper as discussed in Guidance on Creating Good Critiques. It is essential that you all read and understand what is required of a critique before you do your next cri

List of Critiques and Dates

NOTE: This list is subject to change up to the last class on the week preceding the due date.

Week #
Reading to be critiqued
Critique  due
 02 From User interfaces for all to an Information Society for All: Recent achievements and future challenges (C. Stephanidis, 2000, http://ui4all.ics.forth.gr/UI4ALL-2000/ files/Position_Papers/Stephanidis.pdf)

NOTE: It is important that you do this critique before looking at the two posted examples of critiques. This critique will be used for practice purposes to help you get used to creating good critiques. If you submit it you will receive feedback. However, no marks will be recorded for this critique. Future critiques marks will be recorded.
NOTE: This is due on Monday becasue of the start of class


Noon,  S 10
 03  A review and reappraisal of information technologies within a conceptual framework for individuals with disabilities (J.A. Jacko and H.S. Vitense, 2001, available from U of S Library via Springerlink:  http://www.springerlink.com.cyber.usask.ca/content/1615-5297/) Noon, S 14
 04 Using a Universal Access Reference Model to Identify Further Guidance that belongs in ISO 16071, (J. Carter & D. Fourney, 2004, available from U of S Library via Springerlink:  http://www.springerlink.com.cyber.usask.ca/content/1615-5297/)
Noon, S 21
 05W3C Web Content Accessibility Guidelines
NOTE: You need to consider three documents together, the main guidelines, the document on understanding the guidelines and the document on the thechniques for implementing the guidelines.
(http://www.w3.org/TR/WCAG20/Understanding WCAG 2.0 and Techniques for WCAG 2.0.)
Noon, S 28
 06 Government of Canada Accessibility Domain Architecture (http://www.collectionscanada.gc.ca/webarchives/20071125175659/www.tbs-sct.gc.ca/ fap-paf/documents/accessibility/access00_e.asp) Because of the break this is due one day early Noon, O 4
 07 ISO/IEC 20071-21 Information technology — User interface component accessibility - Part 21 Guidance on descriptive video (descriptive audio) NOTE this is not due until:
Noon, O 17
 08no critique due for this week
 09 ISO/IEC TR 19764 Guidelines, methodology, and reference criteria for cultural and linguistic adaptability in information technology products Noon, O 26
 10 D. Fourney & J. Carter, 2006. A standard method of profiling the accessibility needs of computer users with vision and hearing impairments, CVHI 2006, 6 pages. Noon, N 2
 11 ISO/IEC 13066-1 IT - AT Interoperability standard
Noon, N 9
 11 ISO 9241-129 Guidance on individualization Noon, N 16
 12 R. Adams, Decision and stress: cognition and e-accessibility in the information workplace, Universal Access in the Information Society, 5(4): 363–379 [available from U of S Library via Springerlink:  http://www.springerlink.com.cyber.usask.ca/content/1615-5297/] Noon, N 23




Copyright © 2012 - Jim A. Carter Jr.