Steven Faulkner is an accessibility-focused web engineer with 13+ years shaping how the web works for everyone, currently co-editing the WCAG-EM at W3C. He has deep, practical expertise in HTML, ARIA, and accessibility API mappings, having edited core specs like Using ARIA, HTML-AAM and contributed to HTML 5.2 and Web Components guidance. Steven blends hands-on front-end work—improving Custom Element semantics and adding ARIA-aware examples in prominent repos like WICG/webcomponents—with standards-level leadership at W3C. Former Chief Accessibility Officer and long-time technical director, he advises industry and government on measurable, interoperable accessibility outcomes. Based in Stony Stratford, he pairs a humanities background (BA in Psychology and Philosophy) and a graduate certificate in Computer Science to translate complex standards into practical developer guidance. He’s known for pragmatic tooling and docs improvements that make assistive-technology exposure predictable across platforms.
13 years of coding experience
14 years of employment as a software developer
The University of Sydney
Graduate Certificate, Computer Science, Graduate Certificate, Computer Science at Swinbourne University of technology
Contributions:64 commits, 9 PRs, 55 pushes in 1 year 8 months
Contributions summary:Steven primarily contributed to the HTML Accessibility API Mappings (HTML-AAM) documentation within the repository. Their work involved updating accessibility information for various HTML elements and attributes, focusing on how these elements are exposed to assistive technologies. This included mapping to different accessibility APIs like UIA, IA2, and AX, and adding details on the accessible name and description calculations. The user also fixed typos, updated links, and addressed bug reports related to accessibility features.
Contributions summary:Steven's contributions centered on refining the custom elements specification documentation. They focused on enhancing the "Custom Element Semantics" section by adding detailed examples and explanations for developers. Their work included adding code examples with syntax highlighting, incorporating ARIA attributes, and clarifying the use of custom elements and type extensions within a web components context. The user consistently focused on accessibility best practices and providing developers with advice.
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.