QuickPoint Accessibility Conformance Report
Based on VPAT® Version 2.5 (INT — International Edition)
Name of Product/Version: QuickPoint (web application), evaluated August 2026 release
Report Date: 26 August 2026
Product Description: QuickPoint is a text-first tool for authoring and sharing presentations. Authors write structured text (the "jadle" format) in a web editor with live preview; audiences receive a published web link rendered by the QuickPoint viewer.
Contact Information: gregory@quickpoint.me
Notes:
- Scope. This report covers (a) the authoring application at author.quickpoint.me and (b) the published web viewer — the deck a shared link delivers. The PDF export is evaluated informally under EN 301 549 Chapter 10 (see that section); the PPTX export surface is excluded from this edition.
- Third-party embeds. Videos are embedded YouTube/Vimeo players and maps are embedded Google Maps. QuickPoint names these frames for assistive technology; the accessibility of the players' internal controls is the responsibility of their vendors.
- Authored content. As an authoring tool, some outcomes depend on author-supplied content (e.g., the quality of alternative text, color choices in custom themes). Where so, the remarks state what the product enforces, defaults to, or merely enables. All "Supports" claims for the viewer assume decks using QuickPoint's built-in themes.
- Status of this report. Self-assessed by the product team. An independent third-party audit is planned; this report will be reissued with the auditor's findings.
Evaluation Methods Used:
- Manual screen-reader listening sessions with VoiceOver on macOS (Safari) across a purpose-built demonstration deck exercising every element type. These sessions ran through August 2026 and directly drove ~20 remediations before this report.
- An automated accessibility regression suite (28 tests, Playwright) run against the deployed viewer in desktop and mobile-portrait profiles on every release: document structure, landmarks, reading order, live-region announcements, focus management, keyboard operation, sealed off-screen content, media naming, chart data access.
- axe-core (WCAG 2.x A/AA rulesets) scans of every page of the demonstration deck in both orientations on every release.
- veraPDF PDF/UA-1 validation of the PDF export (representative decks pass with zero failures, August 2026).
- Computed contrast verification of the interface palette (documented per-pairing in the product style guide).
- Keyboard-only walkthroughs of authoring and viewing flows.
- Public, reproducible test artifact: the demonstration deck at
https://quickpoint.me/…/accessibility-showcasedescribes, on each slide, what assistive technology should receive — any reader can verify the claims live.
Applicable Standards/Guidelines: This report covers the following, so that one document answers procurement in the US, EU, UK and Canada:
| Standard / Guideline | Included in report |
|---|---|
| Web Content Accessibility Guidelines 2.2, Levels A and AA (W3C) | Level A (Table 1), Level AA (Table 2) |
| Revised Section 508 (U.S. 36 CFR Part 1194) | Chapters 3, 4, 5, 6 |
| EN 301 549 V3.2.1 (2021) — the European harmonised standard behind the Web Accessibility Directive and the European Accessibility Act | Chapters 4–13 |
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.
EN 301 549 conformance — in plain language
If you are evaluating QuickPoint against a European requirement (the Web Accessibility Directive, the European Accessibility Act, an EN 301 549 tender clause, or an Irish, UK or Canadian equivalent), here is what this report says without the standards jargon:
- EN 301 549 is the European accessibility standard. It is what the EU Web Accessibility Directive (binding on universities and public bodies since 2020) and the European Accessibility Act (in force since June 2025) point to. The UK's public-sector regulations and Canada's federal ICT standard use the same requirements or WCAG directly.
- For anything on the web, EN 301 549 requires WCAG 2.1 Level AA. QuickPoint targets WCAG 2.2 Level AA — the newer, stricter version — so it meets and exceeds the web requirement. The detail is in Table 1 and Table 2 below, which are the evidence for EN 301 549 Chapter 9 (Web).
- EN 301 549 also asks for more than web rules — that software work with a user's own assistive technology and honour their system settings (Chapter 11), and that the documentation and support you receive are themselves accessible (Chapter 12). Those chapters are reported below and are Supported.
- QuickPoint is also an authoring tool, and the output it produces is accessible by default (EN 301 549 clause 11.8): the published web deck and the tagged PDF export carry real headings, alt text, list and table structure — the PDF passes independent PDF/UA-1 validation. Most presentation tools cannot say this, which is the single reason a QuickPoint deck clears an accessibility procurement review that a PowerPoint or an AI-generated deck does not.
- Where we fall short, we say so. The "Partially Supports" rows and the remediation list are complete and honest — proactive disclosure of known gaps is exactly what a rigorous accessibility office (and the EN 301 549 process) expects, and none of the open items block the core authoring-and-viewing task.
The paperwork instrument for this in Europe is a clause-by-clause EN 301 549 conformance statement; this VPAT INT-edition ACR is that statement. If your tender needs the values transcribed into a specific template, email the contact above and we will complete it.
WCAG 2.2 Report
This is the evidence for EN 301 549 Chapter 9 (Web), Revised Section 508 (web content), and WCAG conformance directly. EN 301 549 requires Level AA against WCAG 2.1; the tables below report against the newer WCAG 2.2 at Levels A and AA.
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | Viewer: images render with author-supplied alternative text stored with the file (reused consistently across decks); charts expose a text summary and a machine-readable data table; decorative rules and spacing are hidden from assistive technology; media frames are named. Authoring: image upload requires a description; all controls have accessible names; decorative icons are aria-hidden. Alt-text quality is author-supplied. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Partially Supports | No dedicated transcript feature. Authors can (and the demonstration deck does) place a transcript as adjacent text in the reading order; the product does not require it. |
| 1.2.2 Captions (Prerecorded) | Supports | Video is delivered via embedded YouTube/Vimeo players, which retain their platform caption support and controls. Caption availability depends on the source video. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Partially Supports | Depends on the source platform's audio-description support and the author's chosen video. No product-level mechanism. |
| 1.3.1 Info and Relationships | Supports | Verified extensively: real heading elements with levels; real (and correctly nested/numbered) lists; tables with row structure and column headers announced per cell; figures with associated captions; landmarks; labelled form fields. Covered by the automated regression suite. |
| 1.3.2 Meaningful Sequence | Supports | Reading order matches visual order, including across split-page (multi-column) layouts (left half reads completely before the right). Off-screen slides are removed from the reading order entirely. |
| 1.3.3 Sensory Characteristics | Supports | Product instructions do not rely on shape/location alone. Authored content is the author's responsibility. |
| 1.4.1 Use of Color | Supports | Charts never rely on color alone: single-series charts carry direct value labels; multi-series charts carry legends and direct end-labels, with the underlying data available as a table. Editor syntax coloring is supplementary to text labels. |
| 1.4.2 Audio Control | Supports | Audio plays only on user action by default. Where an author opts into auto-play, the player's pause control is immediately available and audio stops on page change. |
| 2.1.1 Keyboard | Supports | Full keyboard operation of both applications, verified by automated tests: all viewer navigation (arrows, Space/Shift+Space, Page Up/Down, Home/End), all controls real buttons, audio seek slider keyboard-operable, chart data disclosure keyboard-operable. |
| 2.1.2 No Keyboard Trap | Supports | Verified; dialogs (shortcuts card, resume prompt) close on Escape and restore focus. |
| 2.1.4 Character Key Shortcuts | Partially Supports | The viewer binds a single printable-character shortcut: ? opens the keyboard-shortcuts card. It cannot yet be remapped or disabled (it is suppressed while typing in any field, and the dialog it opens is immediately dismissible). Remediation planned. |
| 2.2.1 Timing Adjustable | Partially Supports | No time limits by default; reveals and page turns are reader-paced. An author-opt-in auto-advance feature (autoplay:) has no viewer-side pause control yet. Product guidance treats timed content as the exception; remediation planned for decks that use it. |
| 2.2.2 Pause, Stop, Hide | Partially Supports | Same consideration as 2.2.1 for author-opt-in auto-advance. Animations respect the user's reduced-motion preference. |
| 2.3.1 Three Flashes or Below Threshold | Supports | Nothing in the product flashes. Authored content is the author's responsibility. |
| 2.4.1 Bypass Blocks | Supports | Authoring app provides a skip-to-editor link and landmarks. The viewer has minimal repeated chrome; landmarks and per-slide headings provide structure for navigation. |
| 2.4.2 Page Titled | Supports | The browser title is the presentation's name; the authoring app is titled. Verified by the automated suite. |
| 2.4.3 Focus Order | Supports | Verified: slide content first, then Next, Previous, settings. Page turns move focus to the new slide's first heading; off-screen slides are inert. |
| 2.4.4 Link Purpose (In Context) | Supports | Buttons and links carry their visible text as their accessible name. |
| 2.5.1 Pointer Gestures | Supports | No multipoint or path-based gestures anywhere. |
| 2.5.2 Pointer Cancellation | Supports | Standard click activation (up-event); no down-event actions. |
| 2.5.3 Label in Name | Supports | Verified; visible labels equal accessible names throughout. |
| 2.5.4 Motion Actuation | Not Applicable | No motion-operated functionality. |
| 3.1.1 Language of Page | Supports | Document language is set on both applications. |
| 3.2.1 On Focus | Supports | Focus never triggers a change of context. |
| 3.2.2 On Input | Supports | Changing a setting does not automatically change context; actions are explicit. |
| 3.2.6 Consistent Help | Supports | The keyboard-help shortcut (?) and the accessibility-settings button appear in the same location on every page of every deck. |
| 3.3.1 Error Identification | Partially Supports | Form validation errors are identified in text in the authoring app. Known defect: some system errors (e.g., a failed file upload caused by a network problem) are currently logged but not yet surfaced to the user in the interface. Remediation planned. |
| 3.3.2 Labels or Instructions | Supports | All authoring inputs carry visible labels; required accessibility descriptions are explained at the point of entry. |
| 3.3.7 Redundant Entry | Supports | Previously entered information (e.g., file descriptions) is stored with the file and reused; no flow asks for the same information twice. |
| 4.1.2 Name, Role, Value | Supports | Verified extensively, including custom widgets: disclosure buttons expose expanded state; sliders are native inputs with accessible names; tabs, dialogs and toolbars follow ARIA patterns; media frames are named. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | No live media. |
| 1.2.5 Audio Description (Prerecorded) | Partially Supports | Depends on the embedded platform and source video; no product-level mechanism. |
| 1.3.4 Orientation | Supports | Both orientations are first-class and covered by the automated suite; portrait collapses layouts (including tables) into accessible single-column forms. |
| 1.3.5 Identify Input Purpose | Partially Supports | The login email field's autocomplete purpose attribute is pending verification; other personal-data inputs do not exist. |
| 1.4.3 Contrast (Minimum) | Supports | The interface palette is verified at AAA (7:1+) for text, documented pairing-by-pairing in the product style guide. Built-in presentation themes meet AA; author-customized colors are the author's responsibility. |
| 1.4.4 Resize Text | Supports | Browser zoom is supported, and the viewer additionally offers a built-in text-size multiplier up to 4× for all deck content. |
| 1.4.5 Images of Text | Supports | No images of text anywhere in either interface; all deck text is real text. |
| 1.4.10 Reflow | Supports | Verified in a 390px-wide mobile profile by the automated suite: single-column reflow, no horizontal scrolling, responsive table collapse. |
| 1.4.11 Non-text Contrast | Supports | Focus indicators (3px, ≥3:1 against all surfaces), control boundaries, and chart marks meet the requirement; verified in the palette documentation. |
| 1.4.12 Text Spacing | Partially Supports | Slide layouts are fixed-height; formal verification that user text-spacing overrides cause no clipping is scheduled. No defects currently known. |
| 1.4.13 Content on Hover or Focus | Supports | Chart value tooltips use native browser tooltips; the equivalent data is always available in the chart's data table. No custom hover layers. |
| 2.4.5 Multiple Ways | Not Applicable | Each published deck is a single document; the authoring product is a single-page application. Within a deck, sequential keys, Home/End, and author-created toPage: links all navigate. |
| 2.4.6 Headings and Labels | Supports | Verified; headings describe their slides, labels describe their controls. |
| 2.4.7 Focus Visible | Supports | A 3px visible indicator on every sequentially focusable element, in both applications, verified by the automated suite. |
| 2.4.11 Focus Not Obscured (Minimum) | Supports | No sticky overlays; the chart data panel never covers the control that opened it. |
| 2.5.7 Dragging Movements | Supports | Nothing requires dragging; the audio seek slider is keyboard- and single-pointer-operable. |
| 2.5.8 Target Size (Minimum) | Supports | Interactive targets are ≥44px (most ≥48px) in both applications — beyond the 24px requirement. |
| 3.1.2 Language of Parts | Partially Supports | The interface is localized (English/French) with correct document language. Passages in a second language within a deck cannot yet be marked with their own language. |
| 3.2.3 Consistent Navigation | Supports | Navigation is identical across all slides and pages. |
| 3.2.4 Consistent Identification | Supports | Components with the same function are identified identically throughout. |
| 3.3.3 Error Suggestion | Supports | Where validation fails in authoring flows, the message states what is required. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Destructive actions (deletion, canceling a subscription) require explicit confirmation; presentations are recoverable while unpublished. |
| 3.3.8 Accessible Authentication (Minimum) | Supports | Sign-in offers OAuth (Google/GitHub) and email/password with no cognitive function test; password managers are not obstructed. |
| 4.1.3 Status Messages | Supports | Verified: slide changes, save states, copy confirmations and editor actions are announced via live regions without moving focus. |
Functional Performance Statements
Revised Section 508 Chapter 3 (§ 302) · EN 301 549 Chapter 4 (clause 4.2)
These describe how a user with a given disability can operate QuickPoint, independent of any specific success criterion.
| Functional performance | Conformance Level | Remarks and Explanations |
|---|---|---|
| Usage without vision | Supports | Both applications and the published deck are fully operable with a screen reader and keyboard alone: real semantics, named controls, live announcements of slide changes and save/copy actions, sealed off-screen content. Verified in VoiceOver listening sessions and the automated suite. |
| Usage with limited vision | Supports | Browser zoom, plus a viewer text-size multiplier up to 4×; reflow with no horizontal scrolling; high-contrast themes and colour tints in the viewer; interface text verified at AAA (7:1+) contrast. |
| Usage without perception of colour | Supports | No information is conveyed by colour alone anywhere; charts use direct labels and data tables. |
| Usage without hearing | Supports | No functionality requires hearing. Audio never auto-plays by default; where an author adds video, platform captions are available. |
| Usage with limited hearing | Supports | As above; audio is user-controlled and never required to operate the product. |
| Usage without speech | Supports | No functionality requires speech input. |
| Usage with limited manipulation or strength | Supports | Full keyboard operation; no dragging or gestures required; interactive targets ≥44px (most ≥48px). |
| Usage with limited reach | Supports | Software only — no physical reach requirements; keyboard and pointer both fully supported. |
| Usage with limited language, cognitive or learning abilities | Supports | Consistent navigation and identification throughout; explicit confirmation of destructive actions; the viewer's reading ruler, colour tints and text scaling aid reading; plain, labelled controls with visible help in a fixed location. |
Hardware
Revised Section 508 Chapter 4 · EN 301 549 Chapter 8
Not Applicable. QuickPoint is a web application with no hardware component.
Software
Revised Section 508 Chapter 5 · EN 301 549 Chapter 11
| Clause | Conformance Level | Remarks and Explanations |
|---|---|---|
| 11.5 Software that is a platform / has closed functionality | Not Applicable | QuickPoint runs in the user's own browser and does not restrict the use of assistive technology; it has no closed functionality. |
| 11.6.2 Interoperability with assistive technology (accessibility services) | Supports | Built on the standard web platform; exposes name, role, state and value through the accessibility tree; works with screen readers and other browser/OS assistive technology. |
| 11.7 User preferences | Supports | Honours the user's browser and operating-system settings — reduced motion, zoom, and colour/contrast — and adds in-app preferences (theme, text size, reading aids) in the viewer. |
| 11.8.1 Content technology (authoring) | Supports | Output is HTML (published viewer) and tagged PDF — technologies that support the creation of accessible content. |
| 11.8.2 Accessible content creation | Supports | The product produces WCAG 2.2 AA-conformant output by default: correct headings, lists, tables, landmarks and focus order without author intervention. |
| 11.8.3 Preservation of accessibility information in transformations | Supports | Exporting a deck to PDF preserves the structure tree, language, headings, figures with alt text, scoped table headers and lists; the PDF passes veraPDF PDF/UA-1 validation. |
| 11.8.4 Repair assistance | Partially Supports | Image upload cannot proceed without an alternative-text description; the product does not yet audit all author-supplied content (e.g. custom theme colour contrast) or prompt to repair it. |
| 11.8.5 Templates | Supports | The built-in presentation themes produce accessible output; a template that meets the accessibility requirements is provided and is the default. |
Documentation and Support Services
Revised Section 508 Chapter 6 · EN 301 549 Chapter 12
| Clause | Conformance Level | Remarks and Explanations |
|---|---|---|
| 12.1.1 Accessibility and compatibility features | Supports | Accessibility features are documented publicly on the QuickPoint accessibility page, in this report, and in an in-product Accessibility Tour. |
| 12.1.2 Accessible documentation | Supports | Product documentation is delivered as accessible web pages meeting WCAG 2.2 AA. |
| 12.2.2 Information on accessibility and compatibility features | Supports | The above resources describe the accessibility features and how to use them. |
| 12.2.3 Accessible documentation (support) | Supports | Support content is provided in accessible web format. |
| 12.2.4 Support services | Supports | Human support is available in-product (the AI chat hands off to a person) and by email; requests can be made and answered in accessible text. |
Other EN 301 549 chapters
| Chapter | Conformance Level | Remarks and Explanations |
|---|---|---|
| Chapter 5 — Generic requirements | Not Applicable | The generic requirements (closed functionality, biometrics, locking/repeat keys, etc.) address hardware and closed systems; QuickPoint is open software used with the user's own browser and assistive technology. |
| Chapter 6 — ICT with two-way voice communication | Not Applicable | No real-time voice communication. |
| Chapter 7 — ICT with video capabilities | Partially Supports | Video is embedded via third-party players (YouTube/Vimeo) that provide caption and audio-description controls; availability of captions/description depends on the source video, and the players' own controls are the vendors' responsibility. |
| Chapter 9 — Web | Supports (WCAG 2.2 AA) | See the WCAG 2.2 Report above. EN 301 549 requires WCAG 2.1 AA; QuickPoint targets 2.2 AA. |
| Chapter 10 — Non-web documents (PDF export) | Partially Supports | The PDF export is tagged (structure tree, language, headings, figures with alt text, scoped data tables, nested lists, charts as tagged data tables) and passes veraPDF PDF/UA-1 validation with zero failures (August 2026). It is not yet in the formally audited scope pending a confirming PAC 2024 run; PPTX export is not yet evaluated. |
| Chapter 11 — Software | Supports | See the Software section above, including authoring-tool clause 11.8. |
| Chapter 12 — Documentation and support services | Supports | See the Documentation and Support Services section above. |
| Chapter 13 — ICT providing relay or emergency service access | Not Applicable | QuickPoint provides no relay or emergency service. |
Known items scheduled for remediation
Listed here so this report's "Partially Supports" entries are actionable rather than vague:
- A mechanism to disable or remap the
?shortcut (2.1.4). - A viewer-side pause control for author-opt-in auto-advancing decks (2.2.1/2.2.2).
- Surface system errors (e.g. failed uploads) in the interface, not only the console (3.3.1).
- Formal text-spacing override verification on fixed-height slides (1.4.12).
autocompletepurpose attributes on authentication fields (1.3.5).- Per-passage language marking in decks (3.1.2).
- A transcript affordance for audio content (1.2.1).
- A confirming PAC 2024 run to move the PDF export (EN 301 549 Chapter 10) into formally audited scope, and evaluation of the PPTX export surface. (Progress: the PDF export is live and tagged — structure tree, language, headings, figures with alt text, and data tables as Table/TR/TH/TD with column scope — and passes veraPDF PDF/UA-1 validation with zero failures.)
- Author-side repair assistance beyond required image alt text — e.g. contrast checking of custom theme colours (11.8.4).
Revision history
| Date | Change |
|---|---|
| 2026-08-26 | Reissued as VPAT 2.5 INT (International) edition: added Revised Section 508 and EN 301 549 reporting (Functional Performance, Hardware, Software incl. authoring-tool clause 11.8, Documentation & Support Services, and the EN 301 549 chapter map), plus a plain-language EN 301 549 conformance statement. WCAG 2.2 A/AA tables unchanged. |
| 2026-08-24 | First self-assessed edition, WCAG 2.2 A/AA (WCAG edition), authoring + web viewer. |
Reviewing QuickPoint for your institution?
We’ll support your review directly: sandbox access, our screen-reader test evidence, and a named contact who answers. Contact us about your review, or see what’s behind each claim.
"Voluntary Product Accessibility Template" and "VPAT" are registered service marks of the Information Technology Industry Council (ITI). This report was prepared using the VPAT 2.5 INT (International) edition template.