HTML Interview Questions: Semantics and Accessibility
Thirty questions on the topic that appears in almost every front end interview now, and where vague answers are most obvious.
Markup that works for every reader and every input device.
31 notes tagged
Thirty questions on the topic that appears in almost every front end interview now, and where vague answers are most obvious.
The final build. Everything in the path applied to one real site, with a defined standard it has to meet before it is finished.
Data tables, a persistent sidebar, status indicators and a dialog. The interface where dense information has to stay navigable.
Filters, sorting, pagination and a product grid. The page where canonical tags, crawl budget and accessible dynamic updates all become real problems.
Sidebar navigation, an on this page menu, code blocks that scroll, a search box and deep links that survive a sticky header. The hardest layout to get...
Three forms that cover almost every input type, validation pattern and accessibility requirement you will meet in real work.
A grid of project cards with a filter, responsive images and a case study page. The project where card markup, image performance and clickable regions...
Everything worth verifying before a page goes live, grouped so it can be worked through in about twenty minutes.
The Elements panel shows the live DOM, not your file. That difference is why it is the first place to look when markup behaves in a way the source doe...
Automated tools find about a third of problems. Here is what they catch, what they miss, and a manual routine that takes fifteen minutes.
Contrast ratios that meet the guidelines, never relying on colour alone, and honouring the reduced motion preference. Mostly CSS, entirely part of the...
ARIA fills gaps that HTML cannot. It also breaks pages when used carelessly. The rules, the attributes worth knowing, and the ones to leave alone.