Good shout, this seems like a pretty major accessibility bug, bit saddened that as a professional web dev I wasn't aware of it, otherwise I probably would've been applying a standard workaround like @sarciszewski.