Repository navigation
feat(frameworks): re-export a11yTextExtractor for discoverability - #356
Merged
Merged
Conversation
a11yTextExtractor (accessible-name text extraction — aria-label, aria-labelledby, title, alt, placeholder, then textContent) was only exported from core, so users had to import it separately to pass as the textExtractor option. Re-export it from react/vue/solid/svelte/qwik so it sits alongside useAskable, and document the framework-hook usage in the annotating guide. No new dependencies.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
@askable-ui/angular
@askable-ui/context
@askable-ui/core
@askable-ui/create-app
@askable-ui/mcp
@askable-ui/qwik
@askable-ui/react
@askable-ui/react-native
@askable-ui/solid
@askable-ui/svelte
@askable-ui/vue
@askable-ui/web-component
commit: |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
a11yTextExtractor— the accessibility-aware text extractor (prefersaria-label→aria-labelledby→title→alt→placeholder→textContent) — was only exported from@askable-ui/core. To use it, framework consumers had to add a second import from core just to pass it as thetextExtractoroption. For a content-extraction-for-AI library, accessible-name quality is a correctness/a11y concern, so this should be easy to reach.What's included
Re-export
a11yTextExtractorfrom react, vue, solid, svelte, qwik (alongside the existingasMetare-export), so it sits next touseAskable:Documented the framework-hook usage in the Annotating Elements guide's existing "Accessibility-aware text extraction" section.
No new dependencies; the
textExtractoroption already existed on every framework'suseAskableoptions (they extendAskableContextOptions). React Native is intentionally excluded — it's press-driven and has noHTMLElementto extract from.Test plan
tscbuild clean (all 5 packages)🤖 Generated with Claude Code
Generated by Claude Code