James Scholes<p>Recent datepicker experience:<br>1. Control is presented as three separate spin controls, supporting the Up/Down Arrow keys to increment and decrement the value as well as manual typing. But because they're not text inputs, I can't use the Left/Right Arrow keys to review what each separate one contains, only to move between day, month, and year.<br>2. I tab to year.<br>3. I press Down Arrow, and the value is set to 2075. I'm unclear how many use cases require the year to be frequently set to 2075, but I can't imagine it's many so this seems like a fairly ridiculous starting point.<br>4. I press Up Arrow, and the value gets set to 0001. The number of applications for which 0001 is a valid year is likewise vanishingly small.<br>5. I delete the 0001, at which point my <a href="https://dragonscave.space/tags/screenReader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>screenReader</span></a> reports that the current value is "0". Also not a valid year.<br>6. Out of curiosity, I inspect the element to see which third-party component is being used to create this mess... only to find that it's a native `<input>` with `type="date"` and this is just how Google Chrome presents it.</p><p>A good reminder that <a href="https://dragonscave.space/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HTML</span></a> is not always the most <a href="https://dragonscave.space/tags/accessible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>accessible</span></a> or user-friendly.</p><p><a href="https://dragonscave.space/tags/accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>accessibility</span></a> <a href="https://dragonscave.space/tags/usability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>usability</span></a></p>