[nopram2Member]

That will be great, thanks!

[nopram2Member]

Sorry, the html didn’t get through.

The example I was trying to post was:

<form>

<label for=”name” accesskey=”n”>Enter your <u>N</u>ame </label>
<input type=”text” id=”name” autofocus>

<label for=”surname” accesskey=”s”>Enter you <u>S</u>urname
<input type=”text” id=”surname”>

<label for=”dob” accesskey=”b”>Enter your date of <u>B</u>irth</label>
<input type="text" id="dob">

</form>

[nopram2Member]

Hi,

Thanks for your quick response. When I talk about a LABEL I’m talking about a typical FORM where a user enters a bunch of data, as in this very simple example:

<form>

<label for=”name” accesskey=”n”>Enter your <u>N</u>ame </label>
<input type=”text” id=”name” autofocus>

<label for=”surname” accesskey=”s”>Enter you <u>S</u>urname
<input type=”text” id=”surname”>

<label for=”dob” accesskey=”b”>Enter your date of <u>B</u>irth</label>
<input type="text" id="dob">

</form>

As simple as this example is, it is very keyboard friendly using standard HTML5:

1. You can navigate to any input using an access key
2. The form starts with the first input focused so user can start typing right away.

If I were to replace the "date of birth" input with a jqxDateTimeInput, some keyboard features will be missing. I think a simple solution would be if the ID of the input element inside jqxDateTimeInput could be unique and known. As it is today, the input has always an ID of "inputElement" what prevents it from being useful at all.

Martin

[nopram2Member]

Hi,

Thanks for your quick response. When I talk about a LABEL I’m talking about a typical FORM where a user enters a bunch of data, as in this very simple example:

Enter your Name

Enter you Surname

Enter your date of Birth

As simple as this example is, it is very keyboard friendly using standard HTML5:

1. You can navigate to any input using an access key
2. The form starts with the first input focused so user can start typing right away.

If I were to replace the “date of birth” input with a jqxDateTimeInput, some keyboard features will be missing. I think a simple solution would be if the ID of the input element inside jqxDateTimeInput could be unique and known. As it is today, the input has always an ID of “inputElement” what prevents it from being useful at all.

Martin

[Author]

Posts