InputDateTime rendering outside of main body

Posted by: jacob.evans on 18 March 2024, 8:07 am EST

  • Posted 18 March 2024, 8:07 am EST - Updated 18 March 2024, 8:12 am 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 18 March 2024, 8:12 am EST - Updated 18 March 2024, 8:17 am EST

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

  • Posted 20 March 2024, 8:52 am 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, 9: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, 12:37 pm EST

    Hey, is there any update on this?

  • Posted 11 April 2024, 5:49 am 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

  • Posted 17 May 2024, 5:04 am EST

    Hi Sonu,

    Is there any update on this?

    Cheers,

    Jacob

  • Posted 20 May 2024, 12:13 am EST

    Hi Jacob,

    Our Dev team is currently working on accessibility improvements for Wijmo controls. They are also investigating the use cases you reported and will consider incorporating them if feasible. At this time, there are no updates, but I will inform you as soon as I hear back from them.

    Thank you for your patience.

    Regards

  • Posted 19 December 2024, 6:04 am EST

    Hi Jacob,

    As per the dev’s investigation, this is considered by design. Here is an explanation for that:

    As mentioned in the “Why it matters” section of the issue, placing the content under suitable landmarks is required so that the screen reader user can easily navigate to the significant sections of the page.

    This can also be confirmed from the Landmark Regions page, “Screen readers exploit landmark roles to provide keyboard navigation to important sections of a page. Landmark regions can also be used as targets for “skip links” and by browser extensions to enhanced keyboard navigation.”. The landmarks help the screen reader users to identify the structure or organization of the page. Screen readers utilize this information to help the users navigate to the important section of the page by skipping the intermediate content.

    As the dropdown is dynamically added to the page (it is not a static or always available section of the page) and the focus is programmatically shifted to the dropdown there is no need to explicitly define a landmark for it. Hence, this can be considered to be “by design”.

    Regards,

Need extra support?

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

Learn More

Forum Channels