HTML semantics and accessibility for product interfaces
We build semantic HTML interfaces for product teams, with labelled forms and keyboard behavior reviewed as part of the component contract. We align implementation and testing with your accessibility acceptance target.
01Overview
HTML gives page content structure and meaning
HTML describes the structure and meaning of page content. Browsers expose that structure to assistive software through an accessibility tree. HTML is maintained as a Living Standard. CSS controls styling; browser APIs such as media and storage belong to the HTML5 capability discussion.
02Capabilities
Semantic elements, component contracts and readable content
We define the markup users and assistive technology interact with, including inside shared components.
- Semantics
Native elements with meaningful roles
We use landmarks, real headings, labelled fields and data tables to give screen readers meaningful structure. Native button behavior includes keyboard activation; each element provides its own semantics and interaction. We review focus and keyboard operation in the completed interface.
- Components
Markup as part of the component contract
In React and other component libraries, the rendered element is part of the component contract. ARIA describes roles, states and properties for assistive technology; it does not implement keyboard behavior. We specify these responsibilities through design systems work and test custom interactions in the agreed browser and assistive-technology combinations.
- Machines
Document structure for search and extraction
We align headings with the document and use meaningful link text, so a search engine can interpret the page's structure. Essential content stays in the response, with structured data where appropriate. We apply the same approach to public content in fintech products. In our own website migration, Astro builds complete plain HTML ahead of time.
03Fit
Match the markup work to the interface requirement
Use the interface's behavior and acceptance target to decide whether the work belongs in markup, components or styling.
| Your situation | What we recommend |
|---|---|
| Keyboard users cannot reach a control | Review the shared componentCheck whether a clickable container should be a native button, then test keyboard access and focus where it is reused. A React component carries that element choice to each consumer. |
| Custom controls have ARIA but incomplete keyboard behavior | Native semanticsStart with the appropriate native element. Add ARIA roles, states or properties where needed, and implement and test any keyboard or focus behavior the element does not supply. |
| A form review identifies unnamed fields | Associate field labelsGive each field an accessible name. Placeholder text can supplement a label, but it is not a dependable replacement for a persistent, correctly associated label. |
| Heading levels follow visual size rather than content structure | Semantic heading levelsChoose heading levels for the content hierarchy, then use classes for visual styling. The design can keep its appearance while gaining a meaningful heading structure. |
| We need a combobox, a tree grid or a rich text editor | Maintained libraryAssess a component library such as Material UI for the interaction. Check its semantics, keyboard operation and focus behavior in your product's agreed browser and assistive-technology combinations. |
| A customer or a regulator named a standard we have to meet | Agree target and scopeAgree the target and covered surfaces before design and testing. Use UX consulting or a quality audit for an independent review scoped to that requirement. |
| The layout breaks, but the structure is fine | Review the stylingReview CSS layout, content variations and responsive behavior. Keep structural markup changes focused on their own requirements. |
Scope
We build to WCAG 2.2 AA, with the target, covered surfaces and review scope agreed for the engagement. We review focus after an action as part of the completed interaction. unicrew has been building web interfaces since 2012. The company has 100+ senior in-house engineers across six countries, and its information-security management system is ISO 27001:2022 certified. For ownership of the whole interface, use front-end development.
04Stack
HTML alongside styles, behavior and browser APIs
Markup defines the elements these tools style, activate or organize.
05Questions
Questions about semantic HTML and accessibility
Understand the markup contract, the review scope and how the work is priced.
Semantic HTML is HTML that uses elements for their meaning, such as a button for an action or a heading for a section. Appearance alone does not supply those semantics.
HTML is maintained as a Living Standard. HTML5 covers the separate browser API decisions, including media, canvas, storage and geolocation.
Yes. A React component still renders HTML, and its element choices apply wherever that component is used.
We treat the rendered element and keyboard behavior as part of the component contract. A clickable container does not acquire native button behavior through visual styling; we check the resulting interaction where the component is used.
Yes. We review markup, component semantics and keyboard behavior within design and build work, or through UX consulting or a quality audit.
We agree the target standard, covered surfaces and test combinations before starting. A review identifying defects and a formal conformance statement are distinct scopes; we agree which you need.
Semantic markup helps search engines and answer engines interpret a document's structure and content. It does not by itself guarantee rankings or AI citations.
We use meaningful headings and link text, with important content available as text in the response. These support readable, extractable content.
We quote HTML work against the implementation and review scope.
- Time and materials is billed hourly and quoted per project when scope is evolving.
- Fixed price is outcome based and quoted per project after the initial component review.
- Team extension is billed monthly per team member.
Most engagements start within two to four weeks.
Plan the markup and accessibility work
Share the interface, the tasks it supports and your acceptance target. We review where changes belong in shared components or individual pages, then scope the relevant web development or design work.