ETEC 511 – Project Retrospective

I feel that this was an interesting project to be a part of, and coming into it late, eliminated some of my ability to influence the direction of the group, but I think my role became an early critic – asking pointed questions so that I could understand why decision were made – and help support them. One of the things I often did in meetings was try to help tie our decisions back to course readings, course content, and thinking about the project less as a project and more as an assignment. I think I also served as a bit of a wrangler of ideas, trying to limit scope creep.

One other thing I did was in my section (accessibility legislation) really try to refine the information into questions and answers, so that particular section became conversational. I recall talking about making our language plain, simple and understandable and how we could use that as an engagement strategy, and in turn making it more usable, which was I think my most important contribution to the process. I will admit my passenger-ness to the project, and did not feel 100% like it was my project (again, coming in late to it made it a bit of a challenge) so I always saw my role as a bit of a servant to the whole.

From a Nielsen (2003) perspective, Twine was at the same time easy to use and learn the basics of quickly. The simplicity of the design of the tool (questions and answers with expositional text) were easy to construct in Twine. The complexity of the subject matter however, made Twine a difficult choice to manage how each component piece linked. Had we not limited our choices to discuss, we absolutely would have been tangled in a web of, well, Twine. I think that the affordances of Twine’s output, especially in the way we designed the tool, kept the complexity down, which in turn allowed the tool to ultimately be more usable.

I don’t know if Twine ended up being the best choice as we had to bend it quite a lot to make it do what we wanted it to do. The tool ultimately configured us as designers, as we were pretty locked into Twine. While it ended up perfectly fine, it did limit us in some ways, that due to our technical understanding of what was possible and the time constraints it would have taken to further use Twine beyond what it is built for, I wonder if this would have been simpler to build using HTML and delivered a more accessible tool in the end?

References

Nielsen, J. (2003). Usability 101: Introduction to usability. Useit. 

ETEC 511 – IP #1: Users, Uses and Usability

1. Formulate a conception of usability (based on the Issa and Isaias (2015) chapter on HCI and Usability). Use what you’ve learned about usability from that chapter—but you are not summarizing or repeating their ideas. Rather, you are setting out the idea of ‘usability’ you have put together from reading that chapter. Do NOT overly rely on quotes. And remember to use proper citation practices. If you are using text that is not your own, quote and cite it, including page numbers.

HCI (Human Computing Interaction) is essentially a translation service, in that it attempts to communicate between a machine and a human the purpose of the machine. Usability is the measurement of the success of that translation. If a piece of software or website is usable, then it is described as intuitive, easy to use, simple. To be usable, a designer must examine the functionality, efficiency, effectiveness of the software and take into consideration the user’s needs, context and satisfaction. (Issa and Isaias, 2015, p. 30) While this article was written only seven years ago, it seems like the authors only consider positive usage of technology and do not consider, or consider deeply, the idea of designing around bad actors. Wiegers contends that you should design around bad actors, and to prevent users from possibly misconstruing the information conveyed – in that usability should factor in not only the positive uses of a system, but also how it can be misused. (Wiegers, 2021)

2. Then, think about what is missing from this conception, from a specifically educational perspective, and on that basis try and patch together a reasonably grounded and defensible conception of educational usability.

While usability is a key concept in designing learning – especially the examination of context, and user/student needs, it is missing two other key components. While Issa and Isaias (2015) suggest that the user factors in HCI include motivation, enjoyment and experience level (p. 28) it does not adequately address cultural factors of the user/student. While culture will contribute to levels of access and equity, these factors are often great indicators of success in an educational context. This framework is very much built on western ways of knowing and draws from behaviourist theories of development. For instance, when the designed system works, the user is rewarded (by receiving information, having the computer complete a task, etc.). There is no real opportunity to design for remediation and it appears to have a very binary approach to solving complex problems.

3. Revisit Woolgar’s (challenging but rewarding!) account of “usability gone wrong,” which demonstrates several ways a usability study ended up configuring ‘users,’ thereby undermining the usefulness of usability. Identify and discuss 2 of Woolgar’s examples.

At the crux of Woolgar’s arguments of configuring the user during usability trials it was particularly interesting how he suggested that physical location of user testing is a factor in the results of the testing. Of course, when conducting research, you try to control those variables, and it is very clear (to me) that usability testing is far less rigorous than controlled, double-blind research. However, Woolgar (1990, p. 78) recounts how recalling computer features at Brunel University was different than when in the Stratus offices. If we take this as a common occurrence across users, then how we interact with computers will be different based on physical location. So, it follows that bringing users into a testing area to gather feedback on usability will be different than if the device were provided in their usual operating environment.

A second instance of configuring the users is the selection of who is eligible to participate in user testing (Woolgar, 1990, p. 83) – in this case it is noted that often early adopters, and people who are predisposed to like the product would be ideal testers. However, it is entirely unlikely that these people would provide you a new user’s perspective, or someone who was predisposed to not like computers, or be unfamiliar with computers. In fact, the opposite would likely be the case – users who were familiar and comfortable with computers. It only follows that someone who was familiar with computers would be at least more capable of using them, having a concept of what to do with them.

4. Finally, discuss the two excerpts quoted at the top of this IP, that have been drawn from your readings for this unit, and discuss differences you see in these 2 positions on the uses of usability.

Issa and Isaias (2015) are suggesting that user testing is a feedback mechanism to further improve software and hardware and Woolgar (1990) is suggesting that user testing is a confirmation mechanism – to confirm the assumptions made in designing software and hardware. I see both of these linked to a philosophical debate as to the role of computers in human’s lives – whether humans control computers, or computers determine the actions of humans – and the truth is somewhere in the middle.  It is dependent on your role with the computer. Computer programmers control what is possible and what is not within a game, or website. Human users subvert those possibilities through speedruns and other bending of the rules that humans put in place in the first place. Usability in the early days of computing would never have envisioned some of the ways people would have used computers.

References

Issa, T., & Isaias, P. (2015). Usability and human computer interaction (HCI) In Sustainable Design (pp. 19-35). Springer.

Woolgar, S. (1990). Configuring the user: The case of usability trials. The Sociological Review38(1, Suppl.), S58-S99.

Wiegars, K. (2021). Designing around bad actors and dangerous actions. UX Collective. https://uxdesign.cc/designing-around-bad-actors-and-dangerous-actions-8fc7984c510d

Usability in LMS Pages

Inspired by this post from the UT Web Developers outlining a usability checklist developed by Abhilash Thekkel, I thought that there should be a similar thing for LMS pages as well. Of course, some of the usability issues you need to do for a webpage aren’t necessary for a page managed in an LMS.  For instance, #28 Did you include a link to all your main pages on your homepage? doesn’t require any checking because navigation in the LMS is limited and usually controlled by the system and a link to the course home page is usually included. So here’s a list of items to look for when developing a usable course in an LMS.

Technical:

  1. Did you validate your (X)HTML using W3C Markup Validation Service?
  2. Did you validate your CSS using W3C CSS Validation Service?
  3. Did you check your website in at least IE, FF, Opera and Safari?

Images:

  1. Did you add the ALT attributes to all your images that are non-decorative?
  2. Did you make the size of your pages less then 50KB?
  3. Did you choose the appropriate filetype for your images?
  4. Did you add a description to images that support your content?
  5. Did you use plain text instead of images for important content?

Content:

  1. Did you use a sans-serif typeface with at least a 10 point font size for your body text?
  2. Did you adjusted the leading and tracking, if necessary, to increase readability?
  3. Did you align your body text to the left? (depends on language)
  4. Did you make sure that whole sentences  are not entirely in uppercase?
  5. Did you use less then 78 characters, including spaces, per line?
  6. Did you make brief and precise paragraphs with explanatory titles?
  7. Did you use lists to sum things up?
  8. Did you create enough contrast between the text and the background?
  9. Did you make your website also accessible for text-only browsers?
  10. Did you make sure that there are no ‘under construction’ pages, or links to content that do not work?
  11. Did you replace all special characters with the ISO Latin-1 codes?
  12. Did you spell check your content and did you proofread for grammar errors?
  13. Did you make a high contrast version of crucial information?

Navigation:

  1. Did you use no more then 8 items in your main navigation?
  2. Did you use describe the  link text instead of ‘click here’?
  3. Did you use self explanatory link text instead of business or jargon terms?
  4. Did you make a distinction between links and plain text?
  5. Did you make it possible to browse your website using SHIFT-TAB and RETURN?
  6. Did you make sure you didn’t use any javascript links?

Structure:

  1. Did you make a consistent page structure from page to page and tool to tool?
  2. Did you place important content above the fold/scroll?
  3. Did you make your page design on a grid system?
  4. Did you make your website also viewable on low resolutions?

Multimedia:

  1. Did you make sure that music and videoclips don’t start playing automatically?
  2. Did you make sure that music and videoclips can be turned off at any time?
  3. Did you inform the user about the size and length of your music and videoclips?
  4. Did you select or use  music and videoclips with subtitles or descriptions?

Many of the items in the original article are still useful, but they are at the whim of the administrators of the LMS or the LMS vendor itself. If your LMS is not respecting usability guidelines, maybe you shouldn’t be using it. If you are stuck using it, maybe you should advocate through whatever channels you think appropriate, that they adapt to allow learning for everyone.

Aesthetic Attention

Ran across an article about aesthetics from Carleton University called Aesthetics, visual appeal, usability, and user satisfaction: What do the user’s eyes tell the user’s brain? which had confirmed my previous assertions that you have 3 seconds to make an impression with a website – in fact, according to the article, you have 50 milliseconds. It also confirmed my idea that if your first impression is bad, then you’re fighting an uphill struggle to merely regain your credibility. This is a doubly bad situation for an e-learning space, where you have to not only fight to maintain attention, but also external preconceived notions of e-learning from other professors or teachers work online can have an effect on your credibility as an instructor. That credibility can be a class killer, especially at the College level in Canada. Colleges were built on trades, and being an instructor at College requires some real-world experience in the field that you’re instructing in. Any knock on your credibility can be overcome with good teaching technique, or personality but you have to fight for attention. When you are interacting with a screen though, as your sole “interaction” with a teacher, that initial impact is crucial to retaining attention. Positive first impressions will also allow users to forgive minor usability errors, although I didn’t see a definition of what minor was.

The article also goes on to say that users prefer things that they’ve seen before – which seems like an obvious statement – and also contributes to explaining why we see so many two and three column layouts on the web – familiarity. Three columns mimic the newspaper, which is familiar to most members of the 20th century (although, may not be to the members of the 21st century). Never mind that columns organize information into groups which allows users to better scan and assimilate information, but order on a page is aesthetically pleasing. Disorder is disorienting. So a logical ordering of information will help with your credibility long after the initial impression has occurred. Does it follow that a positive first impression and an orderly page improve your credibility? Or is there a finite amount?