Trust & support

Accessibility & Contact Support

Find a clear route to report accessibility barriers, request an alternative format or obtain support when a page, form or document workflow cannot be used.

Accessibility and support

Send an accessibility request, tell us about a barrier, or ask for help using PIQSA.

Website and accessible-format support

Consent-based enquiry handling

Review by the Prep IQ team

Please do not submit passwords, payment details, passport numbers or other sensitive documents through this contact form.

Send a support request

Required fields are marked by the browser. Your consent is required before the enquiry is submitted.

Submissions are stored in the enquiry queue. Email/SMS delivery, service-level promises and automatic acknowledgements are not configured by this form.

Detailed guide

What to know and what to do next

Find a clear route to report accessibility barriers, request an alternative format or obtain support when a page, form or document workflow cannot be used.

Step 1

Report a specific barrier

A useful report identifies the page, task, device or browser, and the barrier encountered. Do not include passwords or private documents unless support specifically requests a necessary file through a safe channel.

Share the page path and the step that failed.
Describe keyboard, screen-reader or visual issues.
Include a short reproduction sequence.

Step 2

Provide an accessible alternative where possible

Support should acknowledge the barrier and help the user continue the task while the underlying issue is investigated. Do not promise a resolution time that the team has not committed to.

Offer a safe alternative contact route.
Prioritise blockers on forms and essential tasks.
Record the issue and workaround.

Step 3

Continuously improve accessibility

Important routes should be tested with keyboard-only interaction, screen readers, zoom and mobile layouts. Automated checks help, but manual review is needed for real usability.

Check labels, focus states and heading structure.
Test validation and error messages.
Recheck after significant UI changes.

Step 4

Report a barrier with enough detail to reproduce it

Describe the page, device or browser where relevant, the task you were trying to complete and what prevented you from doing it. Avoid including sensitive account information in public reports. If you need an alternative format or urgent assistance, state the barrier and the practical accommodation requested.

Identify the affected page and task.
Describe the barrier and its impact.
Request an accessible alternative where needed.

Step 5

Use reports to improve the full journey

Track the issue from acknowledgement through testing and resolution. A correction should be checked with keyboard navigation, focus order, screen-reader semantics or other affected interaction rather than judged only by visual appearance. Keep the contact route usable and publish only accessibility statements that match verified practice.

Record owner and reproduction steps.
Retest the affected interaction.
Confirm the result with the reporter when appropriate.

Frequently asked questions

What if I cannot submit the contact form?

Use a verified alternative contact method and report the page and error so the team can investigate.

Does automated accessibility testing guarantee accessibility?

No. It must be complemented by manual and user-focused testing.

What if the contact form itself is inaccessible?

Provide another published contact route and record the barrier so that the form can be fixed.

Can a page claim full accessibility after one visual review?

No. Verify relevant interactions and assistive-technology behaviour and describe limitations honestly.

Next step

Need help making an informed choice?

Explore destination and course guides, or prepare your questions for Prep IQ.