Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Narrator doesn't read out button headers #640

Closed
RandomEngy opened this issue Sep 20, 2018 · 6 comments
Closed

Narrator doesn't read out button headers #640

RandomEngy opened this issue Sep 20, 2018 · 6 comments
Assignees
Milestone

Comments

@RandomEngy
Copy link

RandomEngy commented Sep 20, 2018

  1. Turn on Narrator with Ctrl+Win+Enter
  2. Tab through the buttons

Expected result:
Narrator reads out headers for the buttons

Actual result:
Nothing is read out, or just "button"

Setting AutomationProperties.Name explicitly on a fluent:Button makes it work, but it would be handy to have the control be accessible "by default".

Setting AutomationProperties.Name on a fluent:DropDownButton or fluent:SplitButton doesn't work. It just never reads out anything on it.


Environment

  • Fluent.Ribbon 7.0.0-alpha0419
  • Windows 10, 17134.228
  • .NET Framework 4.7.2
@batzen
Copy link
Member

batzen commented Sep 20, 2018

The problem here is that Header is of type object and not of type string.
Didn't even notice this problem as i only use the ribbon at work and the whole ui, including the ribbon, is generated and automation information is automatically set for everything.

Will think about a solution to this.
Any suggestions on how to solve this properly are, of course, welcome.

@RandomEngy
Copy link
Author

What some of the .NET controls do to get automation text is just call .ToString() on the object. It's always there and the author of the type can decide how to implement it.

@RandomEngy
Copy link
Author

Thanks! Is there going to be a new alpha out soon?

@batzen
Copy link
Member

batzen commented Dec 23, 2018

Will release a new preview to nuget tomorrow.

@batzen
Copy link
Member

batzen commented Dec 24, 2018

@RandomEngy
Copy link
Author

Thanks! Though I ran into another blocking issue. Opened #680 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants