Frontend developer CV: live links, accessibility and frameworks
A frontend developer CV is built around live links: each project line points to a page the reader can open, names the framework and gives one measured result, such as load time or the accessibility level reached.1
Written 13 October 2026. CitedCV. How we write our guides
Before you write: open every link you will share
A reviewer of a frontend CV clicks. A broken demo, a login wall or a page full of placeholder text costs more than a missing bullet point. Test the links first, then write the lines around what works.
- Open each live link on a phone over mobile data, not on your desk machine with a warm cache.
- Tab through the main flow with the keyboard alone. If focus disappears or gets stuck, fix it or do not share that project.
- Remove placeholder text, test accounts with silly names and console errors a reviewer could see.
- Check that the code link points to the repository for that exact demo, with a README that says how to run it.
- Write down one number per project now: a load-time figure, a bundle size, an accessibility issue count before and after.
Where to host a portfolio
GitHub Pages hosts static HTML, CSS and JavaScript at an address on github.io. Its documented limits are a published site of up to 1 GB and a soft bandwidth limit of 100 GB a month, and GitHub says it is not meant as free hosting for an online business or e-commerce. A personal portfolio fits well inside that.
What employers look at first
The US Bureau of Labor Statistics describes front-end developers as the people who create the technical features for a website's look, building the layout and integrating graphics, applications and content, in languages such as HTML and JavaScript. It puts the education for web developers anywhere from a high school diploma to a bachelor's degree, and says some candidates need no specific credentials when prior work or projects show what they can do.
| First check | Source that points to it | Your answer on the CV |
|---|---|---|
| Work the reader can see | BLS: abilities can be shown through prior work or projects | A portfolio table with live and code links |
| The framework in the posting | O*NET's in-demand list for web developers includes React, TypeScript, Vue.js, GraphQL and Git | A stack cell per project, spelled as in the ad |
| A recognised route in | O*NET survey: 46% bachelor, 17% post-secondary certificate, 17% associate degree; NCS: Level 3 and Level 4 apprenticeships | Education or apprenticeship, or a first paid role |
| Code quality | O*NET task: evaluate code to ensure it is valid, properly structured and meets industry standards | Testing, linting and review lines |
| Accessibility and performance | Rules and thresholds in the next two sections | A line each, with the standard named |
Accessibility: why it now earns its own line
The Web Content Accessibility Guidelines 2.2 are a W3C Recommendation built on four principles (perceivable, operable, understandable, robust) with three conformance levels, A, AA and AAA. Version 2.2 added criteria such as Focus Not Obscured (Minimum), Target Size (Minimum) and Accessible Authentication (Minimum). The US rule and the Turkish checklist below name WCAG directly.
| Market | What applies | Standard named |
|---|---|---|
| European Union | The European Accessibility Act has applied since 28 June 2025; covered services include e-commerce platforms, online banking operations and e-books | Accessibility requirements set in the directive and in each member state’s law |
| United States | The ADA Title II rule for state and local government web content and mobile apps; after an interim final rule of 20 April 2026, compliance is due 26 April 2027 (50,000 people or more) or 26 April 2028 | WCAG 2.1 Level AA |
| Türkiye | A 2025 Presidential circular covers public bodies, banks, private hospitals and schools, transport firms and e-commerce providers; the Family Ministry publishes the checklist | An A-level checklist based on WCAG 2.2 (31 principles, 122 questions) |
How to write accessibility work
- Name the standard and level: WCAG 2.2 AA, WCAG 2.1 AA.
- Name the scope: the checkout flow, the design-system button set, the sign-up form.
- Name the method: keyboard-only test, a screen reader you used, an automated checker, an external audit.
- Give the result: issues fixed, criteria now met, an audit passed.
- Never write that a whole site is fully compliant unless an audit says so, and you can show it.
Performance figures that mean something
Google publishes the thresholds most teams use. Core Web Vitals count as good at a Largest Contentful Paint of 2.5 seconds or less, an Interaction to Next Paint of 200 milliseconds or less and a Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads.
Lab or field
Say which kind of number you quote. A lab score from your own machine is useful in a portfolio note; a field figure from real users is what a product team trusts. 'LCP at the 75th percentile went from 3.9 s to 2.1 s on mobile' tells the reader both the metric and the measurement.
Frameworks: name the job each one did
- One main framework, with the version family when it matters to the posting (React 18, Angular 17).
- How the app rendered: single-page app, server-rendered, static, and why that choice fit.
- State, data fetching and testing tools only where you made real decisions with them.
- Migrations are strong lines: what moved, how long it took, what broke less afterwards.
- A framework you tried over a weekend stays off the CV.
HTML and CSS still count
Semantic HTML and CSS layout are where most accessibility and layout-shift problems are solved, so list them, and back them with a line about a component or layout you built without leaning on a framework.
Example: portfolio table and experience lines
Example only. Arda Şahin is invented; the links use the reserved example.com domain and every figure is a placeholder. Replace them with your own links and numbers you can show.
| Project | Live and code | Stack | Measured result |
|---|---|---|---|
| Recipe planner | recipes.example.com; repository linked from the page footer | React, TypeScript, Vite | Mobile LCP 1.8 s in field data from 2,100 visits |
| Accessible date picker | datepicker.example.com; npm package and repository | TypeScript, Web Components | Keyboard and screen reader tested; meets WCAG 2.2 Target Size (Minimum) |
| Transit timetable clone | transit.example.com; repository | Vue.js, Pinia, Playwright | 48 end-to-end tests; CLS 0.02 |
Frontend Developer, an online grocery company, 2023 to present
- Rebuilt the checkout in React and TypeScript; 75th-percentile mobile LCP from 3.9 s to 2.1 s, measured over four weeks of field data.
- Led the WCAG 2.1 AA fixes for checkout and sign-up: 41 issues from an external audit closed in two sprints, retest passed.
- Built 22 shared components in the design system with Storybook and visual tests, now used by three product teams.
Each line answers what, how measured and for whom. The portfolio table does the same for work outside a job, so a reviewer can verify a claim in one click.
Skills table for frontend roles
| Area | What to list | Evidence that works |
|---|---|---|
| Markup and styling | Semantic HTML, CSS layout (Grid, Flexbox), a CSS approach | A component or layout built from scratch |
| Language | JavaScript, TypeScript | Type coverage added or runtime errors removed |
| Framework | One main framework, one secondary at most | A shipped feature or migration |
| Accessibility | WCAG version and level, testing methods | Issues fixed in a named flow |
| Performance | Core Web Vitals, bundle analysis | A before and after figure with its source |
| Testing | Unit, component, end-to-end tools | Test counts or flaky tests removed |
Certificates, licences and titles
None of the official profiles we read (BLS, O*NET, the National Careers Service) lists a licence for frontend work. If a posting asks for Frontend Engineer and you have no engineering degree, check the title rule in the country first; the computer engineer guide covers Türkiye and links the German one.
Applying abroad
The Germany developer guide covers the Blue Card for IT specialists and German CV structure; the Netherlands developer guide covers English-language teams and sponsoring employers. Read them for the country rules; this page stays with the frontend CV itself.
Proof: the pages behind each claim
Each source was read on 13 October 2026; the links sit under Sources.
| Claim | Source |
|---|---|
| Front-end role description, education range, projects instead of credentials | BLS, Web Developers and Digital Designers |
| In-demand technologies, education survey, task wording | O*NET OnLine 15-1254.00 |
| Apprenticeship routes, junior start | National Careers Service, Web developer |
| Four principles, levels, criteria new in 2.2 | W3C, WCAG 2.2 |
| EAA date and covered services | AccessibleEU, European Commission |
| WCAG 2.1 AA and compliance dates after the 2026 extension | ADA.gov, Title II web rule fact sheet |
| Türkiye checklist: WCAG 2.2, A level, 31 principles, 122 questions; who is covered | Ministry of Family and Social Services |
| Core Web Vitals thresholds and the 75th percentile | web.dev |
| GitHub Pages size, bandwidth and use limits | GitHub Docs |
Accessibility rules and deadlines change. Check the linked official page before relying on a date.
Where this guide ends
- Design-led roles judged on research and case studies: the UX/UI designer guide.
- Server-side work, APIs and databases: the backend guide.
- How developer CVs change from junior to senior in general: the software developer guide.
Next steps
- Test every link on a phone and with the keyboard.
- Build the portfolio table: project, live link, code, stack, one number.
- Add one accessibility line and one performance line to your current role.
- Match the framework spelling to each posting.
CitedCV can turn the projects, links and figures you enter into a CV in English, Turkish or German; it writes only from what you gave it, so the numbers on the page stay yours.
Questions people ask
Should a frontend developer CV include a portfolio link?
Yes, and ideally one link per project: a live page and its code. A reviewer of frontend work expects to open what you built.
How do I show accessibility skills on a CV?
Name the standard and level, the flow you worked on, how you tested it and the result, for example audit issues closed in checkout against WCAG 2.1 AA.
Which frameworks should I list on a frontend CV?
The one you use most, plus at most one more, each tied to a project or job line. Spell them as the posting does.
Is WCAG 2.2 required by law?
It depends on the market. The US Title II rule names WCAG 2.1 AA; the checklist under Türkiye’s 2025 circular is based on WCAG 2.2.
Can I get a frontend job without a degree?
Often yes. BLS puts web developer education from a high school diploma to a bachelor’s, and says projects or prior work can show ability.
What if my strongest frontend work is behind a login?
Describe it in the experience lines with figures, and add a public project or a short recorded walkthrough you are allowed to share.
What performance numbers should a frontend CV mention?
Core Web Vitals are the common ones: LCP, INP and CLS, with Google's good thresholds of 2.5 s, 200 ms and 0.1.
Sources
- U.S. Bureau of Labor Statistics, Occupational Outlook Handbook: Web Developers and Digital Designerswww.bls.gov/ooh/computer-and-information-technology/web-developers.htm
- O*NET OnLine, 15-1254.00 Web Developerswww.onetonline.org/link/summary/15-1254.00
- National Careers Service, Web developer job profilenationalcareers.service.gov.uk/job-profiles/web-developer
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2www.w3.org/TR/WCAG22/
- AccessibleEU (European Commission), The EAA enters into forceaccessible-eu-centre.ec.europa.eu/content-corner/news/new-era-inclusion-begins-eaa-enters-force-2025-06-27_en
- ADA.gov, Fact sheet: rule on web and mobile app accessibility for state and local governmentswww.ada.gov/resources/2024-03-08-web-rule/
- T.C. Aile ve Sosyal Hizmetler Bakanlığı, Web siteleri ve mobil uygulamaların erişilebilirliği genelgesiaile.gov.tr/eyhgm/haberler/web-siteleri-ve-mobil-uygulamalarin-erisilebilirligi-cumhurbaskanligi-genelgesi-yayimlandi/
- web.dev, Web Vitalsweb.dev/articles/vitals
- GitHub Docs, GitHub Pages limitsdocs.github.com/en/pages/getting-started-with-github-pages/github-pages-limits