Tag Info

Hot answers tagged

3

Looking just at the tab order, it would be most appropriate for the following: 1. Username 2. Password 3. Forgot password link 4. Sign in. The rationale being that a user who is going to be using the tab key to place the cursor will be more towards the "expect" end of the spectrum than the "novice" end. They will want to jump to the appropriate fields ...


2

You always want a semantic hierarchy to your page, so people understand the different elements of a page, including the page itself as a container for all these elements. It gives users context. (Often we talk about visual hierarchy, and how we use that information to derive semantic meaning. In the case of HTML and especially when talking about ...


2

In my experience, many keyboard users expect the following tab order for a typical login form: 1. Username field 2. Password field 3. Submit button They’ll often blindly enter the username press Tab enter the password press Enter (or Tab followed by Enter) Now, when the "Forgotten your password" link appears somewhere inbetween, they’ll ...


1

The responsive text is a thorny road to travel. Not only is there the screen size issue, you also need to correct for font size, orientation, and language direction. In my opinion, you should eliminate the text altogether. A user who sees the form will immediately know it's for contact based on the nature of the page and the fields requested. If you must ...


1

There are two aspects here Do headings help in accessibility : Yes, this is because people with disablites who use screen readers or assertive tools can use shortcuts to quickly jump to headings while scanning content to get an idea of a look and feel of the site and decide on what to read.To quote this webaim article When encountering a lengthy web ...


1

Having done some testing with screen readers here's what I've found works best for dates - A plain text input with placeholder text showing the date format. Not all screen readers will read placeholder text, so in the past I've used something like a floating div for placeholder text for sighted users and ARIA attributes to provide a summary of the date ...



Only top voted, non community-wiki answers of a minimum length are eligible