Accessibility Statement

1. Our accessibility commitment

Rloop seeks to make its online platform and Services available to people with a wide range of disabilities.

This includes people with disabilities affecting:

• vision;
• hearing;
• mobility;
• speech;
• cognition;
• learning;
• language processing;
• neurological functioning;
• combinations of disabilities.

Accessibility is an ongoing process. We expect the platform, available technology, legal standards, and user needs to continue evolving.

2. Scope of this Statement

This Statement applies to Rloop-operated:

• public website pages;
• Customer forms;
• account registration and login;
• Contractor applications;
• Contractor dashboards;
• scheduling tools;
• job-management features;
• financial and payment interfaces;
• legal and policy pages;
• support communications;
• future Customer and Contractor platform features.

Third-party websites, payment interfaces, maps, document viewers, and other embedded services may be governed by their providers’ accessibility practices.

3. Accessibility standard

Rloop is working toward substantial alignment with the Web Content Accessibility Guidelines, commonly known as WCAG.

Our current design and development goal is to improve conformance with:

Stating this goal does not mean that every page, workflow, third-party integration, or uploaded document currently satisfies every WCAG 2.2 Level AA success criterion.

We use the guidelines as a continuing design, development, testing, and remediation framework.

4. Measures Rloop may take

Accessibility measures may include:

• using semantic HTML;
• providing descriptive page titles;
• maintaining logical heading structures;
• adding text alternatives for meaningful images;
• supporting keyboard navigation;
• maintaining visible keyboard focus;
• associating labels with form fields;
• presenting understandable validation errors;
• improving color contrast;
• avoiding unnecessary flashing content;
• allowing browser text enlargement;
• using responsive layouts;
• reviewing interactive controls;
• testing important user workflows;
• correcting reported barriers when reasonably possible.

5. Current and planned accessibility features

Depending on the page and feature, Rloop may provide:

• consistent navigation;
• descriptive links and buttons;
• keyboard-operable menus;
• responsive content for mobile and desktop devices;
• text-based status messages;
• form labels and instructions;
• clear success and error messages;
• visual and textual status indicators;
• readable legal documents;
• alternatives to completing a process online;
• support for accessibility-related requests.

6. Assistive technology and browser compatibility

Rloop is designed to work with modern browsers and commonly used assistive technologies.

Users may access the platform using technologies such as:

• screen readers;
• screen magnification;
• keyboard-only navigation;
• voice-control software;
• browser zoom;
• operating-system accessibility settings;
• alternative input devices.

Compatibility may vary based on the browser, operating system, assistive technology, device, configuration, and feature being used.

Keeping browsers and assistive technologies updated may improve compatibility and security.

7. Forms, accounts, and authentication

Rloop uses online forms for registration, applications, contact requests, scheduling, availability, and other platform functions.

We seek to make these forms more accessible by:

• connecting labels with inputs;
• providing instructions before complex fields;
• marking required fields;
• presenting validation feedback;
• preserving user-entered information when reasonably possible;
• supporting keyboard submission;
• avoiding unnecessary time limits.

Users who cannot complete an account or form process may request assistance or an alternative submission method.

8. Documents, images, and uploaded content

Some Rloop workflows involve documents or images, including:

• insurance certificates;
• licenses;
• tax forms;
• identification;
• job photographs;
• estimates;
• receipts and service records.

Documents supplied by users or third parties may not always be fully accessible.

When reasonably possible, Rloop may:

• provide information in an alternative format;
• explain the material contents;
• accept information through another method;
• assist with completing a required workflow.

Accommodation requests involving sensitive documents will remain subject to identity, privacy, and security controls.

9. Accessible communications

Rloop may communicate through:

• website messages;
• email;
• telephone;
• text messaging;
• account notifications;
• written support responses.

A user may request a reasonable communication adjustment, such as:

• receiving information in writing;
• using email instead of telephone;
• receiving a plain-language explanation;
• allowing additional response time;
• communicating through an authorized representative.

The available method may depend on the urgency, identity-verification needs, security risks, and nature of the request.

10. Accessibility when requesting Services

Customers may communicate disability-related access needs that are relevant to scheduling or completing a service.

Relevant information may include:

• preferred communication methods;
• additional time needed to answer a door or provide access;
• the presence of a service animal;
• mobility-related property access instructions;
• the need for written confirmation;
• another reasonable service-related accommodation.

Customers should provide only the information reasonably necessary to communicate and arrange the requested accommodation.

Rloop does not generally require a person to disclose a diagnosis when the relevant accommodation need can be addressed without it.

11. Contractor accessibility responsibilities

Contractors using Rloop must interact respectfully with Customers and other individuals with disabilities.

Contractors must not:

• unlawfully discriminate based on disability;
• harass or demean a person because of a disability;
• improperly interfere with a service animal;
• disregard reasonable access instructions;
• disclose private disability-related information without a legitimate reason.

Contractors remain responsible for performing only work they can perform safely and lawfully.

A safety concern should be communicated based on the actual conditions of the assignment rather than assumptions about a person’s disability.

12. Known and potential limitations

Although Rloop is working to improve accessibility, some barriers may remain.

Potential limitations may include:

• older pages or components;
• incomplete image descriptions;
• complex forms;
• uploaded scans or photographs;
• third-party payment interfaces;
• map integrations;
• browser-specific behavior;
• temporary development defects;
• new features awaiting accessibility review.

Reporting a specific page, control, browser, device, and assistive technology helps us investigate more effectively.

13. Third-party services and content

Rloop may rely on third parties for:

• payment processing;
• hosting;
• security;
• maps and location services;
• email delivery;
• document storage;
• other platform functionality.

Rloop does not control every accessibility feature or limitation of independently operated third-party services.

We may communicate accessibility concerns to a provider, seek an alternative, provide an alternative process, or assist the user when reasonably possible.

14. Requesting an accommodation

To request assistance or a reasonable accommodation, please provide:

• your name;
• a reliable contact method;
• the page, feature, communication, or service involved;
• the task you are trying to complete;
• the barrier encountered;
• the accommodation or alternative that would help;
• any relevant timing requirement.

Rloop may ask reasonable follow-up questions needed to understand the request.

We will not request unnecessary medical information. Some requests may require account or identity verification.

15. Reporting a digital accessibility barrier

Accessibility feedback should identify the problem as clearly as possible.

Helpful details include:

• the page address or page title;
• the affected button, link, field, or content;
• what you expected to happen;
• what actually happened;
• browser and device type;
• assistive technology used;
• screenshots or error text;
• whether the issue prevents completion of an urgent task.

Do not include passwords, complete payment-card numbers, or unrelated sensitive information in an accessibility report.

16. How Rloop responds

After receiving an accessibility request or report, Rloop may:

• acknowledge the request;
• ask for additional details;
• provide immediate assistance;
• offer an alternative process;
• investigate the affected feature;
• correct a technical defect;
• refer the issue to a service provider;
• include the issue in future development work;
• explain when a requested solution is not reasonably available.

Response and remediation timing may depend on the severity of the barrier, complexity, available resources, third-party involvement, security requirements, and effect on the user.

When immediate correction is not possible, we will consider a reasonable alternative method of access.

17. Testing and continuous improvement

Rloop may use a combination of:

• developer review;
• keyboard testing;
• automated accessibility tools;
• browser testing;
• mobile testing;
• manual inspection;
• user feedback;
• periodic remediation.

Automated testing alone cannot identify every accessibility issue.

As Rloop grows, accessibility considerations may be added to design reviews, reusable components, development standards, content procedures, and release testing.

18. Legal rights and responsibilities

This Statement describes Rloop’s accessibility goals and procedures. It does not reduce or replace any accessibility right provided by applicable law.

The Americans with Disabilities Act may require businesses open to the public to provide accessible access to their goods and services, including appropriate access involving websites and online services. :contentReference[oaicite:0]{index=0}

The WCAG standards describe methods for making web content more accessible to people with visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities. :contentReference[oaicite:1]{index=1}

Nothing in this Statement guarantees that a particular legal standard applies to every Rloop page, feature, transaction, Contractor, or third-party service in the same manner.

19. Updates to this Statement

Rloop may update this Statement to reflect:

• accessibility improvements;
• new platform features;
• reported barriers;
• revised technical standards;
• changes to third-party services;
• changes in applicable law or guidance.

The revised Statement will display an updated effective date or last-updated date.