Changes made, not standards recited: an accessibility audit example for Week 6 of HLTH 8152 that logs each barrier found in one composite module, the fix applied, and its cost. Searches like "hlth 8152 week 6 assignment example", "hlth8152 week 6 sample" and "hlth 8152 week 6 example" land here.
What a finished HLTH 8152 Week 6 accessibility audit looks like
A short method section opens the audit: three checks, keyboard only, screen reader, audio muted, each named with what it tests. The Web Content Accessibility Guidelines appear here in a sentence naming their four principles, perceivable, operable, understandable and robust. The body is a change log of seven entries. The injector-step ordering used drag and drop, unusable by keyboard, and was rebuilt as numbered selections. Symptom videos had captions but no description of visual cues, so audio description was added for hives and swelling. Every clip showed hives on light skin only; clips were reshot across a range of skin tones. Red and green feedback gained text labels. A timer on the decision item became adjustable. Every entry notes what the change cost in time or scope.
How a HLTH 8152 Week 6 example is structured
Stating the method before the findings lets a reader judge what the audit could and could not catch; an audit that never says how it looked cannot be trusted about what it missed. The guidelines are named once, early, and their principles are used to group entries rather than being quoted clause by clause, which keeps the document about the module. Entries follow a fixed form, barrier, change, cost, so each can be read alone and the reader sees that every finding produced an action. Ordering runs from barriers that blocked a task outright to those that slowed it, which puts the drag-and-drop failure first. The skin-tone entry sits among the rest instead of being moved to an equity section of its own, because it is an access barrier to recognition. Recording cost keeps the audit honest about trade-offs.
Three ways of looking
Keyboard only, screen reader, sound muted. Each check is named with the kind of barrier it can reveal and the kind it cannot.
Drag and drop, rebuilt
Ordering the injector steps required a mouse. The activity became numbered selections that a keyboard or switch can operate.
Cues described, not just captioned
Captions carried the dialogue but not the hives or swelling. Audio description now names the visual cues the decision depends on.
Skin tones on screen
Every symptom clip showed hives on light skin. Reshot clips cover a range of skin tones, since recognition is the objective.
Color and time
Red and green feedback gained text labels, and the decision timer became adjustable. Each change is logged with what it cost.
Where marks go in HLTH 8152 Week 6
Accessibility audits in this course reward evidence of change more than knowledge of the standard, and each log entry pairs a barrier with the specific alteration it caused. The method criterion is met by naming the three checks and what each could reveal. Literature use counts, satisfied by the guidelines framing the entries without replacing them. Weak audits share habits. A page listing success criteria with ticks beside them shows compliance claimed, not barriers found. Promising captions and alt text in general terms, with no element named, describes intentions. Treating accessibility as a closing section after the design is finished is the pattern the course exists to break. Omitting cost implies every change was free, and a grader will read that as an audit nobody actually ran.
Get a HLTH 8152 Week 6 example written to your instructions
A list of the elements and interactions in your module, with the week 6 prompt and rubric, is enough for an audit written as a change log: barrier, change and cost for each entry. Allow 24-48 hours; the first is free of charge. The seven entries here come from a composite module; yours should come from testing your own.
HLTH 8152 Week 6 questions, answered
Does the audit need to cite the accessibility guidelines?
Most prompts expect the standard named, and the example does so in one sentence using its four principles to group entries. What earns credit is the change each finding produced. An audit quoting success criteria at length without tying any to a module element reads as research, not an audit of the thing you built.
Why is skin tone in an accessibility audit?
Because the module's objective is recognizing symptoms, and a learner who has only seen hives on light skin may not recognize them on darker skin. That is a barrier to the task, whatever category it is filed under. Some sections would place it under representation instead; the example keeps it in the log because it changed the module the same way the others did.
How many changes should the audit document?
Enough to show the module was tested in more than one way. The example logs seven, grouped by what they blocked. A long list of minor fixes is less persuasive than a few barriers that would have stopped a participant entirely. Your prompt may set a number; if not, the checks you run decide it.