Accessibility Statement for RSD MRKT
This is an accessibility statement from rsdmrkt.com.
Measures to support accessibility
RSD MRKT takes the following measures to ensure accessibility of RSD MRKT:
Include accessibility throughout our internal policies.
Provide continual accessibility training for our web staff.
Assign clear accessibility goals and responsibilities for web staff.
Employ formal accessibility quality assurance methods.
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. rsdmrkt.com is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.
Feedback
We welcome your feedback on the accessibility of RSD MRKT. Please let us know if you encounter accessibility barriers on RSD MRKT:
Phone: 1-800-856-9801
E-mal: support@rsdmrkt.com
We try to respond to feedback within 2 business days.
Compatibility with browsers and assistive technology
rsdmrkt.com is designed to be compatible with the following browsers and assistive technologies:
Most modern browsers are tested and supported including Firefox, Chrome, Safari, & Edge.
rsdmrkt.com is not compatible with:
browsers older than 3 major versions or mobile operating systems older than 5 years
Technical specifications
Accessibility of RSD MRKT 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
WAI-ARIA
CSS
JavaScript
These technologies are relied upon for conformance with the accessibility standards used
Assessment approach
RSD MRKT assessed the accessibility of RSD MRKT by the following approaches:
Self-evaluation
Regular evaluation using Google Lighthouse and Wave Plug from webaim.org
Formal complaints
Please use the Report Issue email support@rsdmrkt.com if you encounter an issue.
Date
This statement was created on 26 October 2023 using the W3C Accessibility Statement Generator Tool
