Conversation
fangkristen
commented
Apr 1, 2026
- No discrepancies across browsers (ex: chrome vs safari)
- Accessibility functions
- Pages can scale without distorting page
- No dead links
- Navbar is consistent across the site
- Pages are screen-reader accessible
- Contrast meets standards for accessibility
- Pages are keyboard accessible
- Code is cleaned up and bug-free (ex: debug statements removed)
| const activeOptions = STAGE_OPTIONS[currentStage] || []; | ||
| const isFinalStage = currentStageIndex === stages.length - 1; | ||
|
|
||
| const handleNext = () => { |
There was a problem hiding this comment.
This function is what's causing the non-green state when the sentence section locks.
the nextStage func and lockCurrentStage are happening almost simultaneously, then justLockedKey is cleared immediately.
Call lockCurrentStage first, then delay nextStage and clearJustLockedKey so the pop animation finishes before moving onto the next stage
| {currentStage} | ||
| </h2> | ||
| <div className="tw-text-sm tw-font-semibold tw-text-darkGray"> | ||
| Score: {totalScore}/{passingScore} |
There was a problem hiding this comment.
Should Score: "n/6" be visible during selection? It may lead to students selecting choices for score rather than choosing the best answer. It'd be best to hide it until they click complete, allowing them to see the completion message popup under the quiz.
| questionTotal={stages.length} | ||
| /> | ||
|
|
||
| {allStagesAnswered && ( |
There was a problem hiding this comment.
allStagesAnswered is currently based on selections so the second user clicks an option on phase 4, it completes before the user clicks the complete button., removing the point of the complete button. You can use lockedStages instead so completion happens only after all stages are locked (complete button is clicked/all sentence sections are green)
DarlynGomez
left a comment
There was a problem hiding this comment.
The selection and scoring works well! The main fix needed it the locked stage behavior.