Testing challenge

 Day 20 # This checklist uses The Web Content Accessibility Guidelines (WCAG) as a reference point. The WCAG is a shared standard for web content accessibility for individuals, organizations, and governments.

Content

Content is the most important part of your site.

  • Use plain language and avoid figures of speech, idioms, and complicated metaphors.
  • Make sure that the button, a, and label element content are unique and descriptive.
  • Use left-aligned text for left-to-right (LTR) languages, and right-aligned text for right-to-left (RTL) languages.

Global code

Global code is code that affects your entire website or web app.

  • Validate your HTML.
  • Use a lang attribute on the HTML element.
  • Provide a unique title for each page or view.
  • Ensure that viewport zoom is not disabled.
  • Use landmark elements to indicate important content regions.
  • Ensure a linear content flow.
  • Avoid using the autofocus attribute.
  • Remove session timeouts.
  • Remove title attribute tooltips.

Keyboard

It is important that your interface and content can be operated, and navigated by the use of a keyboard. Some people cannot use a mouse or maybe using other assistive technologies that may not allow for hovering or precise clicking.

  • Make sure there is a visible focus style for interactive elements that are navigated to via keyboard input.
  • Check to see that the keyboard focus order matches the visual layout.
  • Remove invisible focusable elements.

Images

Images are a very common part of most websites. Help make sure they can be enjoyed by all.

  • Make sure that all img elements have an alt attribute.
  • Make sure that decorative images use null alt (empty) attribute values.
  • Provide a text alternative for complex images such as charts, graphs, and maps.
  • For images containing text, make sure the alt description includes the image's text.

Headings

Heading elements (h1, h2, h3, etc.) help breaks up the content of the page into related “chunks” of information. They are incredibly important for helping people who use assistive technology to understand the meaning of a page or view.

  • Use heading elements to introduce content.
  • Use only one h1 element per page or view.
  • Heading elements should be written in a logical sequence.
  • Don't skip heading levels.

Lists

Lists elements let people know a collection of items are related and if they are sequential, and how many items are present in the list grouping.

Use list elements (ol, ul, and dl elements) for list content.

Controls

Controls are interactive elements such as links and buttons that let a person navigate to a destination or perform an action.

  • Use the element for links.
  • Ensure that links are recognizable as links.
  • Ensure that the controls have: focus states.
  • Use the button element for buttons.
  • Provide a skip link and make sure that it is visible when focused.
  • Identify links that open in a new tab or window.

Tables

Tables are a structured set of data that help people understand the relationships between different types of information.

  • Use the table element to describe tabular data.
  • Use the th element for table headers (with appropriate scope attributes).
  • Use the caption element to provide a title for the table.

Forms

Forms allow people to enter information into a site for processing and manipulation. This includes things like sending messages and placing orders.

  • All inputs in a form are associated with a corresponding label element.
  • Use fieldset and legend elements where appropriate.
  • Inputs use autocomplete where appropriate.
  • Make sure that form input errors are displayed in the list above the form after submission.
  • Associate input error messaging with the input it corresponds to.
  • Make sure that error, warning, and success states are not visually communicated by just color.

Media

Media includes content such as pre-recorded and live audio and video.

  • Make sure that the media does not autoplay.
  • Ensure that media controls use appropriate markup.
  • Check to see that all media can be paused.

Video

Video-specific checks.

  • Confirm the presence of captions.
  • Remove seizure triggers.

Audio

Audio-specific checks.

  • Confirm that transcripts are available.

Appearance

How your website app content looks in any given situation.

  • Check your content in specialized browsing modes.
  • Increase text size to 200%.
  • Double-check that good proximity between content is maintained.
  • Make sure color isn't the only way information is conveyed.
  • Use a simple, straightforward, and consistent layout.

Animation

  • Content that moves, either on its own or when triggered by a person activating a control.
  • Ensure animations are subtle and do not flash too much.
  • Provide a mechanism to pause background video.
  • Make sure all animation obeys the prefers-reduced-motion media query.

Color Contrast

Color contrast is how legible colors are when placed next to and on top of each other.

  • Check the contrast for all normal-sized text.
  • Check the contrast for all large-sized text.
  • Check the contrast for all icons.
  • Check the contrast of borders for input elements (text input, radio buttons, checkboxes, etc.).
  • Check text that overlaps images or videos.
  • Check custom ::selection colors.

Mobile / Touch

Things to check mobile experiences for.

  • Check that the site can be rotated to any orientation.
  • Remove horizontal scrolling.
  • Ensure that button and link icons can be activated with ease.
  • Ensure sufficient space between interactive items in order to provide a scroll area.

Comments

Popular posts from this blog

Testing Challenges

WCAG 2.0 - WEB CONTENT ACCESSIBILITY GUIDELINES