HomeFeaturesPricingAboutFor Agencies
Sign inGet started free
Accessibility

Accessibility

Last updated: May 2026

We believe every location finder should be accessible to everyone, without limitations.

dropafinder is committed to making the embeddable location finder widget usable by keyboard users, screen reader users, and people who need readable contrast. We review the widget against WCAG criteria and publish this Accessibility Conformance Report so customers can evaluate the widget for procurement and compliance workflows.

To report an accessibility issue or ask a question, contact us at contact@dropafinder.com.

Voluntary Product Accessibility Template (VPAT)

An Accessibility Conformance Report (ACR) documents how a digital product supports accessibility standards. This report uses the VPAT format to summarize conformance for the dropafinder external widget.

VPAT/ACR May 2026 (PDF)

Report Details

Product
dropafinder Embed Widget
Date
May 2026
Contact
contact@dropafinder.com
Evaluation methods
Code review of embed widget

This Accessibility Conformance Report was prepared by dropafinder based on internal product review of the embeddable location finder widget.

Summary

CriteriaSupporting featuresRemarks and explanations
WCAG 2.1 Level ASupportsSee details below.
WCAG 2.1 Level AASupportsDefault widget supports Level AA; customer-customized themes and customer-provided content remain customer responsibility.
Section 508SupportsSupports applicable Revised Section 508 functional performance criteria. No active remediation items are identified within the evaluated widget scope.

WCAG 2.1 Level A

1.1 Text Alternatives

CriteriaLevelResultNotes
1.1.1 Non-text ContentASupportsAll decorative SVG icons use aria-hidden="true". Functional images such as location thumbnails use descriptive alt text. The map region uses aria-label.

1.3 Adaptable

CriteriaLevelResultNotes
1.3.1 Info and RelationshipsASupportsLocation list uses role="list" and role="listitem". Mobile tab bar uses role="tablist", role="tab", and role="tabpanel" with proper aria-labelledby associations. Detail dialog uses role="dialog" with aria-modal and aria-labelledby. Filter panel uses role="group".
1.3.2 Meaningful SequenceASupportsDOM order matches visual order.
1.3.3 Sensory CharacteristicsASupportsInstructions do not rely solely on shape, color, or position.

1.4 Distinguishable

CriteriaLevelResultNotes
1.4.1 Use of ColorASupportsStatus indicators such as Open, Closed, and Closing use both color and text labels.
1.4.2 Audio ControlANot ApplicableNo audio content.

2.1 Keyboard Accessible

CriteriaLevelResultNotes
2.1.1 KeyboardASupportsAll interactive controls are keyboard-operable. Tab bar handles arrow key navigation. Detail drawer traps focus with Tab and Shift+Tab cycling and Escape to close. Map popups close on Escape.
2.1.2 No Keyboard TrapASupportsFocus trap in detail drawer or modal is intentional and escapable via Escape key.

2.2 Enough Time

CriteriaLevelResultNotes
2.2.1 Timing AdjustableANot ApplicableNo time limits.
2.2.2 Pause, Stop, HideANot ApplicableNo moving content.

2.3 Seizures

CriteriaLevelResultNotes
2.3.1 Three FlashesASupportsNo flashing content.

2.4 Navigable

CriteriaLevelResultNotes
2.4.1 Bypass BlocksASupportsSplit, overlay, and cards-map layouts include a skip-to-list link for keyboard and screen reader users.
2.4.2 Page TitledANot ApplicableWidget is embedded; host page is responsible for page title.
2.4.3 Focus OrderASupportsFocus management is explicit: detail drawer focuses the first focusable element on mount and returns focus to trigger on close. Map popups trap focus while open and restore focus to the triggering marker on close.
2.4.4 Link Purpose (In Context)ASupportsAction links such as Directions, Call, Website, and Share have accessible names.

3.1 Readable

CriteriaLevelResultNotes
3.1.1 Language of PageANot ApplicableWidget is embedded; host page sets language. Widget honors host page language for text rendering.

3.2 Predictable

CriteriaLevelResultNotes
3.2.1 On FocusASupportsNo unexpected context changes on focus.
3.2.2 On InputASupportsFilter and sort controls update results predictably; result count is announced via aria-live.

3.3 Input Assistance

CriteriaLevelResultNotes
3.3.1 Error IdentificationANot ApplicablePrimary widget has no user-submitted forms. Search input does not have format requirements.
3.3.2 Labels or InstructionsASupportsSearch input has accessible label. Filter controls are labeled.

4.1 Compatible

CriteriaLevelResultNotes
4.1.1 ParsingASupportsValid HTML rendered by Svelte.
4.1.2 Name, Role, ValueASupportsAll interactive elements have accessible names. ARIA roles are applied correctly, including tablist, tab, tabpanel, dialog, list, listitem, and group. State is communicated via aria-selected, aria-expanded, aria-pressed, and aria-modal. Map markers include location, address, hours status, and distance where available.
4.1.3 Status MessagesASupportsLive region with aria-live="polite" and aria-atomic="true" announces result count changes and location selection events without requiring focus.

WCAG 2.1 Level AA

Level AA Criteria

CriteriaLevelResultNotes
1.4.3 Contrast (Minimum)AASupportsAll default dropafinder widget themes meet WCAG 2.1 AA contrast requirements for text, including status badges such as Open, Closing, and Closed. The widget supports customer-controlled CSS custom properties; customers who override default colors are responsible for maintaining conforming contrast ratios in their customized theme.
1.4.4 Resize TextAASupportsWidget uses relative units (rem). Text reflows at 200% zoom.
1.4.5 Images of TextAASupportsNo images of text used.
1.4.10 ReflowAASupportsMobile layout adapts at 640px breakpoint. Content does not require horizontal scrolling at 320px viewport.
1.4.11 Non-text ContrastAASupportsInteractive UI controls meet 3:1 contrast in the default theme. Map markers use a layered box-shadow halo (white inner ring plus marker-color outer ring) that creates a self-contained contrast relationship independent of the map tile background behind the marker. Customers who override default colors are responsible for maintaining conforming contrast ratios in their customized theme.
1.4.12 Text SpacingAASupportsWidget does not override text spacing properties set by host page.
1.4.13 Content on Hover or FocusAASupportsNo hover-only content. Tooltips such as map pin titles use the native browser title attribute.
2.4.5 Multiple WaysAASupportsLocations are searchable by text query, filterable by tag, country, rating, and hours, and browsable in list.
2.4.6 Headings and LabelsAASupportsHeading hierarchy is maintained within the widget. Filter and sort controls have visible labels.
2.4.7 Focus VisibleAASupportsFocus styles inherit from host page. Widget applies a visible focus ring (outline) on interactive elements.
3.1.2 Language of PartsAANot ApplicableWidget language follows host page.
3.2.3 Consistent NavigationAASupportsNavigation controls appear consistently across layouts.
3.2.4 Consistent IdentificationAASupportsControls performing the same function use the same accessible name.
3.3.3 Error SuggestionAANot ApplicableNo complex form inputs.
3.3.4 Error PreventionAANot ApplicableNo consequential user actions requiring error prevention.

Section 508 Functional Performance Criteria

Functional Performance Criteria

CriteriaLevelResultNotes
302.1 Without VisionSection 508SupportsAll functions are operable via screen reader. Map results are mirrored in a fully accessible list view. Location details are announced on selection.
302.2 With Limited VisionSection 508SupportsInterface scales without horizontal scroll. High-contrast mode is supported. Distance indicators use sufficient size and contrast.
302.3 Without Perception of ColorSection 508SupportsStatus indicators, filter states, and map markers include text or icon differentiators independent of color.
302.4 Without HearingSection 508Not ApplicableNo audio features are present in the widget.
302.6 Without SpeechSection 508SupportsNo speech input is required. All functions are accessible via typed input and pointer or keyboard alternatives.
302.7 With Limited ManipulationSection 508SupportsInteractive elements provide keyboard alternatives and adequate touch target spacing. No interactions require unavoidable simultaneous multi-key combinations.
302.9 With Limited LanguageSection 508SupportsCore UI uses plain language. Error messages are written plainly. The finder does not link to technical help documentation.
302.10 With Limited CognitiveSection 508SupportsInterface is single-purpose per view. Search flow is linear with clear progress indicators. Error recovery steps are explicit and reversible.

Known Issues and Remediation Schedule

IssueStatus
None identified within evaluated widget scopeNo active remediation schedule is required for the evaluated embed widget as of this report date.

Known Limitations

  1. Customer-customized color themes: Customers who override default CSS custom properties are responsible for maintaining color contrast compliance. dropafinder cannot guarantee contrast for themes it does not control.
  2. Third-party content: Location-specific content, images, and custom field values are provided by dropafinder customers. dropafinder renders this content as provided and cannot guarantee its accessibility compliance.
← Back to home

Embeddable location finders for multi-location businesses. Accessible by everybody.

Product
  • Field Composer
  • Refinements
  • Providers
  • Pricing
Resources
  • Accessibility Statement
  • Accessibility Guide
  • Docs
Company
  • About
  • Contact
  • Terms of Service
  • Privacy Policy
dropafinder is a product of © 2026 SOIVIS LLCTerms of ServicePrivacy Policy