Browser implementations of standard HTML elements like date inputs and <video> have known accessibility bugs, some open for over a decade. Developers who rely on HTML's built-in accessibility are let down when browsers render these elements inaccessibly. Browser makers are uniquely positioned to fix these issues for everyone at once, rather than leaving it to individual developers or third-party libraries. Some progress is happening — Chromium's Form Controls Refresh, Firefox improving number input accessibility, and the W3C's OpenUI project — but more prioritization of accessible HTML element rendering is needed across the board.
Table of contents
On ‘the web is accessible by default’ #heading-1The components of an accessible web #heading-2What browsers could do #heading-3Wrapping up #heading-41 Impression