UX-P5

content/blog/MadUX-Spring/index.md

@@ -1,5 +1,5 @@
 ---
-title: "Case Study: redesigning Randomness"
+title: "Case Study: Redesigning Randomness"
 date: 2024-08-03
 searchHidden: true
 draft: true
@@ -12,5 +12,3 @@ summary: "Summary of prototyping, design and evaluation work completed for the s
 description: "Summary of the design & research conducted as a part of the spring term of my user experience capstone. ✏️🎮️"
 tags: ["UX", "Research", "Development", "MOTHER²"]
 ---
-
-# Redesigning Randomness

content/blog/UX-P5/index.md

@@ -16,8 +16,28 @@ tags: ["UX", "Research", "Accessibility"]
 
 _This is the fifth entry in my UX portfolio series. If you have not read the previous one, you can find it [here](../ux-p4/)_ 👈️
 
-## Card Sorting & Information Architecture
+{{< figure src="./img/WAVE-screenshot.png" align="center" caption="_WAVE_ a suite of evaluation tools that helps authors make their web content more accessible to individuals with disabilities." >}}
 
-## Digital Accessability
+## Interlude
+
+When we last left our summer research study, we completed a pilot round of examination for our study materials before drafting a preliminary report on the result from the pilot. This past two weeks, we have taken a short recess from conducting our study, to explore two important topics in the realm of user experience: Information Architecture and Web Accessibility. Relating to one core goal of the Mad UX program, these weeks allow us to develop a broader understanding of various research methods. Shifting focus in this way also allows us additional time to make changes to our study based on peer feedback, and recruit participants for our final study.
+
+## Information Architecture
+
+Our first week of study during this unit saw my cohort and I returning to the practice of [information architecture](https://www.nngroup.com/articles/information-architecture-sitemaps/), a topic we had briefly covered in more detail in the fall term of our UX capstone. As it relates to digital accessibility, creating clear and effective headings and labels is a crucial part of creating websites that are easy to use for keyboard-only users or users navigating sites with a screen reader. As strange as it may sound (though I suspect some of my fellow _code monkeys_ may relate) one aspect of creating digital applications that I find particularly satisfying and rewarding. As may be evident from the platform of this site, I have a deep love of writing in Markdown (a markup language that emphasizes structure and consistency) extending beyond authoring content for this blog to the notes I take with [Obsidian](https://obsidian.md/) every week.
+
+In video games, information architecture is a crucial piece in organizing menus and interfaces of the game ranging from the settings and title menus to the inventory, stat windows, and skill trees of many RPGs. These interfaces are often developed and evaluated with [card sorts](https://www.nngroup.com/articles/card-sorting-definition/) and [tree tests](https://www.nngroup.com/articles/tree-testing/) depending on the stage of development and the maturity of the interface. For MOTHER², the most appropriate method for testing interfaces like the combat menus used in battle would likely be a tree test as veteran players already have well-defined mental models of _EarthBound's_ interfaces. Conversely, the settings menu for MOTHER² would most likely benefit from a cart sort, to better categorize the new features of the game in a way that matches the expectations of today's RPG players.
+
+## WAI, WCAG, and WAVE (Oh my!)
+
+A majority of the time spent these past weeks saw us revisiting the principles of [universal and inclusive design](https://www.nngroup.com/articles/inclusive-design/) and how they apply to both sites and games. A majority of our time was spent revisiting the [Web Content Accessibility Guidelines](https://www.w3.org/WAI/standards-guidelines/wcag/), which are developed by the [World Wide Web Consortium's Web Accessibility Initiative](https://www.w3.org/WAI/about/). Our main exercises this week was provided by [Accessible University](https://a11y-assessments.pages.oit.duke.edu/accessible-u/). Their site provides a great way to practice your skills in auditing websites for accessibility issues, using tools like [WAVE](https://wave.webaim.org/) and [Orca](https://help.gnome.org/users/orca/stable/introduction.html.en) (or any other screen reader). I found this exercise to be a great way to develop empathy for users who rely on a screen reader and inspired me to audit my own site for accessibility issues (perhaps the subject of a future post...)
+
+## Accessibility in Games
+
+It is important to note, however, that accessibility for digital games has only recently gained greater public awareness in the last 5 years. Apple's [Human Interface Guidelines](https://developer.apple.com/design/human-interface-guidelines/designing-for-games) which is considered the go-to bible for web guidelines by some, only recently expanded to include games last month.
+
+If you are looking to learn more about how the games industry is changing to become more inclusive: check out [this playlist](https://www.youtube.com/watch?v=NInNVEHj_G4&list=PLc38fcMFcV_vvWOhMDriBlVocTZ8mKQzR&pp=iAQB) by [Game Maker's Toolkit](https://www.youtube.com/channel/UCqJ-Xo29CKyLTjn6z2XwYAw).
+
+{{< youtube NInNVEHj_G4 >}}
 
 <!-- _The UX portfolio series continues on. You can continue reading [here](../ux-p6/)._ ⏩️ -->