We are checking the accessibility of our website, and it seems that when you dynamically change the disable state of the date picker, the aria-disabled never change. It stays the same as the one when the component is created.
So if the page initialise with disabled = true, the aria-disabled will always be true, instead of changing when we update the setting.
This is quite important as the product go out soon.
Thanks for your feedback !
You can use syntax like: document.getElementById(‘myWidgetId’).removeAttribute(attributeName);
But I do not want to remove the attribute, that would be worse for the user.
I just need that when the disabled setting is updated, the aria on the html element updates too right ?
Ok, then with setAttribute you can update the attribute’s value.
But should it be done by the jqx component and not manually by the consumer ?? It seems that u propose me a hack, and not a solution ?
I proposed you a solution for your application scenario.
And I thanks you for it.
Now what I ask is a change in the JQX code (on your side), to fix that, because it shouldnt be a hacky solution in my end right ?
- This reply was modified 2 years, 5 months ago by Warez.
It is not a hacky solution. It is 1 code line. In case we do any modifications in our code base, this will be noted in the Release notes.
It it not one line code. YOu have to handle manually all the change feature. Which means listen if the flag has changed or not from the outside. and then call your line of code. Which is not a good code anyway, we are in 2017, who use document.getElementById now….
The newest trend in web development is Custom Elements and document.getElementById is used everywhere there. Anyway, you can select it with jQuery or with whatever you prefer. And my suggestion indeed is 1 line of code. I guess you know exactly where in your code you disable and enable it.
What you seem not understand is that this setAttribute should be done on your side, not mine, JQX has to be aria compliant, this is not my component guys.
You must be logged in to reply to this topic.