DeepSeek vs Gemini vs Grok: WCAG

Prompt

website accessibility wcag checklist

DeepSeekDeepSeek

website accessibility wcag checklist

Of course. Here is a comprehensive WCAG (Web Content Accessibility Guidelines) checklist, broken down into the four core principles (POUR) and key success criteria.

This checklist is based on WCAG 2.1 Level AA, which is the standard most organizations aim to meet for legal compliance and good practice. Level A is the minimum, and Level AAA is the highest (and often not achievable for all content).

The Four Principles of Accessibility (POUR)

All guidelines fall under one of these four principles. For a website to be accessible, it must be:

Perceivable: Information and user interface components must be presentable to users in ways they can perceive.

Operable: User interface components and navigation must be operable.

Understandable: Information and the operation of the user interface must be understandable.

Robust: Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies.

WCAG 2.1 Level AA Checklist

Principle 1: Perceivable

Text Alternatives

[ ] 1.1.1 Non-text Content (Level A): All non-text content (images, icons, charts, etc.) has a text alternative.

Images: Use descriptive alt text (e.g., alt="A person using a laptop at a coffee shop").

Decorative Images: Use empty alt text (alt="").

Complex Images: Provide a longer description in the text or via a link.

Time-based Media

[ ] 1.2.2 Captions (Pre-recorded) (Level A): Synchronized captions are provided for all pre-recorded audio content in videos.

[ ] 1.2.3 Audio Description or Media Alternative (Level A): An audio description or full text transcript is provided for pre-recorded video content.

[ ] 1.2.5 Audio Description (Pre-recorded) (Level AA): Audio description is provided for all pre-recorded video content.

Adaptable

[ ] 1.3.1 Info and Relationships (Level A): Semantic HTML is used to convey structure and meaning.

Use proper heading tags (
to
) in a logical order.

Use lists (
Distinguishable
- [ ] 1.4.1 Use of Color (Level A): Color is not used as the only visual means of conveying information, indicating an action, or prompting a response (e.g., form errors should have an icon or text in addition to red color).
- [ ] 1.4.3 Contrast (Minimum) (Level AA): The contrast ratio between text and its background is at least 4.5:1 (or 3:1 for large text).
- [ ] 1.4.4 Resize Text (Level AA): Text can be resized without assistive technology up to 200% without loss of content or functionality.
- [ ] 1.4.5 Images of Text (Level AA): Text is used instead of images of text, unless the image of text is essential (e.g., a logo).
- [ ] 1.4.10 Reflow (Level AA): Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions, at a width equivalent to 320 CSS pixels. (No horizontal scrolling on mobile).
- [ ] 1.4.11 Non-text Contrast (Level AA): The visual presentation of UI components (like form input borders) and graphical objects (like icons in charts) has a contrast ratio of at least 3:1 against adjacent colors.
- [ ] 1.4.13 Content on Hover or Focus (Level AA): When additional content (like a tooltip) appears on hover or keyboard focus, it is dismissible, hoverable, and persistent.
Principle 2: Operable
Keyboard Accessible
- [ ] 2.1.1 Keyboard (Level A): All functionality is available using only a keyboard (via the Tab key, Enter, Space, Arrow keys, etc.).
- [ ] 2.1.2 No Keyboard Trap (Level A): Keyboard focus is never trapped in a section of the page. Users can tab in and out of all components.
- [ ] 2.1.4 Character Key Shortcuts (Level A): If a single-character keyboard shortcut exists, it can be turned off, remapped, or is only active when the relevant component is focused.
Enough Time
- [ ] 2.2.1 Timing Adjustable (Level A): If there is a time limit (e.g., a session timeout), users can turn it off, adjust it, or extend it.
- [ ] 2.2.2 Pause, Stop, Hide (Level A): For moving, blinking, or scrolling information that starts automatically and lasts more than 5 seconds, there is a mechanism for the user to pause, stop, or hide it.
Seizures and Physical Reactions
- [ ] 2.3.1 Three Flashes or Below Threshold (Level A): No content flashes more than three times in any one-second period.
Navigable
- [ ] 2.4.1 Bypass Blocks (Level A): A "Skip to Main Content" link is provided at the top of the page to allow keyboard users to skip repetitive navigation links.
- [ ] 2.4.2 Page Titled (Level A): Each web page has a descriptive and informative </code> tag.</li> <li>[ ] 2.4.3 Focus Order (Level A): The order in which users navigate (the tab order) follows a logical sequence that preserves meaning and operability.</li> <li>[ ] 2.4.4 Link Purpose (In Context) (Level A): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined context (e.g., the surrounding sentence or list item). Avoid "click here."</li> <li>[ ] 2.4.5 Multiple Ways (Level AA): There is more than one way to locate a web page within a set of web pages (e.g., site search, sitemap, navigation menu).</li> <li>[ ] 2.4.6 Headings and Labels (Level AA): Headings and labels describe the topic or purpose clearly.</li> <li>[ ] 2.4.7 Focus Visible (Level AA): There is a visible focus indicator (a clear outline or highlight) for all interactive elements that receive keyboard focus.</li> </ul> Input Modalities <ul><li>[ ] 2.5.1 Pointer Gestures (Level A): All functionality that uses multipoint or path-based gestures (e.g., pinch-to-zoom, swiping) can also be operated with a single pointer without a gesture.</li> <li>[ ] 2.5.3 Label in Name (Level A): For user interface components with a visible label, the accessible name (what a screen reader reads) matches or contains the visible label.</li> </ul> <hr><h4>Principle 3: Understandable</h4>Readable <ul><li>[ ] 3.1.1 Language of Page (Level A): The default human language of the web page is specified using the <code>lang</code> attribute (e.g., <code><html lang="en"></code>).</li> <li>[ ] 3.1.2 Language of Parts (Level AA): If there is a passage in a different language on the page, it is identified with the <code>lang</code> attribute (e.g., <code>Hola</code>).</li> </ul> Predictable <ul><li>[ ] 3.2.1 On Focus (Level A): When any component receives focus, it does not initiate a change of context (e.g., submitting a form, opening a new window).</li> <li>[ ] 3.2.2 On Input (Level A): Changing the setting of any user interface component (e.g., selecting a dropdown) does not automatically change the context unless the user has been advised of the behavior before using the component.</li> <li>[ ] 3.2.3 Consistent Navigation (Level AA): Navigational mechanisms that are repeated on multiple web pages occur in the same relative order each time.</li> <li>[ ] 3.2.4 Consistent Identification (Level AA): Components that have the same functionality are identified consistently (e.g., don't use "Search" in the menu and "Find" in the footer).</li> </ul> Input Assistance <ul><li>[ ] 3.3.1 Error Identification (Level A): If an input error is automatically detected, the error is</li></ul></div><div class="message-time" data-v-bc3323c8>19:08</div></div></div></div><div class="chat-window" data-v-bc3323c8><div class="header-gemini chat-header" data-v-bc3323c8><div class="model-info" data-v-bc3323c8>GeminiGoogle</div><button class="minimize-button" title="Hide Gemini" data-v-bc3323c8> ⊟ </button></div><div class="chat-messages" data-v-bc3323c8><div class="message user-message" data-v-bc3323c8><div class="message-content" data-v-bc3323c8>website accessibility wcag checklist</div></div><div class="ai-message-gemini message ai-message" data-v-bc3323c8><div class="message-content" data-v-bc3323c8>Okay, here's a comprehensive WCAG checklist, organized by the four principles (POUR) and their associated guidelines. I've included key Success Criteria at various levels (A, AA, AAA). Consider this a starting point - you'll want to dive deeper into each criterion for full understanding. I'll also add notes at the end to help you use this list effectively.P.O.U.R. Principles of WCAG: <ul><li>Perceivable: Information and user interface components must be presentable to users in ways they can perceive.</li> <li>Operable: User interface components and navigation must be operable.</li> <li>Understandable: Information and the operation of the user interface must be understandable.</li> <li>Robust: Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.</li> </ul> WCAG 2.1 Checklist (Organized by Principle and Guideline):I. Perceivable <ul><li>Guideline 1.1: Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.</li> <li>1.1.1 Non-text Content (Level A): All non-text content that is presented to the user has a text alternative that serves an equivalent purpose.</li> <li>Examples: <code>alt</code> attributes for images, transcripts for audio/video, text descriptions for complex graphics, captions for CAPTCHA images.</li> <li>Guideline 1.2: Time-based Media: Provide alternatives for time-based media.</li> <li>1.2.1 Audio-only and Video-only (Prerecorded) (Level A): For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:</li> <li>Audio-only: An alternative for time-based media is provided that presents equivalent information.</li> <li>Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information.</li> <li>1.2.2 Captions (Prerecorded) (Level A): Captions are provided for all prerecorded audio content in synchronized media.</li> <li>1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A): An audio description of the video or media alternative is provided for all prerecorded synchronized media, except when the media is a media alternative for text and is clearly labeled as such.</li> <li>1.2.4 Captions (Live) (Level AA): Captions are provided for all live audio content in synchronized media.</li> <li>1.2.5 Audio Description (Prerecorded) (Level AA): Audio description is provided for all prerecorded video content in synchronized media.</li> <li>1.2.6 Sign Language (Prerecorded) (Level AAA): Sign language interpretation is provided for all prerecorded audio content in synchronized media.</li> <li>1.2.7 Extended Audio Description (Prerecorded) (Level AAA): Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media.</li> <li>1.2.8 Media Alternative (Prerecorded) (Level AAA): A media alternative is provided for all prerecorded synchronized media.</li> <li>1.2.9 Audio-only (Live) (Level AAA): An alternative for time-based media is provided that presents equivalent information for live audio-only content.</li> <li>Guideline 1.3: Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.</li> <li>1.3.1 Info and Relationships (Level A): Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.</li> <li>Examples: Using proper heading levels (<code><h1></code>, <code><h2></code>, etc.), using lists (<code><ul></code>, <code><ol></code>), using data tables correctly (<code><th></code> to associate header cells with data cells), using ARIA attributes where necessary to define roles and relationships.</li> <li>1.3.2 Meaningful Sequence (Level A): When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. This is especially important with CSS-based layouts.</li> <li>1.3.3 Sensory Characteristics (Level A): Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.</li> <li>Example: Instead of saying "Click the blue button on the right," say "Click the 'Submit' button on the right."</li> <li>1.3.4 Orientation (Level AA): Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.</li> <li>1.3.5 Identify Input Purpose (Level AA): The purpose of each input field collecting information about the user can be programmatically determined when:</li> <li>It serves a purpose identified in the Input Purposes for User Interface Components section; and</li> <li>The content is implemented using technologies with support for identifying the expected meaning for form input data.</li> <li>Guideline 1.4: Distinguishable: Make it easier for users to see and hear content including separating foreground from background.</li> <li>1.4.1 Use of Color (Level A): Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.</li> <li>Example: Use text labels in addition to color to indicate required fields.</li> <li>1.4.2 Audio Control (Level A): If any audio on a web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.</li> <li>1.4.3 Contrast (Minimum) (Level AA): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1.</li> <li>Exceptions: Large text (18pt or 14pt bold) requires only 3:1. Incidental text (inactive UI components, pure decoration) has no contrast requirement. Logotypes have no contrast requirement.</li> <li>1.4.4 Resize text (Level AA): Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.</li> <li>1.4.5 Images of Text (Level AA): If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following:</li> <li>Customizable: The image of text can be visually customized to the user's requirements;</li> <li>Essential: A particular presentation of text is essential to the information being conveyed.</li> <li>1.4.6 Contrast (Enhanced) (Level AAA): The visual presentation of text and images of text has a contrast ratio of at least 7:1.</li> <li>Exceptions: Large text (18pt or 14pt bold) requires only 4.5:1. Incidental text has no contrast requirement. Logotypes have no contrast requirement.</li> <li>1.4.7 Low or No Background Audio (Level AAA): For prerecorded audio content that (1) primarily contains speech in the foreground, (2) does not contain audio captcha or audio logo, and (3) is not vocal music intended to be a primary form of expression, at least one of the following is true:</li> <li>No Background: The audio does not contain background sounds.</li> <li>Turn Off: The background sounds are at least 20 decibels lower than the foreground speech content.</li> <li>Control: A mechanism is available to turn the background sound volume up or down independently from the foreground speech content.</li> <li>1.4.8 Visual Presentation (Level AAA): For the visual presentation of blocks of text, a mechanism is available to achieve the following:</li> <li>Foreground and background colors can be chosen by the user.</li> <li>Width is no more than 80 characters or glyphs (40 if CJK).</li> <li>Text is not justified (aligned to both the left and the right margins).</li> <li>Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing.</li> <li>1.4.9 Images of Text (No Exception) (Level AAA): Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.</li> <li>1.4.10 Reflow (Level AA): Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:</li> <li>Vertical scrolling content at a width equivalent to 320 CSS pixels;</li> <li>Horizontal scrolling content at a height equivalent to 256 CSS pixels.</li> <li>1.4.11 Non-text Contrast (Level AA): The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):</li> <li>User Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;</li> <li>Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.</li> <li>1.4.12 Text Spacing (Level AA): In content implemented using markup languages that support text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:</li> <li>Line height (line spacing) to at least 1.5 times the font size;</li> <li>Spacing following paragraphs to at least 2 times the font size;</li> <li>Letter spacing (tracking) to at least 0.12 times the font size;</li> <li>Word spacing to at least 0.16 times the font size.</li> <li>1.4.13 Content on Hover or Focus (Level AA): Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:</li> <li>Dismissible: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus;</li> <li>Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;</li> <li>Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or the information it conveys is no longer valid.</li> </ul> II. Operable <ul><li>Guideline 2.1: Keyboard Accessible: Make all functionality available from a keyboard.</li> <li>2.1.1 Keyboard (Level A): All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying functionality requires input that depends on the path of the user's movement and not just the endpoints.</li> <li>2.1.2 No Keyboard Trap (Level A): If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.</li> <li>2.1.3 Keyboard (No Exception) (Level AAA): All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.</li> <li>2.1.4 Character Key Shortcuts (Level A): If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:</li> <li>Turn off: A mechanism is available to turn the shortcut off;</li> <li>Remap: A mechanism is available to remap the shortcut to use one or more non-printable key (e.g. Ctrl, Alt, etc);</li> <li>Active only on focus: The keyboard shortcut is only active when the component has focus.</li> <li>Guideline 2.2: Enough Time: Provide users enough time to read and use content.</li> <li>2.2.1 Timing Adjustable (Level A): For each time limit that is set by the content, at least one of the following is true:</li> <li>Turn off: The user is allowed to turn off the time limit before encountering it; or</li> <li>Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or</li> <li>Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or</li> <li>Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative is possible; or</li> <li>Essential Exception: The time limit is essential and extending it would invalidate the activity; or</li> <li>20 Second Exception: The time limit is longer than 20 hours.</li> <li>2.2.2 Pause, Stop, Hide (Level A): For moving, blinking, scrolling, or auto-updating information, all of the following are true:</li> <li>Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is essential to the activity; and</li> <li>Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is essential to the activity.</li> <li>2.2.3 No Timing (Level AAA): Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events.</li> <li>2.2.4 Interruptions (Level AAA): Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.</li> <li>2.2.5 Re-authenticating (Level AAA): When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.</li> <li>Guideline 2.3: Seizures: Do not design content in a way that is known to cause seizures.</li> <li>2.3.1 Three Flashes or Below Threshold (Level A): Web pages do not contain anything that flashes more than three times in any one-second period, or the flash is below the general flash and red flash thresholds.</li> <li>2.3.2 Three Flashes (Level AAA): Web pages do not contain anything that flashes more than three times in any one-second period.</li> <li>Guideline 2.4: Navigable: Provide ways to help users navigate, find content, and determine where they are.</li> <li>2.4.1 Bypass Blocks (Level A): A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. Examples: "Skip to main content" links.</li> <li>2.4.2 Page Titled (Level A): Web pages have titles that describe topic or purpose. Example: Meaningful <code><title></code> elements.</li> <li>2.4.3 Focus Order (Level A): If a web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.</li> <li>2.4.4 Link Purpose (In Context) (Level A): The purpose of each link can be determined from the link text alone, or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.</li> <li>2.4.5 Multiple Ways (Level AA): More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. Examples: Site map, search function, table of contents, breadcrumbs.</li> <li>2.4.6 Headings and Labels (Level AA): Headings and labels describe topic or purpose.</li> <li>2.4.7 Focus Visible (Level AA): Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.</li> <li>2.4.8 Location (Level AAA): Information about the user's location within a set of Web pages is available. Examples: Breadcrumbs, highlighting the current page in a navigation menu.</li> <li>2.4.9 Link Purpose (Link Only) (Level AAA): A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.</li> <li>2.4.10 Section Headings (Level AAA): Section headings are used to organize the content.</li> <li>Guideline 2.5: Input Modalities: Make it easier for users to operate functionality through various inputs beyond keyboard.</li> <li>2.5.1 Pointer Gestures (Level A): All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.</li> <li>2.5.2 Pointer Cancellation (Level A): For functionality that can be operated using a single pointer, at least one of the following is true:</li> <li>No Down-Event: The down-event of the pointer is not used to execute any part of the function;</li> <li>Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;</li> <li>Up Reversal: The up-event reverses any outcome from the preceding down-event;</li> <li>Essential: Completing the function on the down-event is essential.</li> <li>2.5.3 Label in Name (Level A): For user interface components with labels that include text or images of text, the name contains the text that is presented visually.</li> <li>2.5.4 Motion Actuation (Level A): Functionality that can be operated by device motion or user motion can also be operated by user interface components, and responding to motion can be disabled to prevent accidental actuation, except when:</li> <li>Supported Interface: The motion is used to operate through an accessibility supported interface;</li> <li>Essential: The motion is essential for the function and doing so would invalidate the activity.</li> <li>2.5.5 Target Size (Level AAA): The size of the target for pointer inputs is at least 44 by 44 CSS pixels, except when:</li> <li>Equivalent: The target is available through an equivalent link or control that is at least 44 by 44 CSS pixels;</li> <li>Inline: The target is in a sentence or block of text;</li> <li>User Agent Control: The size of the target is determined by the user agent and is not modified by the author;</li> <li>Essential: A particular presentation of the target is essential to the information being conveyed.</li> <li>2.5.6 Concurrent Input Modalities (Level AAA): Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to maintain the security of the content, or required to respect user settings.</li> </ul> III. Understandable <ul><li>Guideline 3.1: Readable: Make text content readable and understandable.</li> <li>3.1.1 Language of Page (Level A): The default human language of each Web page can be programmatically determined. Example: Using the <code>lang</code> attribute in the <code><html></code> tag.</li> <li>3.1.2 Language of Parts (Level AA): The language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of undetermined language, and words or phrases that have become part of the vernacular of the immediately surrounding text. Example: Using the <code>lang</code> attribute on elements containing content in a different language.</li> <li>3.1.3 Unusual Words (Level AAA): A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.</li> <li>3.1.4 Abbreviations (Level AAA): A mechanism for identifying the expanded form or meaning of abbreviations is available.</li> <li>3.1.5 Reading Level (Level AAA): When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content or a version that does not require reading ability more advanced than the lower secondary education level is available.</li> <li>3.1.6 Pronunciation (Level AAA): A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.</li> <li>Guideline 3.2: Predictable: Make Web pages appear and operate in predictable ways.</li> <li>3.2.1 On Focus (Level A): When any user interface component receives focus, it does not initiate a change of context.</li> <li>3.2.2 On Input (Level A): Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.</li> <li>3.2.3 Consistent Navigation (Level AA): Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.</li> <li>3.2.4 Consistent Identification (Level AA): Components that have the same functionality within a set of Web pages are identified consistently.</li> <li>3.2.5 Change on Request (Level AAA): Changes of context are initiated only by user request or a mechanism is available to turn off such changes.</li> <li>Guideline 3.3: Input Assistance: Help users avoid and correct mistakes.</li> <li>3.3.1 Error Identification (Level A): If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.</li> <li>3.3.2 Labels or Instructions (Level A): Labels or instructions are provided when content requires user input.</li> <li>3.3.3 Error Suggestion (Level AA): If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.</li> <li>3.3.4 Error Prevention (Legal, Financial, Data) (Level AA): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user-provided data to data storage systems, at least one of the following is true:</li> <li>Reversible: Submissions are reversible.</li> <li>Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.</li> <li>Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.</li> <li>3.3.5 Help (Level AAA): Context-sensitive help is available.</li> <li>3.3.6 Error Prevention (All) (Level AAA): For Web pages that require the user to submit information, at least one of the following is true:</li> <li>Reversible: Submissions are reversible.</li> <li>Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.</li> <li>Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.</li> </ul> IV. Robust <ul><li>Guideline 4.1: Compatible: Maximize compatibility with current and future user agents, including assistive technologies.</li> <li>4.1.1 Parsing (Level A): In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.</li> <li>4.1.2 Name, Role, Value (Level A): For all user interface components (including but not limited to form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.</li> <li>4.1.3 Status Messages (Level AA): In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.</li> </ul> Important Notes & How to Use This Checklist Effectively: <ul><li>Understand the Levels (A, AA, AAA):</li> <li>Level A: The most basic level of accessibility. Addressing these issues is critical.</li> <li>Level AA: The generally accepted target for most websites. Many laws and guidelines require Level AA compliance.</li> <li>Level AAA: The highest level of accessibility. While desirable, it's often not feasible for all content due to practical limitations. Consider these guidelines where possible, but don't let the pursuit of AAA prevent you from achieving A and AA.</li> <li>Testing is Essential: This checklist is a guide, but manual and automated testing are crucial to verify compliance.</li> <li>Tools: Utilize accessibility testing tools (both automated and manual) throughout the development process. Some popular tools include:</li> <li>WAVE (Web Accessibility Evaluation Tool): A browser extension for quick checks.</li> <li>Lighthouse (Google Chrome DevTools): Provides accessibility audits.</li> <li>axe DevTools: Browser extension and CLI tool for automated accessibility testing.</li> <li>Screen Readers (NVDA, VoiceOver, JAWS): Essential for testing the experience for screen reader users.</li> <li>Color Contrast Analyzers: To verify sufficient contrast.</li> <li>Context Matters: Accessibility is not just about following rules; it's about creating a usable experience for all users. Consider the context of your content and your target audience.</li> <li>Involve Users with Disabilities: The best way to ensure accessibility is to involve people with disabilities in the design and testing process. Get their feedback!</li> <li>Keep Learning: Accessibility is an evolving field. Stay up-to-date with the latest guidelines and best practices.</li> <li>Documentation: Document your accessibility efforts. This helps maintain consistency and demonstrates your commitment to accessibility.</li> <li>Prioritize: If you're working on an existing website, prioritize the most critical issues and address them first. Focus on areas that have the biggest impact on the largest number of users.</li> <li>Not a Replacement for Expertise: This checklist is not a substitute for professional accessibility expertise. Consider consulting with an accessibility specialist for complex projects.</li> <li>WCAG 2.2: Be aware that WCAG 2.2 is the latest version (as of late 2023) and includes some new success criteria. While WCAG 2.1 is still widely referenced, it's a good idea to familiarize yourself with the 2.2 updates as well.</li> </ul> By following this checklist and incorporating accessibility testing into your development workflow, you can create websites that are more inclusive and usable for everyone. Good luck! </div><div class="message-time" data-v-bc3323c8>19:08</div></div></div></div><div class="chat-window" data-v-bc3323c8><div class="header-grok chat-header" data-v-bc3323c8><div class="model-info" data-v-bc3323c8>GrokxAI</div><button class="minimize-button" title="Hide Grok" data-v-bc3323c8> ⊟ </button></div><div class="chat-messages" data-v-bc3323c8><div class="message user-message" data-v-bc3323c8><div class="message-content" data-v-bc3323c8>website accessibility wcag checklist</div></div><div class="ai-message-grok message ai-message" data-v-bc3323c8><div class="message-content" data-v-bc3323c8>Website accessibility ensures that all users, including those with disabilities, can perceive, understand, navigate, and interact with a website. The Web Content Accessibility Guidelines (WCAG), developed by the World Wide Web Consortium (W3C), are the most widely accepted standards for web accessibility. The current version, WCAG 2.1 (as of this writing), is organized into four main principles (Perceivable, Operable, Understandable, and Robust), with specific guidelines and success criteria at three levels: A (basic), AA (intermediate), and AAA (advanced). Most organizations aim for Level AA compliance, as it is the standard for many legal requirements.Below is a concise WCAG Checklist based on WCAG 2.1 Level AA. This checklist can serve as a starting point for evaluating and improving a website's accessibility. Note that this is not exhaustive, and full compliance often requires detailed testing with assistive technologies and user feedback.<hr><h3>Principle 1: Perceivable</h3> Information and user interface components must be presented in ways that users can perceive (e.g., through sight, sound, or touch).<h4>Text Alternatives (1.1)</h4> <ul><li>1.1.1 Non-text Content (Level A): Provide text alternatives (alt text) for all non-text content (images, icons, etc.) so screen readers can describe them. Ensure alt text is descriptive or uses <code>alt=""</code> for decorative images.</li> </ul> <h4>Time-based Media (1.2)</h4> <ul><li>1.2.1 Audio-only and Video-only (Prerecorded) (Level A): Provide alternatives for audio-only or video-only content (e.g., transcripts for audio, text descriptions for video).</li> <li>1.2.2 Captions (Prerecorded) (Level A): Include captions for all prerecorded audio content in synchronized media (e.g., videos).</li> <li>1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A): Provide audio descriptions or full text alternatives for prerecorded video content.</li> <li>1.2.4 Captions (Live) (Level AA): Include captions for live audio content in synchronized media.</li> <li>1.2.5 Audio Description (Prerecorded) (Level AA): Provide audio descriptions for prerecorded video content.</li> </ul> <h4>Adaptable (1.3)</h4> <ul><li>1.3.1 Info and Relationships (Level A): Ensure content structure (headings, lists, tables) is programmatically determinable using proper HTML markup (e.g., <code><h1></code>, <code><table></code> with headers).</li> <li>1.3.2 Meaningful Sequence (Level A): Present content in a logical reading order that can be determined programmatically.</li> <li>1.3.3 Sensory Characteristics (Level A): Avoid instructions that rely solely on sensory characteristics (e.g., “click the red button”); use text or labels instead.</li> <li>1.3.4 Orientation (Level AA): Ensure content is not restricted to a single display orientation (portrait or landscape).</li> <li>1.3.5 Identify Input Purpose (Level AA): Label inputs programmatically (e.g., autocomplete attributes for form fields like name or email).</li> </ul> <h4>Distinguishable (1.4)</h4> <ul><li>1.4.1 Use of Color (Level A): Don’t rely on color alone to convey information (e.g., use text labels alongside color-coded elements).</li> <li>1.4.2 Audio Control (Level A): Provide controls to pause, stop, or adjust volume for audio that plays automatically for more than 3 seconds.</li> <li>1.4.3 Contrast (Minimum) (Level AA): Ensure text and images of text have a contrast ratio of at least 4.5:1 (normal text) or 3:1 (large text or UI components).</li> <li>1.4.4 Resize Text (Level AA): Allow text to be resized up to 200% without loss of content or functionality.</li> <li>1.4.5 Images of Text (Level AA): Avoid using images of text unless essential (e.g., logos); use real text for better readability and scalability.</li> </ul> <hr><h3>Principle 2: Operable</h3> User interface components and navigation must be operable by all users, including those using keyboards or assistive technologies.<h4>Keyboard Accessible (2.1)</h4> <ul><li>2.1.1 Keyboard (Level A): Ensure all functionality is accessible via keyboard (e.g., navigation, form submission) without requiring a mouse.</li> <li>2.1.2 No Keyboard Trap (Level A): Ensure users can move focus away from components using only a keyboard (no “traps” where focus gets stuck).</li> <li>2.1.4 Character Key Shortcuts (Level A): If single-character keyboard shortcuts are used, provide a way to turn them off or remap them.</li> </ul> <h4>Enough Time (2.2)</h4> <ul><li>2.2.1 Timing Adjustable (Level A): Allow users to adjust, extend, or turn off time limits for content (e.g., session timeouts), unless the limit is essential.</li> <li>2.2.2 Pause, Stop, Hide (Level A): Provide controls to pause, stop, or hide moving, blinking, or auto-updating content that lasts more than 5 seconds.</li> </ul> <h4>Seizures and Physical Reactions (2.3)</h4> <ul><li>2.3.1 Three Flashes or Below Threshold (Level A): Avoid content that flashes more than 3 times per second to prevent triggering seizures.</li> </ul> <h4>Navigable (2.4)</h4> <ul><li>2.4.1 Bypass Blocks (Level A): Provide a “skip to content” link to bypass repetitive navigation blocks for keyboard and screen reader users.</li> <li>2.4.2 Page Titled (Level A): Ensure each page has a unique, descriptive <code><title></code> tag.</li> <li>2.4.3 Focus Order (Level A): Ensure focus order follows a logical sequence (e.g., left to right, top to bottom) when navigating with a keyboard.</li> <li>2.4.4 Link Purpose (In Context) (Level A): Ensure the purpose of each link is clear from its text or surrounding context.</li> <li>2.4.5 Multiple Ways (Level AA): Provide multiple ways to navigate to pages (e.g., menus, sitemaps, search) unless the page is part of a linear process.</li> <li>2.4.6 Headings and Labels (Level AA): Use descriptive headings and labels to organize content and describe form fields.</li> <li>2.4.7 Focus Visible (Level AA): Ensure a visible focus indicator (e.g., outline) appears when navigating with a keyboard.</li> </ul> <h4>Input Modalities (2.5)</h4> <ul><li>2.5.1 Pointer Gestures (Level A): Avoid requiring multipoint or path-based gestures (e.g., swipe, pinch) unless there’s a single-point alternative.</li> <li>2.5.2 Pointer Cancellation (Level A): Ensure touch or click events can be canceled (e.g., no action on “touch down,” only on “touch up”).</li> <li>2.5.3 Label in Name (Level A): Ensure the visible label of a component matches or is part of its accessible name (for screen readers).</li> <li>2.5.4 Motion Actuation (Level A): Avoid device motion (e.g., shaking) as the only way to trigger functionality; provide alternatives.</li> </ul> <hr><h3>Principle 3: Understandable</h3> Information and the operation of the user interface must be understandable to all users.<h4>Readable (3.1)</h4> <ul><li>3.1.1 Language of Page (Level A): Define the primary language of each page using the <code>lang</code> attribute in HTML (e.g., <code><html lang="en"></code>).</li> <li>3.1.2 Language of Parts (Level AA): Identify changes in language for specific content using the <code>lang</code> attribute (e.g., for a Spanish phrase on an English page).</li> </ul> <h4>Predictable (3.2)</h4> <ul><li>3.2.1 On Focus (Level A): Ensure components don’t unexpectedly change context (e.g., auto-submitting a form) when receiving focus.</li> <li>3.2.2 On Input (Level A): Ensure user input doesn’t cause unexpected context changes (e.g., selecting an option shouldn’t redirect without warning).</li> <li>3.2.3 Consistent Navigation (Level AA): Maintain consistent navigation mechanisms across multiple pages.</li> <li>3.2.4 Consistent Identification (Level AA): Use consistent labels, names, and icons for components with the same functionality.</li> </ul> <h4>Input Assistance (3.3)</h4> <ul><li>3.3.1 Error Identification (Level A): Clearly identify and describe input errors to users in text (e.g., “Please enter a valid email address”).</li> <li>3.3.2 Labels or Instructions (Level A): Provide clear labels or instructions for user input fields.</li> <li>3.3.3 Error Suggestion (Level AA): Offer suggestions to correct input errors when possible (e.g., “Did you mean…?”).</li> <li>3.3.4 Error Prevention (Legal, Financial, Data) (Level AA): For legal, financial, or data submissions, allow users to review, confirm, or reverse actions to prevent errors.</li> </ul> <hr><h3>Principle 4: Robust</h3> Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies.<h4>Compatible (4.1)</h4> <ul><li>4.1.1 Parsing (Level A): Ensure HTML/CSS code is well-formed with no major parsing errors (e.g., properly nested tags, unique IDs).</li> <li>4.1.2 Name, Role, Value (Level A): Ensure custom UI components provide programmatically accessible name, role, and value information (e.g., using ARIA attributes).</li> <li>**4</li></ul></div><div class="message-time" data-v-bc3323c8>19:08</div></div></div></div></div></div><div class="comparison-footer" data-v-bc3323c8><div class="try-sneos" data-v-bc3323c8>💡 Try this comparison yourself:<a href="https://sneos.com?prompt=website%20accessibility%20wcag%20checklist" target="_blank" data-v-bc3323c8>Compare AI models side-by-side on SNEOS</a></div></div></div><h2 id="analysis" tabindex="-1"><a class="header-anchor" href="#analysis">Analysis</a></h2>This comparison demonstrates the different approaches each AI model takes when responding to the same prompt. Here are the key differences observed:<h3 id="response-characteristics" tabindex="-1"><a class="header-anchor" href="#response-characteristics">Response Characteristics</a></h3>DeepSeek: Provides a concise response with 170 sentences.Gemini: Provides a direct response with 348 sentences.Grok: Provides a concise response with 213 sentences.<h2 id="key-takeaways" tabindex="-1"><a class="header-anchor" href="#key-takeaways">Key Takeaways</a></h2><ul><li>Each model brings unique strengths to this type of query</li><li>Response styles vary significantly between models</li><li>Consider your specific use case when choosing between these models</li></ul><h2 id="try-this-comparison-yourself" tabindex="-1"><a class="header-anchor" href="#try-this-comparison-yourself">Try This Comparison Yourself</a></h2>Want to test these models with your own prompts? Visit <a href="https://sneos.com" target="_blank" rel="noopener noreferrer">SNEOS.com</a> to compare AI responses side-by-side in real-time.<hr>This comparison was generated using the <a href="https://sneos.com" target="_blank" rel="noopener noreferrer">SNEOS AI Comparison Tool</a>Published: October 01, 2025 | Models: DeepSeek, Gemini, Grok</div></div></main><footer class="clean-footer"><a href="https://sneos.com" target="_blank" class="sneos-link"> Try AI comparisons on SNEOS.com → </a></footer></div></div> <script type="module" src="/assets/app-mxcCMdWi.js" defer></script> </body> </html>