In order to make the use of color accessible for our color blind and low vision users it's important that the colors have high contrast with the colors around them. We also need to be careful with the way we are using color so that no information is lost in situations where color can't be perceived.

When we think about the controls on our pages we need to make sure they make sense to users who rely on assistive technologies for their output. Users who use a screen reader, zoom, or other tool should understand what all controls are and what will happen when they use them.

Because of various needs, our users may rely on a tool other than a mouse. We want our pages and components to be as functional for these users as they are for mouse users. A general rule of thumb is that if a component is accessible with the keyboard, it will also be accessible with similar tools.

Forms can be very time consuming and confusing for many of our users. In order to assist these users it's important that we make our forms as clear as we can. This includes giving instructions that are easy for all of our users to discover.

While images and icons greatly increase the usability of our pages, they are not accessible to all users by default. We need to think about what we are trying to tell the user with our images and make sure all users can benefit from this. We also need to be careful with any other information that we are providing using visual characteristics as not all users will be able to understand it.

When we design a page and it's content we need to remember that not everyone will be using the same tools. If done correctly the structure of the content will be maintained no matter how our users interact with our pages. Whether it be with a screen reader, with zoom, or with any other tool.

When pages are designed, the content is meant to be discovered in a specific order. This order should be maintained no matter what tool(s) our users are using. In order to do that we need to make sure that without stylesheets all of the content still falls in a logical order.

Changes that occur dynamically while on a page can be disorienting for all users but even more so for users such as screen reader users or users with cognitive disabilities. To lessen these effects we should make these changes as obvious as possible for all users.

In order to better assist our users with disabilities, it's important that we keep our pages and paths as consistent as possible. Consistency helps our return users know what to expect so that they can more quickly navigate the components and pages. It also keeps users from having to relearn the interface on every page.

Motion can both make it difficult for users to read content, as well as distract from other content on the same page. Motion, auto-updating, and flashing should be avoided when possible.

Media generally relies on specific senses, whether it be sight or hearing. All of the content needs to be provided in ways that users who do not have these senses can still understand.

There are many different assistive technologies out there that our users may be using and we can't test with them all. The best thing that we can do to make sure our pages will work with them all is to write clean code. We need to make sure that the way we are writing our HTML and CSS follows the code guidelines that these assistive technologies will also be following.

* The materials outlined on this website are provided "AS IS" and are intended for illustrative purposes only. They should not be relied upon for marketing, legal, tax, financial, regulatory or other advice. You are responsible for the legal aspects of any implementation of the concepts illustrated herein. Further, Expedia, Inc. neither makes any warranty or representation as to the completeness or accuracy of this information, nor assumes any liability or responsibility that may result from reliance on such information. You should not act or rely on such content without seeking the advice of a professional. All brand names, logos and/or trademarks are the property of their respective owners, are used for identification purposes only, and do not necessarily imply product endorsement or affiliation with Expedia, Inc.