Accessibility
Our commitment
DestinationHub is committed to making its self-guided tour and destination-directory platform usable by everyone, including people with disabilities. We design and test the product against the Web Content Accessibility Guidelines (WCAG) 2.2, Level A and AA, the Revised Section 508 standards, and EN 301 549.
Using the accessibility features
The product includes the following accessibility and assistive-technology compatibility features:
- Keyboard: All core functionality can be operated with a keyboard using Tab and Shift+Tab to move between controls, Enter or Space to activate them, arrow keys within menus, tabs, and sliders, and Escape to close dialogs.
- Screen readers: Content, headings, form labels, and status messages are exposed to assistive technology. The product is tested with modern screen readers including NVDA, JAWS, and VoiceOver.
- Zoom and reflow: Text can be enlarged to 200% using standard browser zoom, and content reflows to a single column on small screens without horizontal scrolling.
- Reduced motion: Animations and auto-advancing content respect your operating system’s “reduce motion” setting and can be paused.
- Alternative content: Map-based information is also available through keyboard-accessible list and detail pages.
Feedback and contact
If you encounter an accessibility barrier, or need assistance or an alternative format, please contact us at support@destinationhub.io or through the “Report an issue” option in the application. We aim to respond promptly and will work with you to provide the information or functionality you need.
Accessibility Conformance Report
The following is the published, web version of the DestinationHub Accessibility Conformance Report (based on the VPAT® 2.5 International Edition). A static copy of this report (PDF or Word) is available on request by contacting support@destinationhub.io.
Product and report information
- Product: DestinationHub — v1.2.3
- Report date: July 6, 2026
- Standards evaluated: WCAG 2.2 (Level A and AA), Revised Section 508, EN 301 549 (V3.2.1)
- Product description: DestinationHub is a cloud-based destination management platform used by nonprofits, governments, and other local organizations to create walking tours, manage directories, and share regional content with visitors.
Conformance terms
- Supports: The functionality has at least one method that meets the criterion or meets it with equivalent facilitation.
- Partially Supports: Some functionality does not meet the criterion.
- Does Not Support: The majority of functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
WCAG 2.2 Report
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Partially Supports | Images have text alternatives, decorative graphics are hidden from assistive technology, and icon-only controls expose accessible names. Interactive map markers are not yet exposed to assistive technology, though equivalent place information is available in accessible list form for most categories. Alternative text for organization-uploaded images is authored by the organization. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Supports | Prerecorded audio guides are accompanied by equivalent on-page text. |
| 1.2.2 Captions (Prerecorded) | Partially Supports | First-party instructional videos are captioned; synchronized captions are not guaranteed for prerecorded video uploaded by organizations. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Partially Supports | First-party media provides a text alternative; organization-uploaded video may lack audio description of visual-only information. |
| 1.3.1 Info and Relationships | Partially Supports | Structure, headings, lists, tables, and form labels are conveyed programmatically. Because organization authors compose content in a rich-text editor, a logical heading hierarchy within user-authored content cannot be enforced. |
| 1.3.2 Meaningful Sequence | Supports | Reading and navigation order is programmatically determinable and logical. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not rely solely on shape, size, or visual location. |
| 1.4.1 Use of Color | Supports | Color is never the only means of conveying information or indicating an action. |
| 1.4.2 Audio Control | Not Applicable | No audio plays automatically for more than three seconds; this criterion does not apply. |
| 2.1.1 Keyboard | Partially Supports | The application is keyboard-operable; the interactive map and some map-linked controls are not yet fully keyboard-operable, though equivalent content is available through keyboard-accessible list and detail pages. |
| 2.1.2 No Keyboard Trap | Supports | Keyboard focus can always be moved away from any component. |
| 2.1.4 Character Key Shortcuts | Supports | No single-character key shortcuts are used. |
| 2.2.1 Timing Adjustable | Supports | No essential time limits are imposed on the user. |
| 2.2.2 Pause, Stop, Hide | Supports | Auto-updating and moving content can be paused, and honors reduced-motion preferences. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No content flashes more than three times per second. |
| 2.4.1 Bypass Blocks | Supports | Landmark regions (banner, navigation, main, contentinfo) are provided so assistive technology can bypass repeated blocks. |
| 2.4.2 Page Titled | Supports | Pages have descriptive, unique titles. |
| 2.4.3 Focus Order | Supports | Focusable components receive focus in an order that preserves meaning and operability. |
| 2.4.4 Link Purpose (In Context) | Supports | The purpose of each link is clear from its text or context. |
| 2.5.1 Pointer Gestures | Supports | All functionality that uses multipoint or path-based gestures has a single-pointer alternative. |
| 2.5.2 Pointer Cancellation | Supports | Functionality completes on the up-event, or activation can be aborted or undone. |
| 2.5.3 Label in Name | Supports | The accessible name of a control contains its visible label text. |
| 2.5.4 Motion Actuation | Not Applicable | No functionality is operated by device or user motion. |
| 3.1.1 Language of Page | Supports | The default language of each page is programmatically set. |
| 3.2.1 On Focus | Supports | Receiving focus does not trigger a change of context. |
| 3.2.2 On Input | Supports | Changing a setting does not automatically cause a change of context. |
| 3.2.6 Consistent Help | Supports | Help mechanisms appear in a consistent order across pages. |
| 3.3.1 Error Identification | Supports | Input errors are identified in text and the field in error is indicated. |
| 3.3.2 Labels or Instructions | Supports | Form fields have visible labels or instructions. |
| 3.3.7 Redundant Entry | Supports | Previously entered information is auto-populated or selectable within a process. |
| 4.1.1 Parsing (obsolete) | Supports | Removed as always-satisfied in WCAG 2.2; the framework-generated markup is well-formed. |
| 4.1.2 Name, Role, Value | Supports | Interface components expose name, role, state, and value to assistive technology. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | The product contains no live audio or video content. |
| 1.2.5 Audio Description (Prerecorded) | Does Not Support | The product does not provide a mechanism for supplemental audio-description tracks. Video whose soundtrack already conveys the visual information conforms under the exception; text transcripts are supported but do not satisfy this Level AA criterion. |
| 1.3.4 Orientation | Supports | Content is not restricted to a single display orientation. |
| 1.3.5 Identify Input Purpose | Supports | Common input fields declare their purpose for autofill. |
| 1.4.3 Contrast (Minimum) | Supports | Text and images of text meet the 4.5:1 contrast minimum (3:1 for large text). |
| 1.4.4 Resize Text | Supports | Text can be resized to 200% without loss of content or function. |
| 1.4.5 Images of Text | Supports | Text is used rather than images of text. |
| 1.4.10 Reflow | Supports | Content reflows to a single column without horizontal scrolling. |
| 1.4.11 Non-text Contrast | Supports | User-interface components and meaningful graphics meet the 3:1 contrast minimum. |
| 1.4.12 Text Spacing | Supports | Increased text spacing is supported without loss of content. |
| 1.4.13 Content on Hover or Focus | Supports | Hover/focus content is dismissable, hoverable, and persistent. |
| 2.4.5 Multiple Ways | Partially Supports | More than one way is provided to locate content across the site; some sub-sections are reached primarily through in-page navigation. |
| 2.4.6 Headings and Labels | Supports | Headings and labels are descriptive. |
| 2.4.7 Focus Visible | Supports | A visible focus indicator is provided for keyboard focus. |
| 2.4.11 Focus Not Obscured (Minimum) | Supports | Focused components are not entirely hidden by other content. |
| 2.5.7 Dragging Movements | Supports | Dragging operations have single-pointer (button) alternatives. |
| 2.5.8 Target Size (Minimum) | Supports | Interactive targets meet the 24-by-24 CSS-pixel minimum or qualify under the spacing/inline exceptions. |
| 3.1.2 Language of Parts | Supports | The product is single-language (English); no passages require an inline language change. |
| 3.2.3 Consistent Navigation | Supports | Repeated navigation appears in the same relative order across pages. |
| 3.2.4 Consistent Identification | Supports | Components with the same function are identified consistently. |
| 3.3.3 Error Suggestion | Supports | Correction suggestions are provided when an input error is detected. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Significant submissions are reversible, checked, or confirmed before finalizing. |
| 3.3.8 Accessible Authentication (Minimum) | Supports | No cognitive-function test is required; password managers and paste are supported. |
| 4.1.3 Status Messages | Supports | Status messages are exposed to assistive technology without moving focus. |
Revised Section 508 Report
Chapter 3: Functional Performance Criteria
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Partially Supports | Core functionality is operable with a screen reader; limitations are user-uploaded video without audio description and the visual map, whose content is available through accessible list and detail views. |
| 302.2 With Limited Vision | Supports | Text resizes to 200%, content reflows to a single column, increased text spacing is supported, and text and non-text contrast meet the required ratios. |
| 302.3 Without Perception of Color | Supports | Color is never the sole means of conveying information. |
| 302.4 Without Hearing | Partially Supports | First-party audio has text equivalents and first-party video is captioned; captions are not guaranteed for organization-uploaded media. |
| 302.5 With Limited Hearing | Supports | No content requires fine auditory discrimination; volume is user-controlled and captions/transcripts are available for first-party media. |
| 302.6 Without Speech | Supports | No speech or voice input is required. |
| 302.7 With Limited Manipulation | Partially Supports | Keyboard operation and button alternatives to dragging are provided; the interactive map is not yet fully keyboard-operable, with equivalent content reachable elsewhere. |
| 302.8 With Limited Reach and Strength | Supports | No simultaneous, timed, or precise/forceful actions are required; targets are adequately sized and keyboard/AT operation is supported. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Supports | Consistent navigation and help, clear labels, plain-text error handling with suggestions, no redundant entry, and authentication without a cognitive-function test. |
Chapter 6: Support Documentation and Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 602.2 Accessibility and Compatibility Features | Not Applicable | This provision concerns hardware (Chapter 4) and software (Chapter 5) features. The product is a web application; Chapter 4 does not apply and the applicable Chapter 5 requirements are met through WCAG conformance, so there are no Chapter 4 or 5 features requiring separate explanation. |
| 602.3 Electronic Support Documentation | Supports | Support documentation, including this report, is delivered as accessible web content conforming to the levels above. |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | All support documentation is provided electronically; no non-electronic documentation is produced. |
| 603.2 Information on Accessibility and Compatibility Features | Supports | Accessibility information is available through this page, the standard support channels, and this report. |
| 603.3 Accommodation of Communication Needs | Supports | Support is offered through text-based email, an in-app request form, and telephone, providing equivalent alternatives. |
EN 301 549 Report
The functional performance statements of EN 301 549 Chapter 4 correspond to the Section 508 functional performance criteria above. Web content requirements (Chapter 9) are addressed by the WCAG 2.2 Report above.
Chapter 12: Documentation and Support Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 12.1.1 Accessibility and Compatibility Features | Supports | This Accessibility page lists and explains how to use the product’s accessibility and compatibility features (keyboard operation, screen-reader support, zoom and reflow, supported assistive technologies). |
| 12.1.2 Accessible Documentation | Supports | Product documentation, including this report, is provided in an accessible web (HTML) format. |
| 12.2.2 Information on Accessibility and Compatibility Features | Supports | Support services can provide accessibility information, which is also published on this page and in this report. |
| 12.2.3 Effective Communication | Supports | Multiple support channels (email, in-app request form, telephone) accommodate different communication needs. |
| 12.2.4 Accessible Documentation | Supports | Documentation provided by support services is delivered in accessible electronic formats. |
Legal disclaimer
This Accessibility Conformance Report is provided for informational purposes and reflects DestinationHub’s current assessment of the product as of the report date. Accessibility features may evolve over time and this report may change without notice. It is the responsibility of the reader to determine whether the conformance levels described meet their own accessibility needs, legal obligations, or policy requirements. DestinationHub disclaims all warranties, express or implied, regarding this report. VPAT® is a registered trademark of the Information Technology Industry Council (ITI).