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.
Related
I am facing an issue that in react input element while the focus is on input element a default keyboard pops up after some seconds it automatically moves down. If i want it again even if i click the same input it is not working (I mean i'm not getting keybaord for same input again)
I have tried updating firmware
also tried focusing again with window.self.focus() and refereing to that element and focus both doesn't work whereas in zee tv application it is working fine
I'm using react-big-calendar (in my next.js project) and as you can see in the image above I'm displaying events on it and I have a bug that I can't understand why its happening.
When I press on the +3 more (which shows me all the events happening on the given day) then the dropdown menu that you can see on the top right image opens and then instantly closes and even if I change page it still gives me the same bug and it happens to all the dropdowns that I have on the website I'm working on.
Now one "hack" is to make the min height of the calendar bigger (I can make it 900px instead of the current 700px) so that all 4 events are shown directly instead of showing the +3 more but the problem with this "hack" is that imagine I have A LOT of events on a given day then I would need to set the min height to really really big number which is undesirable.
Note that the bug disappear if I reload the page but obviously I just can't force the user to reload every time he wants to see more events on a given day.
Which version of React-Big-Calendar are you using? Older versions of RBC used an anchor tag, for the 'more', that had an href="#". I could see that causing issues like this. Current version has replaced this code with a 'button' component styled to look like an anchor.
When putting i.e. a
TextField textField = new TextField("🗽🎶🎶");
on a form it works perfect on Android but on iOS it gets garbled.
To reproduce:
show the form -> textfield looks it correct
focus it for edit on it by clicking
change nothing, just select done / loose focus
focus it again for edit on it by clicking
The result are strange symbols.
textField.getText().getBytes() - on iOS gives the bytes: -16,-97,-105,-67, ... before the edit (the same sequence as on Android or in the simulator), but -17,-105,-67,-17, ... after ending "edit" (without editing).
It seems that a 4 byte code -16,-97,-114,-74 for the 🎶 gets a 3 byte code -17,-114,-74 after editing.
I would strongly suggest avoiding emoji's in the code itself. This is an issue with our implementation of the iOS UTF-8 parser that was resolved recently: https://github.com/codenameone/CodenameOne/issues/2365
However, it didn't make it into the 4.0 release so this should work within a couple of weeks when we resume the weekly updates.
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.
I give input the to a input field which has a jquery ui calendar
id("dateSelecterInput").sendKeys(date);
id("dateSelecterSubmit").click();
When you enter something in a input field the calendar pops up, as it should, but when then cover the submit button which is below the input field. The problem is that for Webdriver it cant click the submit button, probably since its not visible ?!?
The problem can be solved be clicking a other element, but its a hack, how to solve it proper?
We use date pickers all over our production site . After clearing the date field and sending keys, can't you press the return key to get the same result , instead of clicking on the button?
if pressing return is not an option, then , yeah, modify your css so that the button is always visible. selenium works the same way an end user would see the site, so.