Accessibility at Blinkist
Our Commitment
At Blinkist, we believe everyone should have equal access to knowledge. We are committed to making our website and mobile apps accessible to people of all abilities, in line with the Web Content Accessibility Guidelines (WCAG) 2.0 AA and U.S. Section 508 of the Rehabilitation Act. We are currently actively working to identify and remove accessibility barriers across our platform.
Assistance and Feedback
As we work towards meeting these standards, we recognize that we have not yet achieved this goal. Please email us at support@blinkist.com if you encounter any accessibility barriers or have suggestions for improving the accessibility of this website and our mobile apps.
We will respond promptly and do our best to address your concerns.
Blinkist Accessibility Conformance Report — Web App
Revised Section 508 Edition (Based on VPAT(R) Version 2.5Rev)
| Product | Blinkist — Web App |
| Report Date | January 28, 2026 |
| Description | Browser-based experience providing access to Blinkist content, including discovery, user library, account/settings, and reading/listening to book summaries and guides. |
| Contact | support@blinkist.com |
Notes
Evaluation was performed on a representative sample of pages and user flows within the defined scope. This report reflects the state of the product as of January 28, 2026.
Evaluation Methodology
Automated checks (Axe DevTools):
- Tool: Axe DevTools 4.11.0
- Coverage: 20 scans across representative pages
Manual and assistive-technology (AT) testing:
- macOS + VoiceOver + Firefox
- macOS + VoiceOver + Chrome
- iOS + VoiceOver + Safari
Scopes Covered
This report covers the Blinkist web experience delivered via www.blinkist.com, including the homepage, login, authenticated app pages for browsing and managing content, and the reader/player experience.
Out of scope: Blinkist native mobile applications (iOS/Android) and the Blinkist Business web product.
Applicable Standards/Guidelines
| Standard/Guideline | Level | Included In Report |
|---|---|---|
| Web Content Accessibility Guidelines 2.0 | A | Yes |
| Web Content Accessibility Guidelines 2.0 | AA | Yes |
| Web Content Accessibility Guidelines 2.0 | AAA | No |
| Web Content Accessibility Guidelines 2.1 | A | Yes |
| Web Content Accessibility Guidelines 2.1 | AA | Yes |
| Web Content Accessibility Guidelines 2.1 | AAA | No |
| Web Content Accessibility Guidelines 2.2 | A | Yes |
| Web Content Accessibility Guidelines 2.2 | AA | Yes |
| Web Content Accessibility Guidelines 2.2 | AAA | No |
| Revised Section 508 standards (2017; corrected 2018) | — | Yes |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion.
WCAG 2.x Report
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Partially Supports | Automated scan identified missing/insufficient text alternatives for images (12 instances) on the live events page. Manual testing reported images without alt text and decorative icon images not marked as decorative on book detail, collection, spaces, and highlights pages. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Partially Supports | Generally, the product provides an equivalent text alternative for prerecorded audio-only and video-only content. Exception: Prerecorded guide audio lacks an available transcript. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | No prerecorded video-with-audio content is included in the in-scope web experience. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | No prerecorded video content is included in the in-scope web experience. |
| 1.3.1 Info and Relationships | Partially Supports | Automated scan flagged 33 elements that visually appear to be headings but lack semantic heading markup across guides, categories, settings, spaces, books, explore, highlights, and library pages. Manual testing reported misleading heading structure and incorrect heading levels. |
| 1.3.2 Meaningful Sequence | Supports | No issues with meaningful reading/focus order were identified for in-scope user flows during evaluation. |
| 1.3.3 Sensory Characteristics | Supports | No instructions relying solely on sensory characteristics were reported. |
| 1.4.1 Use of Color | Supports | No instances were reported where information is conveyed only through color. |
| 1.4.2 Audio Control | Not Applicable | No audio plays automatically for more than 3 seconds on page load. |
| 2.1.1 Keyboard | Partially Supports | Automated scan found keyboard accessibility risks involving scrollable regions. Manual testing reported key controls not reachable via keyboard on guides, login, and reader/player pages. Focus-management issues with the main navigation overlay were also reported. |
| 2.1.2 No Keyboard Trap | Supports | No keyboard traps were reported for in-scope user flows. |
| 2.1.4 Character Key Shortcuts | Not Applicable | No single-character keyboard shortcuts were identified. |
| 2.2.1 Timing Adjustable | Supports | No time limits affecting task completion were reported. Note: Some transient success notifications/toasts auto-dismiss but are informational. |
| 2.2.2 Pause, Stop, Hide | Supports | No moving, blinking, scrolling, or auto-updating content requiring pause/stop/hide controls was reported. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No flashing content exceeding thresholds was reported. |
| 2.4.1 Bypass Blocks | Partially Supports | Manual testing reported that only navigation landmarks were present on most in-scope pages. No landmarks at all were reported on the reader/player page. |
| 2.4.2 Page Titled | Does Not Support | Most in-scope pages use a generic, repeated page title (e.g., "Blinkist: Big ideas in small packages") that does not sufficiently distinguish the specific page/section. |
| 2.4.3 Focus Order | Partially Supports | On the reader/player page, keyboard focus can move into controls that are not visible (hidden behind a collapsed container), causing focus to "disappear". |
| 2.4.4 Link Purpose (In Context) | Partially Supports | Automated scan found 36 links without accessible text across settings and login pages. Manual testing reported misleading link names on book detail pages. |
| 2.5.1 Pointer Gestures | Supports | No multipoint or path-based gestures are required for operation. |
| 2.5.2 Pointer Cancellation | Supports | No issues with pointer cancellation were identified. |
| 2.5.3 Label in Name | Supports | No issues were reported where a control has a visible text label not included in its accessible name. |
| 2.5.4 Motion Actuation | Not Applicable | No functionality is triggered via device motion. |
| 3.1.1 Language of Page | Supports | Default page language is correctly identified. |
| 3.2.1 On Focus | Supports | No changes of context triggered by focus alone were reported. |
| 3.2.2 On Input | Supports | No changes of context triggered by user input without warning were reported. |
| 3.2.6 Consistent Help | Supports | Help mechanisms appear in a consistent location across the in-scope web experience. |
| 3.3.1 Error Identification | Supports | Errors are identified in text for in-scope forms/flows. |
| 3.3.2 Labels or Instructions | Supports | Form fields and required inputs provide labels or instructions. |
| 3.3.7 Redundant Entry | Supports | No redundant re-entry of previously provided information was reported. |
| 4.1.1 Parsing | Supports | No parsing/markup issues that would prevent assistive technologies from reliably interpreting the content were reported. |
| 4.1.2 Name, Role, Value | Partially Supports | Automated scan found 81 interactive elements with missing/invalid accessible names or ARIA usage. Manual testing reported icon buttons without accessible names on library, login, spaces, reader/player, and highlights pages. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Partially Supports | Live video-with-audio content is included in scope (e.g., live events), but captions are not provided. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | No prerecorded video content is included in the in-scope web experience. |
| 1.3.4 Orientation | Supports | Content is not restricted to a single display orientation. |
| 1.3.5 Identify Input Purpose | Supports | Common input fields expose their purpose using programmatic cues (e.g., autocomplete) where applicable. |
| 1.4.3 Contrast (Minimum) | Partially Supports | Automated scan found 117 text elements with insufficient color contrast across settings, login, library, for-you, guides, spaces, and homepage. |
| 1.4.4 Resize text | Partially Supports | Automated scan found viewport settings that may disable pinch-to-zoom on 5 settings/login pages. |
| 1.4.5 Images of Text | Supports | No images of text were reported (logos excluded). |
| 1.4.10 Reflow | Supports | Content reflows without requiring two-dimensional scrolling. |
| 1.4.11 Non-text Contrast | Partially Supports | Manual testing reported low-contrast non-text indicators including focus indicators and selection states on login, settings, email preferences, and account pages. |
| 1.4.12 Text Spacing | Supports | WCAG text spacing overrides did not identify clipping, overlap, or loss of functionality. |
| 1.4.13 Content on Hover or Focus | Supports | Hover/focus-triggered content can be dismissed, hovered, and remains available as required. |
| 2.4.5 Multiple Ways | Supports | Multiple ways of locating content are provided (navigation, collections/categories, search). |
| 2.4.6 Headings and Labels | Partially Supports | Manual testing reported missing headings on spaces pages, incorrect heading levels on settings pages, no headings on content settings pages, and confusing heading structure on reader/player and highlights pages. |
| 2.4.7 Focus Visible | Partially Supports | Manual testing reported missing visible focus indicators on primary action buttons across guides, book detail, collection, spaces, email preferences, and highlights pages. |
| 2.4.11 Focus Not Obscured (Minimum) | Partially Supports | Focusable audio controls visually hidden behind a collapsed container on the reader/player page. |
| 2.5.7 Dragging Movements | Not Applicable | No functionality requires dragging movements. |
| 2.5.8 Target Size (Minimum) | Supports | Touch targets meet the minimum target size requirement. |
| 3.1.2 Language of Parts | Partially Supports | Passages/parts in a different language are not programmatically marked, so screen readers use the page/system language pronunciation. |
| 3.2.3 Consistent Navigation | Supports | Repeated navigation mechanisms are presented consistently. |
| 3.2.4 Consistent Identification | Supports | Components with the same functionality are identified consistently. |
| 3.3.3 Error Suggestion | Supports | Suggestions are provided to help users correct input errors. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Appropriate confirmation/review/undo mechanisms are provided. |
| 3.3.8 Accessible Authentication (Minimum) | Supports | Authentication does not rely on a cognitive function test; paste/autofill is supported. |
| 4.1.3 Status Messages | Partially Supports | No VoiceOver notification when popovers opened on settings pages and when the chapter outline was expanded on the reader/player page. |
Revised Section 508 Report
Note: Chapter 4 (Hardware) is not applicable for Blinkist (software only) and is intentionally omitted.
Chapter 3: Functional Performance Criteria
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Partially Supports | Some functionality is not fully operable with screen readers due to missing accessible names/roles and insufficient programmatic structure. See WCAG: 1.1.1, 1.3.1, 2.1.1, 2.4.3, 4.1.2, 4.1.3. |
| 302.2 With Limited Vision | Partially Supports | Some functionality presents barriers for users with low vision due to insufficient contrast, low-contrast indicators, and zoom/resize limitations. See WCAG: 1.4.3, 1.4.4, 1.4.11, 2.4.7, 2.4.11. |
| 302.3 Without Perception of Color | Partially Supports | While information is not conveyed by color alone, some indicators do not meet contrast requirements. See WCAG: 1.4.3, 1.4.11. |
| 302.4 Without Hearing | Partially Supports | Live video-with-audio without captions, and some prerecorded audio lacks a transcript. See WCAG: 1.2.1, 1.2.4. |
| 302.5 With Limited Hearing | Partially Supports | Live video-with-audio without captions, and some prerecorded audio lacks a transcript. See WCAG: 1.2.1, 1.2.4. |
| 302.6 Without Speech | Supports | No speech input is required. |
| 302.7 With Limited Manipulation | Partially Supports | Some functionality presents barriers for keyboard-only users due to keyboard access and focus management issues. See WCAG: 2.1.1, 2.4.3, 2.4.7, 2.4.11. |
| 302.8 With Limited Reach and Strength | Partially Supports | Some functionality presents barriers due to keyboard access and focus management issues. See WCAG: 2.1.1, 2.4.3, 2.4.7, 2.4.11. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Partially Supports | Some content may increase cognitive load due to non-descriptive repeated page titles and inconsistent language markup. See WCAG: 2.4.2, 3.1.2. |
Chapter 5: Software
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 502.2.1 User Control of Accessibility Features | Partially Supports | Some pages include viewport settings that may prevent user scaling/pinch-to-zoom. See WCAG: 1.4.4. |
| 502.2.2 No Disruption of Accessibility Features | Partially Supports | Some pages include viewport settings that may prevent user scaling/pinch-to-zoom. See WCAG: 1.4.4. |
| 502.3.1 Object Information | Partially Supports | Some interactive elements do not expose accurate object information to assistive technologies. See WCAG: 4.1.2. |
| 502.3.2 Modification of Object Information | Partially Supports | Dynamic UI changes are not consistently conveyed to assistive technologies. See WCAG: 4.1.2, 4.1.3. |
| 502.3.3 Row, Column, and Headers | Not Applicable | No data tables or grid structures requiring programmatic row/column header relationships were identified. |
| 502.3.4 Values | Partially Supports | Some controls do not reliably expose required values/states. See WCAG: 4.1.2. |
| 502.3.5 Modification of Values | Partially Supports | Changes in control values/states are not consistently conveyed. See WCAG: 4.1.2, 4.1.3. |
| 502.3.6 Label Relationships | Partially Supports | Some controls lack programmatic labels. See WCAG: 1.3.1, 4.1.2. |
| 502.3.7 Hierarchical Relationships | Partially Supports | Some pages have insufficient semantic structure. See WCAG: 1.3.1. |
| 502.3.8 Text | Partially Supports | Some multilingual content is not programmatically identified. See WCAG: 3.1.2. |
| 502.3.9 Modification of Text | Partially Supports | Some dynamic content updates are not announced to assistive technologies. See WCAG: 4.1.3. |
| 502.3.11 Actions on Objects | Partially Supports | Some interactive elements are not operable via keyboard/assistive technology. See WCAG: 2.1.1, 4.1.2. |
| 502.3.12 Focus Cursor | Partially Supports | Keyboard focus can move to controls that are not visible. See WCAG: 2.4.3, 2.4.7, 2.4.11. |
| 502.3.13 Modification of Focus Cursor | Partially Supports | Focus changes are not consistently perceivable. See WCAG: 2.4.7, 2.4.11. |
| 502.3.14 Event Notification | Partially Supports | Some UI events are not consistently announced. See WCAG: 4.1.3. |
| 502.4 Platform Accessibility Features | Partially Supports | Some pages may limit use of platform/browser zoom features. See WCAG: 1.4.4. |
| 503.2 User Preferences | Partially Supports | The web experience does not provide a general mechanism to set and persist user preferences. Some pages may prevent user scaling. See WCAG: 1.4.4. |
| 504.2.1 Preservation of Information | Partially Supports | Export/conversion functionality does not preserve accessibility information in the exported output. |
| 504.2.2 PDF Export | Partially Supports | Exported PDFs are not always accessible (e.g., not properly tagged for reading order/structure). |
Chapter 6: Support Documentation and Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 602.2 Accessibility and Compatibility Features | Not Evaluated | Not evaluated for this report. |
| 602.3 Electronic Support Documentation | See WCAG 2.x section | See information in WCAG 2.x section. |
| 602.4 Alternate Formats | Not Applicable | No non-electronic support documentation is provided. |
| 603.2 Information on Accessibility Features | Not Evaluated | Not evaluated for this report. |
| 603.3 Accommodation of Communication Needs | Not Evaluated | Not evaluated for this report. |
Legal Disclaimer
This Accessibility Conformance Report (ACR) is provided for informational purposes only and represents Blinkist's understanding of the product's accessibility conformance as of the report date, based on the evaluation methods described above. This document does not create any warranties, express or implied, and does not constitute a legally binding commitment. Conformance may vary depending on configuration, content, user settings, assistive technology, browser/device, and other factors, and the product may change over time.