The Foundational Role of Semantic HTML in Digital Inclusion
The conversation began with a technical exploration of semantic HTML, which refers to the use of HTML elements that convey the meaning and structure of the content rather than just its visual appearance. Dilwoar Hussain, Lead Frontend Developer at the Ministry of Housing, Communities and Local Government, explained that the web is built on specific building blocks. While generic elements like <div> and <span> provide layout containers, they offer no information to assistive technologies. Conversely, semantic elements like <nav>, <header>, and <button> provide immediate context to screen readers and search engines.
James Gordon, Senior Frontend Developer at the Department for Work and Pensions, highlighted a common pitfall in modern web development: the "pseudo-link." He noted that developers often use images or generic text with JavaScript click events to mimic the behavior of a link. While this may look correct to a sighted user, a screen reader may only identify it as an image, leaving a visually impaired user unable to navigate the site. Gordon argued that using the semantic <a> tag ensures that the underlying code remains interpretable by any assistive technology, effectively "future-proofing" the website against evolving hardware and software.
Supporting this view, Michael Cheung, Senior Frontend Developer at NHS England, and Holly Blues of DWP Digital, noted that semantic HTML provides "accessibility for free." By using the correct tags, developers leverage the browser’s built-in functionality, which includes automatic keyboard focus and standardized interaction patterns. This reduces the need for complex, custom scripts that are often prone to bugs and compatibility issues.
Current Landscape: Data and Regulatory Context
The push for better frontend practices comes at a time of increased scrutiny regarding web accessibility. According to the "WebAIM Million" 2024 report, an annual accessibility analysis of the top one million homepages, 95.9% of pages still have detectable WCAG 2 failures. The most common issues include low contrast text, missing alternative text for images, and empty links—all of which are directly addressed by the semantic practices discussed by the GDS panel.
In the United Kingdom, the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 require all public sector digital services to meet the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard. Failure to comply can result in investigations by the Equality and Human Rights Commission (EHRC). The "Unlocking Accessibility" series serves as a knowledge-sharing platform to help government departments meet these high standards efficiently.
The Philosophy of "Accessible from the Start"
A recurring theme among the experts was the rejection of "accessibility overlays" or third-party plugins in favor of clean, hand-coded solutions. Dilwoar Hussain emphasized the importance of early collaboration between developers, designers, and content writers. By identifying potential accessibility hurdles during the design phase—such as color contrast issues or complex navigation patterns—teams can avoid the costly and time-consuming process of retrofitting code later in the development lifecycle.
The developers advocated for a "Keep It Simple" (KISS) approach. James Gordon noted that starting with the simplest possible implementation using semantic HTML allows for a more stable foundation. This is often achieved through "progressive enhancement," a strategy where the core content and functionality are made available to everyone, while more advanced features are added for users with modern browsers or specific capabilities.
Michael Cheung pointed out that modern browsers come equipped with powerful diagnostic tools. The "accessibility tree" within browser DevTools allows developers to see exactly how a screen reader perceives the page. By regularly testing with just a keyboard—tabbing through links and buttons—developers can identify focus traps and logical ordering errors without needing expensive software.

Navigating Dynamic Content and Interactivity
As web applications become more interactive, maintaining accessibility becomes significantly more complex. Features such as modals (pop-up windows), carousels, and accordions often disrupt the natural flow of a document. David Biddle, a Frontend Developer at GDS, explained that the first step should always be to check if a native HTML element can handle the task. For example, the recently standardized <dialog> element provides a built-in way to create modals that handle keyboard focus and backdrop interactions automatically.
For more complex dynamic updates, the experts highlighted the use of ARIA (Accessible Rich Internet Applications) attributes. Dilwoar Hussain detailed how the aria-expanded attribute is used in collapsible sections, such as accordions. When a user toggles a section, the code updates the attribute from "false" to "true," prompting the screen reader to announce the change in state. Without these attributes, a non-sighted user would have no way of knowing that their interaction had successfully revealed new content.
Holly Blues emphasized the importance of the Document Object Model (DOM) hierarchy. Ensuring that the HTML follows a logical order is vital for keyboard users who navigate the site linearly. If the visual layout (controlled by CSS) does not match the underlying code order, it can lead to a disorienting experience where the focus "jumps" unexpectedly across the screen.
The Role of Standardized Design Systems
One of the most significant advantages for UK government developers is the availability of the GOV.UK Design System. This system provides a library of pre-tested, accessible components that departments can reuse. Holly Blues noted that using these components ensures a consistent user journey across different government services. Because these components have already undergone extensive research and accessibility auditing, developers can focus on building specific service logic rather than reinventing the wheel for basic elements like buttons or form inputs.
Similarly, Michael Cheung referenced the NHS Design System, which tailors components to the specific needs of healthcare users. When a component is not available in their specific system, developers often look to the W3C’s ARIA Authoring Practices Guide (APG), which provides gold-standard examples of accessible patterns for complex widgets like tabs or sliders.
Chronology of Accessibility Standards in the UK Public Sector
The evolution of these practices can be traced through a series of technical and legislative milestones:
- 2011: GDS is established, leading to the "Digital by Default" strategy.
- 2012: GOV.UK launches, replacing Directgov and prioritizing clean, semantic markup.
- 2018: The Public Sector Bodies Accessibility Regulations are enacted, legally requiring WCAG 2.1 AA compliance.
- 2021: GDS launches the "Unlocking Accessibility" blog series to foster a cross-government community of practice.
- 2023: WCAG 2.2 is officially published, adding new criteria regarding focus appearance and redundant entry, which frontend developers are now integrating into their workflows.
- 2024: The current panel discussion underscores a shift toward "inclusive design," focusing on the user experience of disabled people rather than just checkbox compliance.
Broader Implications and Analysis
The insights provided by the GDS panel suggest that the future of frontend development is increasingly tied to technical empathy. The move away from "div soup"—the over-reliance on non-semantic tags—represents a professionalization of the field. Experts argue that accessible code is higher-quality code; it is more maintainable, performs better on low-bandwidth connections, and is more compatible with search engine optimization (SEO) algorithms.
Furthermore, the economic impact of digital accessibility cannot be overstated. In the UK, the "Purple Pound"—the spending power of disabled people and their families—is estimated at £274 billion per year. When government services are inaccessible, it not only disenfranchises a significant portion of the population but also increases administrative costs, as users are forced to rely on more expensive channels like telephone helplines or in-person appointments.
As the "Unlocking Accessibility" series continues, GDS intends to expand the conversation to other roles, including quality assurance testers and product managers. However, as this panel has demonstrated, the frontend developer remains the primary guardian of the user interface. By adhering to semantic HTML, leveraging robust design systems, and conducting rigorous manual testing, these professionals ensure that the digital architecture of the state remains open to everyone.
