HTML5 development
Build modern, semantic, and accessibleweb applications with HTML5 development
Good HTML is what search engines read, what screen readers announce and what still works when a script fails. We write templates and front-end code against the current standard, and repair older markup that gets in the way of accessibility and search.
What HTML work covers
Rarely a project alone, but often where front-end quality is won or lost.
Design to templates
Hand-written HTML and CSS from your design, ready for a developer or a CMS to fill with content, using headings, landmarks and lists that match the meaning of the page.
Accessibility fixes
Replacing clickable divs with real buttons, adding labels to forms and fixing heading order and keyboard traps, in the code rather than with an overlay widget.
Replacing script-heavy components
Swapping custom modals and menus for native elements where browser support allows, leaving less JavaScript to load and maintain.
Structured markup for search
Correct titles, canonical tags and JSON-LD added to templates, so each page describes itself accurately to search engines.
The standards, as of October 2026
HTML5 is the popular name for what is now a continuously updated standard.
There is no version to wait for
The WHATWG HTML Standard is a living document with no version number, and W3C and WHATWG agreed in 2019 to work on a single version. Its own introduction answers "Is this HTML5?" with "Yes".
Native dialog and popover
MDN lists dialog as Baseline widely available, across browsers since March 2022. The Popover API is Baseline 2025, so it is newer: check your audience's browsers before relying on it.
WCAG 2.2 is the current target
WCAG 2.2 is the W3C Recommendation in force, in its December 2024 version. A future major version is described by W3C as a multi-year effort, so there is no reason to wait for it.
Accessibility and the law
We are not lawyers, but buyers selling into the EU should know this.
European Accessibility Act
According to the European Commission, the Act has applied since 28 June 2025 to key products and services, including phones, computers, e-books, banking and electronic communications. It is a directive, so national rules differ.
Small businesses
Microenterprises providing services are exempt, and some transition periods run to 2030. Ask your legal adviser whether and how it applies to you before scoping work.
What we will and won't say
We build to WCAG 2.2 AA as a target and test with keyboard, a screen reader and automated tools. We don't certify conformance. That needs an independent audit, ideally with disabled users.
Why automated checks aren't enough
Scanners catch missing labels and low contrast. They can't tell whether alt text makes sense or whether a page reads in a sensible order, so someone has to check those by hand.
How HTML work runs
Writing the outline first avoids most of the later accessibility repair.
Outline the page
Before styling, we write the heading structure and landmarks, which shows up problems in the content order early.
Write the markup, then style it
The page has to make sense with CSS turned off. Styling then builds on that rather than hiding structural problems.
Test without a mouse
We tab through every interactive element and use a screen reader on the key journeys, then run automated checks.
Validate and hand over
Templates are checked with the Nu HTML Checker and handed over with notes on the patterns to reuse, so later pages stay consistent.
How HTML work is scoped
Priced by the number of distinct page templates, not by pages of content.
A handful of templates can serve a very large site, so templates are what we count when we quote a fixed scope. An accessibility fix starts with a review of a sample of your key journeys. For ongoing front-end help, time is charged from $20/h in USD, invoiced in USD, GBP, EUR or INR.
We work as an engineering team in India with 3–5 hours of overlap with the UK and Europe; US calls by appointment. HTML work usually sits inside something larger, so see our WordPress and Next.js pages if templates need to connect to a CMS or an application.
Why this page shows no client sites
Most of our work is delivered under NDA, so many projects cannot be named.
You can judge any supplier's markup without a client reference, though: run their own website through a validator and a screen reader. It is a fairer test than a portfolio thumbnail.
Questions about HTML work
Mostly about accessibility and whether this is worth paying for separately.
Is HTML5 still current?
Can you make our site compliant?
Will an accessibility overlay widget solve this?
Does semantic HTML help SEO?
Send us the page that worries you most
A link and a note of who needs to use it is enough. We will look at the structure and tell you what we would fix first.
We reply within one business day (IST).