As of May 2023
BROEKMAN communications fully endorses accessiBe
The leading AI-powered web accessibility solution that makes websites accessible to people with disabilities, and compliant with the WCAG, ADA, and other accessibility legislation. By using AI and automation, accessiBe signficantly reduces costs and time, making web accessibility achievable for all businesses.
MAKING THE WEB INCLUSIVE FOR ALL – $49- per month saves you from having to do 20-30hrs worth of work upfront plus all the research, headaches of learning curve, etc. SIGN UP HERE
NOTE: The following is NOT the Web Content Accessibility Guidelines (WCAG) 2.0. It is, however, a simple checklist that presents our recommendations for implementing HTML-related principles and techniques for those seeking WCAG 2.0 conformance.
This checklist cannot be used to verify conformance with WCAG 2.0. You must reference official WCAG 2.0 documentation to determine any level of conformance or non-conformance.
This checklist should not be referenced in policies or in policy adoption. While this is a useful resource for technical implementation of WCAG for HTML content, it is not a useful policy checklist. Official WCAG 2.0 documentation provides much better mechanisms for implementing accessibility into policy or law.
WCAG 2.0 covers accessibility of all web content and is not technology specific. The language of this checklist has been targeted primarily for evaluation of HTML content. It is, therefore, fairly limited and subject to technology changes, whereas WCAG 2.0 is much less so.
This checklist contains WebAIM’s interpretation of WCAG guidelines and success criteria and our own recommended techniques for satisfying those success criteria. The first column of the table below links to the official WCAG 2.0 success criteria.
Perceivable Web content is made available to the senses – sight, hearing, and/or touch
Guideline 1.1 Text Alternatives: Provide text alternatives for any non-text content
All images, form image buttons, and image map hot spots have appropriate, equivalent alternative text.
Images that do not convey content, are decorative, or contain content that is already conveyed in text are given null alt text (alt=””) or implemented as CSS backgrounds. All linked images have descriptive alternative text.
Equivalent alternatives to complex images are provided in context or on a separate (linked and/or referenced via longdesc) page.
Guideline 1.2 Time-based Media: Provide alternatives for time-based media
NOTE: If the audio or video is designated as an alternative to web content (e.g., an audio or sign language version of a web page, for example), then the web content itself serves as the alternative.
A descriptive text transcript (including all relevant visual and auditory clues and indicators) is provided for non-live, web-based audio (audio podcasts, MP3 files, etc.).
A text or audio description is provided for non-live, web-based video-only (e.g., video that has no audio track).
Synchronized captions are provided for all live multimedia that contains audio (audio-only broadcasts, web casts, video conferences, Flash animations, etc.)
Audio descriptions are provided for all video content
NOTE: Only required if the video conveys content visually that is not available in the default audio track.
When an audio description track cannot be added to video due to audio timing (e.g., no pauses in the audio), an alternative version of the video with pauses that allow audio descriptions is provided.
Semantic markup is used to designate headings (<h1>), lists (<ul>, <ol>, and <dl>), emphasized or special text (<strong>, <code>, <abbr>, <blockquote>, for example), etc. Semantic markup is used appropriately.
Tables are used for tabular data. Where necessary, data cells are associated with their headers. Data table captions and summaries are used where appropriate.
Text labels are associated with form input elements. Related form elements are grouped with fieldset/legend.
Instructions do not rely upon shape, size, or visual location (e.g., “Click the square icon to continue” or “Instructions are in the right-hand column”).
Instructions do not rely upon sound (e.g., “A beeping sound indicates you may continue.”).
Guideline 1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background
Color is not used as the sole method of conveying content or distinguishing visual elements.
Color alone is not used to distinguish links from surrounding text unless the luminance contrast between the link and the surrounding text is at least 3:1 and an additional differentiation (e.g., it becomes underlined) is provided when the link is hovered over or receives focus.
Are NOT fully justified (aligned to both the left and the right margins).
Have adequate line spacing (at least 1/2 the height of the text) and paragraph spacing (1.5 times line spacing).
Have a specified foreground and background color. These can be applied to specific elements or to the page as a whole using CSS (and thus inherited by all other elements).
Do NOT require horizontal scrolling when the text size is doubled.
All page functionality is available using the keyboard, unless the functionality cannot be accomplished in any known way using a keyboard (e.g., free hand drawing).
Page-specified shortcut keys and accesskeys (accesskey should typically be avoided) do not conflict with existing browser and screen reader shortcuts.
Keyboard focus is never locked or trapped at one particular page element. The user can navigate to and from all navigable page elements using only a keyboard.
If a page or application has a time limit, the user is given options to turn off, adjust, or extend that time limit. This is not a requirement for real-time events (e.g., an auction), where the time limit is absolutely required, or if the time limit is longer than 20 hours.
Automatically moving, blinking, or scrolling content that lasts longer than 5 seconds can be paused, stopped, or hidden by the user. Moving, blinking, or scrolling can be used to draw attention to or highlight content as long as it lasts less than 5 seconds.
Automatically updating content (e.g., automatically redirecting or refreshing a page, a news ticker, AJAX updated field, a notification alert, etc.) can be paused, stopped, or hidden by the user or the user can manually control the timing of the updates.
No page content flashes more than 3 times per second unless that flashing content is sufficiently small and the flashes are of low contrast and do not contain too much red. (See general flash and red flash thresholds)
A link is provided to skip navigation and other page elements that are repeated across web pages.
If a page has a proper heading structure, this may be considered a sufficient technique instead of a “Skip to main content” link. Note that navigating by headings is not yet supported in all browsers.
If a page uses frames and the frames are appropriately titled, this is a sufficient technique for bypassing individual frames.
The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone, or from the link text and its context (e.g., surrounding paragraph, list item, table cell, or table headers).
Links (or form image buttons) with the same text that go to different locations are readily distinguishable.
Multiple ways are available to find other web pages on the site – at least two of: a list of related pages, table of contents, site map, site search, or list of all available web pages.
Page headings and labels for form and interactive controls are informative. Avoid duplicating heading (e.g., “More Details”) or label text (e.g., “First Name”) unless the structure provides adequate differentiation between them.
If a web page is part of a sequence of pages or within a complex site structure, an indication of the current page location is provided, for example, through breadcrumbs or specifying the current step in a sequence (e.g., “Step 2 of 5 – Shipping Address”).
Words that may be ambiguous, unknown, or used in a very specific way are defined through adjacent text, a definition list, a glossary, or other suitable method.
Expansions for abbreviations are provided by expanding or explaining the definition the first time it is used, using the <abbr> element, or linking to a definition or glossary. NOTE: WCAG 2.0 gives no exception for regularly understood abbreviations (e.g., “HTML” on a web design site must always be expanded).
A more understandable alternative is provided for content that is more advanced than can be reasonably read by a person with roughly 9 years of primary education.
If the pronunciation of a word is vital to understanding that word, its pronunciation is provided immediately following the word or via a link or glossary.
Guideline 3.2 Predictable: Make Web pages appear and operate in predictable ways
When a page element receives focus, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user.
When a user inputs information or interacts with a control, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user unless the user is informed of the change ahead of time.
Elements that have the same functionality across multiple web pages are consistently identified. For example, a search box at the top of the site should always be labeled the same way.
Substantial changes to the page, the spawning of pop-up windows, uncontrolled changes of keyboard focus, or any other change that could confuse or disorient the user must be initiated by the user. Alternatively, the user is provided an option to disable such changes.
Guideline 3.3 Input Assistance: Help users avoid and correct mistakes
Required form elements or form elements that require a specific format, value, or length provide this information within the element’s label.
If utilized, form validation errors are presented in an efficient, intuitive, and accessible manner. The error is clearly identified, quick access to the problematic element is provided, and user is allowed to easily fix the error and resubmit the form.
Sufficient labels, cues, and instructions for required interactive elements are provided via instructions, examples, properly positioned form labels, and/or fieldsets/legends.
Markup is used in a way that facilitates accessibility. This includes following the HTML/XHTML specifications and using forms, form labels, frame titles, etc. appropriately.
A veteran branding agent, marketer and publicity generator, Jeremy Broekman is the founder of eponymous PR/marketing agency, Broekman Communications, specializing in entertainment and corporate marketing. Jeremy brings 20+ years of experience across 50 feature film campaigns with Universal Studios Television and 40+ films as an independent publicist. As a fractional CMO for hire, Jeremy serves corporate, entertainment, real estate, start-up and C-suite executives. Jeremy launches successful marketing, promotions and advertising campaigns and consults teams in the areas of business development, brand strategy and social media. Jeremy is a Spartan racer, charismatic connector and master networker. His presentations are highly motivational and energizing, showing teams how to overcome obstacles and develop a shared vision. From traditional PR, publicity and promotions to event production to social media & advertising campaigns, Jeremy is the Connector & bridge maker to hire to make things happen.
