InputDateTime rendering outside of main body

Posted by: jacob.evans on 17 March 2024, 11:07 pm EST

  • Posted 17 March 2024, 11:07 pm EST - Updated 17 March 2024, 11:12 pm EST

    Hey,

    We are currently implementing accessibility standards as defined by WCAG, using Axe DevTools as a guideline. I have encountered an issue with the input date time, when the input is expanded, it is rendered outside the main body of the page, and causing an accessibility issue of not having a landmark role. I am able to attach a landmark role (although this seems incorrect, as there are no appropriate roles and I believe the dropdown should be nested within the main body of the page). Doing this causes further accessibility issues when the Time picker is open; as it is the listbox options (the times to select) expect the parent element to have a certain role (‘listbox’, or ‘group’). Is this an issue you are aware of / intend to fix?

    .

  • Posted 17 March 2024, 11:12 pm EST - Updated 17 March 2024, 11:17 pm EST

    This is how the elements look, and demonstrates how the dropdown is rendered outside the main body.

  • Posted 19 March 2024, 11:52 pm EST

    Hi Jacob,

    At present, all the dropdown elements are rendered outside the control due to the current architecture of the Wijmo controls. I’m actively investigating your issue and exploring options to improve accessibility. I’ll keep you updated on any progress or solutions as soon as possible.

    Thank you for your cooperation and understanding.

    Best regards.

  • Posted 21 March 2024, 12:09 am EST

    Hi Jacob,

    I have replicated the issue on my end and have escalated it to our Development team for further investigation. The issue has been assigned an internal tracking ID WJM-33612. We will keep you updated and respond as soon as we receive any updates from our team. Thank you for your patience and understanding.

    Regards

  • Posted 10 April 2024, 3:37 am EST

    Hey, is there any update on this?

  • Posted 10 April 2024, 8:49 pm EST

    Hi Jacob,

    Sorry, but there is currently no update on the issue. The problem is still under investigation by the development team. I have requested them to prioritize the issue and provide a resolution as soon as possible. I will keep you updated as soon as I hear back from them.

    Regards

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels