Accessibility Statement for lifeboostcoffee.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 | Ensure Buttons Have Accessible Names | 1 |
| Best Practice | Ensures the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds | 25 |
| Best Practice | Ensures the order of headings is semantically correct | 11 |
| Best Practice | Landmarks should have a unique role or role/label/title (i.e. accessible name) combination | 23 |
| Best Practice | Ensures links have discernible text | 23 |
| Best Practice | Ensure Required ARIA Attributes Are Present | 2 |
| Best Practice | Ensures <img> elements have alternate text or a role of none or presentation | 6 |
| Best Practice | Ensures the contentinfo landmark is at top level | 7 |
| Best Practice | Ensures the document has at most one contentinfo landmark | 7 |
| Best Practice | Ensures interactive controls are not nested as they are not always announced by screen readers or can cause focus problems for assistive technologies | 1 |
| Best Practice | Ensures all page content is contained by landmarks | 2 |
| Best Practice | Ensure ARIA Attributes Are Allowed for Each Role | 2 |
| Best Practice | Ensure ARIA Parent Elements Have Required Child Elements | 2 |
| Best Practice | Ensures that lists are structured correctly | 2 |
| Best Practice | Ensures headings have discernible text | 5 |
| Best Practice | Ensures <dl> elements are structured correctly | 2 |
| Best Practice | Ensures the main landmark is at top level | 2 |
| Best Practice | Ensures the document has at most one main landmark | 2 |
| Best Practice | Ensures select element has an accessible name | 3 |
| Best Practice | Ensure that the page, or at least one of its frames contains a level-one heading | 2 |
| Best Practice | Ensures <meta name="viewport"> does not disable text scaling and zooming | 1 |
| Best Practice | Ensure ARIA Roles Are Correctly Applied | 24 |
| Best Practice | Elements marked as presentational should not have global ARIA or tabindex to ensure all screen readers ignore them | 1 |
| Best Practice | Ensures <li> elements are used semantically | 1 |
| Best Practice | Ensure Prohibited ARIA Attributes Are Not Used | 2 |
| Best Practice | Ensure ARIA Attributes Have Valid Values | 1 |
| Best Practice | Ensures <iframe> and <frame> elements have an accessible name | 2 |
-
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.
AccessibilityChecker 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.