Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Visual Example

 

Compliant Example:

Non-Compliant Example:


Acceptance Criteria

It’s important to provide screen reader and keyboard only users with a mechanism to initiate a change in page behavior.

For example if typing information in a form field or selecting an item within a drop down menu will trigger a sudden and unexpected change to the page.

This can be confusing and disorienting to screen reader and keyboard only users.

As a screen reader and keyboard only user I should:

  • be provided with a form label

  • be able to use the TAB key on the keyboard to access the form control

  • be provided with a mechanism to initiate the change in page behavior, such as an “Update” , “Submit” or “Apply” button

As a screen reader user I should:

  • be able to explicitly associate the text label with the form control

When the form field has keyboard focus: 

  • the screen reader should announce the form label

When the form button has keyboard focus: 

  • the screen reader should announce the button label


Markup and Code

 

<form>
  <div>
	<label for="phone-number">Phone Number</label>
	<input id="phone-number" type="text" aria-describedby="phoneinstructions">
	<p id="phoneinstructions">Enter your 10 digit phone number including area code.</p>
  </div>   
</form>

View markup on github

  • No labels