<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/accessibility-annotation-kits-only-annotate-zay4bqs0n" -->

---
title: Accessibility annotation kits only annotate | daily.dev
description: Accessibility annotation kits help designers communicate intent to developers, but they only annotate—they don't guarantee accessible outcomes. The piece walks...
canonical: https://daily.dev/posts/accessibility-annotation-kits-only-annotate-zay4bqs0n
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Accessibility annotation kits only annotate | daily.dev
og:description: Accessibility annotation kits help designers communicate intent to developers, but they only annotate—they don't guarantee accessible outcomes. The piece walks...
og:url: https://daily.dev/posts/accessibility-annotation-kits-only-annotate-zay4bqs0n
og:image: https://api.daily.dev/og/posts/ZAy4Bqs0n.png
og:image:alt: Accessibility annotation kits only annotate
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Accessibility annotation kits only annotate

**[Eric Bailey](https://daily.dev/sources/ericwbailey)** · 22 min read · 0 upvotes · 0 comments

## Summary

Accessibility annotation kits help designers communicate intent to developers, but they only annotate—they don't guarantee accessible outcomes. The piece walks through when annotation kits work well (simple, well-understood components with mature design systems) versus when they break down: developers or designers lacking specialized knowledge can misapply annotations like tabindex or misuse heading structures, and complex widgets like tree views expose the limited vocabulary of these kits, leading to approximate, jury-rigged descriptions. Root causes include industrialized workflows that discourage designer-developer collaboration and systemic underinvestment in accessibility education. Recommendations include deepening knowledge of interaction patterns and ARIA, testing with real assistive technology and disabled users, pushing for better platform primitives (e.g. Open UI) and design/dev tooling that carries intent through to code, and fostering collaborative workflows with leadership buy-in.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://ericwbailey.website/published/accessibility-annotation-kits-only-annotate>

## Questions this post answers

### why is declaring role="button" on a div not enough to make it work like a real button

Declaring ARIA roles like role="button" on a div only tells assistive technology to announce it as a button; it does not confer any actual interactivity or keyboard behavior. Interactivity such as click handling, focus management, and keyboard activation must be supplied separately, typically through JavaScript, otherwise the element only appears accessible on the surface.

_Developers wiring up custom interactive components can find grounded ARIA guidance like this through daily.dev._

### why do accessibility annotation kits fail for complex components like tree views

Accessibility annotation kits use a limited, shorthand vocabulary of stickers and labels that cannot capture the full scope of considerations a complex widget like a tree view requires, including ARIA roles and states, keyboard navigation, focus management, selection state, loading states, and assistive technology compatibility quirks. Designers end up jury-rigging labels to approximate these needs, and developers implement annotations literally, producing an experience that vaguely resembles the intended pattern but behaves incorrectly for assistive technology users.

_Teams building complex accessible widgets rely on daily.dev to surface deeper guidance beyond basic annotation checklists._

### why is testing accessibility annotations with a design system not enough to guarantee accessibility

Design system documentation frequently claims to be accessible without having done proper due diligence, so relying on it as a primary accessibility reference is unreliable. Testing a tree view component with VoiceOver on macOS revealed that elaborate annotations did not translate into correct assistive technology behavior, requiring rework, which shows real assistive technology testing is necessary rather than trusting documentation or annotations alone.

_Anyone validating accessible components against real assistive technology can track these lessons on daily.dev._

## Similar posts on daily.dev

- [Level up design-to-code collaboration with GitHub’s open source Annotation Toolkit](https://daily.dev/posts/level-up-design-to-code-collaboration-with-github-s-open-source-annotation-toolkit-usecrunjb) · GitHub Blog · 64 upvotes · 1 comments
- [Why Accessibility Is An Operational Capability, Not A Feature — Smashing Magazine](https://daily.dev/posts/why-accessibility-is-an-operational-capability-not-a-feature-smashing-magazine-vush3kmuc) · Smashing Magazine · 5 upvotes · 0 comments
- [Accessibility Semantics: The UI Tree You Cannot See](https://daily.dev/posts/accessibility-semantics-the-ui-tree-you-cannot-see-ag1eahrwx) · Awesome Java Newsletter · 0 upvotes · 0 comments
- [Accessibility Isn’t a Checklist. It’s an Architecture Decision](https://daily.dev/posts/accessibility-isn-t-a-checklist-it-s-an-architecture-decision-ps8j3bwgr) · Medium · 0 upvotes · 0 comments
- [AI-Generated UI Is Inaccessible by Default – Frontend Masters Blog](https://daily.dev/posts/ai-generated-ui-is-inaccessible-by-default-frontend-masters-blog-ikugehhcg) · Frontend Masters · 2 upvotes · 0 comments

---

Tags: [#html](https://daily.dev/tags/html), [#accessibility](https://daily.dev/tags/accessibility), [#design-systems](https://daily.dev/tags/design-systems)

[View this post on daily.dev](https://daily.dev/posts/accessibility-annotation-kits-only-annotate-zay4bqs0n)

```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":"Accessibility annotation kits only annotate","url":"https://daily.dev/posts/accessibility-annotation-kits-only-annotate-zay4bqs0n","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/accessibility-annotation-kits-only-annotate-zay4bqs0n"},"datePublished":"2026-09-20T07:44:34.846Z","dateModified":"2026-09-20T07:49:30.477Z","description":"Accessibility annotation kits help designers communicate intent to developers, but they only annotate—they don't guarantee accessible outcomes. The piece walks...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/170a959994b240b62f307f928a7dfadd?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/170a959994b240b62f307f928a7dfadd?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Eric Bailey","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":"Eric Bailey","logo":"https://media.daily.dev/image/upload/s--r1vwe6z1--/f_auto,q_auto/v1789890198/logos/ericwbailey?_a=BAMAMicg0","url":"https://daily.dev/sources/ericwbailey"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/accessibility-annotation-kits-only-annotate-zay4bqs0n","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"html,accessibility,design-systems","timeRequired":"PT22M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Eric Bailey","item":"https://daily.dev/sources/ericwbailey"},{"@type":"ListItem","position":3,"name":"Accessibility annotation kits only annotate"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/accessibility-annotation-kits-only-annotate-zay4bqs0n#faq","mainEntity":[{"@type":"Question","name":"why is declaring role=\"button\" on a div not enough to make it work like a real button","acceptedAnswer":{"@type":"Answer","text":"Declaring ARIA roles like role=\"button\" on a div only tells assistive technology to announce it as a button; it does not confer any actual interactivity or keyboard behavior. Interactivity such as click handling, focus management, and keyboard activation must be supplied separately, typically through JavaScript, otherwise the element only appears accessible on the surface. Developers wiring up custom interactive components can find grounded ARIA guidance like this through daily.dev."}},{"@type":"Question","name":"why do accessibility annotation kits fail for complex components like tree views","acceptedAnswer":{"@type":"Answer","text":"Accessibility annotation kits use a limited, shorthand vocabulary of stickers and labels that cannot capture the full scope of considerations a complex widget like a tree view requires, including ARIA roles and states, keyboard navigation, focus management, selection state, loading states, and assistive technology compatibility quirks. Designers end up jury-rigging labels to approximate these needs, and developers implement annotations literally, producing an experience that vaguely resembles the intended pattern but behaves incorrectly for assistive technology users. Teams building complex accessible widgets rely on daily.dev to surface deeper guidance beyond basic annotation checklists."}},{"@type":"Question","name":"why is testing accessibility annotations with a design system not enough to guarantee accessibility","acceptedAnswer":{"@type":"Answer","text":"Design system documentation frequently claims to be accessible without having done proper due diligence, so relying on it as a primary accessibility reference is unreliable. Testing a tree view component with VoiceOver on macOS revealed that elaborate annotations did not translate into correct assistive technology behavior, requiring rework, which shows real assistive technology testing is necessary rather than trusting documentation or annotations alone. Anyone validating accessible components against real assistive technology can track these lessons on daily.dev."}}]}
```

