reported-bugs

FTA: “And in the font we use on GOV.UK, the new line character has a bigger width than a space character – which is apparently unusual. […] One of them incorrectly used the width of the new line character in its calculations, and so the box that it made was too small.” I don’t understand that explanation. If the newline character in the font is wider than a space, why would the box end up too small if width calculations assume a newline will be rendered where the actual page will use a space? (full bug report is here: https://github.com/alphagov/reported-bugs/issues/66, but I don’t think see it linked with a WebKit issue)

Article from 2020... many of these issues are no longer a thing and/or are just really weird to call out. From their accessibility bullets: > cannot be dictated or selected when using Dragon Naturally Speaking Isn't this just a speech-to-text engine? I can say that I haven't ran into anyone using this for web control in my entire career. I'm certain it has an accessibility use-case and all, but I haven't ran into a practical example. I'm very apt to write this off as "moot," and would also suspect it may have been addressed since 2020. Does anyone here use Dragon Naturally Speaking for web control? Good faith real question. > appears as unlabeled in NVDA's element list Fixed - https://github.com/alphagov/reported-bugs/issues/41#issuecom... > appears as a spin button in NVDA's object navigation, which has an edit field and two buttons insi