Frontend engineer requirements, with the quote you would need

Frontend postings ask for a framework, accessibility, and partnership with design. The evidence is a screen someone used. Naming React in a skills row does not show that you handled forms, performance, or keyboard access.

Examples on this page are fictional composites, not customers and not testimonials.

Often required

A UI someone other than you used
Internal tool or public site. Say who it was for.
The framework only if you shipped with it
A course project can be quoted if it is on the resume and labeled as a project.
A specific interface problem
Forms, empty states, slow lists, or localization. Pick the one you wrote about.
Design handoff
Figma, a spec, or pairing with a designer, quoted from your text.
Accessibility or browser constraints
Only if you mention a check, a bug, or a user who needed it.

Often preferred, and easy to fake

Tests for UI behavior
Performance work with a measurement
A design system you extended

What a citation looks like

React

“Rebuilt the claims search in React so adjusters could filter by date without a full reload.”

React is tied to a user and a behavior. That supports React. It does not support Next.js.

Accessibility audit

“No sentence.”

Using semantic HTML once, if unstated, is not an audit. Leave the requirement unsupported.

The gap people paper over

Do not add WCAG levels, Lighthouse scores, or a design system you only consumed as a user of the app.

Questions

Is HTML and CSS enough when they ask for React?

It is a partial overlap at best, and often unsupported. Say what you built, and do not rename it.

Should the resume be one column?

Yes for the export from this app. Tables and text boxes are omitted because many parsers handle them poorly. That is not a guarantee a given parser will accept the file.

Related: Software engineer, UX designer

Check your resume against a real posting