The reason I ask is: when I run Jaws 12 on IE9 and hit this page: http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/form/_autoComplete.html
Jaws does not automatically switch to forms mode when I tab to the first combobox: US State test 1. It announces that it is an edit combobox but I cannot use down arrow or alt down arrow to navigate through the state options and pick a state. Is this expected behavior?
According to this blog: http://www.paciellogroup.com/blog/2010/10/jaws-support-for-aria/ Jaws is supposed to automatically switch to forms mode for edit inputs and alt down arrow is supposed to drop down the combobox, neither of which seems to be happening...
This is surprising since dijit widgets are supposed to be accessible...am I missing something here?
As a blind jaws user welcome to the wonderful world of cross browser accessibility quirks. I would say Jaws is supposed to automatically switch to forms mode when encountering a dijit combobox. Using Jaws 13 when I tab to the combo box in either Firefox 12 or Google chrome 18 Jaws automatically enters forms mode. If I navigate to the combobox using arrow keys Jaws does not automatically enter forms mode but this is the expected behavior based on the blog entry you have posted. The current computer I am on has IE 7 and I have behavior similar to yours. Forms mode is not entered when I tab to the combobox. Even when I tab to the combobox and hit enter forms mode is not activated. The only way for me to interact with the combobox is to navigate to it with arrow keys then hit enter. Doing this turns on forms mode and allows me to interact with it. I will test with IE 9 when I get a chance and update my answer with my results.
Related
I am using a combobox in a webapp with Vaadin 14. When the user clicks into the textfield, he can enter text.
I do not want that. The values of the combobox itself should not be editable, but the user should still be able to select the predefined values.
This is the standard behaviour of these components.
How to do that in Vaadin 14.6.8?
The standard behavior of a ComboBox is that you can both type and select – thus the "combo".
I believe you are looking for the Select component: https://vaadin.com/docs/v14/ds/components/select
The solution I found on the internet (on the feature request site):
cb.getElement().setAttribute("onkeydown", "return false");
It works partially, the cursor keeps blinking in the textfield, but custom user input is disabled.
I'm using ReactJS and I have a lot of <button> in my code. I notice that I can use the Tab key to move over the button and there will be an outline on focused button like this:
But on this website which I'm trying to replicate, the buttons they use do not get Tab-focused on normal but just when we turn on the VoiceOver accessibility mode.
And the border of the Tab focus is also different.
I wonder how can we implement this in React?
Changing tabIndex to 0 or -1 doesn't work.
Thanks everyone!
Update
I ask because this leads to a problem:
If I use the UI Keyboard (UIKB) first and then try to type with the real keyboard keydown event. The tab focus would just stuck on the UIKB letter and return it twice.
This doesn't happen on the Wordle game because they just allow using tab focus when in accessibility mode.
tabIndex = -1 doesn't work because I want to allow the user use the tab focus just in a11y mode like Wordle, I don't want to totally disable it.
I'm trying to change year of datepicker using Ctrl + PageUp of below URL
http://oaa-accessibility.org/example/15/
It is working fine till I launch JAWS, Once I launched JAWS its not working.
We observed it is changing month instead of year. For month change shortcut is pageUp. In code we are getting ctrlKey as false and assuming user pressed only PageUp and responding to that request.
It might be overlapping with shortcut keys with JAWS
Can some one help me understand how to make Ctrl + PageUp working while JAWS is running.
is it mandatory to have Ctrl+Pageup to change year of calendar to meet accessibility guidelines?
Below is the response which I got from JAWS tech support team
When position on the item where I wanted to perform the control+page up command on, I had to perform the insert+Number row 3 command to allow the next keystroke to pass through and then perform the keystroke and it worked properly for me.
I have a group box containing 4 radio buttons and then 10 regular button. I have Visual Studio's "Tab Order" view enabled here in the screenshot below:
When I run the application and try to tab over everything, the GroupBox (3) gets focus, press Tab, 3.0 (Radio Button #1) gets focus, Press Tab then 4.0 gets focus, 4.1, 4.2 etc.
I tried to search around for a fix, but everything seems to be ASP related.
In my Windows Mobile project, I have a form (let's call it form M to help keep thing straight) that I need to display modally, so I am using the ShowDialog method on a new copy of the form. When I show it from a form (form A) that takes up the whole screen (WindowState Maximized, Location 0,0, all other properties default except for name, the designer picks this up and shows it without a title bar), it shows up fine with the title bar intact.
However, if I display another modal window on top of this form (form B) that takes up the whole screen and uses the same form properties as form A, and then try to show the modal dialog form M from that form, the title bar is not visible and I can see the top part of form B behind it. Form M also has all default properties except for ControlBox False, and as such shows up in the designer with the title bar.
Any ideas as to what to look for? I have tried just about every combination of manipulating the properties of the parent and modal forms (WindowState, FormBorderStyle, ControlBox, TopMost, etc.) and have not found a combination that works yet.
It exhibits the same behavior both in the Windows Mobile 6 Classic emulator and on my device.
Here is what the form M is supposed to look like, which it does when shown on top of form A:
Good Form http://imagebin.antiyes.com/images/0710161001266357909_33.png
And when form M is displayed on top of form B (and form A):
Bad Form http://imagebin.antiyes.com/images/0020949001266357931_33.png
(These screen captures are taken from my Dell Axim X51V, which has a 480x640 screen.)
This project worked fine in the past, I just converted it from VS2005 to VS2008, and I am wondering of something in the conversion is causing this to happen.
EDIT: I noticed that this is happening with other forms with title bars in my application that try to show on top of form B, and it is exhibiting the same behavior. If when this happens, I press the Calendar hardware button to open up the calendar application, and then press Ctrl+Q (I am using MyMobiler for screen shots and keyboard control of the device), the Calendar window goes away and the form M shows up, this time with the title bar showing just fine.