Re: Generic windows forms accessibility for generic screen readers
Typically the accessible description attribute is used to provide information that tooltips might provide, for example. The accessible name attribute isn't usually used unless your making edit boxes, tree views
Re: Generic windows forms accessibility for generic screen readers
Ian really is a wonderful gentleman. He always gives very helpful answers without ever being snide or snarky, neither contentious nor contrary.Kai
URL: https://forum.audiogames.net/post/519684/#p519684
--
Audiogames
Re: Generic windows forms accessibility for generic screen readers
Ian - you are a legend. I had to see this for myself so I just ran your code in a dummy project and it's as you report. It says the text on the first button and then the accessible name of the second.I'd failed
Re: Generic windows forms accessibility for generic screen readers
I just tested with the following code: public partial class Form1 : Form { public Form1() { InitializeComponent(); var b = new Button(); b.Text = "Pre
Re: Generic windows forms accessibility for generic screen readers
Very much appreciate your feedback. I think I'll just leave the general UI without specific accessibility hints so all the buttons and UI elements read out as theiy're named or have text on them. I just wanted to be sure
Re: Generic windows forms accessibility for generic screen readers
Actually, as another kind of important followup to this: in general the OS-provided controls are already accessible and extending them will get you into trouble. So if it's a button and it already does the button things
Re: Generic windows forms accessibility for generic screen readers
I'd suggest NVDA and Narrator as your test, and then let people using other screen readers report bugs. I know that many shops have gone that route, though I don't have specific examples offhand.There is no standard
