If a page, form, product record, demo, chat experience, document, or checkout path prevents access, contact us. We will provide reasonable assistance or an alternate way to receive the information or complete the task.
Revision summary: Added the WCAG 2.2 AA target, tested environments, known limitations, review process, and barrier-reporting path.1. Our target
We use the Web Content Accessibility Guidelines 2.2 Level AA as the design and testing target for public website experiences, while recognizing that ongoing content and third-party integrations require continuing review.
2. Practices in the website
- Responsive layouts for mobile, tablet, desktop, zoom, and text reflow
- Semantic headings, landmarks, labels, accessible names, and status messages
- Keyboard access and visible focus treatment
- Skip navigation and current-page identification
- Text alternatives and decorative-image handling
- Reduced-motion support for users who request it
- Contrast and non-color indicators for important states
3. Tested environments
The public application is reviewed at 320, 390, 768, 1024, and 1440 pixel widths using current Chromium-based browsers. Automated checks cover keyboard focus, accessible names, target size, reflow, reduced motion, and representative screen-reader semantics. Third-party checkout and identity experiences are reviewed separately within the access available to Temen.
- Keyboard-only navigation
- Browser zoom and narrow reflow
- Reduced-motion preference
- Windows screen-reader and browser combinations
- Representative iOS and Android mobile browser layouts
4. Known limitations
Product content can originate with publishers and may contain complex tables, legacy formatting, or incomplete media descriptions. Interactive demonstrations and third-party checkout, scheduling, identity, and document experiences can have accessibility behavior controlled partly by their providers. Temen reviews and improves the presentation under its control and can provide an alternate format when needed.
5. Feedback and assistance
Tell us the page or task, the problem encountered, the browser or assistive technology if you are comfortable sharing it, and the preferred way to respond. Do not include passwords, product keys, payment data, or tenant secrets.
6. Continuing review
Accessibility is part of design, code review, responsive testing, content review, and launch validation. We prioritize issues that block navigation, understanding, form completion, cart use, checkout, contact, or access to service information.
7. Report an accessibility barrier
Use the accessibility request form to identify the page, product, document, or task that prevented access. The form routes to Temen’s accountable sales-operations path and requests only the information needed to investigate and provide an alternate format.
Report an accessibility barrier