Accessibility Statement

Version 2.0 · Last reviewed: April 24, 2026  ·  Next review: October 24, 2026

We build accessibility tools for the web. Holding ourselves to the same standard we set for our customers is not optional — it is our obligation. This statement also sets clear expectations about what our tools do, what they do not do, and our testing status. Found a barrier? [email protected]

1. Scope of This Statement

This Accessibility Statement applies to the following properties operated by Angstroma, Inc. (“Angstroma”, “we”, “us”):

• The Angstroma portal at angstroma.com, including signed-in customer areas and documentation.
• The Angstroma Chrome extension (“Extension”) published at the Chrome Web Store.
• The Angstroma widget SDK (“Widget”) delivered via cdn.angstroma.com and embedded on customer websites.
• Angstroma AI features including AI Summarize, AI Translate, AI Alt-text, AI Grammar, AI Simplify, AI Flashcards, AI Homework Helper, and related tools.

This statement does not cover third-party websites on which the Widget is installed by our customers. Customers are responsible for the accessibility of their own websites; see Section 10.

2. Conformance Status

“Partially conformant” means that some parts of the content do not fully conform to the accessibility standard. We are actively working toward full WCAG 2.1 AA conformance, with a review scheduled every six months.

Our stated target is WCAG 2.1 Level AA as defined by the W3C Web Accessibility Initiative. We also reference WCAG 2.2 recommendations as best practice. Our conformance status is based on self-assessment and internal testing. It is not currently certified by an independent auditor.

3. What the Portal Does Well

• Semantic HTML5 throughout — headings, landmarks, lists, and tables used correctly
• Keyboard navigation supported on all interactive elements (forms, modals, navigation)
• All interactive elements have visible focus indicators
• Color contrast meets WCAG AA — 4.5:1 for normal text, 3:1 for large text
• All images have descriptive alt text; decorative images use empty alt attributes
• Forms have associated labels and descriptive error messages
• All modals use Radix UI Dialog with proper ARIA roles and focus trapping
• No content flashes or auto-playing media
• Touch targets are minimum 44×44 px
• Skip navigation link available for screen reader and keyboard users
• Icons have accessible labels or are marked decorative with aria-hidden

4. Known Portal Issues & Remediation Roadmap

We are honest about what is not yet fully accessible on angstroma.com. The following known issues are on our remediation roadmap:

If you encounter an accessibility issue not listed here, please report it — we treat all reports as high priority.

5. The Angstroma Chrome Extension

The Extension provides a side-panel interface and on-page tools designed to help users who face accessibility barriers on arbitrary websites. Published at the Chrome Web Store as “Angstroma Accessibility.”

What the Extension includes

• Approximately 80 accessibility tools covering vision (contrast, color-blindness filters, text size), reading (dyslexia-friendly fonts, line/letter/word spacing, bionic reading), focus (reading masks, rulers, spotlights), navigation (large cursor, keyboard mode, highlight links), motion (reduced motion, pause GIFs), cognitive (simplified layout, reading mode), and audio (basic text-to-speech, media controls).
• One-tap accessibility profile presets (Seizure Safe, Vision Impaired, ADHD Friendly, Dyslexia, Screen Reader, Keyboard Only) that enable common tool bundles.
• A Quick Actions row surfacing the most-used tools.
• Optional Pro-tier productivity tools (sticky notes, focus timer, speed reader, and similar) and Pro-tier AI-powered tools (see Section 7).

How the Extension works

Accessibility tools in the Extension operate by injecting CSS and DOM modifications into the web page in the user’s active browser tab. The Extension requires the activeTab permission so that changes apply only to the page the user is actively viewing. The Extension does not broadcast modifications to Angstroma servers, does not track which websites the user visits, and does not transmit page content to our servers (except where the user explicitly invokes an AI feature; see Section 7 and Section 12).

Known Extension limitations

Language and localization status

If you notice a translation error or missing translation in any language, please report it via [email protected]. Bidirectional languages (Arabic) should render in right-to-left; report any layout breakage in that context as a priority item.

• Sites that use strict CSP without style-src ‘unsafe-inline’ may block style injection.
• Pages that render content entirely inside Shadow DOM (web components) may not receive all style overrides.
• Cross-origin iframes cannot be modified by content scripts due to browser security.
• Dynamically-injected content (single-page apps, infinite scroll) may require the user to toggle the tool off and on.
• Text-to-speech relies on the operating system’s installed voices; voice quality varies.

6. The Angstroma Widget SDK

The Widget is a JavaScript library that Angstroma customers embed on their own websites via a <script> tag. It provides an on-page accessibility menu that end-users (the customer’s site visitors) can open to adjust visual, reading, and navigation settings.

Angstroma is responsible for the accessibility of the Widget interface itself (menu open/close, keyboard navigation within the menu, contrast of controls, ARIA semantics). Angstroma is not responsible for the accessibility of the customer’s host website. Installing the Widget does not automatically make a website accessible, WCAG-conformant, or legally compliant. See Section 10.

The Widget never blocks visitor access to its accessibility features due to the customer’s billing status. Even if a customer’s subscription lapses, the Widget continues to serve accessibility functions to their site visitors — blocking access to an accessibility feature because of a billing state would itself create accessibility harm, and we will not do it.

7. AI Features

Angstroma offers optional AI-powered features, including but not limited to: AI Summarize, AI Explain Selection, AI Translate, AI Grammar Check, AI Rephrase, AI Simplify, AI Citation Formatter, AI Alt-text Generator, AI Flashcards, AI Essay Outliner, and AI Homework Helper. These features are powered by large language models operated by Anthropic PBC (Claude API).

AI features require transmitting the user-selected text or image to Anthropic’s Claude API. We scrub identifiable personal information from inputs before transmission where technically feasible. We do not train any AI model on user content. See our Privacy Policy and Data Processing Agreement for detail.

8. Testing Status — All Tools Are Provided as “Beta”

“Beta” in this context means:

• Tools are actively developed and may change, be improved, or be removed.
• A tool may not work on every website. Web platforms are heterogeneous; no single tool can behave identically across all pages.
• A tool may produce unexpected visual or behavioral results on some sites. If that happens, toggle the tool off and report it via the Feedback channel.
• Subscribing to a paid plan does not change the beta status. Payment unlocks additional productivity tools and AI credits; it does not convert our free accessibility tools into warranted production features. See Section 11.

We disclose the testing status because we believe in honesty with users. A tool labeled as “final” when it is still evolving would mislead users who rely on it for accessibility. We would rather be accurate than marketable.

9. Login, Authentication & Account Management

The sign-in, sign-up, password-reset, two-factor authentication (2FA), and account-recovery flows used on angstroma.com and within the Extension are designed with the following accessibility features:

• All form fields have programmatically associated labels (never label-by-placeholder alone).
• Password-strength and validation errors are communicated in plain text and programmatically (via aria-describedby / role=“alert”).
• Password fields include a visible show/hide toggle with an accessible name.
• The session cookie is HttpOnly, Secure, and SameSite=Strict. Users may not experience session handling directly, but the security properties do not require any inaccessible UI.
• 2FA is offered via TOTP authenticator apps and FIDO2 security keys. We do not use SMS-based 2FA — SMS codes are inaccessible to many users (no deaf-dialer support, delivery failures in assistive-tech flows).
• Recovery codes are printable, copyable, and can be downloaded as a plain text file for offline storage.
• OAuth sign-in (Google) uses the upstream provider’s accessibility features. Angstroma has no control over the accessibility of the Google sign-in page during the handoff.
• Rate-limiting and lockout messages are communicated in text with time-remaining information, not just generic errors.

Known login-flow limitations: some error-recovery flows trigger additional rate-limit pauses that do not always announce via live regions. If you are unable to complete a login or recovery task using assistive technology, contact [email protected] and we will assist you through an alternative channel within 2 business days.

10. What Our Tools Do Not Do

What we do not claim

• We do not claim that installing the Widget makes a customer’s website ADA-compliant.
• We do not claim that our scanner certifies WCAG conformance. Automated tools identify a subset of possible issues; manual expert review is required for certification-grade conformance claims.
• We do not claim that the Extension converts an inaccessible website into an accessible one for all users. Structural accessibility problems (missing landmarks, broken keyboard navigation, uncaptioned videos) cannot be fully resolved from the client side.
• We do not claim that AI features are factually accurate. See Section 7.
• We do not provide legal advice. If you need legal guidance on accessibility obligations, consult a qualified attorney.

Our tools help, but the obligation is yours

If you operate a website or service subject to accessibility laws, you remain responsible for the accessibility of that website or service. Angstroma’s tools can assist with specific user needs and can surface issues via our scanner, but primary responsibility for accessible design, semantics, content, and remediation rests with you. We encourage customers to pair our tools with (i) accessible HTML foundations, (ii) manual testing with assistive technology, and (iii) expert audits when legal certainty is needed.

11. Pricing and What Each Tier Covers

Our accessibility tools — the approximately 80 features described in Section 5 — are available at no cost on the free tier of the Extension and via the Widget on customer sites. Paid plans (Extension+, Solo, Starter, Pro, Schools, Enterprise) do not unlock additional accessibility features. They unlock separate productivity tools (sticky notes, focus timer, speed reader, flashcard review, and similar) and AI features (summarize, grammar check, and similar).

We draw this line deliberately: charging for accessibility would itself create an accessibility barrier. Productivity features are a separate product decision and are offered as paid add-ons.

Any change to this pricing structure would be communicated via email to existing users at least 30 days in advance.

12. Data Collected in the Accessibility Context

Operation of accessibility tools:

• The Extension’s CSS and DOM modifications are performed entirely within the user’s browser. We do not receive a copy of the page the user is viewing, and we do not log which websites the user visits.
• The user’s tool preferences (which features are enabled, font size level, theme selection) are stored in browser-local storage. If the user signs in and enables cloud sync, those preferences are additionally synced to Angstroma servers to persist across devices.
• AI features transmit the user-selected text or image to Anthropic’s Claude API. We log the request metadata (user ID, feature name, token count, timestamp) but not the content of the request. We do not train models on user content.
• The Widget does not collect end-visitor PII. Usage counts are aggregated at the customer-tenant level for analytics and billing.

For complete details on data processing, lawful bases, retention, and data-subject rights, see our Privacy Policy, Data Processing Agreement, and Cookies Notice.

13. Technical Approach

angstroma.com is built with Next.js 16 and React 19. Our approach to accessibility includes:

• Radix UI primitives for all interactive components — dialog, dropdown, select, and more
• Automated accessibility linting with oxlint (jsx-a11y rules) in our CI pipeline
• Manual keyboard navigation testing on all new features before release
• Our own Angstroma widget deployed on angstroma.com — we use it, we test it
• Regular automated WCAG scanning using our own scanner tool
• Periodic manual review against WCAG 2.1 AA success criteria
• The Chrome Extension is built on Manifest V3 with a strict Content Security Policy (script-src ‘self’), no eval, no remote scripts.

14. Assistive Technology Compatibility

We test angstroma.com and the Extension with the following assistive technologies:

15. “As Is” Disclaimer

Nothing in this section affects rights that cannot be waived or limited under applicable consumer-protection law (for example, certain rights under EU consumer legislation or US state consumer statutes).

16. Limitation of Liability

Some jurisdictions do not allow certain limitations of liability; in those jurisdictions, the foregoing applies only to the extent permitted by law. This section does not limit liability for fraud, gross negligence, or any liability that cannot be excluded under applicable law.

17. Feedback and Contact

We welcome feedback on the accessibility of angstroma.com, the Extension, the Widget, and AI features. If you experience a barrier, please tell us:

• Email: [email protected]
• Acknowledgement: within 2 business days
• Resolution or plan: within 10 business days

When reporting, please include: (i) the URL of the page or the name of the Extension tool, (ii) a description of the barrier, (iii) the assistive technology and browser you were using, and (iv) the operating system. Screenshots or short screen recordings are welcome but not required.

18. Formal Complaints and Enforcement

If you are not satisfied with our response, you have the following options depending on your location:

• United States: Contact the U.S. Department of Justice ADA Information Line at 1-800-514-0301, or file a complaint at ada.gov
• European Union: Contact your national enforcement body responsible for the European Accessibility Act
• United Kingdom: Contact the Equality and Human Rights Commission (EHRC)

We are committed to resolving accessibility concerns directly and encourage you to contact us first.

19. Legal Compliance Context

This statement is published in accordance with:

• European Accessibility Act (EAA) — Directive (EU) 2019/882, applicable to digital services from June 2025
• Americans with Disabilities Act (ADA) — Title III requirements as interpreted by US courts
• EN 301 549 — European accessibility standard harmonized with WCAG 2.1
• Section 508 — US federal technology accessibility standard (reference)
• UK Equality Act 2010 — disability discrimination compliance (reference)
• Accessibility for Ontarians with Disabilities Act (AODA) — Canadian reference
• Disability Discrimination Act (DDA) — Australian reference

Governing law. This Accessibility Statement and any disputes arising from it are governed by the laws of the State of Delaware, United States, without regard to conflict-of-laws principles, except where mandatory local consumer-protection law provides otherwise. Users located in the European Union or United Kingdom retain all non-waivable rights under applicable local law.

20. Updates to This Statement

We review and update this Accessibility Statement at least every six months, or sooner when a material change occurs (a significant new feature launches, a known issue is remediated, a law changes, or a testing-status change occurs). The current version and last-reviewed date are shown at the top of this page.

Version history

• Version 2.0 — 2026-04-24 — Comprehensive rewrite. Added scope for Extension, Widget, and AI features. Added testing-status disclosure. Added explicit non-compliance disclaimer, pricing transparency, warranty-and-liability sections, and login-accessibility section.
• Version 1.0 — 2026-04-10 — Initial statement covering angstroma.com portal.