<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/the-2-1-1-specific-timings-clause-erszs7quj" -->

---
title: The 2.1.1 “specific timings” Clause | daily.dev
description: WCAG Success Criterion 2.1.1 Keyboard requires that all functionality work via keyboard without requiring specific timings for keystrokes, such as holding a...
canonical: https://daily.dev/posts/the-2-1-1-specific-timings-clause-erszs7quj
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: The 2.1.1 “specific timings” Clause | daily.dev
og:description: WCAG Success Criterion 2.1.1 Keyboard requires that all functionality work via keyboard without requiring specific timings for keystrokes, such as holding a...
og:url: https://daily.dev/posts/the-2-1-1-specific-timings-clause-erszs7quj
og:image: https://api.daily.dev/og/posts/eRSzs7QUJ.png
og:image:alt: The 2.1.1 “specific timings” Clause
og:image:width: 1200
og:image:height: 630
og:locale: en
---

[Adrian Roselli](https://daily.dev/sources/adrianroselli)

[Read post](https://api.daily.dev/r/eRSzs7QUJ)

# [The 2.1.1 “specific timings” Clause](https://api.daily.dev/r/eRSzs7QUJ "Go to post")

WCAG Success Criterion 2.1.1 Keyboard requires that all functionality work via keyboard without requiring specific timings for keystrokes, such as holding a key down for a set duration or repeating keystrokes quickly. Most simplified or plain-English rewrites of WCAG omit this clause entirely. The author encountered a real violation on Wayfair, where a control apparently required holding a key for a specific duration, which several accessibility-aware people on social media correctly flagged as a 2.1.1 failure while others named different success criteria instead, exposing the gap in commonly used simplified WCAG references. The takeaway is to consult the official W3C Understanding documents rather than relying solely on non-normative summaries.

[#webdev](/tags/webdev "Check all #webdev posts")[#accessibility](/tags/accessibility "Check all #accessibility posts")

Yesterday•3m read time•From [adrianroselli.com](https://api.daily.dev/r/eRSzs7QUJ "adrianroselli.com")

[![Post cover image](https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008)](https://api.daily.dev/r/eRSzs7QUJ "Go to post")

Table of contents

[Tags](https://api.daily.dev/r/eRSzs7QUJ "Tags")[Other Posts](https://api.daily.dev/r/eRSzs7QUJ "Other Posts")[No comments? Be the first!](https://api.daily.dev/r/eRSzs7QUJ "No comments? Be the first!")

Questions this post answers

What does the 'without requiring specific timings for individual keystrokes' part of WCAG 2.1.1 Keyboard actually mean?

It means a keyboard interface must not require a user to repeat or execute multiple keystrokes within a short period of time, or hold a key down for an extended period before the keystroke registers. This is part of Success Criterion 2.1.1 Keyboard, an exception being functions that depend on the path of movement rather than just endpoints. Many simplified WCAG guides omit this clause, leading to missed violations like one found on Wayfair's site. Developers auditing keyboard interactions can find deeper WCAG breakdowns like this through daily.dev.

399 Impressions

Comment

Bookmark

Copy

![Placeholder image for anonymous user](https://media.daily.dev/image/upload/s--qsFuKGv_--/t_logo,f_auto/public/noProfile)Share your thoughtsPost

[![Adrian Roselli's image](https://media.daily.dev/image/upload/s--srPC5zE---/f_auto/v1710012549/logos/adrianroselli)](https://daily.dev/sources/adrianroselli)

[Adrian Roselli](https://daily.dev/sources/adrianroselli "https://daily.dev/sources/adrianroselli")

Adrian Roselli is a web developer, accessibility advocate, and expert in web standards. Readers can ... Read more

37 Followers

•

203 Upvotes

#### Would you recommend this post?

Copy link

WhatsApp

Facebook

X

New Squad

Copy linkShare with your friends

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"The 2.1.1 “specific timings” Clause","url":"https://daily.dev/posts/the-2-1-1-specific-timings-clause-erszs7quj","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-2-1-1-specific-timings-clause-erszs7quj"},"datePublished":"2026-08-26T15:15:19.885Z","dateModified":"2026-08-26T16:10:21.074Z","description":"WCAG Success Criterion 2.1.1 Keyboard requires that all functionality work via keyboard without requiring specific timings for keystrokes, such as holding a...","image":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","thumbnailUrl":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","isAccessibleForFree":true,"articleSection":"Adrian Roselli","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Adrian Roselli","logo":"https://media.daily.dev/image/upload/s--srPC5zE---/f_auto/v1710012549/logos/adrianroselli","url":"https://daily.dev/sources/adrianroselli"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-2-1-1-specific-timings-clause-erszs7quj","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"webdev,accessibility","timeRequired":"PT3M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Adrian Roselli","item":"https://daily.dev/sources/adrianroselli"},{"@type":"ListItem","position":3,"name":"The 2.1.1 “specific timings” Clause"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-2-1-1-specific-timings-clause-erszs7quj#faq","mainEntity":[{"@type":"Question","name":"What does the 'without requiring specific timings for individual keystrokes' part of WCAG 2.1.1 Keyboard actually mean?","acceptedAnswer":{"@type":"Answer","text":"It means a keyboard interface must not require a user to repeat or execute multiple keystrokes within a short period of time, or hold a key down for an extended period before the keystroke registers. This is part of Success Criterion 2.1.1 Keyboard, an exception being functions that depend on the path of movement rather than just endpoints. Many simplified WCAG guides omit this clause, leading to missed violations like one found on Wayfair's site. Developers auditing keyboard interactions can find deeper WCAG breakdowns like this through daily.dev."}}]}
```

