Versatile Pro LLC

Accessibility Statement

Web Accessibility Policy Versatile Pro LLC | Effective Date: March 28, 2026

1. Introduction and Commitment

Versatile Pro LLC is committed to ensuring that all digital content and web properties we develop, maintain, or remediate are accessible to everyone, including people with disabilities. We believe that the web should be usable by all people regardless of ability, technology, or context.

This policy outlines our standards, practices, and ongoing commitment to web accessibility in accordance with internationally recognised guidelines and applicable legal requirements.

2. Scope

This policy applies to:

  • All websites and web applications developed or maintained by Versatile Pro LLC
  • Client websites on which we perform accessibility remediation services
  • Internal digital tools and systems used by our team
  • Third-party components and plugins integrated into our projects

3. Accessibility Standards

We design and develop in conformance with the following standards:

3.1 WCAG 2.1 Level AA Our primary target is the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C). These guidelines are organised around four principles — Perceivable, Operable, Understandable, and Robust (POUR).

3.2 Additional Standards

  • PDF/UA-1 (ISO 14289-1) — for all PDF documents we produce or remediate
  • Section 508 of the Rehabilitation Act — for US federal requirements
  • European Accessibility Act (EAA) — for EU-facing client projects
  • WAI-ARIA 1.2 — for dynamic content and custom interactive components

4. Accessibility Remediation Services

As part of our professional services, we audit and remediate websites to address accessibility barriers. Our remediation work covers the following areas:

4.1 Heading Structure We ensure all pages have a logical, sequential heading hierarchy (H1 → H2 → H3) without skipping levels. Where visual styles cannot be changed, we apply aria-level attributes to correct the programmatic structure without altering the page appearance.

4.2 Keyboard Navigation All interactive components — including navigation menus, dropdowns, modal dialogs, tabs, and form controls — are fully operable via keyboard alone. We implement standard keyboard patterns including Tab, Shift+Tab, Enter, Space, Escape, and Arrow key navigation per the WAI-ARIA Authoring Practices Guide.

4.3 Skip Navigation A visible “Skip to Content” link is provided as the first focusable element on every page, allowing keyboard and screen reader users to bypass repetitive navigation and jump directly to the main content area.

4.4 Colour Contrast We verify that all text meets minimum contrast ratios: 4.5:1 for normal text and 3:1 for large text (18pt or 14pt bold) against their backgrounds. Where background images are used, we add overlays or apply background colour directly to text elements to ensure automated tools can compute contrast accurately.

4.5 Alternative Text All meaningful images carry descriptive alt text. Decorative images are marked with empty alt attributes (alt=””) and role=”presentation” so screen readers skip them. We avoid generic values such as “image” or “image container”.

4.6 ARIA Labelling We apply ARIA roles, states, and properties accurately — aria-label, aria-labelledby, aria-describedby, aria-expanded, aria-current, and aria-haspopup are added only where they provide genuine benefit. We follow the principle of using native HTML semantics first and ARIA only when necessary.

4.7 Landmark Regions Every page contains appropriate landmark regions — banner, navigation, main, and contentinfo — so screen reader users can quickly jump between sections. Duplicate or incorrectly assigned landmarks are identified and corrected.

4.8 Form Accessibility All form inputs are associated with visible, descriptive labels using the for/id pairing or aria-labelledby. Error messages are programmatically associated with their fields and announced to assistive technologies.

4.9 PDF Accessibility (PDF/UA-1) PDFs we produce or remediate are tagged with a logical reading order, include document metadata, have alt text on all images, and pass automated PDF/UA-1 validation.

5. Testing and Quality Assurance

We use a combination of automated and manual testing methods:

5.1 Automated Testing Tools

  • WAVE (Web Accessibility Evaluation Tool) — primary audit tool
  • AccessScan — supplementary automated scanning
  • axe DevTools — browser extension testing
  • Lighthouse Accessibility Audit — integrated in Chrome DevTools
  • PDF Accessibility Checker (PAC 2024) — for PDF/UA-1 validation

5.2 Manual Testing

  • Keyboard-only navigation testing on all interactive components
  • Screen reader testing with NVDA (Windows) and VoiceOver (macOS/iOS)
  • Zoom and reflow testing at 200% and 400% magnification
  • Colour contrast verification using browser DevTools and Colour Contrast Analyser

6. Supported Assistive Technologies

Our remediated websites are tested to be compatible with:

  • NVDA with Firefox and Chrome (Windows)
  • VoiceOver with Safari (macOS and iOS)
  • TalkBack with Chrome (Android)
  • Windows High Contrast Mode
  • Keyboard-only navigation in all major browsers
  • Browser zoom up to 400% without loss of content or functionality

7. Ongoing Commitment

Accessibility is not a one-time fix but a continuous practice. We are committed to:

  • Including accessibility requirements at the start of every new project
  • Re-testing after significant content or code updates
  • Staying current with evolving WCAG guidelines including WCAG 2.2
  • Providing accessibility awareness within our team
  • Documenting all remediation work and maintaining audit logs for clients

8. Third-Party Content

While we strive to ensure accessibility across all content, some third-party tools, plugins, or embedded content such as external video players or map embeds may not fully conform to WCAG 2.1 AA. Where we identify such issues, we will:

  • Notify the third-party provider and request remediation
  • Provide an accessible alternative where technically feasible
  • Document known limitations in the relevant Accessibility Statement

9. Feedback and Complaints

We welcome feedback on the accessibility of any website we have developed or remediated. If you experience any accessibility barriers or wish to report an issue, please contact us using the details in Section 13 below.

We aim to acknowledge all accessibility feedback within 2 business days and to provide a substantive response or resolution within 10 business days.

10. Legal and Regulatory Basis

Our accessibility commitment is informed by the following legal frameworks:

  • Americans with Disabilities Act (ADA) — Title III, as applied to websites
  • Section 508 of the Rehabilitation Act of 1973 (as amended)
  • European Accessibility Act (EAA) — Directive 2019/882
  • Web Accessibility Directive — for public sector bodies in the EU
  • Ontario Accessibility for Ontarians with Disabilities Act (AODA)

11. Policy Review

This policy is reviewed annually or whenever significant changes occur in accessibility standards, legal requirements, or our service offerings. The most current version of this policy will always be available upon request.

12. Related Documents

  • Accessibility Statement (published per client website)
  • WCAG 2.1 Quick Reference — https://www.w3.org/WAI/WCAG21/quickref/
  • WAI-ARIA Authoring Practices Guide — https://www.w3.org/WAI/ARIA/apg/
  • PDF/UA-1 Standard (ISO 14289-1)

13. Contact Us

If you have any questions or concerns about this Accessibility Policy, or to report an accessibility barrier, please contact us:

Email: wi@versatileprollc.com Phone: (414) 928-8668 Mailing Address: Versatile Pro LLC 333 W Brown Deer Rd, Unit G-399 Milwaukee, WI 53217

This policy was last reviewed and updated on March 28, 2026.