On Mon, Aug 12, 2019 at 11:20 AM, George Bell wrote:
Would it not make sense to inform software developers of their pure laziness in not labelling buttons anyway?Yes, but probably not in those terms (not that they're not true). Not only is accessibility becoming more of a "designed-in" phenomenon but so are certain coding conventions like labeling buttons.
When brought to the attention with something like, "this poses an accessibility issue for screen reader users, as well as being inconsistent as far as labeling buttons goes," you're more likely to get the desired result.
Also, there are times when certain things are being pulled up out of standard libraries for a given application that may have been coded long ago. Those using those may be entirely unaware that there were lapses as far as accessibility-friendliness when those libraries were initially coded. There's not a lot of regression testing to begin with for stuff that's "been around since dirt" and what there is likely has zero focus on the accessibility angle, while new code is a different kettle of fish.
Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362
The color of truth is grey.
~ André Gide