Courses
HTML and CSS Intermediate: Layouts That Don't Fall Apart on Phones
Final Check: HTML and CSS Intermediate
Fifteen scenario questions across the whole course. If you get twelve or more right, you're ready for HTML and CSS Advanced.
Course content
Join this Course
Sign in to save your progress.
-
Layout Without Float Hacks
-
Flexbox for Real Rows and Columns
-
CSS Grid When Flexbox Isn't Enough
-
-
-
Pages That Survive Phones
-
Responsive Layout With Media Queries That Make Sense
-
Mobile-First Without Building Everything Twice
-
Images and Typography That Scale Without Breaking
-
-
-
Components You Can Reuse
-
Navigation That Still Works on a Narrow Screen
-
Cards, Buttons and Shared Styles Across Pages
-
Custom Properties (CSS Variables) You Won't Regret
-
-
-
Forms and States That Look Finished
-
Focus, Hover and Disabled States People Can See
-
Accessible Forms: Labels, Errors and Keyboard Paths
-
-
-
Keep Layouts From Fighting You
-
Fix Overlap, Overflow and Z-Index Without Guessing
-
Organize CSS So You Can Find Things Later
-
-
- Final Check: HTML and CSS Intermediate
1.
Flexbox is primarily for…
2.
Grid is a better default when…
3.
gap on a flex container…
4.
Mobile-first media queries typically use…
5.
A breakpoint should be chosen by…
6.
max-width: 100%; height: auto on images…
7.
Custom properties inherit, which means…
8.
:focus-visible is useful because…
9.
aria-invalid="true" plus an error id in aria-describedby…
10.
Horizontal overflow on mobile is usually fixed by…
11.
position: relative on a parent is often used to…
12.
Shared .btn and .card classes help because…
13.
scroll-padding-top exists mainly to…
14.
Organizing CSS into base / layout / components helps you…
15.
Prefer fixing overflow causes over body { overflow-x: hidden } because…
About
Fifteen scenario questions across the whole course. If you get twelve or more right, you're ready for HTML and CSS Advanced.
- Duration
- 15 min
- Last update
- 08/20/2026
Was this helpful?
0
0
Comments (0)
Sign in to commentNo comments yet.