Recap and Feedback
We connected layout and semantic HTML to the tasks people need to complete. Responsive layouts kept information available as space and text changed; native headings, links and controls provided a meaningful structure.
The date-range form showed how an interface supports recovery: preserve proposed input, explain the error, and help the user reach the affected field. Focus directed attention after submission, while background updates changed an existing status region without moving focus.
Browser checks protected retained values and keyboard recovery. An audit connected a barrier to its task, conditions, repair and retest, recording manual observations and the limits of automated checks.
This part had also the last marketplace project exercises.
For your own notes, follow an invalid form submission through correction. What should remain available, where should focus move, and which parts would you check with an automated test or manual investigation?
Use the feedback form below to describe what helped your learning and what needs clarification.
Reflection and feedback
0 / 5 points
Consider the following statements and answer them based on your experiences from studying the materials and working on the assignments in this part. When answering the numeric statements, answer them so that value 1 means that you strongly disagree with the statement, and value 7 means that you strongly agree with the statement. Please be as honest as possible when answering. The feedback will be used to improve the course.