nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Navigating of DCT

niniti

When I am inputting info in the fields of DCT, at some points I have to use mouse or mouse pad only. Like if I want to open replicants, I have to click on "+" sign at the top right corner by mouse or mouse pad.

Is there a way I can use keyboard to use these functionalities ?

Thanks

Find more posts tagged with

Comments

ISCBorisB

When I am inputting info in the fields of DCT, at some points I have to use mouse or mouse pad only. Like if I want to open replicants, I have to click on "+" sign at the top right corner by mouse or mouse pad.

Is there a way I can use keyboard to use these functionalities ?

Thanks

Unfortunately, no. Browsers' Keyboard accessibility is based on the page elements focusing.
For the replicant controls IWOV uses "no label" images with the "onClick" handlers. You
can not focus such construct thus no keyboard.

Whether that's a design flaw is debatable. An argument that Data Entry Form "Tab" should switch
between data Fields and not get stuck in dozens tiny controls is a solid one.

Adam Stoller

Unfortunately, no. Browsers' Keyboard accessibility is based on the page elements focusing.
For the replicant controls IWOV uses "no label" images with the "onClick" handlers. You
can not focus such construct thus no keyboard.

Whether that's a design flaw is debatable. An argument that Data Entry Form "Tab" should switch
between data Fields and not get stuck in dozens tiny controls is a solid one.

To follow on this - I just looked at the source for a simple DCT/DCR I have (when rendered) and in a situation where I have 2 instances of a replicant, the first instance has:[html]

[/html]and the second instance has:[html]

[/html]As indicated, the images do not have a label attribute associated with them, and the id associated with the '+' image in each instance of the replicant differs (add_img_1 and add_img_3) and it's not clear (at face-value) why the second instance is '3' instead of '2').

You could try to do some fancy CSS stuff (e.g.: see accesskeys) but (a) this article was written in 2003 and indicates a very limited set of browsers supporting such directives [hopefully that's changed, I didn't do an exhaustive search] and (b) it isn't clear [again, limited investigation] whether you can assign an accesskey to an image as opposed to an anchor.

You could file a case with Support to try to get the lack of label-specification or built-in hotkey support filed as a bug (I believe this was something that was planned for the 7.x release, before Interwoven was acquired by Autonomy), but while it might help in some future release, it is extremely unlikely that it will help you now.