Accessibility Statement for Archway Recovery Services
This is an accessibility statement from Archway Recovery Services.
Measures to support accessibility
Archway Recovery Services takes the following measures to ensure accessibility of Archway Recovery Services:
-
Include accessibility throughout our internal policies.
-
Integrate accessibility into our procurement practices.
-
Appoint an accessibility officer and/or ombudsperson.
-
Provide continual accessibility training for our staff.
-
Assign clear accessibility goals and responsibilities.
Conformance status
The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. Archway Recovery Services is fully conformant with WCAG 2.1 level AA. Fully conformant means that the content fully conforms to the accessibility standard without any exceptions.
Additional accessibility considerations
“Although our goal is WCAG 2.1 Level AA conformance, standard sometimes change. Our goal is to help you. If you struggle with our website, please call us for information about the services we provide: 707-399-9190
Feedback
We welcome your feedback on the accessibility of Archway Recovery Services. Please let us know if you encounter accessibility barriers on Archway Recovery Services:
-
Phone: 707-399-9190
-
E-mail: Kevin@ArchwayRecovery.org
-
Visitor Address: 609 Jefferson St. Fairfield, CA 94533
We try to respond to feedback within 2 business days.
Technical specifications
Accessibility of Archway Recovery Services relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:
-
HTML
These technologies are relied upon for conformance with the accessibility standards used.
Assessment approach
Archway Recovery Services assessed the accessibility of Archway Recovery Services by the following approaches:
-
Self-evaluation
April 6,2022
This statement was created on CA using the W3C Accessibility Statement Generator Tool.
I'm a paragraph. Click here to add your own text and edit me. It's easy.