Accessibility Statement
Effective date: April 17, 2026
Palm Commissions, LLC ("Palm Commissions," "we," or "us") is committed to making the Palm Commissions web application accessible to the widest possible audience, including people with disabilities. We believe that every independent insurance and real estate agent should be able to track and verify their commissions regardless of how they use the web.
1. Conformance target
We design and test Palm Commissions against the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level. WCAG defines requirements for designers and developers to improve accessibility for people with disabilities across visual, auditory, motor, and cognitive categories.
2. Measures we take
- Semantic HTML, ARIA landmarks, and labeled form controls across the dashboard, upload, tracking, settings, and billing surfaces.
- Keyboard-operable modals, table actions, and form controls with visible
:focus-visibleindicators that meet WCAG contrast requirements. - Screen-reader live regions for error messages, async status changes, and copy-to-clipboard confirmations.
- Descriptive accessible names on row-level action buttons (edit, delete, accept) so screen reader users can tell one row's controls from another.
- Chart visualizations provided as
<figure>elements with visually hidden text summaries of the data.
3. Known limitations
We audit Palm Commissions continuously and maintain a public backlog of accessibility issues. Areas with known, tracked gaps today:
- Custom filter dropdowns in the commission history table do not yet follow the full WAI-ARIA combobox pattern — keyboard users can still operate them, but screen-reader announcement of the listbox open state is limited.
- Sortable column headers in some tables are activated by mouse click only; keyboard sort activation is in progress.
- The invite/referral leaderboard is rendered with
<div>elements rather than a native<table>— screen reader navigation is less rich than other tables in the app.
Each of these limitations is tracked with an open GitHub issue and has a targeted fix on the roadmap. If you hit a barrier that is not listed here, we want to hear about it (seeContact below).
4. Assistive technology we test with
We test the most common screen reader / browser combinations:
- NVDA on the latest Firefox and Chrome (Windows).
- VoiceOver on the latest Safari (macOS and iOS).
- Keyboard-only navigation (no pointing device) across every major flow.
5. Feedback and accommodation requests
If you encounter an accessibility barrier or need an accommodation to use Palm Commissions, please contact us. We aim to respond within five business days.
- Send us a message through the and include "Accessibility request" in your note.
- In-app: use the Feedback button in the dashboard sidebar — submissions are read by the same team.
6. Regulatory context
This statement is intended to support compliance with the Americans with Disabilities Act (ADA) Title III, Section 508 of the Rehabilitation Act, and the European Accessibility Act (EAA). This statement does not constitute a legal guarantee of conformance; where there is a conflict between this statement and a specific regulatory requirement, the regulatory requirement controls.