noblerefa.blogg.se - Example of my checklist traits

#Example of my checklist traits update#
#Example of my checklist traits verification#

#Example of my checklist traits update#

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?įor details, see our Auto-updating content page.

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)?.

Does the web page or document have a title that describes its topic or purpose?.

Are links and buttons used appropriately and labeled correctly?įor details, see our Links and buttons page.

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?įor details, see our Keyboard accessibility page.

Make content and controls operable by all users.

Is content accessible on mobile devices?įor details, see our Mobile devices page.

Are pop-ups such as menus, dialogs, and tooltips accessible?.

Does the content scale well when text is enlarged?.

Does the interface have sufficient contrast between text color and background color?įor details, see our Color contrast page.

Have you avoided using visual characteristics to communicate information (e.g., “click the circle on the right” or “required fields are in red”)?įor details, see our Visual characteristics page.

Is the tab order and read order logical and intuitive?įor details, see our Tab and read order page.

Are tables used solely for presenting rows and columns of data (not for layout), and are the column and row headers identified?.

#Example of my checklist traits verification#

Do form fields within web pages and documents have appropriately coded labels and prompts, and do they provide helpful, accessible error and verification messages?.Does video have captions and audio description? Does audio have a transcript?įor details, see our Audio and video page.Are common regions of the web page properly identified (e.g., as banner, main content, or navigation)?.Are lists used to identify all content that can be described as a list of something?.Do headings form an outline of the page content?.Make content and controls perceivable by all users. These overview pages also include links to techniques pages related to specific technologies.įor a checklist of items specifically related to digital documents (e.g., Word, PDF), see the Documents section of our website. Links in the following sections lead to pages that provide an overview of each issue. Many of the items in this checklist apply to multiple technologies (e.g., websites, documents, videos, online courses, online meetings). In order to be accessible, content must be perceivable, operable, understandable, and robust (POUR). It is organized loosely using the four main principles of WCAG. Our intent in creating it is to present accessibility information in a way that we feel is easier to understand. It was created to assist the UW community, including web designers, developers, content creators, and purchasing agents, in creating accessible content and procuring accessible applications.

The following checklist is based on the W3C’s Web Content Accessibility Guidelines (WCAG) 2.1, but is not a substitute for the WCAG specification.