Accessibility
Accessibility is part of how we build Addienator.
Addienator.com and the application are being tested for clear structure, keyboard use, visible focus, readable contrast, responsive layouts, and understandable feedback. Reports from real users help identify barriers that testing can miss.
Draft statement with replace-before-launch fields
This statement is a construction draft. The service operator is [[REPLACE BEFORE LAUNCH: FINAL LEGAL BUSINESS NAME]], with the postal address [[REPLACE BEFORE LAUNCH: FINAL LEGAL BUSINESS POSTAL ADDRESS]]. These fields and the final accessibility statement require legal and accessibility review before launch.
Current approach
Accessibility work across the website and application
Testing happens component by component and again across complete user flows.
Keyboard and focus
Navigation, controls, dialogs, and forms are reviewed for keyboard operation, visible focus, logical order, and predictable opening and closing behavior.
Structure and presentation
Pages are reviewed for one clear main heading, meaningful heading order, readable contrast, useful alternative text, responsive reflow, and the absence of horizontal overflow.
Complete user flows
Account, membership, form, language, and application flows are part of the final integrated review. Component checks do not by themselves prove that every complete journey is accessible.
Describe the barrier
Tell us which page or application step you were using, what you expected to happen, and what prevented you from completing the task.
Include helpful context
If you are comfortable doing so, include your browser, device, and assistive technology. Do not send passwords, API keys, other credentials or secrets, payment-card information, or confidential source materials.
Use the Accessibility request type
The working Contact and Support form includes an Accessibility request type. Selecting it routes the request to support. The form requires consent, does not save the submitter’s IP address in the form entry, and uses honeypot and no-entry spam controls.
No final conformance claim yet
The final standard, conformance level, compatibility details, known limitations, assessment date, and response commitments are not yet approved. This draft does not claim certification or complete conformance.
Contact for accessibility requests
Use the Contact and Support form and select Accessibility so the request routes to support. You may also contact support@addienator.com. No response-time or remediation-time promise is made by this draft.
Report an accessibility issue
Open the working Contact and Support form and choose Accessibility. Your request will be routed to support.
