Oppia.org — Logged-In Learner UX Audit — Full Report (9 CUJs + New Dashboard)

Lens / cue	Applies to	Evidence	Why it matters	Caveat
Accessible Authentication	h05/h05_d_02	host_supplied-1	The finding connects to WCAG accessible-authentication guidance: sign-in should not rely on avoidable memory or cognitive tests without alternatives.	UXHC can flag authentication burden, but WCAG evaluation needs the actual auth flow and security constraints; this is not WCAG conformance certification.
Contrast And Visual Presentation	h04/h04_d_17	host_supplied-1	The finding connects to WCAG contrast and visual-presentation guidance: important information or controls may not be perceivable enough.	UXHC can flag visible contrast risk, but measured contrast ratios and state-by-state review are needed before conformance claims.
Contrast And Visual Presentation	h04/h04_d_19	host_supplied-1	The finding connects to WCAG contrast and visual-presentation guidance: important information or controls may not be perceivable enough.	UXHC can flag visible contrast risk, but measured contrast ratios and state-by-state review are needed before conformance claims.
Focus Order, Visibility, And Obscured Focus	h04/h04_d_08	host_supplied-1	The finding connects to WCAG focus guidance: keyboard users need a visible, logical focus path that is not hidden by the interface.	UXHC can flag likely focus risk, but keyboard traversal and viewport-state testing are needed before WCAG conformance claims.
Labels, Instructions, And Input Purpose	h02/h02_d_01	host_supplied-1	The finding connects to WCAG labels-and-instructions guidance: users need visible and programmatic cues for what controls mean.	UXHC can flag labeling risk, but programmatic label associations and accessible-name checks require technical review; this is not WCAG conformance certification.
Modals, Popovers, Tooltips, And Focus Management	h04/h04_d_10	host_supplied-1	The finding connects to accessible overlay guidance: modals and popovers must preserve focus, escape, labels, and context.	UXHC can flag overlay access risk, but keyboard and screen-reader testing are required before WCAG conformance claims.

Lens / cue	Applies to	Evidence	Why it matters	Caveat
CJK Layout And Typography Requirements	h04/h04_d_04	host_supplied-1	The finding may need CJK layout review because typography, line breaking, punctuation, or annotations could change the user's reading path.	CJK layout quality varies by language context and requires target-language content and rendered typography evidence, not translated strings alone.
CJK Layout And Typography Requirements	h04/h04_d_18	host_supplied-1	The finding may need CJK layout review because typography, line breaking, punctuation, or annotations could change the user's reading path.	CJK layout quality varies by language context and requires target-language content and rendered typography evidence, not translated strings alone.
CJK Layout And Typography Requirements	h04/h04_d_19	host_supplied-1	The finding may need CJK layout review because typography, line breaking, punctuation, or annotations could change the user's reading path.	CJK layout quality varies by language context and requires target-language content and rendered typography evidence, not translated strings alone.
Indigenous-Language Orthography And Voice Support	h02/h02_d_02	host_supplied-1	The finding may need target-language validation because spelling, diacritics, pronunciation, or assistive-technology output can affect comprehension and dignity.	Language support should be validated with speakers and local language authorities; UXHC can only flag visible or stated risks.
Literacy, Orality, And Multimodal Access	h05/h05_d_02	host_supplied-1	The finding may need multimodal support because dense text or text-only instruction can exclude users whose access path is oral, visual, assisted, or low-literacy.	Literacy and modality needs vary widely; the lens should preserve agency rather than simplify or infantilize users.
Local Contexts And Traditional Knowledge Labels	h04/h04_d_13	host_supplied-1	The finding may need stronger cultural provenance or permission cues at the point where users view, reuse, or export content.	Labels depend on community-defined protocols; absence of a label in the evidence is not proof that no protocol applies.

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h01_d_01	Every interface begins with a title/header that describes page contents	1.0	Issue	high	host_supplied-1	Homepage shows 'Loading \| Oppia' title on SPA load — confirm load artifact present. Title eventually resolves.
h01_d_02	Headings and subheadings are short, straightforward and descriptive	1.0	Issue	high	host_supplied-1	Dashboard main content shows 'Loading...' for 5+ seconds with blank skeleton — no content shimmer or spinner.
h01_d_03	Value proposition is clearly stated on the home page (tagline or welcome blurb)	2.0	Issue	high	host_supplied-1	Once loaded, active tab is visually indicated; breadcrumb shows location. But login success is implicit — no confirmation.
h01_d_04	The items on the home page are clearly focused on primary actions	2.0	Issue	high	host_supplied-1	Login success is implicit (redirect to dashboard); no explicit 'You are now logged in' toast or confirmation message.
h01_d_05	Each page is clearly branded so that the user knows they are on the same site	1.0	Issue	high	host_supplied-1	Two uncaught JS console errors on dashboard after login — silent failures that may affect functionality.
h01_d_06	Navigation makes it clear which page I am on	2.0	Issue	medium	host_supplied-1	OAuth error states handled by Google (external); Oppia-level OAuth failure states not observed or tested.
h01_d_07	Link names match the title of destination pages, so users will know when they have reached the intended page	2.0	Issue	medium	host_supplied-1	No forms on sign-up screen — Google handles auth. Dashboard nav links match destinations.
h01_d_08	Standard elements (page titles, site navigation, page navigation, privacy policy, etc.) are easy to locate	2.0	Issue	high	host_supplied-1	Navigation reflects URL change; title eventually resolves from 'Loading \| Oppia'.
h01_d_09	Logo is in a consistent location, and clicking the logo returns the user back to the home page	1.0	Issue	high	host_supplied-1	No real-time status indicators; SPA title bug and silent JS errors reduce system transparency.

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h02_d_01	Navigation tabs are located at the top of the page, and look like clickable versions of real-world tabs	3.0	Major	high	host_supplied-1	Language is plain and appropriate — 'Goals', 'Progress', 'Continue' map to learner mental models.
h02_d_02	Items that are not clickable do not have characteristics that suggest that they are clickable	3.0	Major	high	host_supplied-1	Dashboard structure (Home > Goals > Progress) maps well to academic learning concepts.
h02_d_03	Items that are clickable look like they are clickable	2.0	Issue	high	host_supplied-1	OAuth redirect breaks Oppia context — user transported to Google's auth page unexpectedly.

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h03_d_01	There is a search box	2.0	Issue	medium	host_supplied-1	Browser back works but OAuth flow effectively disables it during redirect chain.
h03_d_02	There are clearly marked exits on every page allowing the user to bail out of the current task without having to depend on the browser Back button	1.0	Issue	high	host_supplied-1	No explicit Sign Up CTA — new users must discover that 'Sign In' also handles account creation.
h03_d_03	The site does not disable the browser Back button and the Back button appears on the browser toolbar on every page	2.0	Issue	medium	host_supplied-1	Browser back available; cookie consent OK button dismisses overlay. OAuth redirect chain limits back.
h03_d_04	Clicking the back button always takes the user back to the page they came from	2.0	Issue	high	host_supplied-1	Cookie consent appears immediately without user action — must be dismissed before proceeding.
h03_d_05	Undo and redo are supported	2.0	Issue	medium	host_supplied-1	Logout accessible via User Menu avatar; no other session management controls observed.

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h04_d_01	In your expert opinion, site content does not look like advertisements	2.0	Issue	medium	host_supplied-1	Home link present in logged-out nav but disappears in logged-in state — inconsistency.
h04_d_02	Clickable elements use a consistent style/color for primary, secondary, and tertiary actions	1.0	Issue	high	host_supplied-1	H4 headings used as tab controls — violates ARIA tab pattern; inconsistent heading semantics.
h04_d_03	Value proposition is clearly stated on the home page (tagline or welcome blurb)	2.0	Issue	high	host_supplied-1	'Setting a goal!' CTA styled as inline link text — looks like body text, not a button.
h04_d_04	Navigation choices are ordered in the most logical or task-oriented manner, with less important corporate information at the bottom	3.0	Major	medium	host_supplied-1	Color palette appears consistent across navigation and content areas.
h04_d_05	All corporate information is grouped in one distinct area, such as About Us	3.0	Major	medium	host_supplied-1	Typography appears consistent; lesson card labels are uniformly styled.
h04_d_06	The home page of the site has a memorable URL	2.0	Issue	medium	host_supplied-1	Icon in User Menu button — label 'User Menu' may not match user expectation of 'Account'.
h04_d_07	Terminology is consistent with general web usage	2.0	Issue	medium	host_supplied-1	Navigation items change between logged-in and logged-out states without clear pattern.
h04_d_08	There is a visible change when the mouse points at something clickable, excluding cursor changes	3.0	Major	low	host_supplied-1	No forms on this screen — form styling N/A; rated neutral.
h04_d_09	Hypertext links that invoke actions, such as downloads or new windows, are clearly distinguished from hypertext links that load another page	2.0	Issue	medium	host_supplied-1	Error message style not observed — JS errors are silent; no in-page error displays.
h04_d_10	If the site spawns new windows, these will not confuse the user and can be easily closed	3.0	Major	medium	host_supplied-1	Spacing and layout appears consistent; grid-based card layout consistent.
h04_d_11	Menu instructions, prompts and messages appear in the same place on each screen	2.0	Issue	high	host_supplied-1	Interactive tab elements and 'setting a goal!' CTA not consistently styled as interactive.
h04_d_12	The content is up-to-date, authoritative and trustworthy	2.0	Issue	medium	host_supplied-1	Breadcrumb uses '>' ASCII character instead of semantic separator.
h04_d_13	The site contains third-party support, such as citations or testimonials, to verify the accuracy of information	3.0	Major	high	host_supplied-1	Terminology consistent — 'Lessons', 'Goals', 'Progress' used throughout.
h04_d_14	It is clear that there is a real organization behind the site, such as a physical address or office photo	2.0	Issue	high	host_supplied-1	No Sign Up CTA in nav; Sign In is the only auth entry point; new users must infer.
h04_d_15	The content is fresh: the site includes recent content	2.0	Issue	high	host_supplied-1	H4 used for tab controls creates false visual hierarchy.
h04_d_16	The site is free of typographic errors and spelling mistakes	2.0	Issue	medium	host_supplied-1	Active tab not clearly differentiated in accessibility tree.
h04_d_17	The visual design is consistent, including colors, layout, iconography, etc.	3.0	Major	high	host_supplied-1	Oppia logo and brand colors present throughout; footer includes mission.
h04_d_18	On content pages, line lengths are neither too short (under 50 characters per line) nor too long (over 100 characters per line) when viewed in a standard browser width window	3.0	Major	medium	host_supplied-1	Language selector present in nav; multiple languages supported.
h04_d_19	Fonts are used consistently and are legible	3.0	Major	medium	host_supplied-1	No jarring animations or motion observed; loading state is simple text.
h04_d_20	The site can be used without scrolling horizontally	2.0	Issue	low	host_supplied-1	Touch target sizes not verified; mobile not tested in this session.
h04_d_21	Design components, such as radio buttons and checkboxes, are used appropriately	2.0	Issue	medium	host_supplied-1	Focus states not directly observable; H4 misuse likely affects keyboard navigation.

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h05_d_01	Pages are free of scroll stoppers: headings or page elements that create the illusion that users have reached the top or bottom of a page when they have not	3.0	Major	high	host_supplied-1	OAuth reduces password reuse risk; no destructive actions available at account creation.
h05_d_02	The user does not need to consult user manuals or other external information to use the site	3.0	Major	high	host_supplied-1	No irreversible actions at account creation stage.
h05_d_03	User confirmation is required before carrying out potentially dangerous actions, such as deleting something	3.0	Major	high	host_supplied-1	No user input forms at this stage that could generate errors.
h05_d_04	The site provides feedback that helps the user learn how to use the site	3.0	Major	medium	host_supplied-1	Dashboard defaults to Home tab; category sections have sensible defaults.
h05_d_05	There is sufficient space between targets to prevent the user from hitting multiple or incorrect targets	1.0	Issue	high	host_supplied-1	No warning shown that Google account is required before initiating sign-up flow — users without Google accounts hit a dead end.

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h06_d_01	Search suggestions or filters are provided	2.0	Issue	high	host_supplied-1	Dashboard tabs are visible but not labeled as tabs — no affordance for tab interaction.
h06_d_02	Each page is clearly labeled with a descriptive and useful title that makes sense as a bookmark	2.0	Issue	medium	host_supplied-1	Breadcrumb provides minimal context; new user cannot know where they are in the site.
h06_d_03	Links and link titles are descriptive and predictive, and there are no Click here links	2.0	Issue	high	host_supplied-1	'Setting a goal!' link styled as body text — low affordance; hard to identify as interactive.
h06_d_04	Buttons and links show that they have been clicked	2.0	Issue	high	host_supplied-1	New user must remember that 'Sign In' is also 'Sign Up'; dashboard state not explained.

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h07_d_01	Useful content is presented on the home page or within one click of the home page	1.0	Issue	medium	host_supplied-1	No keyboard shortcuts observed on dashboard or in auth flow.
h07_d_02	The terms used for navigation items and hypertext links are unambiguous and jargon-free	2.0	Issue	medium	host_supplied-1	Greeting 'Good Morning, jkhobson1!' is personalized; category topics available.
h07_d_03	If there are product pages, they contain the detail necessary to make a purchase, and users can zoom in on product images	2.0	Issue	low	host_supplied-1	No bulk actions applicable at this stage.
h07_d_04	The words, phrases and concepts used will be familiar to the typical user	1.0	Issue	high	host_supplied-1	No 'continue where you left off' widget — confirmed unresolved bug; progress not persisted.
h07_d_05	Content feels friendly for new users	1.0	Issue	high	host_supplied-1	No search functionality on the dashboard — users must browse categories.
h07_d_06	Content feels customizable or useable for frequent or expert users	2.0	Issue	medium	host_supplied-1	OAuth flow adds multi-step friction; redirect chain is longer than necessary.
h07_d_07	The screen density is appropriate for the target users and their tasks	1.0	Issue	high	host_supplied-1	No adaptive UI behaviors — same content shown for new and returning users.
h07_d_08	Icons and graphics are standard and/or intuitive (concrete and familiar)	2.0	Issue	low	host_supplied-1	No expert or power-user modes at dashboard level.
h07_d_09	Where tooltips are used, they provide useful additional help and do not simply duplicate text in the icon, link or field label	1.0	Issue	high	host_supplied-1	No cross-device continuation; progress persistence bug means no resumable sessions.

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h08_d_01	By just looking at the home page, the first time user will understand where to start	3.0	Major	medium	host_supplied-1	Dashboard is clean and visually simple; good use of white space around card grid.
h08_d_02	Primary actions are easy to find and understand	3.0	Major	medium	host_supplied-1	Information density is appropriate — lesson cards with counts and thumbnails.
h08_d_03	Individual pages are free of clutter and irrelevant information, and attention-attracting features are used sparingly and only where relevant	3.0	Major	medium	host_supplied-1	Adequate white space between sections; category cards well-spaced.
h08_d_04	The home page is professionally designed and will create a positive first impression	3.0	Major	medium	host_supplied-1	Color palette appears harmonious; brand colors consistently applied.
h08_d_05	The home page looks like a home page; pages lower in the site will not be confused with it	2.0	Issue	high	host_supplied-1	Typography hierarchy undermined by H4 misuse for tab labels.
h08_d_06	The site avoids advertisements, especially pop-ups	3.0	Major	medium	host_supplied-1	Image quality appears good; lesson card thumbnails and avatar visible.
h08_d_07	Text is concise, with no needless instructions or welcome notes	3.0	Major	medium	host_supplied-1	No jarring animations; transitions appear smooth.
h08_d_08	Pages use bulleted and numbered lists in preference to narrative text	1.0	Issue	high	host_supplied-1	Loading state is blank/text-only with no skeleton UI — 5+ second blank screen for new users.
h08_d_09	The most important items in a list are placed at the top	2.0	Issue	low	host_supplied-1	Mobile layout not directly tested; desktop layout is well-structured.
h08_d_10	Pages are quick to scan, with ample headings and subheadings and short paragraphs	2.0	Issue	low	host_supplied-1	Color contrast not directly testable from accessibility snapshots.
h08_d_11	Information is organized hierarchically, from the general to the specific, and the organization is clear and logical	2.0	Issue	low	host_supplied-1	Responsive design not directly tested in this session.
h08_d_12	Text links are long enough to be understood, but short enough to minimize wrapping, especially when used as a navigation list	2.0	Issue	low	host_supplied-1	Limited hover/focus states visible in accessibility snapshot.
h08_d_13	On all pages, the most important information, such as frequently used topics, features and functions, is presented on the first screenful of information above the fold	3.0	Major	high	host_supplied-1	Oppia logo, brand colors, and mission statement present throughout.
h08_d_14	The relationship between controls and their actions is obvious	3.0	Major	high	host_supplied-1	Professional, clean first impression on dashboard; category cards inviting.
h08_d_15	There is a clear visual starting point to every page	2.0	Issue	low	host_supplied-1	Dark mode not observed or tested.
h08_d_16	The site is pleasant to look at	2.0	Issue	low	host_supplied-1	Print view not applicable or tested at this stage.

Item	Checklist text	Score	Status	Confidence	Severity basis	Evidence	Rationale
h09_d_01	The site uses a customised 404 page, which includes tips on how to find the missing page and links to Home and Search	2.0	Issue	medium		host_supplied-1	OAuth errors shown by Google (external); Oppia does not provide contextual auth error help.
h09_d_02	Error messages contain clear instructions on what to do next, including form error states	1.0	Issue	high		host_supplied-1	Two silent JS console errors with no recovery path; users unaware anything is wrong.

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h10_d_01	Help is available and easy to find	1.0	Issue	high	host_supplied-1	No contextual help visible anywhere on the dashboard for new users.
h10_d_02	FAQs are present if appropriate	1.0	Issue	high	host_supplied-1	No help center, FAQ, or search accessible from the dashboard.
h10_d_03	When giving instructions, pages tell users what to do rather than what to avoid doing	1.0	Issue	high	host_supplied-1	No onboarding modal, welcome sequence, or guided tour for first-time users.
h10_d_04	The site shows users how to do common tasks where appropriate, such as demonstrations of the site's functionality	2.0	Issue	low	host_supplied-1	Tooltips may exist on some elements but none observed in this session.
h10_d_05	It is easy to contact someone for assistance and a reply is received quickly	2.0	Issue	medium	host_supplied-1	OAuth error guidance provided by Google; Oppia-specific auth help unavailable.

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h11_d_01	P - Content alternatives are provided, content is adaptable, and content is easy to hear and see	2.0	Issue	high	host_supplied-1	H4 used as tab controls violates ARIA tab pattern. Dashboard may lack accessible names for sections. Progress ring unlabeled. Cookie consent banner may lack accessible label. SPA title bug creates screen reader confusion.
h11_d_02	O - All functionality is available and flexible, enough time is provided, content is safe, and content is easy to find	1.0	Issue	medium	host_supplied-1	Keyboard navigation possible via standard browser; no focus traps observed. Cookie consent dismissible via keyboard. Tab order not fully verified.
h11_d_03	U - Content text is readable and understandable, content appears and operates in predictable ways, and users are helped to avoid and correct mistakes	1.0	Issue	high	host_supplied-1	Language is clear and simple. SPA title bug creates momentary confusion. 'Sign In' covering Sign Up reduces understandability for first-time users.
h11_d_04	R - Compatibility is maximized for current and future user agents	2.0	Issue	high	host_supplied-1	H4 elements used as tab controls are not robust across AT. Custom interactive elements without proper ARIA roles undermine robustness. 2 silent JS errors may affect AT compatibility.

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h12_d_01	The interface acknowledges and responds to user emotions, either through design, content, or interactive elements	1.0	Issue	medium	host_supplied-1	Sign-up experience is emotionally neutral. Missing welcome/onboarding moment is a minor emotional gap for new learners.
h12_d_02	The design ensures users feel safe and secure, minimizing anxiety-inducing elements	2.0	Issue	high	host_supplied-1	Google-only auth creates safety/access concern for users on shared devices, restricted networks, or in regions where Google is blocked (including parts of Oppia's target population in under-resourced communities).
h12_d_03	The content and design elements respect and reflect a wide range of cultural norms and values	2.0	Issue	high	host_supplied-1	Google-only authentication excludes learners in Google-restricted regions (China, some corporate/school networks). Oppia serves global learners; this is a meaningful access gap.
h12_d_04	Information is presented in a way that shows understanding and consideration for the user's emotional state	1.0	Issue	medium	host_supplied-1	Dashboard greeting is personalized. No welcome sequence showing understanding of first-time learner anxiety or excitement.
h12_d_05	Design and content are accessible to users with various physical and cognitive abilities, promoting inclusivity	2.0	Issue	high	host_supplied-1	H4 misuse, custom elements, ARIA concerns affect users with assistive technology. Same as H11 concerns.
h12_d_06	Features and functionalities empower users, giving them control and choice in their interactions	1.0	Issue	medium	host_supplied-1	User can sign in and out; basic session control available. No additional empowerment features at sign-up stage.

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h13_d_01	The interface reflects the brand's values and aesthetics consistently across all elements	1.0	Issue	high	host_supplied-1	Oppia brand and mission ('For free, for everyone, forever') is consistent throughout the sign-up journey.
h13_d_02	Navigation and workflows are intuitive, creating a seamless experience from start to finish	2.0	Issue	high	host_supplied-1	OAuth redirect breaks Oppia context — user leaves Oppia for Google, then returns. No seamless embedded auth. This creates a jarring journey break.
h13_d_03	The system offers personalized options or content based on user data and preferences	1.0	Issue	medium	host_supplied-1	Dashboard greeting with username is personalized. Limited additional personalization at sign-up stage.
h13_d_04	Easy access to support and a straightforward method for users to provide feedback	2.0	Issue	high	host_supplied-1	No help channel for sign-up failures within Oppia. Google-level errors not explained by Oppia context.
h13_d_05	Features or elements make the user feel valued and rewarded for their engagement	2.0	Issue	high	host_supplied-1	No welcome celebration or onboarding sequence for first-time account creation. Users land on the dashboard without any sense of milestone or accomplishment.
h13_d_06	Clear communication about data usage, privacy policies, and other aspects that build user trust	2.0	Issue	high	host_supplied-1	No privacy statement or data use explanation shown during or after OAuth. Users not informed what data Oppia collects via Google.

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h14_d_01	Follows the current product's established style guide and brand voice	1.0	Issue	medium	host_supplied-1	Interface mostly follows Oppia style guide. Minor inconsistencies in interactive element labeling.
h14_d_02	Content is clear	1.0	Issue	medium	host_supplied-1	Dashboard content is generally clear. 'Setting a goal!' inline link is ambiguous.
h14_d_03	Content avoids jargon and uses simple, everyday language	1.0	Issue	high	host_supplied-1	'Sign In' covering Sign Up is a UX writing gap. Dashboard labels are otherwise learner-appropriate.
h14_d_04	All UI labels use simple and concise words	2.0	Issue	high	host_supplied-1	'Sign In with Google' does not clarify account creation. 'User Menu' label may not match expectation. 'Setting a goal!' styled as link is ambiguous.
h14_d_05	Calls to action are specific, use active language, and are clearly organized by importance	2.0	Issue	high	host_supplied-1	No explicit Sign Up CTA. 'Sign In with Google' covers both but doesn't tell new users they can create an account this way.
h14_d_06	No paragraphs more than three lines	0.0	Passed	medium	host_supplied-1	Dashboard content is concise; no paragraphs over three lines observed.
h14_d_07	The content above the fold, including headings, subheadings, and copy, makes each page's purpose clear and obvious	2.0	Issue	high	host_supplied-1	Important auth content competes with category clutter above the fold. SPA loading blank screen occupies the above-fold area for 5+ seconds.

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h01_d_01	Every interface begins with a title/header that describes page contents	2.0	Issue	high	host_supplied-1	Active tab state reflected correctly; no toast on goal addition — user must notice goal card appeared
h01_d_02	Headings and subheadings are short, straightforward and descriptive	3.0	Major	high	host_supplied-1	Goal appears immediately in Current Goals after toggle — good real-time feedback without page reload
h01_d_03	Value proposition is clearly stated on the home page (tagline or welcome blurb)	2.0	Issue	high	host_supplied-1	'0% Complete' shown immediately on new goal card — partial progress visibility
h01_d_04	The items on the home page are clearly focused on primary actions	3.0	Major	high	host_supplied-1	Goal state changes are instant and reflected in UI without reload
h01_d_05	Each page is clearly branded so that the user knows they are on the same site	2.0	Issue	medium	host_supplied-1	Silent errors if goal operations fail — no error state shown to user
h01_d_06	Navigation makes it clear which page I am on	2.0	Issue	medium	host_supplied-1	No specific error messaging for goal limit reached or removal failures
h01_d_07	Link names match the title of destination pages, so users will know when they have reached the intended page	2.0	Issue	low	host_supplied-1	No forms on goals screen — rated neutral
h01_d_08	Standard elements (page titles, site navigation, page navigation, privacy policy, etc.) are easy to locate	3.0	Major	high	host_supplied-1	Goals tab shows [active] state in accessibility tree when selected
h01_d_09	Logo is in a consistent location, and clicking the logo returns the user back to the home page	2.0	Issue	high	host_supplied-1	Progress ring on goal card is unlabeled — no accessible real-time status for screen readers

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h02_d_01	Navigation tabs are located at the top of the page, and look like clickable versions of real-world tabs	3.0	Major	high	host_supplied-1	'Learn Money', 'Complete a chapter in Money' — plain, learner-appropriate language
h02_d_02	Items that are not clickable do not have characteristics that suggest that they are clickable	3.0	Major	high	host_supplied-1	Goal setting mental model (select topic, track progress) maps well to real-world learning
h02_d_03	Items that are clickable look like they are clickable	3.0	Major	high	host_supplied-1	Progress ring and percentage are familiar goal-tracking metaphors

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h03_d_01	There is a search box	1.0	Issue	high	host_supplied-1	No undo after goal removal — accidental remove is permanent with no recovery
h03_d_02	There are clearly marked exits on every page allowing the user to bail out of the current task without having to depend on the browser Back button	3.0	Major	medium	host_supplied-1	Remove option available via More options dropdown — user can exit a goal
h03_d_03	The site does not disable the browser Back button and the Back button appears on the browser toolbar on every page	2.0	Issue	high	host_supplied-1	Remove requires navigating hidden dropdown — not immediately obvious
h03_d_04	Clicking the back button always takes the user back to the page they came from	3.0	Major	high	host_supplied-1	Goal addition is user-initiated via toggle; no forced goal assignments
h03_d_05	Undo and redo are supported	2.0	Issue	high	host_supplied-1	No confirmation before removal; accidental removal cannot be undone

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h04_d_01	In your expert opinion, site content does not look like advertisements	2.0	Issue	high	host_supplied-1	More options uses div-as-button inconsistent with native button elements used elsewhere
h04_d_02	Clickable elements use a consistent style/color for primary, secondary, and tertiary actions	1.0	Issue	high	host_supplied-1	div[role=button] for More options and bare div for Remove violate HTML5 interactive element standards
h04_d_03	Value proposition is clearly stated on the home page (tagline or welcome blurb)	2.0	Issue	high	host_supplied-1	Remove action hidden inside dropdown — low affordance and discoverability
h04_d_04	Navigation choices are ordered in the most logical or task-oriented manner, with less important corporate information at the bottom	3.0	Major	medium	host_supplied-1	Color palette consistent throughout goals view
h04_d_05	All corporate information is grouped in one distinct area, such as About Us	3.0	Major	medium	host_supplied-1	Typography consistent with rest of dashboard
h04_d_06	The home page of the site has a memorable URL	2.0	Issue	high	host_supplied-1	'paw image' used as column header icon — decorative, not functional label
h04_d_07	Terminology is consistent with general web usage	3.0	Major	medium	host_supplied-1	Goal list structure consistent with lesson catalog structure
h04_d_08	There is a visible change when the mouse points at something clickable, excluding cursor changes	3.0	Major	low	host_supplied-1	No form fields on goals screen
h04_d_09	Hypertext links that invoke actions, such as downloads or new windows, are clearly distinguished from hypertext links that load another page	2.0	Issue	medium	host_supplied-1	No error styling observed for goal operations
h04_d_10	If the site spawns new windows, these will not confuse the user and can be easily closed	3.0	Major	medium	host_supplied-1	Spacing and layout consistent
h04_d_11	Menu instructions, prompts and messages appear in the same place on each screen	1.0	Issue	high	host_supplied-1	Goal toggle controls are custom div elements — not styled or behaving as standard checkboxes
h04_d_12	The content is up-to-date, authoritative and trustworthy	2.0	Issue	high	host_supplied-1	Breadcrumb still uses > ASCII separator
h04_d_13	The site contains third-party support, such as citations or testimonials, to verify the accuracy of information	3.0	Major	high	host_supplied-1	Consistent terminology: Goals, Topics, Lessons throughout
h04_d_14	It is clear that there is a real organization behind the site, such as a physical address or office photo	2.0	Issue	high	host_supplied-1	No explicit 'Add Goal' CTA — requires toggle discovery in Edit Goals list
h04_d_15	The content is fresh: the site includes recent content	2.0	Issue	high	host_supplied-1	20-topic flat list has no visual hierarchy by subject area
h04_d_16	The site is free of typographic errors and spelling mistakes	2.0	Issue	high	host_supplied-1	Selected/unselected goal state in Edit Goals list not clearly communicated visually
h04_d_17	The visual design is consistent, including colors, layout, iconography, etc.	3.0	Major	high	host_supplied-1	Brand elements consistent
h04_d_18	On content pages, line lengths are neither too short (under 50 characters per line) nor too long (over 100 characters per line) when viewed in a standard browser width window	3.0	Major	high	host_supplied-1	Language selector present
h04_d_19	Fonts are used consistently and are legible	3.0	Major	medium	host_supplied-1	No jarring animations
h04_d_20	The site can be used without scrolling horizontally	2.0	Issue	low	host_supplied-1	Touch targets on custom div toggles likely small — not verified on mobile
h04_d_21	Design components, such as radio buttons and checkboxes, are used appropriately	1.0	Issue	high	host_supplied-1	Focus states on div-as-button elements uncertain — keyboard nav likely broken

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h05_d_01	Pages are free of scroll stoppers: headings or page elements that create the illusion that users have reached the top or bottom of a page when they have not	3.0	Major	high	host_supplied-1	'Limit of 5 goals' shown proactively before limit is reached
h05_d_02	The user does not need to consult user manuals or other external information to use the site	2.0	Issue	high	host_supplied-1	No confirmation dialog before goal removal — accidental removal is immediate
h05_d_03	User confirmation is required before carrying out potentially dangerous actions, such as deleting something	3.0	Major	medium	host_supplied-1	No form validation needed on goals screen
h05_d_04	The site provides feedback that helps the user learn how to use the site	3.0	Major	high	host_supplied-1	Sensible defaults — empty state message guides user toward adding goals
h05_d_05	There is sufficient space between targets to prevent the user from hitting multiple or incorrect targets	3.0	Major	high	host_supplied-1	Limit of 5 goals communicated before user hits the limit

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h06_d_01	Search suggestions or filters are provided	2.0	Issue	high	host_supplied-1	Edit Goals list shows topics but toggle state (selected vs unselected) is visually unclear
h06_d_02	Each page is clearly labeled with a descriptive and useful title that makes sense as a bookmark	2.0	Issue	high	host_supplied-1	No indication in Edit Goals list which topics are currently active goals
h06_d_03	Links and link titles are descriptive and predictive, and there are no Click here links	1.0	Issue	high	host_supplied-1	More options dropdown is hidden — no visual affordance that Remove exists until hover/click
h06_d_04	Buttons and links show that they have been clicked	2.0	Issue	high	host_supplied-1	User must remember that toggle = add goal; no persistent visible affordance

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h07_d_01	Useful content is presented on the home page or within one click of the home page	1.0	Issue	medium	host_supplied-1	No keyboard shortcuts for goal management
h07_d_02	The terms used for navigation items and hypertext links are unambiguous and jargon-free	2.0	Issue	medium	host_supplied-1	Goals are personalized to user selections; but no recommendations based on user level
h07_d_03	If there are product pages, they contain the detail necessary to make a purchase, and users can zoom in on product images	1.0	Issue	high	host_supplied-1	No bulk goal selection or management
h07_d_04	The words, phrases and concepts used will be familiar to the typical user	2.0	Issue	high	host_supplied-1	Current goal card shows direct link to first lesson — partial continuity support
h07_d_05	Content feels friendly for new users	1.0	Issue	high	host_supplied-1	No search or filter on 20-topic goal list — requires full scroll to browse
h07_d_06	Content feels customizable or useable for frequent or expert users	2.0	Issue	medium	host_supplied-1	Goal addition is fast but requires discovery of toggle mechanism
h07_d_07	The screen density is appropriate for the target users and their tasks	1.0	Issue	high	host_supplied-1	No adaptive filtering (e.g., hide completed topics, surface recommended topics)
h07_d_08	Icons and graphics are standard and/or intuitive (concrete and familiar)	2.0	Issue	low	host_supplied-1	No advanced goal management features
h07_d_09	Where tooltips are used, they provide useful additional help and do not simply duplicate text in the icon, link or field label	2.0	Issue	medium	host_supplied-1	Goal state reflects added goals — persistence needs verification given known progress bug

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h08_d_01	By just looking at the home page, the first time user will understand where to start	2.0	Issue	high	host_supplied-1	20-topic flat list without grouping is verbose and cognitively demanding
h08_d_02	Primary actions are easy to find and understand	2.0	Issue	high	host_supplied-1	Information density is high in the flat goal list — 20 items before scrolling
h08_d_03	Individual pages are free of clutter and irrelevant information, and attention-attracting features are used sparingly and only where relevant	3.0	Major	medium	host_supplied-1	Adequate whitespace between goal cards and list items
h08_d_04	The home page is professionally designed and will create a positive first impression	3.0	Major	medium	host_supplied-1	Color palette harmonious
h08_d_05	The home page looks like a home page; pages lower in the site will not be confused with it	2.0	Issue	high	host_supplied-1	H4 used for tab controls — visual hierarchy issue persists from LI.1
h08_d_06	The site avoids advertisements, especially pop-ups	3.0	Major	medium	host_supplied-1	Image quality adequate — paw icon and subject imagery visible
h08_d_07	Text is concise, with no needless instructions or welcome notes	3.0	Major	high	host_supplied-1	No jarring animations on goal toggle
h08_d_08	Pages use bulleted and numbered lists in preference to narrative text	2.0	Issue	high	host_supplied-1	Loading state on dashboard still shows blank/text-only
h08_d_09	The most important items in a list are placed at the top	2.0	Issue	low	host_supplied-1	Mobile not tested
h08_d_10	Pages are quick to scan, with ample headings and subheadings and short paragraphs	2.0	Issue	low	host_supplied-1	Contrast not directly testable
h08_d_11	Information is organized hierarchically, from the general to the specific, and the organization is clear and logical	2.0	Issue	low	host_supplied-1	Responsive not tested
h08_d_12	Text links are long enough to be understood, but short enough to minimize wrapping, especially when used as a navigation list	2.0	Issue	high	host_supplied-1	Toggle state change feedback limited to DOM update — no animation or explicit confirmation
h08_d_13	On all pages, the most important information, such as frequently used topics, features and functions, is presented on the first screenful of information above the fold	3.0	Major	high	host_supplied-1	Brand consistent
h08_d_14	The relationship between controls and their actions is obvious	3.0	Major	high	host_supplied-1	Goal card design is clean and inviting
h08_d_15	There is a clear visual starting point to every page	2.0	Issue	low	host_supplied-1	Dark mode not tested
h08_d_16	The site is pleasant to look at	2.0	Issue	low	host_supplied-1	Print not applicable

Item	Checklist text	Score	Status	Confidence	Severity basis	Evidence	Rationale
h09_d_01	The site uses a customised 404 page, which includes tips on how to find the missing page and links to Home and Search	2.0	Issue	medium		host_supplied-1	No goal operation error messages observed
h09_d_02	Error messages contain clear instructions on what to do next, including form error states	1.0	Issue	high		host_supplied-1	No undo or recovery after accidental goal removal

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h10_d_01	Help is available and easy to find	2.0	Issue	high	host_supplied-1	'Start learning by selecting a goal from below!' provides minimal guidance
h10_d_02	FAQs are present if appropriate	1.0	Issue	high	host_supplied-1	No help center or FAQ for goal management accessible from this view
h10_d_03	When giving instructions, pages tell users what to do rather than what to avoid doing	2.0	Issue	high	host_supplied-1	Minimal onboarding for goal system — no explanation of why to set goals or how limit of 5 was chosen
h10_d_04	The site shows users how to do common tasks where appropriate, such as demonstrations of the site's functionality	2.0	Issue	medium	host_supplied-1	No tooltips observed on goal list items or progress rings
h10_d_05	It is easy to contact someone for assistance and a reply is received quickly	2.0	Issue	low	host_supplied-1	No documentation for error states in goal management

Item	Score	Status	Confidence	Evidence	Rationale
h11_d_01	1.0	Issue	medium	host_supplied-1	Goals section text readable; adequate contrast
h11_d_02	2.0	Issue	high	host_supplied-1	Div-as-button breaks keyboard operability for goal toggles
h11_d_03	1.0	Issue	medium	host_supplied-1	Goal labels understandable; pinned state not labeled for screen readers
h11_d_04	2.0	Issue	low	host_supplied-1	Angular SPA may not expose semantic roles to assistive technology

Item	Score	Status	Confidence	Evidence	Rationale
h12_d_01	0.0	Passed	high	host_supplied-1	Language neutral and inclusive; no exclusionary terminology
h12_d_02	0.0	Passed	high	host_supplied-1	No stereotypes or biased assumptions in goal-setting UI
h12_d_03	2.0	Issue	high	host_supplied-1	Div-as-button impacts keyboard-only and screen reader users
h12_d_04	1.0	Issue	low	host_supplied-1	Goals section culturally neutral; minor date formatting consideration
h12_d_05	2.0	Issue	high	host_supplied-1	Non-semantic div elements for goal toggles fail accessible interaction requirements
h12_d_06	1.0	Issue	medium	host_supplied-1	Users can toggle goals; discoverability limited but some agency present

Item	Score	Status	Confidence	Evidence	Rationale
h13_d_01	1.0	Issue	medium	host_supplied-1	Dashboard entry visible; goals section findable but not prominently surfaced
h13_d_02	2.0	Issue	high	host_supplied-1	Goal toggle discovery poor; users not guided to management actions
h13_d_03	2.0	Issue	high	host_supplied-1	No meaningful confirmation shown after goal toggle; system change uncommunicated
h13_d_04	2.0	Issue	high	host_supplied-1	No tooltips or onboarding at goal-setting moments; learner left without guidance
h13_d_05	2.0	Issue	medium	host_supplied-1	Silent goal toggle failures leave no recovery path; success unverifiable
h13_d_06	2.0	Issue	medium	host_supplied-1	Setting a goal has no reward moment or motivational response

Item	Score	Status	Confidence	Evidence	Rationale
h14_d_01	1.0	Issue	medium	host_supplied-1	Action labels generally clear; minor gaps in toggle state labels
h14_d_02	1.0	Issue	medium	host_supplied-1	Little microcopy for goal management; sparse but not misleading
h14_d_03	0.0	Passed	high	host_supplied-1	No jargon in goal-setting UI; plain language throughout
h14_d_04	1.0	Issue	high	host_supplied-1	More options CTA vague; does not clearly indicate available goal actions
h14_d_05	1.0	Issue	low	host_supplied-1	Limited evidence for error message quality; assumed cosmetic issues
h14_d_06	2.0	Issue	medium	host_supplied-1	Empty state copy insufficient; no guidance when no goals are set
h14_d_07	1.0	Issue	medium	host_supplied-1	Terminology generally consistent throughout goal-setting flow

Mission Context

Severity ratings reflect the supplied evidence, user goal, optional-profile scope, and any stated evidence limits. Support flows and activities should never outrank the checklist scorecard.

C+

62.73%

Developing - significant gaps

Plain Language Read

The biggest visible usability risk is important information may appear too late. It affects Aesthetic and Minimalist Design and should be fixed before broader polish.

Next Research Recommendation

Fix severity 3-4 checklist items first, then rerun the same source state for comparison.

Accessibility Readiness Signal

Accessibility Readiness Signal: WCAG AAA-level criteria are implicated by Inconsistent interface patterns may slow users; this remains evidence-limited until manual accessibility testing.

Cultural Context Signal

Cultural Context Signal: CJK Layout And Typography Requirements flags Consistency and trust cues need review as needing evidence-bound local or community-context validation.

Before using this interface, address Aesthetic and Minimalist Design first: Move the task-critical information above the fold and defer supporting details until after the first decision.

Major Finding - Immediate Attention

Important information may appear too late

Brand consistent in lesson player

Heuristic Scorecard - AI Audit, 14 Heuristics

A-

80.56% - avg severity 0.78

Visibility of System Status

Above average - minor gaps

41.67% - avg severity 2.33

Match Between System and the Real World

Poor - major usability problems

55.0% - avg severity 1.8

User Control and Freedom

Needs attention - failing in places

46.43% - avg severity 2.14

Consistency and Standards

Poor - major usability problems

55.0% - avg severity 1.8

Error Prevention

Needs attention - failing in places

A-

81.25% - avg severity 0.75

Recognition Rather Than Recall

Above average - minor gaps

B+

75.0% - avg severity 1.0

Flexibility and Efficiency of Use

Good - a few notable issues

D-

39.06% - avg severity 2.44

Aesthetic and Minimalist Design

Critical - severe experience failures

87.5% - avg severity 0.5

Help Users Recognize, Diagnose, and Recover from Errors

Strong - meets standard

70.0% - avg severity 1.2

Help and Documentation

Acceptable - some improvement needed

B-

68.75% - avg severity 1.25

Accessibility and Ease of Access

Below average - multiple issues

B+

79.17% - avg severity 0.8333333333333334

Empathetic Engagement and Inclusion

Above average - minor gaps

41.67% - avg severity 2.3333333333333335

Customer Journey and Satisfaction

Poor - major usability problems

57.14% - avg severity 1.7142857142857142

UX Writing / Content and Tone

Needs attention - failing in places

Findings - Prioritized Fix Order

Major Aesthetic and Minimalist Design - h08_d_13

Important information may appear too late

Observed Issue

Brand consistent in lesson player

Recommendation

Move the task-critical information above the fold and defer supporting details until after the first decision.

This checklist item indicates measurable heuristic friction for the evaluated surface.

Supporting lenses: Inverted Pyramid, Visual Hierarchy

Evidence: h08_d_13 - Confidence: high

Major Aesthetic and Minimalist Design - h08_d_03

Page clutter competing with primary actions

Observed Issue

Good whitespace in lesson player

Recommendation

Audit the screen for competing visual elements and remove or demote anything that does not support the user's next action.

This checklist item indicates measurable heuristic friction for the evaluated surface.

Supporting lenses: Choice Overload, Hick-Hyman Law

Evidence: h08_d_03 - Confidence: high

Major Aesthetic and Minimalist Design - h08_d_01

Primary action hierarchy is not clear

Observed Issue

Lesson player is clean and visually focused; narrative content is well-presented

Recommendation

Make the primary action the clearest visual starting point and reduce secondary actions around it.

This checklist item indicates measurable heuristic friction for the evaluated surface.

Supporting lenses: Visual Hierarchy, Fitts's Law

Evidence: h08_d_01 - Confidence: high

Major Aesthetic and Minimalist Design - h08_d_02

Primary action hierarchy is not clear

Observed Issue

Lesson cards show content progressively — good information density

Recommendation

Make the primary action the clearest visual starting point and reduce secondary actions around it.

This checklist item indicates measurable heuristic friction for the evaluated surface.

Supporting lenses: Visual Hierarchy, Fitts's Law

Evidence: h08_d_02 - Confidence: high

Major Aesthetic and Minimalist Design - h08_d_04

Visual hierarchy is not supporting the task

Observed Issue

Color palette harmonious in lesson player

Recommendation

Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.

This checklist item indicates measurable heuristic friction for the evaluated surface.

Supporting lenses: ISO 9241-125 Visual Presentation Of Information, Law of Similarity

Evidence: h08_d_04 - Confidence: medium

Major Aesthetic and Minimalist Design - h08_d_06

Visual hierarchy is not supporting the task

Observed Issue

Lesson images well-rendered with descriptive alt text

Recommendation

Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.

This checklist item indicates measurable heuristic friction for the evaluated surface.

Supporting lenses: ISO 9241-125 Visual Presentation Of Information, Visual Hierarchy

Evidence: h08_d_06 - Confidence: high

Major Aesthetic and Minimalist Design - h08_d_07

Visual hierarchy is not supporting the task

Observed Issue

No jarring animations in lesson player

Recommendation

Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.

This checklist item indicates measurable heuristic friction for the evaluated surface.

Supporting lenses: Cognitive Load, ISO 9241-125 Visual Presentation Of Information

Evidence: h08_d_07 - Confidence: high

Major Aesthetic and Minimalist Design - h08_d_14

Visual hierarchy is not supporting the task

Observed Issue

Lesson player first impression is clean and engaging

Recommendation

Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.

This checklist item indicates measurable heuristic friction for the evaluated surface.

Supporting lenses: Law of Proximity, Affordance and Signifiers

Evidence: h08_d_14 - Confidence: high

Major Consistency and Standards - h04_d_04

Consistency and trust cues need review

Observed Issue

Color palette consistent throughout lesson player

Recommendation

Audit repeated navigation, labels, components, and trust cues, then align any pattern that changes meaning across screens.

This checklist item indicates measurable heuristic friction for the evaluated surface.

Supporting lenses: Shneiderman's Eight Golden Rules, CJK Layout And Typography Requirements

Evidence: h04_d_04 - Confidence: medium

Major Consistency and Standards - h04_d_05

Consistency and trust cues need review

Observed Issue

Typography consistent; lesson narrative is well-formatted

Recommendation

Audit repeated navigation, labels, components, and trust cues, then align any pattern that changes meaning across screens.

This checklist item indicates measurable heuristic friction for the evaluated surface.

Supporting lenses: Law of Common Region, Shneiderman's Eight Golden Rules

Evidence: h04_d_05 - Confidence: medium

Owner-Role Triage Matrix

Owner	Linked finding	Next action	Impact	Effort	Confidence
Designer	h08 / h08_d_13	Move the task-critical information above the fold and defer supporting details until after the first decision.	high	Low	high
Designer	h08 / h08_d_03	Audit the screen for competing visual elements and remove or demote anything that does not support the user's next action.	high	Low	high
Designer	h08 / h08_d_01	Make the primary action the clearest visual starting point and reduce secondary actions around it.	high	Low	high
Designer	h08 / h08_d_02	Make the primary action the clearest visual starting point and reduce secondary actions around it.	high	Low	high
Designer	h08 / h08_d_04	Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.	high	Low	medium
Designer	h08 / h08_d_06	Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.	high	Low	high
Designer	h08 / h08_d_07	Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.	high	Low	high
Designer	h08 / h08_d_14	Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.	high	Low	high
Product	h04 / h04_d_04	Audit repeated navigation, labels, components, and trust cues, then align any pattern that changes meaning across screens.	high	Low	medium
Product	h04 / h04_d_05	Audit repeated navigation, labels, components, and trust cues, then align any pattern that changes meaning across screens.	high	Low	medium

What Is Working Well

Visibility of System Status holds up with A- (80.56%).
Recognition Rather Than Recall holds up with A- (81.25%).
Help Users Recognize, Diagnose, and Recover from Errors holds up with A (87.5%).

Evidence Limits

source: source preparation status was partial (ratings may be incomplete or unavailable)
source: URL entries were recorded without a browser screenshot (visual and interaction-state ratings are limited)
h01_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
77 additional evidence-limit summary row(s) are collapsed below.

Show detailed evidence-limit notes (81 source notes)

source: source preparation status was partial (ratings may be incomplete or unavailable)
source: URL entries were recorded without a browser screenshot (visual and interaction-state ratings are limited)
h01_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_05: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_06: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_07: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_08: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_09: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h02_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h02_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h02_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h03_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h03_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h03_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h03_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h03_d_05: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_05: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_06: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_07: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_08: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_09: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_10: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_11: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_12: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_13: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_14: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_15: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_16: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_17: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_18: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_19: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_20: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_21: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h05_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h05_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h05_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h05_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h05_d_05: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h06_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h06_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h06_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h06_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_05: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_06: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_07: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_08: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_09: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_05: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_06: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_07: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_08: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_09: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_10: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_11: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_12: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_13: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_14: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_15: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_16: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h09_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h09_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h10_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h10_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h10_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h10_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h10_d_05: no evidence reference supplied for checklist rating (rating may be difficult to audit later)

WCAG-Informed Accessibility Readiness

Support-only advisory. This section does not change H01-H14 scores, 0-4 checklist ratings, report readiness, or finding order.

WCAG Level Signal: AAA

Top signal: Accessibility Readiness Signal: WCAG AAA-level criteria are implicated by Inconsistent interface patterns may slow users; this remains evidence-limited until manual accessibility testing.

Caveat: Evidence-limited accessibility support guidance only; not WCAG, ADA, legal, procurement, or conformance certification.

Lens / cue	Applies to	Evidence	Why it matters	Caveat
Contrast And Visual Presentation	h04/h04_d_17	h04_d_17	The finding connects to WCAG contrast and visual-presentation guidance: important information or controls may not be perceivable enough.	UXHC can flag visible contrast risk, but measured contrast ratios and state-by-state review are needed before conformance claims.
Contrast And Visual Presentation	h04/h04_d_19	h04_d_19	The finding connects to WCAG contrast and visual-presentation guidance: important information or controls may not be perceivable enough.	UXHC can flag visible contrast risk, but measured contrast ratios and state-by-state review are needed before conformance claims.
Focus Order, Visibility, And Obscured Focus	h04/h04_d_08	h04_d_08	The finding connects to WCAG focus guidance: keyboard users need a visible, logical focus path that is not hidden by the interface.	UXHC can flag likely focus risk, but keyboard traversal and viewport-state testing are needed before WCAG conformance claims.
Labels, Instructions, And Input Purpose	h02/h02_d_01	h02_d_01	The finding connects to WCAG labels-and-instructions guidance: users need visible and programmatic cues for what controls mean.	UXHC can flag labeling risk, but programmatic label associations and accessible-name checks require technical review; this is not WCAG conformance certification.
Modals, Popovers, Tooltips, And Focus Management	h04/h04_d_10	h04_d_10	The finding connects to accessible overlay guidance: modals and popovers must preserve focus, escape, labels, and context.	UXHC can flag overlay access risk, but keyboard and screen-reader testing are required before WCAG conformance claims.
Accessible Authentication	h05/h05_d_02	h05_d_02	The finding connects to WCAG accessible-authentication guidance: sign-in should not rely on avoidable memory or cognitive tests without alternatives.	UXHC can flag authentication burden, but WCAG evaluation needs the actual auth flow and security constraints; this is not WCAG conformance certification.

Cultural Context Integrity Advisory

Support-only advisory. This section does not change H01-H14 scores, 0-4 checklist ratings, report readiness, or finding order.

Context Integrity Index: 0 - Insufficient Context Safety

Top signal: Cultural Context Signal: CJK Layout And Typography Requirements flags Consistency and trust cues need review as needing evidence-bound local or community-context validation.

Caveat: Evidence-limited support guidance only; not a cultural certification, moral judgment, universal cultural claim, or substitute for affected-community review.

Lens / cue	Applies to	Evidence	Why it matters	Caveat
CJK Layout And Typography Requirements	h04/h04_d_04	h04_d_04	The finding may need CJK layout review because typography, line breaking, punctuation, or annotations could change the user's reading path.	CJK layout quality varies by language context and requires target-language content and rendered typography evidence, not translated strings alone.
CJK Layout And Typography Requirements	h04/h04_d_18	h04_d_18	The finding may need CJK layout review because typography, line breaking, punctuation, or annotations could change the user's reading path.	CJK layout quality varies by language context and requires target-language content and rendered typography evidence, not translated strings alone.
CJK Layout And Typography Requirements	h04/h04_d_19	h04_d_19	The finding may need CJK layout review because typography, line breaking, punctuation, or annotations could change the user's reading path.	CJK layout quality varies by language context and requires target-language content and rendered typography evidence, not translated strings alone.
Local Contexts And Traditional Knowledge Labels	h04/h04_d_13	h04_d_13	The finding may need stronger cultural provenance or permission cues at the point where users view, reuse, or export content.	Labels depend on community-defined protocols; absence of a label in the evidence is not proof that no protocol applies.
Mediated Payment And Trust Recovery	h03/h03_d_04	h03_d_04	The finding may create trust or recovery risk in mediated payment contexts where fees, receipts, agent support, and disputes must be visible.	Financial-service risk depends on local regulation, agent networks, cost, literacy, and trust channels; UXHC cannot validate the business or legal model.
Script Directionality And Mixed-Script Layout	h04/h04_d_18	h04_d_18	The finding may need directionality and mixed-script testing because labels, layout, or data strings could break in RTL or bidi contexts.	Directionality varies by language and context; it needs actual target-language rendering evidence because English screenshots cannot prove RTL readiness.

Recommended Next Validation Steps

Validation Step 1

Fix severity 3-4 checklist items first, then rerun the same source state for comparison.

Supporting UX Laws And Principles

Support-only explanation. These lenses do not create findings, change 0-4 checklist ratings, or certify compliance.

Lens	Source family	Applies to	Why it matters	Caveat / evidence needed
Shneiderman's Eight Golden Rules	UX/UI Support Lens	h04/h04_d_04, h04/h04_d_05, h04/h04_d_13	The finding is also consistent with Shneiderman-style interface review principles. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	The rules are broad and require domain-specific interpretation. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Visual Hierarchy	UX/UI Support Lens	h08/h08_d_13, h08/h08_d_01, h08/h08_d_02	The finding is supported by visual hierarchy: the screen does not make the most important next action visually primary. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Hierarchy needs to match the user's current task, not only stakeholder importance. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Jakob's Law / Familiar Conventions	UX/UI Support Lens	h02/h02_d_01, h04/h04_d_11, h04/h04_d_07	The finding is supported by convention risk: users may bring expectations the interface does not satisfy. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Conventions vary by platform, culture, domain, and user expertise. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
CJK Layout And Typography Requirements	Cultural Context Support	h04/h04_d_04, h04/h04_d_18, h04/h04_d_19	The finding may need CJK layout review because typography, line breaking, punctuation, or annotations could change the user's reading path. Applicability: Use only when interface evidence raises a culturally situated, language, access-context, authority, data-governance, or community-validation issue.	CJK layout quality varies by language context and requires target-language content and rendered typography evidence, not translated strings alone. Evidence needed: Requires local context, affected-community review, language/script evidence, or a clear evidence limit before stronger claims.
ISO 9241-125 Visual Presentation Of Information	ISO UX/UI/HCI Support	h08/h08_d_04, h08/h08_d_06, h08/h08_d_07	The finding aligns with ISO 9241-125 style visual presentation guidance around legibility, grouping, hierarchy, and understandable visual coding. Applicability: Use when the finding benefits from ISO-informed framing around context of use, interaction quality, evidence traceability, process quality, or operational risk.	ISO-informed support reference only; not formal ISO standards compliance, conformance, certification, procurement proof, or legal assurance. Evidence needed: Requires project, process, technical, or audit evidence before standards-strength claims.
Information Scent	UX/UI Support Lens	h06/h06_d_03, h01/h01_d_07, h10/h10_d_01	The finding is supported by information scent: navigation cues do not clearly predict destination value. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Information scent depends on user goals and vocabulary. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.

Support-only context; not a separate score, proof of user behavior, compliance claim, or replacement for the H01-H14 checklist.

Do not use this as a replacement rubric; map it back to the active UXHC checklist item.

Do not make every business priority visually dominant; hierarchy requires tradeoffs.

Do not use convention as a reason to block purposeful innovation; flag learning cost instead.

Support-only context guidance; not cultural certification, community approval, a universal claim about any culture, or a substitute for local/community review.

Prioritized Fix Roadmap

When	Recommended action
Sprint 1	Move the task-critical information above the fold and defer supporting details until after the first decision.
Sprint 1	Audit the screen for competing visual elements and remove or demote anything that does not support the user's next action.
Sprint 1	Make the primary action the clearest visual starting point and reduce secondary actions around it.
Sprint 1	Make the primary action the clearest visual starting point and reduce secondary actions around it.
Sprint 1	Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.
Sprint 1	Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.
Sprint 1	Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.
Sprint 1	Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.
Sprint 1	Audit repeated navigation, labels, components, and trust cues, then align any pattern that changes meaning across screens.
Sprint 1	Audit repeated navigation, labels, components, and trust cues, then align any pattern that changes meaning across screens.
Sprint 1	Audit repeated navigation, labels, components, and trust cues, then align any pattern that changes meaning across screens.
Sprint 1	Audit repeated navigation, labels, components, and trust cues, then align any pattern that changes meaning across screens.

High-Impact / Low-Effort Micro-Solutions

Role	Micro-solution	Linked finding	Why high impact	Estimated effort
Designer	Move the task-critical information above the fold and defer supporting details until after the first decision.	h08 / h08_d_13	This checklist item indicates measurable heuristic friction for the evaluated surface.	Low
Designer	Audit the screen for competing visual elements and remove or demote anything that does not support the user's next action.	h08 / h08_d_03	This checklist item indicates measurable heuristic friction for the evaluated surface.	Low
Designer	Make the primary action the clearest visual starting point and reduce secondary actions around it.	h08 / h08_d_01	This checklist item indicates measurable heuristic friction for the evaluated surface.	Low
Designer	Make the primary action the clearest visual starting point and reduce secondary actions around it.	h08 / h08_d_02	This checklist item indicates measurable heuristic friction for the evaluated surface.	Low
Designer	Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.	h08 / h08_d_04	This checklist item indicates measurable heuristic friction for the evaluated surface.	Low
Designer	Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.	h08 / h08_d_06	This checklist item indicates measurable heuristic friction for the evaluated surface.	Low

Audit Scope and Omitted Profiles

Active scope: Active scope: H1-H14, 102/102 scored

Status: confirmation_required

Optional profile mode: ask

Scored optional profiles: none

Omitted optional profiles:

accessibility (h11): Accessibility and Ease of Access
inclusion (h12): Empathetic Engagement and Inclusion
journey (h13): Customer Journey and Satisfaction
ux_writing (h14): UX Writing and Content Design

For a full advanced audit, rerun with optional_profile_mode='all_optionals' or profiles=['accessibility','inclusion','journey','ux_writing'].

Evidence Gallery

Compact traceability view capped at 20 evidence refs. Full detail remains in the Evidence Appendix.

Additional Evidence

Linked finding: not linked to a top finding

url-1

url_capture partial

https://www.oppia.org/learner-dashboard

Parent/region: none
State: not supplied
Source: https://www.oppia.org/learner-dashboard
Metadata: not supplied
Bounds/notes: not supplied

url-2

url_capture partial

https://www.oppia.org/explore/1qMMSHbUvhQ4?topic_url_fragment=money&classroom_url_fragment=finance&story_url_fragment=pearl-supermarket&node_id=node_1

Parent/region: none
State: not supplied
Source: https://www.oppia.org/explore/1qMMSHbUvhQ4?topic_url_fragment=money&classroom_url_fragment=finance&story_url_fragment=pearl-supermarket&node_id=node_1
Metadata: not supplied
Bounds/notes: not supplied

Complete Checklist Scores

All checklist rows are shown. Use the Score and Status columns to scan Passed, Issue, and Major rows without JavaScript filters.

Visibility of System Status (h01) - 9 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h01_d_01	Every interface begins with a title/header that describes page contents	0.0	Passed	high	host_supplied-1	Progress tab permanently shows empty state — no system status feedback for any lesson activity
h01_d_02	Headings and subheadings are short, straightforward and descriptive	0.0	Passed	high	host_supplied-1	After setting goal and interacting with lesson, dashboard Progress shows no update — zero feedback on learning activity
h01_d_03	Value proposition is clearly stated on the home page (tagline or welcome blurb)	0.0	Passed	high	host_supplied-1	No progress indicators update in the dashboard — the 0% Complete on goal card does not change after lesson interaction
h01_d_04	The items on the home page are clearly focused on primary actions	2.0	Issue	high	host_supplied-1	Lesson player advances on Continue press — individual card transitions show immediate feedback
h01_d_05	Each page is clearly branded so that the user knows they are on the same site	0.0	Passed	high	host_supplied-1	84 console warnings accumulate during lesson (21 per Continue press) — silent failures not shown to user
h01_d_06	Navigation makes it clear which page I am on	1.0	Issue	high	host_supplied-1	beforeunload dialog appears on lesson exit — partial status feedback about unsaved state
h01_d_07	Link names match the title of destination pages, so users will know when they have reached the intended page	2.0	Issue	low	host_supplied-1	No forms in this flow — rated neutral
h01_d_08	Standard elements (page titles, site navigation, page navigation, privacy policy, etc.) are easy to locate	2.0	Issue	medium	host_supplied-1	Lesson player shows current card content; dashboard tab active states work
h01_d_09	Logo is in a consistent location, and clicking the logo returns the user back to the home page	0.0	Passed	high	host_supplied-1	No real-time progress updates anywhere — skill proficiency section is permanently empty

Match Between System and the Real World (h02) - 3 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h02_d_01	Navigation tabs are located at the top of the page, and look like clickable versions of real-world tabs	3.0	Major	high	host_supplied-1	Lesson content language is clear and age-appropriate; narrative story format is engaging
h02_d_02	Items that are not clickable do not have characteristics that suggest that they are clickable	2.0	Issue	high	host_supplied-1	Progress tab promises recommendations but delivers empty state — breaks mental model of progress tracking
h02_d_03	Items that are clickable look like they are clickable	2.0	Issue	high	host_supplied-1	Progress ring metaphor exists but never updates — metaphor creates false expectation

User Control and Freedom (h03) - 5 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h03_d_01	There is a search box	1.0	Issue	high	host_supplied-1	No undo for lesson navigation; beforeunload dialog is the only protection from progress loss
h03_d_02	There are clearly marked exits on every page allowing the user to bail out of the current task without having to depend on the browser Back button	1.0	Issue	high	host_supplied-1	Back button exists in lesson player DOM but has no accessible text label — not discoverable by keyboard/screen reader users
h03_d_03	The site does not disable the browser Back button and the Back button appears on the browser toolbar on every page	2.0	Issue	medium	host_supplied-1	Browser back and HOME button in lesson player provide exit paths — but no labeled Exit button
h03_d_04	Clicking the back button always takes the user back to the page they came from	3.0	Major	high	host_supplied-1	Lesson progression is entirely user-driven via Continue button; no forced progression
h03_d_05	Undo and redo are supported	2.0	Issue	medium	host_supplied-1	beforeunload dialog provides partial session control — but dialog content not inspected; progress is still lost on exit

Consistency and Standards (h04) - 21 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h04_d_01	In your expert opinion, site content does not look like advertisements	1.0	Issue	high	host_supplied-1	Two H1 elements on lesson page violates single H1 convention; H4-as-tabs pattern persists from dashboard
h04_d_02	Clickable elements use a consistent style/color for primary, secondary, and tertiary actions	0.0	Passed	high	host_supplied-1	H1 element nested inside <button> element — violates both HTML5 content model and WCAG 4.1.2
h04_d_03	Value proposition is clearly stated on the home page (tagline or welcome blurb)	2.0	Issue	high	host_supplied-1	Continue button is clear and consistently labeled; HOME button in player is clear
h04_d_04	Navigation choices are ordered in the most logical or task-oriented manner, with less important corporate information at the bottom	3.0	Major	medium	host_supplied-1	Color palette consistent throughout lesson player
h04_d_05	All corporate information is grouped in one distinct area, such as About Us	3.0	Major	medium	host_supplied-1	Typography consistent; lesson narrative is well-formatted
h04_d_06	The home page of the site has a memorable URL	1.0	Issue	high	host_supplied-1	Back button icon-only with no label; Lesson Info button contains both icon and text but H1 nesting is wrong
h04_d_07	Terminology is consistent with general web usage	2.0	Issue	medium	host_supplied-1	Lesson player navigation is different from dashboard navigation — some inconsistency in patterns
h04_d_08	There is a visible change when the mouse points at something clickable, excluding cursor changes	3.0	Major	low	host_supplied-1	No form fields in lesson player — rated neutral
h04_d_09	Hypertext links that invoke actions, such as downloads or new windows, are clearly distinguished from hypertext links that load another page	2.0	Issue	medium	host_supplied-1	No error messages for lesson interaction — warnings are silent
h04_d_10	If the site spawns new windows, these will not confuse the user and can be easily closed	3.0	Major	medium	host_supplied-1	Spacing consistent in lesson player content area
h04_d_11	Menu instructions, prompts and messages appear in the same place on each screen	2.0	Issue	medium	host_supplied-1	Continue and HOME buttons are consistently styled; Back button is icon-only inconsistency
h04_d_12	The content is up-to-date, authoritative and trustworthy	2.0	Issue	medium	host_supplied-1	Breadcrumb still uses > ASCII on dashboard; lesson player has no breadcrumb
h04_d_13	The site contains third-party support, such as citations or testimonials, to verify the accuracy of information	3.0	Major	high	host_supplied-1	Terminology consistent — 'Continue', 'Lesson Info', 'HOME' are clear
h04_d_14	It is clear that there is a real organization behind the site, such as a physical address or office photo	2.0	Issue	high	host_supplied-1	Broken #/ link in Progress section is a non-functional CTA
h04_d_15	The content is fresh: the site includes recent content	2.0	Issue	high	host_supplied-1	Lesson content heading hierarchy: two H1s (Introduction to Money + Lesson Info in button) breaks hierarchy
h04_d_16	The site is free of typographic errors and spelling mistakes	2.0	Issue	high	host_supplied-1	Progress tab shows empty state without clear indication that goal IS set — confusing state feedback
h04_d_17	The visual design is consistent, including colors, layout, iconography, etc.	3.0	Major	high	host_supplied-1	Brand consistent in lesson player
h04_d_18	On content pages, line lengths are neither too short (under 50 characters per line) nor too long (over 100 characters per line) when viewed in a standard browser width window	3.0	Major	high	host_supplied-1	Language selector available
h04_d_19	Fonts are used consistently and are legible	3.0	Major	medium	host_supplied-1	No jarring animations in lesson player
h04_d_20	The site can be used without scrolling horizontally	2.0	Issue	medium	host_supplied-1	Continue button appears adequately sized; Back button icon-only may have small touch target
h04_d_21	Design components, such as radio buttons and checkboxes, are used appropriately	1.0	Issue	high	host_supplied-1	Focus states not verified; back button has no accessible label; lesson info button has H1 in button

Error Prevention (h05) - 5 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h05_d_01	Pages are free of scroll stoppers: headings or page elements that create the illusion that users have reached the top or bottom of a page when they have not	2.0	Issue	medium	host_supplied-1	beforeunload dialog provides partial protection from accidental progress loss
h05_d_02	The user does not need to consult user manuals or other external information to use the site	2.0	Issue	medium	host_supplied-1	beforeunload dialog on lesson exit — but 84 warnings suggest potential for silent crashes
h05_d_03	User confirmation is required before carrying out potentially dangerous actions, such as deleting something	2.0	Issue	low	host_supplied-1	No user input validation needed in narrative lesson cards
h05_d_04	The site provides feedback that helps the user learn how to use the site	2.0	Issue	medium	host_supplied-1	Lesson continues from last card position within session — no cross-session defaults
h05_d_05	There is sufficient space between targets to prevent the user from hitting multiple or incorrect targets	1.0	Issue	high	host_supplied-1	No warning that progress will not be saved cross-session — user expects progress to persist but it does not

Recognition Rather Than Recall (h06) - 4 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h06_d_01	Search suggestions or filters are provided	0.0	Passed	high	host_supplied-1	Progress section never shows skill data — recommendations promised but never delivered
h06_d_02	Each page is clearly labeled with a descriptive and useful title that makes sense as a bookmark	1.0	Issue	high	host_supplied-1	User must remember that progress is not saved — no visual reminder in lesson or on dashboard
h06_d_03	Links and link titles are descriptive and predictive, and there are no Click here links	2.0	Issue	high	host_supplied-1	Continue button is clearly labeled; lesson card progress (0/5) is visible in lesson player
h06_d_04	Buttons and links show that they have been clicked	0.0	Passed	high	host_supplied-1	After returning from lesson, dashboard shows identical empty state — user cannot recall any progress was made

Flexibility and Efficiency of Use (h07) - 9 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h07_d_01	Useful content is presented on the home page or within one click of the home page	1.0	Issue	medium	host_supplied-1	No keyboard shortcuts in lesson player or dashboard
h07_d_02	The terms used for navigation items and hypertext links are unambiguous and jargon-free	1.0	Issue	high	host_supplied-1	Dashboard shows no personalized recommendations despite active goal — core personalization feature non-functional
h07_d_03	If there are product pages, they contain the detail necessary to make a purchase, and users can zoom in on product images	2.0	Issue	low	host_supplied-1	No bulk actions applicable
h07_d_04	The words, phrases and concepts used will be familiar to the typical user	0.0	Passed	high	host_supplied-1	No 'continue where you left off' — confirmed unresolved; progress persistence bug means no resumable state exists
h07_d_05	Content feels friendly for new users	1.0	Issue	high	host_supplied-1	No search on dashboard; no way to find recommendations
h07_d_06	Content feels customizable or useable for frequent or expert users	2.0	Issue	high	host_supplied-1	Lesson player advances smoothly on Continue press — efficiency within session is fine
h07_d_07	The screen density is appropriate for the target users and their tasks	0.0	Passed	high	host_supplied-1	No adaptive content or personalization at any level — same content shown regardless of lesson activity
h07_d_08	Icons and graphics are standard and/or intuitive (concrete and familiar)	2.0	Issue	low	host_supplied-1	No expert mode applicable
h07_d_09	Where tooltips are used, they provide useful additional help and do not simply duplicate text in the icon, link or field label	0.0	Passed	high	host_supplied-1	Zero cross-session continuation — progress persistence bug means every session starts from zero

Aesthetic and Minimalist Design (h08) - 16 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h08_d_01	By just looking at the home page, the first time user will understand where to start	3.0	Major	high	host_supplied-1	Lesson player is clean and visually focused; narrative content is well-presented
h08_d_02	Primary actions are easy to find and understand	3.0	Major	high	host_supplied-1	Lesson cards show content progressively — good information density
h08_d_03	Individual pages are free of clutter and irrelevant information, and attention-attracting features are used sparingly and only where relevant	3.0	Major	high	host_supplied-1	Good whitespace in lesson player
h08_d_04	The home page is professionally designed and will create a positive first impression	3.0	Major	medium	host_supplied-1	Color palette harmonious in lesson player
h08_d_05	The home page looks like a home page; pages lower in the site will not be confused with it	2.0	Issue	high	host_supplied-1	Two H1s on lesson page undermine typography hierarchy
h08_d_06	The site avoids advertisements, especially pop-ups	3.0	Major	high	host_supplied-1	Lesson images well-rendered with descriptive alt text
h08_d_07	Text is concise, with no needless instructions or welcome notes	3.0	Major	high	host_supplied-1	No jarring animations in lesson player
h08_d_08	Pages use bulleted and numbered lists in preference to narrative text	1.0	Issue	high	host_supplied-1	Lesson player loading showed 'Loading \| Oppia' title; 84 console warnings may indicate render issues
h08_d_09	The most important items in a list are placed at the top	2.0	Issue	low	host_supplied-1	Mobile not directly tested
h08_d_10	Pages are quick to scan, with ample headings and subheadings and short paragraphs	2.0	Issue	low	host_supplied-1	Contrast not directly testable
h08_d_11	Information is organized hierarchically, from the general to the specific, and the organization is clear and logical	2.0	Issue	low	host_supplied-1	Responsive not tested
h08_d_12	Text links are long enough to be understood, but short enough to minimize wrapping, especially when used as a navigation list	2.0	Issue	medium	host_supplied-1	Continue button provides clear visual feedback; back button icon-only
h08_d_13	On all pages, the most important information, such as frequently used topics, features and functions, is presented on the first screenful of information above the fold	3.0	Major	high	host_supplied-1	Brand consistent in lesson player
h08_d_14	The relationship between controls and their actions is obvious	3.0	Major	high	host_supplied-1	Lesson player first impression is clean and engaging
h08_d_15	There is a clear visual starting point to every page	2.0	Issue	low	host_supplied-1	Dark mode not tested
h08_d_16	The site is pleasant to look at	2.0	Issue	low	host_supplied-1	Print not applicable

Help Users Recognize, Diagnose, and Recover from Errors (h09) - 2 checklist items

Item	Checklist text	Score	Status	Confidence	Severity basis	Evidence	Rationale
h09_d_01	The site uses a customised 404 page, which includes tips on how to find the missing page and links to Home and Search	1.0	Issue	high		host_supplied-1	84 silent console warnings — no user-visible error messages for underlying JS issues
h09_d_02	Error messages contain clear instructions on what to do next, including form error states	0.0	Passed	high		host_supplied-1	Progress loss is permanent and unrecoverable — no recovery path for the core bug; no undo, no re-sync

Help and Documentation (h10) - 5 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h10_d_01	Help is available and easy to find	1.0	Issue	high	host_supplied-1	No contextual help explaining why Progress tab is empty when a goal is set
h10_d_02	FAQs are present if appropriate	1.0	Issue	high	host_supplied-1	No help center accessible to explain the empty Progress state
h10_d_03	When giving instructions, pages tell users what to do rather than what to avoid doing	2.0	Issue	medium	host_supplied-1	Empty state message 'Setting a goal allows Oppia to give you better recommendations' gives some direction
h10_d_04	The site shows users how to do common tasks where appropriate, such as demonstrations of the site's functionality	1.0	Issue	medium	host_supplied-1	No tooltips to explain progress tracking concepts or empty state
h10_d_05	It is easy to contact someone for assistance and a reply is received quickly	1.0	Issue	high	host_supplied-1	No error documentation or troubleshooting for the broken progress loop

Accessibility and Ease of Access (h11) - 4 checklist items

Item	Score	Status	Confidence	Evidence	Rationale
h11_d_01	1.0	Issue	medium	host_supplied-1	Progress tracking page text readable; adequate contrast on dashboard
h11_d_02	1.0	Issue	medium	host_supplied-1	Dashboard keyboard navigation generally functional
h11_d_03	1.0	Issue	medium	host_supplied-1	Progress ring labels (0%) are understandable; misleading content not an operability failure
h11_d_04	2.0	Issue	low	host_supplied-1	Angular SPA may not expose semantic roles to assistive technology

Empathetic Engagement and Inclusion (h12) - 6 checklist items

Item	Score	Status	Confidence	Evidence	Rationale
h12_d_01	0.0	Passed	high	host_supplied-1	No exclusionary language in progress tracking interface
h12_d_02	0.0	Passed	high	host_supplied-1	No stereotypes or biased assumptions in progress display
h12_d_03	1.0	Issue	medium	host_supplied-1	Progress tracking interactions generally accessible; minor concerns
h12_d_04	0.0	Passed	high	host_supplied-1	Progress display culturally neutral
h12_d_05	1.0	Issue	medium	host_supplied-1	Interaction patterns mostly accessible; ring graphic lacks text alternative
h12_d_06	3.0	Major	high	host_supplied-1	Users have no agency over permanent 0% progress display; system denies their learning reality

Customer Journey and Satisfaction (h13) - 6 checklist items

Item	Score	Status	Confidence	Evidence	Rationale
h13_d_01	1.0	Issue	medium	host_supplied-1	Dashboard entry to progress tracking is clear
h13_d_02	2.0	Issue	high	host_supplied-1	Recommendation path not discoverable; no recommendations are ever surfaced
h13_d_03	3.0	Major	high	host_supplied-1	Zero personalization confirmed; no personalized lesson suggestions or adaptive content
h13_d_04	2.0	Issue	high	host_supplied-1	No support or coaching at key progress milestones
h13_d_05	3.0	Major	high	host_supplied-1	No reward after lesson completion; 0% ring never updates so no sense of progress
h13_d_06	3.0	Major	high	host_supplied-1	Journey completion reward completely absent; learner receives no acknowledgment of growth

UX Writing / Content and Tone (h14) - 7 checklist items

Item	Score	Status	Confidence	Evidence	Rationale
h14_d_01	2.0	Issue	high	host_supplied-1	"0% Complete" label technically accurate but deeply misleading; implies learner has done nothing
h14_d_02	2.0	Issue	high	host_supplied-1	No microcopy explaining why progress shows 0% or how to advance
h14_d_03	0.0	Passed	high	host_supplied-1	No jargon in progress tracking UI
h14_d_04	2.0	Issue	medium	host_supplied-1	No clear CTA to continue learning from the progress view
h14_d_05	3.0	Major	high	host_supplied-1	No error messaging when progress fails to save; learner has no way to know
h14_d_06	2.0	Issue	medium	host_supplied-1	Empty state for no lessons completed is not compelling or motivating
h14_d_07	1.0	Issue	medium	host_supplied-1	Minor inconsistency between Complete/Finish terminology across progress flow

Evidence Appendix

Evidence ref	Parent	Source type	Quality	Label/title	Bounds/notes	Screenshot/source	Metadata
url-1		url_capture	partial	https://www.oppia.org/learner-dashboard		https://www.oppia.org/learner-dashboard
url-2		url_capture	partial	https://www.oppia.org/explore/1qMMSHbUvhQ4?topic_url_fragment=money&classroom_url_fragment=finance&story_url_fragment=pearl-supermarket&node_id=node_1		https://www.oppia.org/explore/1qMMSHbUvhQ4?topic_url_fragment=money&classroom_url_fragment=finance&story_url_fragment=pearl-supermarket&node_id=node_1

Mission Context

Severity ratings reflect the supplied evidence, user goal, optional-profile scope, and any stated evidence limits. Support flows and activities should never outrank the checklist scorecard.

D-

36.56%

Critical - severe experience failures

Plain Language Read

The biggest visible usability risk is visual hierarchy is not supporting the task. It affects Aesthetic and Minimalist Design and should be fixed before broader polish.

Next Research Recommendation

Fix severity 3-4 checklist items first, then rerun the same source state for comparison.

Accessibility Readiness Signal

Accessibility Readiness Signal: WCAG AAA-level criteria are implicated by Error Prevention needs targeted review; this remains evidence-limited until manual accessibility testing.

Cultural Context Signal

Cultural Context Signal: CJK Layout And Typography Requirements flags Consistency and trust cues need review as needing evidence-bound local or community-context validation.

Before using this interface, address Aesthetic and Minimalist Design first: Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.

Critical Finding - Immediate Attention

Visual hierarchy is not supporting the task

H1/H2 hierarchy correct on error page — no heading misuse

Heuristic Scorecard - AI Audit, 14 Heuristics

11.11% - avg severity 3.56

Visibility of System Status

Failing - unusable or near-unusable

D-

33.33% - avg severity 2.67

Match Between System and the Real World

Critical - severe experience failures

5.0% - avg severity 3.8

User Control and Freedom

Failing - unusable or near-unusable

21.43% - avg severity 3.14

Consistency and Standards

Failing - unusable or near-unusable

10.0% - avg severity 3.6

Error Prevention

Failing - unusable or near-unusable

25.0% - avg severity 3.0

Recognition Rather Than Recall

Failing - unusable or near-unusable

D-

38.89% - avg severity 2.44

Flexibility and Efficiency of Use

Critical - severe experience failures

26.56% - avg severity 2.94

Aesthetic and Minimalist Design

Failing - unusable or near-unusable

D-

37.5% - avg severity 2.5

Help Users Recognize, Diagnose, and Recover from Errors

Critical - severe experience failures

C-

50.0% - avg severity 2.0

Help and Documentation

Struggling - widespread issues

87.5% - avg severity 0.5

Accessibility and Ease of Access

Very good - strong performer

87.5% - avg severity 0.5

Empathetic Engagement and Inclusion

Very good - strong performer

Observed Issue

Full nav bar intact; 'home page' link in body text; multiple exit paths available

Recommendation

Add or clarify exits, back behavior, and recovery controls so users can leave wrong paths without losing context.

This checklist item indicates measurable heuristic friction for the evaluated surface.

Supporting lenses: Peak-End Rule, Mediated Payment And Trust Recovery

Evidence: h03_d_02 - Confidence: high

Owner-Role Triage Matrix

Owner	Linked finding	Next action	Impact	Effort	Confidence
Designer	h08 / h08_d_05	Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.	high	Medium	high
Product	h04 / h04_d_01	Audit repeated navigation, labels, components, and trust cues, then align any pattern that changes meaning across screens.	high	Medium	high
Product	h04 / h04_d_15	Audit repeated navigation, labels, components, and trust cues, then align any pattern that changes meaning across screens.	high	Medium	high
Product	h04 / h04_d_16	Run a content QA pass on the affected screens and fix visible typos before stakeholder or user review.	high	Medium	high
Product	h04 / h04_d_02	Standardize repeated components, labels, and visual treatments so the same action looks and behaves the same way everywhere.	high	Medium	high
Product	h04 / h04_d_07	Standardize repeated components, labels, and visual treatments so the same action looks and behaves the same way everywhere.	high	Medium	high
Engineer	h05 / h05_d_01	Review the affected element against Error Prevention and make the next user action clearer, safer, or easier to recover from.	high	Medium	high
Engineer	h05 / h05_d_02	Review the affected element against Error Prevention and make the next user action clearer, safer, or easier to recover from.	high	Medium	high
Engineer	h05 / h05_d_03	Review the affected element against Error Prevention and make the next user action clearer, safer, or easier to recover from.	high	Medium	high
Engineer	h03 / h03_d_02	Add or clarify exits, back behavior, and recovery controls so users can leave wrong paths without losing context.	high	Medium	high

What Is Working Well

Accessibility and Ease of Access holds up with A (87.5%).
Empathetic Engagement and Inclusion holds up with A (87.5%).

Evidence Limits

source: source preparation status was partial (ratings may be incomplete or unavailable)
source: URL entries were recorded without a browser screenshot (visual and interaction-state ratings are limited)
h01_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
77 additional evidence-limit summary row(s) are collapsed below.

Show detailed evidence-limit notes (81 source notes)

source: source preparation status was partial (ratings may be incomplete or unavailable)
source: URL entries were recorded without a browser screenshot (visual and interaction-state ratings are limited)
h01_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_05: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_06: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_07: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_08: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h01_d_09: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h02_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h02_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h02_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h03_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h03_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h03_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h03_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h03_d_05: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_05: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_06: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_07: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_08: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_09: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_10: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_11: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_12: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_13: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_14: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_15: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_16: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_17: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_18: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_19: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_20: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h04_d_21: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h05_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h05_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h05_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h05_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h05_d_05: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h06_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h06_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h06_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h06_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_05: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_06: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_07: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_08: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h07_d_09: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_05: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_06: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_07: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_08: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_09: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_10: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_11: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_12: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_13: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_14: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_15: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h08_d_16: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h09_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h09_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h10_d_01: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h10_d_02: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h10_d_03: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h10_d_04: no evidence reference supplied for checklist rating (rating may be difficult to audit later)
h10_d_05: no evidence reference supplied for checklist rating (rating may be difficult to audit later)

WCAG-Informed Accessibility Readiness

Support-only advisory. This section does not change H01-H14 scores, 0-4 checklist ratings, report readiness, or finding order.

WCAG Level Signal: AAA

Top signal: Accessibility Readiness Signal: WCAG AAA-level criteria are implicated by Error Prevention needs targeted review; this remains evidence-limited until manual accessibility testing.

Caveat: Evidence-limited accessibility support guidance only; not WCAG, ADA, legal, procurement, or conformance certification.

Lens / cue	Applies to	Evidence	Why it matters	Caveat
Accessible Authentication	h05/h05_d_02	h05_d_02	The finding connects to WCAG accessible-authentication guidance: sign-in should not rely on avoidable memory or cognitive tests without alternatives.	UXHC can flag authentication burden, but WCAG evaluation needs the actual auth flow and security constraints; this is not WCAG conformance certification.
Bypass Blocks, Navigation, Headings, And Labels	h01/h01_d_06	h01_d_06	The finding connects to WCAG navigation guidance: page structure, headings, labels, and bypass paths should help users find the task.	UXHC can flag navigation clarity risk, but source and assistive-technology review are required before WCAG conformance claims.
Bypass Blocks, Navigation, Headings, And Labels	h01/h01_d_01	h01_d_01	The finding connects to WCAG navigation guidance: page structure, headings, labels, and bypass paths should help users find the task.	UXHC can flag navigation clarity risk, but source and assistive-technology review are required before WCAG conformance claims.
Focus Order, Visibility, And Obscured Focus	h01/h01_d_06	h01_d_06	The finding connects to WCAG focus guidance: keyboard users need a visible, logical focus path that is not hidden by the interface.	UXHC can flag likely focus risk, but keyboard traversal and viewport-state testing are needed before WCAG conformance claims.
Accessible Forms Component Pattern	h05/h05_d_03	h05_d_03	The finding connects to accessible form-pattern guidance: forms need clear labels, instructions, validation, and recovery paths.	UXHC can flag visible form risks, but programmatic labels, descriptions, and error associations require technical review; this is not WCAG conformance certification.
Info, Relationships, And Semantic Structure	h01/h01_d_01	h01_d_01	The finding connects to WCAG info-and-relationships guidance: visual grouping should remain meaningful when presented through assistive technology.	UXHC can infer likely structure risk from evidence, but DOM and assistive-technology testing are required before claiming WCAG compliance.

Cultural Context Integrity Advisory

Support-only advisory. This section does not change H01-H14 scores, 0-4 checklist ratings, report readiness, or finding order.

Context Integrity Index: 0 - Insufficient Context Safety

Top signal: Cultural Context Signal: CJK Layout And Typography Requirements flags Consistency and trust cues need review as needing evidence-bound local or community-context validation.

Caveat: Evidence-limited support guidance only; not a cultural certification, moral judgment, universal cultural claim, or substitute for affected-community review.

Lens / cue	Applies to	Evidence	Why it matters	Caveat
CJK Layout And Typography Requirements	h04/h04_d_01	h04_d_01	The finding may need CJK layout review because typography, line breaking, punctuation, or annotations could change the user's reading path.	CJK layout quality varies by language context and requires target-language content and rendered typography evidence, not translated strings alone.
Literacy, Orality, And Multimodal Access	h05/h05_d_02	h05_d_02	The finding may need multimodal support because dense text or text-only instruction can exclude users whose access path is oral, visual, assisted, or low-literacy.	Literacy and modality needs vary widely; the lens should preserve agency rather than simplify or infantilize users.
Local Contexts And Traditional Knowledge Labels	h04/h04_d_16	h04_d_16	The finding may need stronger cultural provenance or permission cues at the point where users view, reuse, or export content.	Labels depend on community-defined protocols; absence of a label in the evidence is not proof that no protocol applies.
Mediated Payment And Trust Recovery	h01/h01_d_08	h01_d_08	The finding may create trust or recovery risk in mediated payment contexts where fees, receipts, agent support, and disputes must be visible.	Financial-service risk depends on local regulation, agent networks, cost, literacy, and trust channels; UXHC cannot validate the business or legal model.
Mediated Payment And Trust Recovery	h03/h03_d_02	h03_d_02	The finding may create trust or recovery risk in mediated payment contexts where fees, receipts, agent support, and disputes must be visible.	Financial-service risk depends on local regulation, agent networks, cost, literacy, and trust channels; UXHC cannot validate the business or legal model.
Mediated Payment And Trust Recovery	h03/h03_d_03	h03_d_03	The finding may create trust or recovery risk in mediated payment contexts where fees, receipts, agent support, and disputes must be visible.	Financial-service risk depends on local regulation, agent networks, cost, literacy, and trust channels; UXHC cannot validate the business or legal model.

Recommended Next Validation Steps

Validation Step 1

Fix severity 3-4 checklist items first, then rerun the same source state for comparison.

Supporting UX Laws And Principles

Support-only explanation. These lenses do not create findings, change 0-4 checklist ratings, or certify compliance.

Lens	Source family	Applies to	Why it matters	Caveat / evidence needed
Shneiderman's Eight Golden Rules	UX/UI Support Lens	h04/h04_d_01, h04/h04_d_15, h04/h04_d_16	The finding is also consistent with Shneiderman-style interface review principles. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	The rules are broad and require domain-specific interpretation. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Feedback	UX/UI Support Lens	h01/h01_d_02, h08/h08_d_12, h05/h05_d_04	The finding is supported by feedback risk: users may not know what happened or what to do next. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Feedback must be timely, perceivable, and tied to the user's action. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Peak-End Rule	UX/UI Support Lens	h03/h03_d_02, h03/h03_d_03, h03/h03_d_04	The finding is supported by peak-end risk: this moment may heavily shape how users remember the experience. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Memory effects need real user evidence to confirm; use this as a risk lens. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Visual Hierarchy	UX/UI Support Lens	h08/h08_d_05, h01/h01_d_04, h08/h08_d_13	The finding is supported by visual hierarchy: the screen does not make the most important next action visually primary. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Hierarchy needs to match the user's current task, not only stakeholder importance. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
ISO 9241-11 Usability In Context	ISO UX/UI/HCI Support	h07/h07_d_03, h07/h07_d_04, h07/h07_d_09	This finding connects to ISO 9241-11 style usability-in-context framing: usable for whom, for what task, and in what context. Applicability: Use when the finding benefits from ISO-informed framing around context of use, interaction quality, evidence traceability, process quality, or operational risk.	ISO-informed support reference only; not formal ISO standards compliance, conformance, certification, procurement proof, or legal assurance. Evidence needed: Requires project, process, technical, or audit evidence before standards-strength claims.
Information Scent	UX/UI Support Lens	h10/h10_d_01, h06/h06_d_03, h06/h06_d_01	The finding is supported by information scent: navigation cues do not clearly predict destination value. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Information scent depends on user goals and vocabulary. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.

Support-only context; not a separate score, proof of user behavior, compliance claim, or replacement for the H01-H14 checklist.

Do not use this as a replacement rubric; map it back to the active UXHC checklist item.

Do not add decorative animation where clear status text or recovery instruction is needed.

Do not compensate for broken flows with a pleasant ending; fix the friction first.

Do not make every business priority visually dominant; hierarchy requires tradeoffs.

Prioritized Fix Roadmap

When	Recommended action
Immediate	Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.
Immediate	Audit repeated navigation, labels, components, and trust cues, then align any pattern that changes meaning across screens.
Immediate	Audit repeated navigation, labels, components, and trust cues, then align any pattern that changes meaning across screens.
Immediate	Run a content QA pass on the affected screens and fix visible typos before stakeholder or user review.
Immediate	Standardize repeated components, labels, and visual treatments so the same action looks and behaves the same way everywhere.
Immediate	Standardize repeated components, labels, and visual treatments so the same action looks and behaves the same way everywhere.
Immediate	Review the affected element against Error Prevention and make the next user action clearer, safer, or easier to recover from.
Immediate	Review the affected element against Error Prevention and make the next user action clearer, safer, or easier to recover from.
Immediate	Review the affected element against Error Prevention and make the next user action clearer, safer, or easier to recover from.
Immediate	Add or clarify exits, back behavior, and recovery controls so users can leave wrong paths without losing context.
Immediate	Add or clarify exits, back behavior, and recovery controls so users can leave wrong paths without losing context.
Immediate	Add or clarify exits, back behavior, and recovery controls so users can leave wrong paths without losing context.

High-Impact / Low-Effort Micro-Solutions

Role	Micro-solution	Linked finding	Why high impact	Estimated effort
Designer	Rework the visual hierarchy so the page guides users from the main purpose to the next action without extra scanning.	h08 / h08_d_05	This checklist item indicates measurable heuristic friction for the evaluated surface.	Low-Medium
Product	Audit repeated navigation, labels, components, and trust cues, then align any pattern that changes meaning across screens.	h04 / h04_d_01	This checklist item indicates measurable heuristic friction for the evaluated surface.	Low-Medium
Product	Audit repeated navigation, labels, components, and trust cues, then align any pattern that changes meaning across screens.	h04 / h04_d_15	This checklist item indicates measurable heuristic friction for the evaluated surface.	Low-Medium
Product	Run a content QA pass on the affected screens and fix visible typos before stakeholder or user review.	h04 / h04_d_16	This checklist item indicates measurable heuristic friction for the evaluated surface.	Low-Medium
Product	Standardize repeated components, labels, and visual treatments so the same action looks and behaves the same way everywhere.	h04 / h04_d_02	This checklist item indicates measurable heuristic friction for the evaluated surface.	Low-Medium
Product	Standardize repeated components, labels, and visual treatments so the same action looks and behaves the same way everywhere.	h04 / h04_d_07	This checklist item indicates measurable heuristic friction for the evaluated surface.	Low-Medium

Audit Scope and Omitted Profiles

Active scope: Active scope: H1-H14, 102/102 scored

Status: confirmation_required

Optional profile mode: ask

Scored optional profiles: none

Omitted optional profiles:

accessibility (h11): Accessibility and Ease of Access
inclusion (h12): Empathetic Engagement and Inclusion
journey (h13): Customer Journey and Satisfaction
ux_writing (h14): UX Writing and Content Design

For a full advanced audit, rerun with optional_profile_mode='all_optionals' or profiles=['accessibility','inclusion','journey','ux_writing'].

Evidence Gallery

Compact traceability view capped at 20 evidence refs. Full detail remains in the Evidence Appendix.

Additional Evidence

Linked finding: not linked to a top finding

url-1

url_capture partial

https://www.oppia.org/admin

Parent/region: none
State: not supplied
Source: https://www.oppia.org/admin
Metadata: not supplied
Bounds/notes: not supplied

url-2

url_capture partial

https://www.oppia.org/moderator

Parent/region: none
State: not supplied
Source: https://www.oppia.org/moderator
Metadata: not supplied
Bounds/notes: not supplied

Complete Checklist Scores

All checklist rows are shown. Use the Score and Status columns to scan Passed, Issue, and Major rows without JavaScript filters.

Visibility of System Status (h01) - 9 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h01_d_01	Every interface begins with a title/header that describes page contents	4.0	Major	high	host_supplied-1	Page title 'Error 401 \| Oppia' correctly communicates error status immediately
h01_d_02	Headings and subheadings are short, straightforward and descriptive	4.0	Major	high	host_supplied-1	H1 'Error 401 - Unauthorized' and H2 role message provide clear, immediate error feedback
h01_d_03	Value proposition is clearly stated on the home page (tagline or welcome blurb)	3.0	Major	high	host_supplied-1	Error state is visually clear with heading, mascot image, and explanatory text
h01_d_04	The items on the home page are clearly focused on primary actions	4.0	Major	high	host_supplied-1	Both /admin and /moderator correctly return 401 pages — system correctly identifies and surfaces access restriction
h01_d_05	Each page is clearly branded so that the user knows they are on the same site	3.0	Major	high	host_supplied-1	No silent failures — the error is surfaced visibly to the user
h01_d_06	Navigation makes it clear which page I am on	4.0	Major	high	host_supplied-1	Error state is prominently and clearly displayed — no ambiguity about what happened
h01_d_07	Link names match the title of destination pages, so users will know when they have reached the intended page	3.0	Major	low	host_supplied-1	No forms on error page — rated neutral
h01_d_08	Standard elements (page titles, site navigation, page navigation, privacy policy, etc.) are easy to locate	4.0	Major	high	host_supplied-1	Navigation remains intact on error page — clear wayfinding back to accessible areas
h01_d_09	Logo is in a consistent location, and clicking the logo returns the user back to the home page	3.0	Major	high	host_supplied-1	No real-time elements on error page — static content is appropriate

Match Between System and the Real World (h02) - 3 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h02_d_01	Navigation tabs are located at the top of the page, and look like clickable versions of real-world tabs	2.0	Issue	high	host_supplied-1	'super admin' and 'moderator' are Oppia-internal role names not accessible to regular learners — jargon mismatch
h02_d_02	Items that are not clickable do not have characteristics that suggest that they are clickable	3.0	Major	high	host_supplied-1	The concept of 'you don't have access' maps to real-world mental models of restricted areas
h02_d_03	Items that are clickable look like they are clickable	3.0	Major	high	host_supplied-1	'Oops!' mascot and 'Sorry about this' tone are familiar error-state metaphors

User Control and Freedom (h03) - 5 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h03_d_01	There is a search box	3.0	Major	high	host_supplied-1	No actions on error page that need undo; user can freely navigate away
h03_d_02	There are clearly marked exits on every page allowing the user to bail out of the current task without having to depend on the browser Back button	4.0	Major	high	host_supplied-1	Full nav bar intact; 'home page' link in body text; multiple exit paths available
h03_d_03	The site does not disable the browser Back button and the Back button appears on the browser toolbar on every page	4.0	Major	high	host_supplied-1	User can navigate back via browser, nav bar, or 'home page' link — multiple easy exit paths
h03_d_04	Clicking the back button always takes the user back to the page they came from	4.0	Major	high	host_supplied-1	Error page is passive — no forced actions required; user can leave at any time
h03_d_05	Undo and redo are supported	4.0	Major	high	host_supplied-1	No session data at risk on error page

Consistency and Standards (h04) - 21 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h04_d_01	In your expert opinion, site content does not look like advertisements	4.0	Major	high	host_supplied-1	Error page format is consistent across /admin and /moderator — same layout, same structure
h04_d_02	Clickable elements use a consistent style/color for primary, secondary, and tertiary actions	4.0	Major	high	host_supplied-1	H1/H2 heading hierarchy is correct on error page
h04_d_03	Value proposition is clearly stated on the home page (tagline or welcome blurb)	3.0	Major	high	host_supplied-1	Recovery links labeled as 'home page' and 'issue tracker' — clear and consistent link text
h04_d_04	Navigation choices are ordered in the most logical or task-oriented manner, with less important corporate information at the bottom	3.0	Major	medium	host_supplied-1	Color palette consistent with rest of site on error page
h04_d_05	All corporate information is grouped in one distinct area, such as About Us	3.0	Major	medium	host_supplied-1	Typography consistent with rest of site
h04_d_06	The home page of the site has a memorable URL	3.0	Major	medium	host_supplied-1	'Oops!' mascot is a recognizable Oppia error character — consistent brand use
h04_d_07	Terminology is consistent with general web usage	4.0	Major	high	host_supplied-1	Nav bar maintains same structure as rest of site on error page
h04_d_08	There is a visible change when the mouse points at something clickable, excluding cursor changes	3.0	Major	low	host_supplied-1	No form elements on error page
h04_d_09	Hypertext links that invoke actions, such as downloads or new windows, are clearly distinguished from hypertext links that load another page	3.0	Major	high	host_supplied-1	Error message styling is clear and prominent
h04_d_10	If the site spawns new windows, these will not confuse the user and can be easily closed	3.0	Major	medium	host_supplied-1	Consistent spacing and layout with rest of site
h04_d_11	Menu instructions, prompts and messages appear in the same place on each screen	3.0	Major	medium	host_supplied-1	Links on error page consistently styled
h04_d_12	The content is up-to-date, authoritative and trustworthy	2.0	Issue	medium	host_supplied-1	Breadcrumb still uses > separator — persists from dashboard
h04_d_13	The site contains third-party support, such as citations or testimonials, to verify the accuracy of information	2.0	Issue	high	host_supplied-1	'super admin' and 'moderator' terminology is inconsistent with user-facing language — developer jargon in learner-facing page
h04_d_14	It is clear that there is a real organization behind the site, such as a physical address or office photo	3.0	Major	high	host_supplied-1	'home page' CTA is clear and appropriately placed in error message body
h04_d_15	The content is fresh: the site includes recent content	4.0	Major	high	host_supplied-1	Correct heading hierarchy: H1 for error title, H2 for role requirement — appropriate semantic structure
h04_d_16	The site is free of typographic errors and spelling mistakes	4.0	Major	high	host_supplied-1	Error state is unambiguously communicated — no state confusion
h04_d_17	The visual design is consistent, including colors, layout, iconography, etc.	3.0	Major	high	host_supplied-1	Brand mascot ('Oops!') and colors consistent
h04_d_18	On content pages, line lengths are neither too short (under 50 characters per line) nor too long (over 100 characters per line) when viewed in a standard browser width window	3.0	Major	high	host_supplied-1	Language selector available
h04_d_19	Fonts are used consistently and are legible	3.0	Major	high	host_supplied-1	No animations on static error page
h04_d_20	The site can be used without scrolling horizontally	3.0	Major	medium	host_supplied-1	Links on error page have adequate size
h04_d_21	Design components, such as radio buttons and checkboxes, are used appropriately	3.0	Major	medium	host_supplied-1	Standard link focus states apply; page is mostly static content

Error Prevention (h05) - 5 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h05_d_01	Pages are free of scroll stoppers: headings or page elements that create the illusion that users have reached the top or bottom of a page when they have not	4.0	Major	high	host_supplied-1	Access restriction is correctly enforced — no accidental data access possible
h05_d_02	The user does not need to consult user manuals or other external information to use the site	4.0	Major	high	host_supplied-1	No destructive actions on error page
h05_d_03	User confirmation is required before carrying out potentially dangerous actions, such as deleting something	4.0	Major	high	host_supplied-1	No form inputs — no validation needed
h05_d_04	The site provides feedback that helps the user learn how to use the site	3.0	Major	high	host_supplied-1	Error page defaults to showing recovery options — good default
h05_d_05	There is sufficient space between targets to prevent the user from hitting multiple or incorrect targets	3.0	Major	high	host_supplied-1	Access restriction is properly enforced before any privileged content is shown

Recognition Rather Than Recall (h06) - 4 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h06_d_01	Search suggestions or filters are provided	3.0	Major	high	host_supplied-1	'home page' link in body is labeled and recognizable; nav bar provides full site navigation
h06_d_02	Each page is clearly labeled with a descriptive and useful title that makes sense as a bookmark	3.0	Major	high	host_supplied-1	Nav bar provides full context for where user is and where they can go
h06_d_03	Links and link titles are descriptive and predictive, and there are no Click here links	3.0	Major	medium	host_supplied-1	Recovery links have clear text; 'issue tracker' link label is slightly opaque but recognizable to technical users
h06_d_04	Buttons and links show that they have been clicked	3.0	Major	high	host_supplied-1	No complex memory burden on a static error page

Flexibility and Efficiency of Use (h07) - 9 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h07_d_01	Useful content is presented on the home page or within one click of the home page	2.0	Issue	medium	host_supplied-1	No keyboard shortcuts; standard nav bar shortcuts apply
h07_d_02	The terms used for navigation items and hypertext links are unambiguous and jargon-free	2.0	Issue	medium	host_supplied-1	Error message correctly identifies the required role — role-specific messaging is a form of personalization
h07_d_03	If there are product pages, they contain the detail necessary to make a purchase, and users can zoom in on product images	3.0	Major	low	host_supplied-1	No bulk actions applicable on error page
h07_d_04	The words, phrases and concepts used will be familiar to the typical user	3.0	Major	high	host_supplied-1	User can immediately navigate to any accessible page via nav bar
h07_d_05	Content feels friendly for new users	2.0	Issue	medium	host_supplied-1	No search on error page; full nav provides browsable access to accessible areas
h07_d_06	Content feels customizable or useable for frequent or expert users	3.0	Major	high	host_supplied-1	Error page loads quickly; recovery path is immediate
h07_d_07	The screen density is appropriate for the target users and their tasks	2.0	Issue	low	host_supplied-1	No adaptive elements on error page
h07_d_08	Icons and graphics are standard and/or intuitive (concrete and familiar)	2.0	Issue	low	host_supplied-1	No advanced features applicable
h07_d_09	Where tooltips are used, they provide useful additional help and do not simply duplicate text in the icon, link or field label	3.0	Major	high	host_supplied-1	No session state involved in error page

Aesthetic and Minimalist Design (h08) - 16 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h08_d_01	By just looking at the home page, the first time user will understand where to start	3.0	Major	high	host_supplied-1	Clean, uncluttered error page with mascot and clear message
h08_d_02	Primary actions are easy to find and understand	3.0	Major	high	host_supplied-1	Minimal content — appropriate for an error page
h08_d_03	Individual pages are free of clutter and irrelevant information, and attention-attracting features are used sparingly and only where relevant	3.0	Major	medium	host_supplied-1	Adequate whitespace; error page is visually balanced
h08_d_04	The home page is professionally designed and will create a positive first impression	3.0	Major	medium	host_supplied-1	Color palette consistent and appropriate
h08_d_05	The home page looks like a home page; pages lower in the site will not be confused with it	4.0	Major	high	host_supplied-1	H1/H2 hierarchy correct on error page — no heading misuse
h08_d_06	The site avoids advertisements, especially pop-ups	3.0	Major	high	host_supplied-1	'Oops!' mascot image is on-brand and visually appropriate
h08_d_07	Text is concise, with no needless instructions or welcome notes	3.0	Major	high	host_supplied-1	No animations on error page
h08_d_08	Pages use bulleted and numbered lists in preference to narrative text	3.0	Major	medium	host_supplied-1	Page title briefly showed 'Loading \| Oppia' then resolved — consistent with SPA behavior
h08_d_09	The most important items in a list are placed at the top	3.0	Major	low	host_supplied-1	Mobile not tested — error page layout likely responsive
h08_d_10	Pages are quick to scan, with ample headings and subheadings and short paragraphs	3.0	Major	low	host_supplied-1	Contrast not directly testable but standard Oppia palette used
h08_d_11	Information is organized hierarchically, from the general to the specific, and the organization is clear and logical	3.0	Major	low	host_supplied-1	Responsive design not directly tested
h08_d_12	Text links are long enough to be understood, but short enough to minimize wrapping, especially when used as a navigation list	3.0	Major	high	host_supplied-1	Error page is static — no interactive feedback needed
h08_d_13	On all pages, the most important information, such as frequently used topics, features and functions, is presented on the first screenful of information above the fold	3.0	Major	high	host_supplied-1	Brand mascot and footer consistent with rest of site
h08_d_14	The relationship between controls and their actions is obvious	3.0	Major	high	host_supplied-1	Error page has professional, branded appearance
h08_d_15	There is a clear visual starting point to every page	2.0	Issue	low	host_supplied-1	Dark mode not tested
h08_d_16	The site is pleasant to look at	2.0	Issue	low	host_supplied-1	Print not applicable

Help Users Recognize, Diagnose, and Recover from Errors (h09) - 2 checklist items

Item	Checklist text	Score	Status	Confidence	Severity basis	Evidence	Rationale
h09_d_01	The site uses a customised 404 page, which includes tips on how to find the missing page and links to Home and Search	3.0	Major	high		host_supplied-1	Error is clearly communicated; recovery path ('home page') is labeled and linked
h09_d_02	Error messages contain clear instructions on what to do next, including form error states	2.0	Issue	high		host_supplied-1	GitHub issue tracker recovery link is developer-facing — not actionable for most learners who don't have GitHub accounts

Help and Documentation (h10) - 5 checklist items

Item	Checklist text	Score	Status	Confidence	Evidence	Rationale
h10_d_01	Help is available and easy to find	3.0	Major	high	host_supplied-1	Contextual body text explains the error and recovery path in plain language (aside from jargon)
h10_d_02	FAQs are present if appropriate	1.0	Issue	high	host_supplied-1	GitHub issue tracker as help resource is wrong audience — learners cannot use this effectively
h10_d_03	When giving instructions, pages tell users what to do rather than what to avoid doing	2.0	Issue	medium	host_supplied-1	No onboarding-style guidance for what to do if user believes they should have access
h10_d_04	The site shows users how to do common tasks where appropriate, such as demonstrations of the site's functionality	2.0	Issue	low	host_supplied-1	No tooltips on error page
h10_d_05	It is easy to contact someone for assistance and a reply is received quickly	2.0	Issue	high	host_supplied-1	'issue tracker' is the only error documentation resource — inappropriate for learner audience

Accessibility and Ease of Access (h11) - 4 checklist items

Item	Score	Status	Confidence	Evidence	Rationale
h11_d_01	0.0	Passed	high	host_supplied-1	401 error page text is readable with clear contrast
h11_d_02	0.0	Passed	high	host_supplied-1	Error page links are keyboard navigable
h11_d_03	2.0	Issue	high	host_supplied-1	"401" status code is not understandable to learners without technical context
h11_d_04	0.0	Passed	high	host_supplied-1	Static error page is robust; no dynamic rendering concerns

Empathetic Engagement and Inclusion (h12) - 6 checklist items

Item	Score	Status	Confidence	Evidence	Rationale
h12_d_01	1.0	Issue	high	host_supplied-1	"Moderator" and "super admin" are privileged technical role labels not meaningful to learners
h12_d_02	0.0	Passed	high	host_supplied-1	No stereotypes on 401 error page
h12_d_03	0.0	Passed	high	host_supplied-1	Error page accessible to diverse abilities
h12_d_04	0.0	Passed	high	host_supplied-1	Error page culturally neutral
h12_d_05	0.0	Passed	high	host_supplied-1	Basic link interaction patterns accessible
h12_d_06	2.0	Issue	high	host_supplied-1	User shown an error with no actionable recovery path; system denies agency

Customer Journey and Satisfaction (h13) - 6 checklist items

Item	Score	Status	Confidence	Evidence	Rationale
h13_d_01	1.0	Issue	medium	host_supplied-1	User arrival at 401 is accidental; some entry context exists
h13_d_02	3.0	Major	high	host_supplied-1	No path forward shown; 401 page is a complete dead end for learners
h13_d_03	2.0	Issue	medium	host_supplied-1	No personalized recovery path or alternative content shown
h13_d_04	2.0	Issue	high	host_supplied-1	GitHub issue tracker as support contact is wrong audience — learners cannot use it
h13_d_05	3.0	Major	high	host_supplied-1	Dead end with no recovery — learner has no next step after 401 error
h13_d_06	2.0	Issue	high	host_supplied-1	Zero trust signals on 401 error page; no brand reassurance or alternative navigation

UX Writing / Content and Tone (h14) - 7 checklist items

Item	Score	Status	Confidence	Evidence	Rationale
h14_d_01	3.0	Major	high	host_supplied-1	"401", "super admin", "moderator" labels are developer jargon inaccessible to learners
h14_d_02	3.0	Major	high	host_supplied-1	No helpful microcopy explaining what the error means or what learner can do
h14_d_03	3.0	Major	high	host_supplied-1	"401 Error", "moderator", "super admin" are all unexplained jargon
h14_d_04	3.0	Major	high	host_supplied-1	No actionable CTA on error page; learner left stranded
h14_d_05	3.0	Major	high	host_supplied-1	Error message is not clear or helpful for learner audience
h14_d_06	2.0	Issue	high	host_supplied-1	No recovery path copy; page ends at error with no alternative offered
h14_d_07	2.0	Issue	medium	host_supplied-1	"Super admin" vs standard user role terminology is internally inconsistent

Evidence Appendix

Evidence ref	Parent	Source type	Quality	Label/title	Bounds/notes	Screenshot/source	Metadata
url-1		url_capture	partial	https://www.oppia.org/admin		https://www.oppia.org/admin
url-2		url_capture	partial	https://www.oppia.org/moderator		https://www.oppia.org/moderator

Owner	Linked finding	Next action	Impact	Effort	Confidence	Supporting roles
Engineer	h11 / h11_d_01	Add text alternatives and non-color cues so critical content remains perceivable across assistive and display settings.	low	Medium	low	Research
Product	h04 / h04_d_07	Standardize repeated components, labels, and visual treatments so the same action looks and behaves the same way everywhere.	low	Low	high
Engineer	h09 / h09_d_02	Rewrite error messages to state what happened, what field or action is affected, and the next recovery step.	low	Medium	low	Research
Designer	h14 / h14_d_03	Replace internal language with short, everyday wording that users can scan at the smallest supported viewport.	low	Low	high
Designer	h14 / h14_d_04	Replace internal language with short, everyday wording that users can scan at the smallest supported viewport.	low	Low	high
Product	h01 / h01_d_06	Mark the current page clearly in navigation and align link labels with destination page titles.	low	Low-Medium	low	Research

Lens / cue	Applies to	Evidence	Why it matters	Caveat
WCAG POUR Principles	h11/h11_d_01	host_supplied-1	The finding is supported by WCAG POUR framing, but the report remains a heuristic audit rather than a compliance certification.	UXHC can cite surface evidence but does not certify WCAG compliance.
Bypass Blocks, Navigation, Headings, And Labels	h01/h01_d_06	host_supplied-1	The finding connects to WCAG navigation guidance: page structure, headings, labels, and bypass paths should help users find the task.	UXHC can flag navigation clarity risk, but source and assistive-technology review are required before WCAG conformance claims.
Error Identification, Suggestion, And Prevention	h09/h09_d_02	host_supplied-1	The finding connects to WCAG input-assistance guidance: errors should be identified, explained, and recoverable without unnecessary re-entry.	UXHC can flag error-support risk, but WCAG evaluation needs rendered form states, programmatic associations, and assistive-technology checks; this is not conformance certification.
Focus Order, Visibility, And Obscured Focus	h01/h01_d_06	host_supplied-1	The finding connects to WCAG focus guidance: keyboard users need a visible, logical focus path that is not hidden by the interface.	UXHC can flag likely focus risk, but keyboard traversal and viewport-state testing are needed before WCAG conformance claims.
Accessible Forms Component Pattern	h09/h09_d_02	host_supplied-1	The finding connects to accessible form-pattern guidance: forms need clear labels, instructions, validation, and recovery paths.	UXHC can flag visible form risks, but programmatic labels, descriptions, and error associations require technical review; this is not WCAG conformance certification.
Reflow, Resize Text, And Text Spacing	h14/h14_d_04	host_supplied-1	The finding connects to WCAG reflow and text-resizing guidance: users should not lose content or function when display needs change.	UXHC can identify likely responsive access risk, but browser zoom and text-spacing tests are required before WCAG conformance claims.

Lens	Source family	Applies to	Why it matters	Caveat / evidence needed
Error Identification, Suggestion, And Prevention	WCAG Accessibility Support	h09/h09_d_02	The finding connects to WCAG input-assistance guidance: errors should be identified, explained, and recoverable without unnecessary re-entry. Applicability: Use when evidence suggests a perceivable, operable, understandable, robust, component, keyboard, focus, contrast, media, authentication, or input-assistance risk.	UXHC can flag error-support risk, but WCAG evaluation needs rendered form states, programmatic associations, and assistive-technology checks; this is not conformance certification. Evidence needed: Requires rendered/code/manual accessibility evidence before any conformance-strength statement.
Accessible Forms Component Pattern	WCAG Accessibility Support	h09/h09_d_02	The finding connects to accessible form-pattern guidance: forms need clear labels, instructions, validation, and recovery paths. Applicability: Use when evidence suggests a perceivable, operable, understandable, robust, component, keyboard, focus, contrast, media, authentication, or input-assistance risk.	UXHC can flag visible form risks, but programmatic labels, descriptions, and error associations require technical review; this is not WCAG conformance certification. Evidence needed: Requires rendered/code/manual accessibility evidence before any conformance-strength statement.
WCAG POUR Principles	WCAG Accessibility Support	h11/h11_d_01	The finding is supported by WCAG POUR framing, but the report remains a heuristic audit rather than a compliance certification. Applicability: Use when evidence suggests a perceivable, operable, understandable, robust, component, keyboard, focus, contrast, media, authentication, or input-assistance risk.	UXHC can cite surface evidence but does not certify WCAG compliance. Evidence needed: Requires rendered/code/manual accessibility evidence before any conformance-strength statement.
Plain Language Principle	UX/UI Support Lens	h14/h14_d_03	The finding is supported by plain-language risk: the wording may slow understanding or recovery. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Plain language depends on audience, domain vocabulary, localization, and risk level. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Jakob's Law / Familiar Conventions	UX/UI Support Lens	h04/h04_d_07	The finding is supported by convention risk: users may bring expectations the interface does not satisfy. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Conventions vary by platform, culture, domain, and user expertise. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Cognitive Load	UX/UI Support Lens	h14/h14_d_03	The finding is supported by cognitive-load risk: users must spend effort understanding the interface before doing the task. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Some complexity is inherent; the design question is whether the system carries the avoidable burden. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.

When	Recommended action
Sprint 3	Add text alternatives and non-color cues so critical content remains perceivable across assistive and display settings.
Sprint 3	Standardize repeated components, labels, and visual treatments so the same action looks and behaves the same way everywhere.
Sprint 3	Rewrite error messages to state what happened, what field or action is affected, and the next recovery step.
Sprint 3	Replace internal language with short, everyday wording that users can scan at the smallest supported viewport.
Sprint 3	Replace internal language with short, everyday wording that users can scan at the smallest supported viewport.
Sprint 3	Mark the current page clearly in navigation and align link labels with destination page titles.

Owner	Linked finding	Next action	Impact	Effort	Confidence
Engineer	h05 / h05_d_04	Review the affected element against Error Prevention and make the next user action clearer, safer, or easier to recover from.	high	Medium	medium
Engineer	h09 / h09_d_02	Rewrite error messages to state what happened, what field or action is affected, and the next recovery step.	high	Medium	medium
Engineer	h09 / h09_d_01	Create a helpful missing-page state with plain language, search, home, and the most likely recovery links.	high	Medium	medium
Product	h01 / h01_d_06	Mark the current page clearly in navigation and align link labels with destination page titles.	high	Medium	medium
Designer	h08 / h08_d_13	Move the task-critical information above the fold and defer supporting details until after the first decision.	high	Low	medium
Designer	h08 / h08_d_01	Make the primary action the clearest visual starting point and reduce secondary actions around it.	high	Low	medium
Product	h01 / h01_d_08	Mark the current page clearly in navigation and align link labels with destination page titles.	medium	Low-Medium	medium
Product	h07 / h07_d_06	Review the affected element against Flexibility and Efficiency of Use and make the next user action clearer, safer, or easier to recover from.	low	Low-Medium	medium
Product	h06 / h06_d_01	Add visible suggestions, filters, or recent choices so users can recognize options instead of remembering them.	low	Low-Medium	medium
Engineer	h03 / h03_d_01	Add or expose search where users naturally look for it so they have a reliable recovery path.	low	Medium	medium

Lens	Source family	Applies to	Why it matters	Caveat / evidence needed
Peak-End Rule	UX/UI Support Lens	h09/h09_d_02, h09/h09_d_01, h03/h03_d_01	The finding is supported by peak-end risk: this moment may heavily shape how users remember the experience. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Memory effects need real user evidence to confirm; use this as a risk lens. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Visual Hierarchy	UX/UI Support Lens	h08/h08_d_13, h08/h08_d_01	The finding is supported by visual hierarchy: the screen does not make the most important next action visually primary. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Hierarchy needs to match the user's current task, not only stakeholder importance. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Accessible Forms Component Pattern	WCAG Accessibility Support	h09/h09_d_02	The finding connects to accessible form-pattern guidance: forms need clear labels, instructions, validation, and recovery paths. Applicability: Use when evidence suggests a perceivable, operable, understandable, robust, component, keyboard, focus, contrast, media, authentication, or input-assistance risk.	UXHC can flag visible form risks, but programmatic labels, descriptions, and error associations require technical review; this is not WCAG conformance certification. Evidence needed: Requires rendered/code/manual accessibility evidence before any conformance-strength statement.
KLM / GOMS Expert Efficiency Models	UX/UI Support Lens	h07/h07_d_06	The finding is supported by expert-efficiency risk: repeated users may spend avoidable effort on extra operations. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	These models are best for routine expert tasks; novice learning and emotional safety need other lenses too. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Inverted Pyramid	UX/UI Support Lens	h08/h08_d_13	The finding is supported by inverted-pyramid content design: users need the most important information first. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Narrative or learning flows may intentionally sequence information differently. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Feedback	UX/UI Support Lens	h05/h05_d_04	The finding is supported by feedback risk: users may not know what happened or what to do next. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Feedback must be timely, perceivable, and tied to the user's action. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.

Lens / cue	Applies to	Evidence	Why it matters	Caveat
Faith-Aware Observance Settings	h12/h12_d_02	host_supplied-1	The finding may need faith-aware review because interaction timing, notifications, or settings could conflict with observance needs.	Faith-aware UX must be opt-in, private, and validated by the relevant tradition or community; it cannot be inferred from identity alone.
Indigenous-Language Orthography And Voice Support	h10/h10_d_04	host_supplied-1	The finding may need target-language validation because spelling, diacritics, pronunciation, or assistive-technology output can affect comprehension and dignity.	Language support should be validated with speakers and local language authorities; UXHC can only flag visible or stated risks.

Lens	Source family	Applies to	Why it matters	Caveat / evidence needed
Goal-Gradient Effect	UX/UI Support Lens	h13/h13_d_05	The finding is supported by goal-gradient risk: users may lack a meaningful sense of progress toward completion. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Progress indicators must reflect real progress and should not create false urgency. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
WCAG POUR Principles	WCAG Accessibility Support	h11/h11_d_01	The finding is supported by WCAG POUR framing, but the report remains a heuristic audit rather than a compliance certification. Applicability: Use when evidence suggests a perceivable, operable, understandable, robust, component, keyboard, focus, contrast, media, authentication, or input-assistance risk.	UXHC can cite surface evidence but does not certify WCAG compliance. Evidence needed: Requires rendered/code/manual accessibility evidence before any conformance-strength statement.
Peak-End Rule	UX/UI Support Lens	h03/h03_d_02	The finding is supported by peak-end risk: this moment may heavily shape how users remember the experience. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Memory effects need real user evidence to confirm; use this as a risk lens. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Goodhart's Law / Metric Gaming	UX/UI Support Lens	h13/h13_d_05	The finding is supported by measurement-risk framing: optimizing a metric may obscure user friction or harm. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Metrics are useful signals when paired with qualitative evidence and guardrails. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Feedback	UX/UI Support Lens	h05/h05_d_04	The finding is supported by feedback risk: users may not know what happened or what to do next. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Feedback must be timely, perceivable, and tied to the user's action. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Bypass Blocks, Navigation, Headings, And Labels	WCAG Accessibility Support	h01/h01_d_06	The finding connects to WCAG navigation guidance: page structure, headings, labels, and bypass paths should help users find the task. Applicability: Use when evidence suggests a perceivable, operable, understandable, robust, component, keyboard, focus, contrast, media, authentication, or input-assistance risk.	UXHC can flag navigation clarity risk, but source and assistive-technology review are required before WCAG conformance claims. Evidence needed: Requires rendered/code/manual accessibility evidence before any conformance-strength statement.

When	Recommended action
Sprint 2	Add or clarify exits, back behavior, and recovery controls so users can leave wrong paths without losing context.
Sprint 2	Mark the current page clearly in navigation and align link labels with destination page titles.
Sprint 3	Add text alternatives and non-color cues so critical content remains perceivable across assistive and display settings.
Sprint 3	Review the affected element against Customer Journey and Satisfaction and make the next user action clearer, safer, or easier to recover from.
Sprint 3	Remove pressure patterns and add calm, clear reassurance around permissions, consequences, and recovery options.
Sprint 3	Review the affected element against Error Prevention and make the next user action clearer, safer, or easier to recover from.
Sprint 3	Review the affected element against Flexibility and Efficiency of Use and make the next user action clearer, safer, or easier to recover from.
Sprint 3	Review the affected element against Help and Documentation and make the next user action clearer, safer, or easier to recover from.
Sprint 3	Rewrite calls to action as specific verb-led labels and make the primary action clearly outrank secondary choices.

Lens	Source family	Applies to	Why it matters	Caveat / evidence needed
Visual Hierarchy	UX/UI Support Lens	h08/h08_d_02, h08/h08_d_04, h08/h08_d_16	The finding is supported by visual hierarchy: the screen does not make the most important next action visually primary. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Hierarchy needs to match the user's current task, not only stakeholder importance. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Fitts's Law	UX/UI Support Lens	h08/h08_d_02, h02/h02_d_03, h08/h08_d_01	The finding is supported by target-acquisition risk: the important action is not easy enough to locate or activate. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Motor models predict tendencies; device, posture, tremor, screen size, and assistive technology can change the risk. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
WCAG POUR Principles	WCAG Accessibility Support	h11/h11_d_01, h12/h12_d_05, h11/h11_d_02	The finding is supported by WCAG POUR framing, but the report remains a heuristic audit rather than a compliance certification. Applicability: Use when evidence suggests a perceivable, operable, understandable, robust, component, keyboard, focus, contrast, media, authentication, or input-assistance risk.	UXHC can cite surface evidence but does not certify WCAG compliance. Evidence needed: Requires rendered/code/manual accessibility evidence before any conformance-strength statement.
Affordance and Signifiers	UX/UI Support Lens	h02/h02_d_03, h04/h04_d_08, h02/h02_d_02	The finding is supported by affordance/signifier risk: available actions are not visibly legible. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Affordances can be physical, learned, or signaled; validate with user context. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Jakob's Law / Familiar Conventions	UX/UI Support Lens	h04/h04_d_04, h04/h04_d_07, h07/h07_d_08	The finding is supported by convention risk: users may bring expectations the interface does not satisfy. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Conventions vary by platform, culture, domain, and user expertise. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
ISO 9241-11 Usability In Context	ISO UX/UI/HCI Support	h13/h13_d_01, h07/h07_d_01, h07/h07_d_05	This finding connects to ISO 9241-11 style usability-in-context framing: usable for whom, for what task, and in what context. Applicability: Use when the finding benefits from ISO-informed framing around context of use, interaction quality, evidence traceability, process quality, or operational risk.	ISO-informed support reference only; not formal ISO standards compliance, conformance, certification, procurement proof, or legal assurance. Evidence needed: Requires project, process, technical, or audit evidence before standards-strength claims.

Owner	Linked finding	Next action	Impact	Effort	Confidence
Research	h13 / h13_d_03	Review the affected element against Customer Journey and Satisfaction and make the next user action clearer, safer, or easier to recover from.	high	Low-Medium	high
Product	h01 / h01_d_06	Mark the current page clearly in navigation and align link labels with destination page titles.	high	Low-Medium	high
Research	h12 / h12_d_04	Review the screen through emotional, cultural, and situational user contexts, then remove the highest-friction exclusion point.	medium	Low-Medium	high
Engineer	h05 / h05_d_04	Review the affected element against Error Prevention and make the next user action clearer, safer, or easier to recover from.	medium	Medium	high
Product	h07 / h07_d_06	Review the affected element against Flexibility and Efficiency of Use and make the next user action clearer, safer, or easier to recover from.	medium	Low-Medium	high
Research	h12 / h12_d_01	Review the screen through emotional, cultural, and situational user contexts, then remove the highest-friction exclusion point.	low	Low-Medium	medium
Research	h12 / h12_d_06	Expose user controls for notifications, permissions, personalization, or recovery where users can find them quickly.	low	Low-Medium	medium
Engineer	h09 / h09_d_02	Rewrite error messages to state what happened, what field or action is affected, and the next recovery step.	low	Medium	medium
Product	h02 / h02_d_01	Review the affected element against Match Between System and the Real World and make the next user action clearer, safer, or easier to recover from.	low	Low-Medium	medium
Product	h06 / h06_d_03	Rewrite links so each label describes the destination or result before the user clicks.	low	Low-Medium	medium

Lens / cue	Applies to	Evidence	Why it matters	Caveat
Dadirri / Deep Listening	h12/h12_d_04	host_supplied-1	The finding suggests a need for slower, relational feedback or support before the interface claims to understand user context.	Deep listening is culturally grounded in specific context and cannot be claimed from a generic interview or survey pattern.
Faith-Aware Observance Settings	h12/h12_d_06	host_supplied-1	The finding may need faith-aware review because interaction timing, notifications, or settings could conflict with observance needs.	Faith-aware UX must be opt-in, private, and validated by the relevant tradition or community; it cannot be inferred from identity alone.
Yarning And Reciprocal Story	h12/h12_d_01	host_supplied-1	The finding may need reciprocal story or reporting-back practices before the team treats user feedback as settled evidence.	Yarning requires relationship, cultural safety, and local involvement; it is not a label for any informal conversation.

Lens	Source family	Applies to	Why it matters	Caveat / evidence needed
Labels, Instructions, And Input Purpose	WCAG Accessibility Support	h02/h02_d_01, h06/h06_d_03	The finding connects to WCAG labels-and-instructions guidance: users need visible and programmatic cues for what controls mean. Applicability: Use when evidence suggests a perceivable, operable, understandable, robust, component, keyboard, focus, contrast, media, authentication, or input-assistance risk.	UXHC can flag labeling risk, but programmatic label associations and accessible-name checks require technical review; this is not WCAG conformance certification. Evidence needed: Requires rendered/code/manual accessibility evidence before any conformance-strength statement.
KLM / GOMS Expert Efficiency Models	UX/UI Support Lens	h07/h07_d_06	The finding is supported by expert-efficiency risk: repeated users may spend avoidable effort on extra operations. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	These models are best for routine expert tasks; novice learning and emotional safety need other lenses too. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Peak-End Rule	UX/UI Support Lens	h09/h09_d_02	The finding is supported by peak-end risk: this moment may heavily shape how users remember the experience. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Memory effects need real user evidence to confirm; use this as a risk lens. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Accessible Forms Component Pattern	WCAG Accessibility Support	h09/h09_d_02	The finding connects to accessible form-pattern guidance: forms need clear labels, instructions, validation, and recovery paths. Applicability: Use when evidence suggests a perceivable, operable, understandable, robust, component, keyboard, focus, contrast, media, authentication, or input-assistance risk.	UXHC can flag visible form risks, but programmatic labels, descriptions, and error associations require technical review; this is not WCAG conformance certification. Evidence needed: Requires rendered/code/manual accessibility evidence before any conformance-strength statement.
Information Scent	UX/UI Support Lens	h06/h06_d_03	The finding is supported by information scent: navigation cues do not clearly predict destination value. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Information scent depends on user goals and vocabulary. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.
Feedback	UX/UI Support Lens	h05/h05_d_04	The finding is supported by feedback risk: users may not know what happened or what to do next. Applicability: Use only when it helps explain an evidence-backed UXHC finding or bounded host observation.	Feedback must be timely, perceivable, and tied to the user's action. Evidence needed: Visible interface evidence, source context, or a stated evidence limit must remain the basis for the finding.

Oppia.org — Logged-In LearnerUX Audit Report

Critical Findings Across All CUJs

Jump to CUJ

Mission Context

Important information may appear too late

Heuristic Scorecard - AI Audit, 14 Heuristics

Findings - Prioritized Fix Order

Important information may appear too late

Page clutter competing with primary actions

Primary action hierarchy is not clear

Primary action hierarchy is not clear

Visual hierarchy is not supporting the task

Visual hierarchy is not supporting the task

Visual hierarchy is not supporting the task

Visual hierarchy is not supporting the task

Consistency and trust cues need review

Consistency and trust cues need review

Owner-Role Triage Matrix

What Is Working Well

Evidence Limits

WCAG-Informed Accessibility Readiness

Cultural Context Integrity Advisory

Recommended Next Validation Steps

Supporting UX Laws And Principles

Prioritized Fix Roadmap

High-Impact / Low-Effort Micro-Solutions

Audit Scope and Omitted Profiles

Complete Checklist Scores

Evidence Appendix

Mission Context

Important information may appear too late

Heuristic Scorecard - AI Audit, 14 Heuristics

Findings - Prioritized Fix Order

Important information may appear too late

Page clutter competing with primary actions

Visual hierarchy is not supporting the task

Visual hierarchy is not supporting the task

Visual hierarchy is not supporting the task

Visual hierarchy is not supporting the task

Consistency and trust cues need review

Consistency and trust cues need review

Consistency and trust cues need review

Consistency and trust cues need review

Owner-Role Triage Matrix

What Is Working Well

Evidence Limits

WCAG-Informed Accessibility Readiness

Cultural Context Integrity Advisory

Recommended Next Validation Steps

Supporting UX Laws And Principles

Prioritized Fix Roadmap

High-Impact / Low-Effort Micro-Solutions

Audit Scope and Omitted Profiles

Evidence Gallery

Additional Evidence

Complete Checklist Scores

Evidence Appendix

Mission Context

Important information may appear too late

Heuristic Scorecard - AI Audit, 14 Heuristics

Findings - Prioritized Fix Order

Important information may appear too late

Page clutter competing with primary actions

Primary action hierarchy is not clear

Primary action hierarchy is not clear

Visual hierarchy is not supporting the task

Visual hierarchy is not supporting the task

Visual hierarchy is not supporting the task

Visual hierarchy is not supporting the task

Consistency and trust cues need review

Consistency and trust cues need review

Owner-Role Triage Matrix

What Is Working Well

Evidence Limits

WCAG-Informed Accessibility Readiness

Cultural Context Integrity Advisory

Recommended Next Validation Steps

Supporting UX Laws And Principles

Prioritized Fix Roadmap

High-Impact / Low-Effort Micro-Solutions

Oppia.org — Logged-In Learner
UX Audit Report