Accessibility Statement for palantrix.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 thorough manual audit was conducted, covering all WCAG criteria that require human judgment
- Ongoing issue tracking automatically detects regressions and recognizes resolved items between scans
| WCAG Criterion | Issue Description | Pages Affected |
|---|---|---|
| Best Practice | Verify all button elements have accessible text content for assistive technologies | 3 |
| Best Practice | Evaluate text and background color combinations meet the 4.5:1 AA contrast ratio | 1 |
| Best Practice | Check that heading levels follow a logical hierarchical sequence without skipping levels | 2 |
| Best Practice | Confirm that all hyperlink elements have meaningful, discernible text content | 1 |
| Best Practice | Check all visible page content is within defined landmark regions for navigation | 8 |
| Best Practice | Check that HTML document includes a non-empty title element to identify the page purpose | 1 |
| Best Practice | Confirm the HTML element includes a lang attribute for assistive technology support | 1 |
| Best Practice | Check that the page includes at least one level-one heading to establish content hierarchy | 1 |
| Best Practice | Check that the page contains no more than one banner landmark region | 3 |
| Best Practice | Check that landmark regions have unique accessible names to help users distinguish between them | 3 |
| Best Practice | Identify interactive controls nested inside other interactive elements, which creates keyboard navigation and announcement issues | 1 |
| Best Practice | Confirm the container elements with ARIA roles include the required child role elements | 1 |
| Best Practice | Confirm that scrollable content areas can be reached and navigated using keyboard controls | 6 |
| Best Practice | Ensure visible labels match the element accessible name for voice control users | 4 |
| Best Practice | Detect paragraphs styled as headings instead of using proper heading elements | 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 thorough manual audit 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.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.