Accessibility Statement for theliftbx.com
-
WCAG 2.2 Level AA
-
EN 301 549 v3.2.1 (European standard)
-
Section 508 of the Rehabilitation Act (United States)
-
Title II and III of the Americans with Disabilities Act (ADA)
- Weekly automated scans identify all critical, machine-detectable issues across pages using WCAG logic
- A defined set of 22 manual checks is conducted internally by our team based on guided instructions from the platform
- Ongoing issue tracking automatically detects regressions and recognizes resolved items between scans
| WCAG Criterion | Issue Description | Source |
|---|---|---|
| No active issues found. | ||
| WCAG Criterion | Issue Description | Pages Affected |
|---|---|---|
| Best Practice | Evaluate text and background color combinations meet the 4.5:1 AA contrast ratio | 12 |
| Best Practice | Check that heading levels follow a logical hierarchical sequence without skipping levels | 14 |
| Best Practice | Verify images have alternative text or are explicitly marked as decorative | 14 |
| Best Practice | Confirm the banner landmark region is at the top level of document structure | 14 |
| Best Practice | Confirm that complementary landmark regions (aside) are positioned at the top level | 14 |
| Best Practice | Check that the page contains no more than one banner landmark region | 14 |
| Best Practice | Check that landmark regions have unique accessible names to help users distinguish between them | 14 |
| Best Practice | Check all visible page content is within defined landmark regions for navigation | 14 |
| Best Practice | Validate that assigned ARIA roles are appropriate and permitted for the given HTML element type | 14 |
| Best Practice | Validate list elements (ul, ol) contain only permitted child elements like li | 4 |
| Best Practice | Verify that every form control has an associated visible label that is programmatically linked | 1 |
| Best Practice | Ensure every id attribute value in the document is unique | 14 |
| Best Practice | Check that elements in the focus order have appropriate interactive roles | 6 |
| Best Practice | Ensure visible labels match the element accessible name for voice control users | 14 |
| Best Practice | Detect paragraphs styled as headings instead of using proper heading elements | 3 |
| Best Practice | Confirm that dialog and alertdialog elements have descriptive accessible names | 14 |
| Best Practice | Confirm the container elements with ARIA roles include the required child role elements | 3 |
| Best Practice | Confirm that all hyperlink elements have meaningful, discernible text content | 1 |
| Best Practice | Identify table header cells (th) that are empty and lack descriptive text | 1 |
| Best Practice | Ensure non-empty data cells in large tables have associated header cells | 1 |
-
Automated Testing:
Conducted weekly using the AccessibilityChecker.org testing platform, covering both mobile and desktop interfaces to identify machine-detectable issues. -
Manual Testing:
A set of 17 essential manual tests is performed to assess aspects that require human judgment, using popular browsers (Chrome, Firefox, Safari) on both desktop and mobile devices. -
Interactive Element Testing (User-Performed):
Interactive components (such as forms, menus, dialogs, and dynamic content) are evaluated through user testing using the AccessibilityChecker browser extension. -
Assistive Technology Compatibility:
Tested with major screen readers (e.g., NVDA, JAWS, VoiceOver) and across popular browsers (Chrome, Firefox, Safari) on both desktop and mobile devices.
This website underwent a full manual accessibility audit and remediation by AccessibilityChecker.org, verified through multiple rounds of QA with assistive technology, including screen readers (NVDA, JAWS, VoiceOver), keyboard navigation, and contrast testing.
Certain parts of this website rely on components that are developed and controlled by third parties. The code of these components cannot be modified by the website owner or by any agency, and they may contain accessibility issues that we are unable to fix directly:
- Shopify Checkout: the checkout flow is generated and hosted by Shopify, which does not permit merchants to modify its code.
- Product reviews module: star ratings, review listings, and the \\\"Write a Review\\\" window are rendered by a third-party application.
- Help and support widget: the help section is delivered through an external frame by a third-party support provider.
- GovX ID verification: the military and first responder discount verification is provided by GovX, an external service.
- Customer account module: the account window (orders and profile) is rendered by an external module.
- Certain built-in Shopify elements whose code Shopify does not allow to be changed.
If you experience difficulty with any of these components, please contact us through the details on this page and we will gladly provide the information or complete the action you need through an alternative method.
AccessibilityChecker.org provides automated testing results and supports manual and interactive testing; however, completion of all manual and interactive tests remains the sole responsibility of the customer. The customer is also fully responsible for implementing any recommended corrections or remediation actions.
This tool is not all inclusive, and does not constitute legal advice, a legal guarantee, or certification of compliance with any accessibility laws, regulations, or standards. Accessibility requirements may change over time, and compliance depends on ongoing maintenance and review. The customer is solely responsible for ensuring the contemplated domain is reviewed periodically and remains compliant with applicable accessibility requirements.