Skip to main content

Oregon State Flag An official website of the State of Oregon » Homepage

Web Accessibility Checklist for Developers

Q: Do images have alternative text?
A: More about Making Images Accessible
Q: Does the web page or document include headings, lists, ARIA landmarks, and other semantic elements to communicate document structure (resource also mentions tables)?
A: More about Providing Structure in Web Pages and Documents
Q: Is the tab order and read order logical and intuitive?
A: More about Ensuring Proper Tab and Read Order for HTML and PDF documents
Q: Do form fields within web pages and documents have appropriately coded labels and prompts?
A: More about Creating Accessible Forms
Q: Have you avoided using visual characteristics to communicate information (e.g., "click the circle on the right" or "required fields are in red")?
A: More about Avoiding Reliance on Visual Characteristics
Q: Does the interface have sufficient contrast between text color and background color?
A: More about Providing Sufficient Color Contrast
Q: Does the content scale well when text is enlarged up to 200 percent?
A: More about Supporting Enlarged Text
Q: Can all menus, links, buttons, and other controls be operated by keyboard, to make them accessible to users who are unable to use a mouse?
A: More about Designing for Keyboard Accessibility
Q: Does the web page include a visible focus indicator so all users, especially those using a keyboard, can easily track their current position?
A: More about Providing Visible Focus for Keyboard Users
Q: Do pages that have time limits include mechanisms for adjusting those limits for users who need more time?
A: More about Providing Accessible Time Limits
Q: Do features that scroll or update automatically (e.g., slideshows, carousels) have prominent accessible controls that enable users to pause or advance these features on their own?
A: More about Ensuring Accessibility of Scrolling or Updating content
Q: Have you avoided using content that flashes or flickers?
A: More about Avoiding Flashing or Flickering Content
Q: Does the web page or document have a title that describes its topic or purpose?
A: More about Providing an Informative Title
Q: Are mechanisms in place that allow users to bypass blocks of content (e.g., a "skip to main content" link on a web page or bookmarks in a PDF)?
A: More about Facilitating Efficient Navigation
Q: Is link text meaningful, independent of context?
A: More about Using Meaningful Link Text
Q: Does the website include two or more ways of finding content, such as a navigation menu, search feature, or site map?
A: More about Providing Multiple Ways of Finding Content
Q: Has the language of the web page or document (or individual parts of a multilingual document) been defined?
A: More about Identifying Language of a Document and its Parts
Q: Have you avoided links, controls, or form fields that automatically trigger a change in context?
A: More about Providing Predictable Behavior
Q: Does the website include consistent navigation?
A: More about Providing Consistent Site-wide Navigation
Q: Do online forms provide helpful, accessible error and verification messages?
A: More about Using Accessible Methods of Form Validation
Q: Is the web page coded using valid HTML?
A: More about Validating Your Code
Q: Do rich, dynamic, web interfaces, such as modal windows, drop-down menus, slideshows, and carousels, include ARIA markup?
A: More about Using ARIA for Web Applications