I'm using JAWS (2019) as a screen reader for a WinForms application.
When I set the Control.AccessibleName property - JAWS read it properly
but when I change the Control.AccessibleDescription property JAWS just doesn't read it.
I tried to use [INSERT] + [B] - It just read the screen again without the description.
Is anyone familiar with that behavior?
OK, It was easy one.
If you want JAWS to read the custom text you need to set the property:
ControlName.AccessibleRole = AccessibleRole.Application;
and then JAWS will read whatever you wrote in ControlName.AccessibleDescription
Related
I have a number of buttons on a WinForms User Control. I have given each button an AccessibilityName and an AccessibilityDescription. JAWS will read the AccessibilityName however doesn't read the description even if I press [INSERT+B]. I'm unsure why this is happening or if I need to set the AccessibilityRole.
Any help would be appreciated.
At the time of writing this, attempts to expose supplemental
information through the Button.AccessibleDescription property
typically do not work. This is because the AccessibleDescription
string value does not get exposed through the UIA properties that are
commonly used for supplemental information, (for example, the UIA
FullDescription or HelpText properties).
Source: https://learn.microsoft.com/en-us/accessibility-tools-docs/items/WinForms/Button_HelpText
The linked page suggests using Button.QueryAccessibilityHelp event handler.
I am not sure but this bug fix may be relevant, but I am not familiar enough with WinForms accessibility to know if this is the same issue.
Currently my React component consists of a few labels and one input box. And it has a view mode and en edit mode.
When I go into edit mode, NVDA automatically goes into forms mode, due to which I'm not able to enter any text in input box or navigate through labels using arrow keys.
By default, on pressing Enter, NVDA goes in forms mode (see NVDA's keyboard shortcuts for forms) which takes all next keyboard input as shortcut to some command. To come out of that mode, we need to use the NVDA key (Default is insert key) + space. After that, we can resume typing. We are not even able to navigate through arrow key as it begins reading each character.
Readonly : ReadOnly Looks like this
Edit Mode: Edit Mode looks like this
Is there a way to prevent NVDA from going into forms mode automatically?
Any help would be appreciated.
NVDA Version : 2018.11
Firefox: 60.0.1 (64-bit)
I'm not sure I follow what the question is.
You have forms mode backwards. When in forms mode (meaning, that you're in a <form>), you want to type stuff into input fields and such. The keyboard events go to the form instead of to the screen reader so that what you type is what you see.
When you exit forms mode, you're back in "screen reader mode" and characters that you type will be interpreted as screen reader quicknav keys (such as 'B' to go to the next button, 'T' to go to the next table, etc).
NVDA (and JAWS) have options on whether to automatically go into forms mode when focus goes to a form element.
So given that, are you asking how you can force a screen reader to switch modes?
I am moving all strings in my Silverlight app to the db, but am having some trouble keeping the formatting. Really the only issue is for paragraph sized strings, which in the app used to keep the paragraph sized right and spacing between paragraphs. Unfortunately now that I need to bind the textblock I have to use it's text property instead of just sandwiching the text between the opening and closing tags to let the formatting do its thing. The result is that the formatting is displayed as part of the text now and isn't applied. Does anyone know how to get around this? I've tried adding Char(13), \n, different configurations of ' ', it all displays exactly how I enter it. Any ideas?
You need to use a rich text box control. Here are some options for Silverlight: What is the best substitute for FlowDocument in Silverlight?
Silverlight uses \r for line breaks and in SQL Server line breaks are \r\n. There is a nice value converter in this post that converts between the two.
I have a Scroll Viewer and inside that a text block with multiple pages contents.
How can I print everything within the Scroll Viewer.I'm Using WPF MVVM pattern.
Is text block is the right control for this?Or shall I go for any other WPF controls.?
Thanks in advance..
DocumentViewer ir a better control for paginated printing
I don't know what is exactly the problem,But something related to Printer.
From Control Panel->Printers & Fax
1.Right Click the Printer and take Printer preferences
2.Change the Source property to 'Manual Feed'& Apply.(Initially it was'AutoSelect')
3.Still got some error.
4.Again me changed the Source property back to 'Auto Select'& Apply.
5.Changed the Quick set Property to 'Defaults'& Apply
5.Now its Working Fine
I am looking for an embeddable interactive console. I want the user to be able to type in some custom commands, and the application to write command responses in it. Would be awesome if it would understand powershell or python, ans supports command completion.
I already built my own bash-like terminal, but I do not want to totally reinvent the wheel, so I'm looking for a third-party stable component before going any further with it.
If someone is interested, I found PoshConsole, a powershell console:
http://poshconsole.codeplex.com/
Thanks
PS: you can find a screen of what I am trying to achieve here:
http://www.hiboox.fr/go/images-100/codein,0a2809b63e05c3d0cac678962e0e3d5a.jpg.html
Nothing found since I asked the question, and to stick with the "do it yourself" way of thinking:
I wrote a terminal-like control in .NET.
http://wpfterminal.codeplex.com/
You can see an example in this screenshot (terminal is integrated in a bigger project) :
http://images4.hiboox.com/images/4210/0a2809b63e05c3d0cac678962e0e3d5a.jpg
Basic mechanisms
Actually what I did was to define a lastPromptIndex integer, and everytime a user presses the ENTER key and a new prompt appears, this value is updated.
After that, it's simple, you just need to process any text input before the textbox validates the input. If the textbox caret was located before your lastPromptIndex, you need to raise an error (usually a beep sound) and you must invalidate the text input, so nothing is written in the textbox. I also automatically set the caret position to the end of the textbox, so the user can immediatly input some text.
Extensions
You can enable command completion by looking for an "UP key" input if the caret is before the prompt index, etc. What you need is just to process input events before they are sent to the textbox internal mechanisms. I don't know if SWT controls allow it, but I'm pretty sure they do, like any serious UI system.