IdeaLine
Template draft. This is standard boilerplate prepared for review. It is not legal advice. Replace every [highlighted placeholder], confirm each statement matches how IdeaLine actually operates, have a qualified lawyer review it for your jurisdictions, and delete this notice before publishing.

Accessibility Conformance Report

Download: PDF Word (.docx) Plain text

Based on VPAT® 2.5 (WCAG 2.2, Revised Section 508, EN 301 549 editions) · Self-assessed · Report date 17 October 2026

Product
IdeaLine web application, marketing website and legal documents (version 0.1.x)
Report date
17 October 2026
Vendor
[COMPANY LEGAL NAME]
Contact
[ACCESSIBILITY CONTACT EMAIL]
Evaluation method
Self-assessment using automated scans, scripted keyboard and behavior tests, reflow / text-spacing / forced-colors emulation, and source review. See the evidence key. Independent audit and assistive-technology testing: pending.
Applicable standards
WCAG 2.2 A and AA; Revised Section 508 (36 CFR 1194, Appendix C); EN 301 549 V3.2.1 (with the WCAG 2.2 additions expected in V4.x)

1. Summary

Of the 55 WCAG 2.2 Level A and AA success criteria, IdeaLine supports 47, partially supports 1, does not support 0 and finds 7 not applicable (media criteria; IdeaLine has no audio or video). The one partial criterion is 3.3.4 (optional delete confirmation). The one failing requirement is outside WCAG: the calendar PDF download is not a tagged PDF (Section 508 504.2.2).

Terms: Supports: the functionality has at least one method that meets the criterion without known defects. Partially Supports: some functionality does not meet it. Does Not Support: the majority does not meet it. Not Applicable: the criterion is not relevant to the product.

2. WCAG 2.2 Level A and AA

The table applies to the website, legal pages and web application together. Evidence codes are explained in section 6.

WCAG 2.2 success criteria
CriterionConformance levelRemarks and explanationsEvidence
1.1.1
Non-text Content (Level A)
SupportsIcons are hidden from assistive technology or have text names; icon-only buttons have accessible names. Charts and badges are accompanied by text. The calendar picture downloads (PNG, JPG, PDF) are images by nature; the Excel, CSV and JSON exports are the accessible equivalent (see Section 508 504.2.2 below).E1 E6
1.2.1
Audio-only and Video-only (Prerecorded) (Level A)
Not ApplicableIdeaLine publishes no audio or video.
1.2.2
Captions (Prerecorded) (Level A)
Not ApplicableNo synchronized media.
1.2.3
Audio Description or Media Alternative (Prerecorded) (Level A)
Not ApplicableNo synchronized media.
1.2.4
Captions (Live) (Level AA)
Not ApplicableNo live media.
1.2.5
Audio Description (Prerecorded) (Level AA)
Not ApplicableNo synchronized media.
1.3.1
Info and Relationships (Level A)
SupportsLandmarks, heading levels, lists, data tables with header cells, grouped controls and programmatically associated labels are used throughout. The calendar is a grid with rows, column headers and cells. Screen-reader verification is pending (see notes).E1 E6
1.3.2
Meaningful Sequence (Level A)
SupportsReading order follows source order; layouts that reorder visually keep a logical DOM order.E2 E6
1.3.3
Sensory Characteristics (Level A)
SupportsInstructions never rely only on shape, color, position or sound.E6
1.3.4
Orientation (Level AA)
SupportsNo orientation lock; layouts work in portrait and landscape.E3
1.3.5
Identify Input Purpose (Level AA)
SupportsSign-in, access request and profile fields carry autocomplete tokens (username, current-password, new-password, name, email, organization).E1 E6
1.4.1
Use of Color (Level A)
SupportsStatus, selection and errors are also shown with text, icons, borders or shape. Links in body text are underlined.E5 E6
1.4.2
Audio Control (Level A)
Not ApplicableNo audio plays.
1.4.3
Contrast (Minimum) (Level AA)
SupportsText measures at least 4.5:1 (3:1 for large text) in both light and dark themes on all scanned pages and views.E1
1.4.4
Resize Text (Level AA)
SupportsText scales to 200% without loss of content or function; sizes use rem units.E3 E4
1.4.5
Images of Text (Level AA)
SupportsText is real text. Exceptions: the logo, and calendar picture downloads the user creates.E6
1.4.10
Reflow (Level AA)
SupportsNo horizontal page scrolling at 320 CSS px. Wide data tables scroll inside their own focusable container, which is permitted for data tables.E3
1.4.11
Non-text Contrast (Level AA)
SupportsInput borders, focus rings, checkboxes, switches and icon buttons meet 3:1.E1 E5
1.4.12
Text Spacing (Level AA)
SupportsIncreasing line, paragraph, letter and word spacing causes no clipping or overlap on tested pages.E4
1.4.13
Content on Hover or Focus (Level AA)
SupportsNo custom hover or focus pop-ups; tooltips are the browser's own. Menus open on click and close with Escape.E6
2.1.1
Keyboard (Level A)
SupportsEvery function works from the keyboard. Drag and drop has keyboard and button equivalents (edit forms, Move up / Move down, Alt + arrow keys).E2 E7
2.1.2
No Keyboard Trap (Level A)
SupportsFocus can always move away. Dialogs trap focus only while modal and close with Escape.E2
2.1.4
Character Key Shortcuts (Level A)
SupportsThere are no single-character keyboard shortcuts.E6
2.2.1
Timing Adjustable (Level A)
SupportsThe 30-minute inactivity sign-out warns two minutes beforehand in an alert dialog and the user can choose Stay signed in. Changed during this audit (previously there was no warning).E7
2.2.2
Pause, Stop, Hide (Level A)
SupportsNo auto-updating or scrolling content. Decorative pulse and glow animations stop within 5 seconds and are removed entirely when the user prefers reduced motion. Drag feedback animations occur only while the user is dragging.E5 E6
2.3.1
Three Flashes or Below Threshold (Level A)
SupportsNothing flashes.E6
2.4.1
Bypass Blocks (Level A)
SupportsA "Skip to main content" link is the first focusable item on every page, and pages use landmarks.E2
2.4.2
Page Titled (Level A)
SupportsEvery page has a unique, descriptive title.E1
2.4.3
Focus Order (Level A)
SupportsFocus order follows the visual order; dialogs move focus in and return it to the trigger on close.E2 E7
2.4.4
Link Purpose (In Context) (Level A)
SupportsLink text describes the destination; links that open a new tab say so for assistive technology.E1 E6
2.4.5
Multiple Ways (Level AA)
SupportsSite: main navigation, footer, sitemap and Resources. App: tabs and global search.E6
2.4.6
Headings and Labels (Level AA)
SupportsHeadings and labels describe their topic or purpose.E1 E6
2.4.7
Focus Visible (Level AA)
SupportsA 3 px high-contrast focus indicator is shown on every interactive element, including in forced-colors mode.E2 E5
2.4.11
Focus Not Obscured (Minimum) (Level AA)
SupportsSticky headers and the consent / cookie banners reserve scroll padding so a focused element is not hidden. Changed during this audit.E2
2.5.1
Pointer Gestures (Level A)
SupportsNo multipoint or path-based gestures are required.E6
2.5.2
Pointer Cancellation (Level A)
SupportsActions run on release (click); a drag can be cancelled with Escape.E6 E7
2.5.3
Label in Name (Level A)
SupportsVisible labels are contained in the accessible names of controls.E1 E6
2.5.4
Motion Actuation (Level A)
Not ApplicableNo function is triggered by device motion.
2.5.7
Dragging Movements (Level AA)
SupportsEvery drag has a single-pointer alternative: card, calendar and idea moves via the edit form (status, dates); tab and list reordering via Move up / Move down buttons.E2 E7
2.5.8
Target Size (Minimum) (Level AA)
SupportsInteractive targets are at least 24 by 24 CSS px, or are inline text links or have sufficient spacing.E1
3.1.1
Language of Page (Level A)
SupportsEvery page declares lang="en".E1
3.1.2
Language of Parts (Level AA)
SupportsAll content is in English.E6
3.2.1
On Focus (Level A)
SupportsFocusing an element does not change context.E2
3.2.2
On Input (Level A)
SupportsChanging a control does not submit or navigate without warning; the calendar size menu updates the view in place and returns focus to itself.E2 E7
3.2.3
Consistent Navigation (Level AA)
SupportsNavigation, header and footer appear in the same order on every page and view.E6
3.2.4
Consistent Identification (Level AA)
SupportsThe same icons and labels mean the same thing across the site and app.E6
3.2.6
Consistent Help (Level A)
SupportsA Help link (to Resources) and a contact link appear in the same place in the footer of every site page, legal page and app screen. Changed during this audit.E6
3.3.1
Error Identification (Level A)
SupportsErrors are described in text, associated with the field or announced in an alert region.E7
3.3.2
Labels or Instructions (Level A)
SupportsEvery field has a visible label; format hints (such as 12-character passwords) are shown before submission.E1 E7
3.3.3
Error Suggestion (Level AA)
SupportsMessages say how to fix the problem.E7
3.3.4
Error Prevention (Legal, Financial, Data) (Level AA)
Partially SupportsDeleting a person, a project, an account or a whole workspace asks for confirmation, and importing a backup asks first. A user may tick "Don't ask me again" for ordinary item deletes, after which those deletes are immediate and cannot be undone. Planned: an Undo toast or recycle bin.E7
3.3.7
Redundant Entry (Level A)
SupportsForms ask for each item once; the access request and sign-in forms are single step.E6
3.3.8
Accessible Authentication (Minimum) (Level AA)
SupportsSign-in works with a password manager (autocomplete set, paste allowed) or an emailed sign-in link. There is no puzzle, memory test or transcription step.E6 E7
4.1.2
Name, Role, Value (Level A)
SupportsNative elements are used first; custom widgets (tabs, combobox, switches, dialogs, toggle buttons) expose name, role, state and value.E1 E6
4.1.3
Status Messages (Level AA)
SupportsToasts, results counts and form errors use status or alert live regions.E6 E7

Success criterion 4.1.1 Parsing was removed in WCAG 2.2; it is covered by EN 301 549 9.4.1.1 below.

3. Revised Section 508

Chapter 3: Functional Performance Criteria
CriterionConformance levelRemarks and explanations
302.1
Without Vision
SupportsFull keyboard operation, semantic structure and labels support screen readers. Screen-reader verification is pending.
302.2
With Limited Vision
SupportsReflow to 320 px, 200% text resize, light and dark themes, high contrast and forced-colors support.
302.3
Without Perception of Color
SupportsColor is never the only cue.
302.4
Without Hearing
Not ApplicableNo audio content.
302.5
With Limited Hearing
Not ApplicableNo audio content.
302.6
Without Speech
SupportsNo speech input is required.
302.7
With Limited Manipulation
SupportsNo fine motor gestures, 24 px minimum targets, drag alternatives and no timing-dependent actions except the session warning, which can be extended.
302.8
With Limited Reach and Strength
SupportsSoftware only; no reach or strength demands.
302.9
With Limited Language, Cognitive, and Learning Abilities
SupportsPlain language, consistent layout, error suggestions, confirmation before destructive actions, no cognitive tests to sign in. Optional delete-confirmation opt-out is noted under 3.3.4.
Chapter 5: Software
CriterionConformance levelRemarks and explanations
501.1
Scope
SupportsSoftware is the web application at idealine.io/app. Its web content conforms as listed in the WCAG tables.
502.2.1
User Control of Accessibility Features
SupportsBrowser and operating-system accessibility settings (zoom, color scheme, reduced motion, forced colors) are honored.
502.2.2
No Disruption of Accessibility Features
SupportsThe application does not disable platform accessibility features.
502.3
Accessibility Services
SupportsStandard HTML and ARIA expose role, state, name and value to the browser accessibility API.
502.4
Platform Accessibility Features
SupportsStandard browser keyboard behavior is not overridden.
503.2
User Preferences
SupportsLight, dark and automatic themes follow the system setting; reduced motion is respected.
503.3
Alternative User Interfaces
Not ApplicableThe application does not offer an alternative user interface.
503.4
User Controls for Captions and Audio Description
Not ApplicableNo media.
504.2
Content Creation or Editing
Partially SupportsIdeaLine is a content planning tool. Exports to Excel, CSV and JSON are text-based and accessible. See 504.2.2.
504.2.1
Preservation of Information Provided for Accessibility in Format Conversion
SupportsExports carry the text of every item; nothing relies on color or position alone.
504.2.2
PDF Export
Does Not SupportThe calendar PDF download is a picture of the calendar and is not tagged (not PDF/UA). Use the Excel or CSV export for an accessible equivalent. The next version should offer a tagged PDF or accessible HTML calendar export.
504.3
Prompts
SupportsPrompts and error messages are text and available to assistive technology.
504.4
Templates
SupportsProject templates are plain, structured text.
Chapter 6: Support Documentation and Services
CriterionConformance levelRemarks and explanations
602.2
Accessibility and Compatibility Features
SupportsDocumented in Resources, "Keyboard and accessibility", and in the Accessibility Statement.
602.3
Electronic Support Documentation
SupportsHelp and policy documents are HTML pages built to the same WCAG criteria; policy documents are also offered as tagged PDF, Word and plain text.
602.4
Alternate Formats for Non-electronic Support Documentation
Not ApplicableThere is no printed documentation.
603.2
Information on Accessibility and Compatibility Features
SupportsProvided in the Accessibility Statement and this report.
603.3
Accommodation of Communication Needs
SupportsSupport is available by email; a telephone number is provided on request. Contact details are on the Accessibility Statement. (Complete the telephone and response-time placeholders before publishing.)

Chapter 4 (Hardware) is not applicable: IdeaLine is software delivered as a service.

4. EN 301 549 (European Accessibility Act)

EN 301 549 clauses
ClauseConformance levelRemarks and explanations
4.2.x
Functional performance statements (usage without vision, with limited vision, without perception of color, without hearing, with limited hearing, without vocal capability, with limited manipulation or strength, with limited reach, minimize photosensitive seizure triggers, with limited cognition, privacy)
SupportsMapped to Section 508 302.1 to 302.9 above. No flashing content (photosensitive seizures). Privacy: no accessibility feature exposes personal data.
5.2
Activation of accessibility features
SupportsNo accessibility feature is deactivated by the application.
5.4
Preservation of accessibility information during conversion
SupportsSee 504.2.1.
5.6 / 5.7 / 5.9
Locking or toggle controls, key repeat, simultaneous user actions
SupportsToggle states are programmatically exposed; no key repeat or simultaneous key presses are required.
6, 7, 8, 13
Two-way voice, video, hardware, relay services
Not ApplicableNot provided.
9.1.1 to 9.4.1.3
Web (clause 9): every WCAG 2.1 Level A and AA criterion (including 9.4.1.1 Parsing)
SupportsConforms; see the WCAG 2.2 table, which is a superset (4.1.1 Parsing is satisfied: no duplicate IDs or malformed nesting were found by the scan).
9.2.x (WCAG 2.2 additions)
2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7, 3.3.8 (expected in the newer EN 301 549 V4.x)
SupportsConforms; see the WCAG 2.2 table.
10
Non-web documents (PDF, Word downloads)
Partially SupportsPolicy PDFs are tagged with headings, lists and tables; Word files use heading styles. The calendar PDF/PNG/JPG downloads are not accessible (see 504.2.2).
11
Software (non-web)
Not ApplicableIdeaLine is web content, covered by clause 9.
11.8.x
Authoring tools
Partially SupportsSee Section 508 504.2.
12.1
Product documentation
SupportsResources and Accessibility Statement; HTML.
12.2
Support services
SupportsSupport by email with accessibility contact; telephone on request.

Status of the standard: V3.2.1 is the version currently cited in the Official Journal for the presumption of conformity. A revised edition (V4.1.1, adding the WCAG 2.2 criteria) was published by ETSI in September 2026 and is expected to be cited later. [Check the current citation status with counsel before relying on this paragraph]

5. ADA

The Americans with Disabilities Act has no technical standard of its own for private products. The Department of Justice's Title II rule (state and local governments) adopts WCAG 2.1 Level AA, and courts commonly look to WCAG for Title III (businesses open to the public). IdeaLine's conformance to WCAG 2.2 AA, shown above, is intended to help public-sector and private customers meet those obligations. This report is not legal advice and does not certify compliance with any law.

6. Evidence key

Evidence
CodeMethod
E1Automated rule scan (names, labels, roles, ARIA references, landmarks, headings, duplicate IDs, contrast, target size) on every site page, legal page and app view, in light and dark themes at 1360 px and 390 px wide.
E2Keyboard walkthrough in a real browser: Tab / Shift+Tab / Enter / Space / Esc / arrow keys, checking that every control is reachable, shows a focus indicator and is not hidden under sticky or fixed content.
E3Reflow and zoom: no two-dimensional scrolling at 320 CSS px wide (equivalent to 400% zoom on a 1280 px screen).
E4Text-spacing override (line height 1.5, paragraph spacing 2x, letter spacing 0.12em, word spacing 0.16em) with a check for clipped or overlapping text.
E5Emulation of dark mode, forced-colors (high contrast), and reduced motion.
E6Manual review of the source markup, ARIA use and scripts.
E7Scripted behavior tests: session time-out warning, form errors, dialogs and focus return, drag alternatives, consent banner.
E8Downloadable document checks: tagged PDF structure, Word heading styles, text equivalents.

Full test output and the feature-by-feature audit are in the accessibility audit package supplied with the product ("audit" folder) and available to customers on request.

This report describes the state of IdeaLine on the report date, from the vendor's own testing. It is provided for information. Accessibility conformance can change with each release. [COMPANY LEGAL NAME] makes no warranty that the product is free of barriers, and this report does not create any contractual commitment other than as stated in a signed agreement. The VPAT® is a registered trademark of the Information Technology Industry Council (ITI).