EduSwap
Policy details

How EduSwap approaches accessibility and inclusion

1. Commitment to accessibility

EduSwap Pty Ltd is committed to making the EduSwap platform accessible, usable and inclusive for school staff, including users who rely on assistive technology or other accessibility supports.

The platform is intended to support equitable access and to align with relevant Department of Education digital accessibility expectations.

EduSwap’s goal is to conform with WCAG 2.1 Level AA.

This Statement should be read together with EduSwap’s Terms of Service, Privacy Policy and other platform policies.

2. Accessibility standards referenced

Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.

Australian Government Digital Service Standard.

Relevant NSW and Victorian Department of Education digital accessibility requirements.

Inclusive design principles that support usable, school-friendly digital experiences.

3.1 Perceivable

Text alternatives are provided for non-text content where appropriate.

Colour contrast is designed to support readability.

Text can be resized without loss of core functionality.

Headings, labels and content structure are designed to remain consistent and understandable.

Critical information should not rely solely on images.

3.2 Operable

Keyboard navigation is supported across key platform experiences.

Logical tab order is maintained where reasonably practicable.

Visible focus indicators are used to support keyboard and assistive navigation.

The interface avoids flashing content or harmful visual effects.

Core user flows are not intended to depend on strict time limits.

3.3 Understandable

Navigation and page structure are designed to be predictable and consistent.

Forms and inputs aim to provide clear instructions and helpful guidance.

Error states aim to provide descriptive feedback and practical next steps.

Language is written to be clear, direct and suitable for school environments.

3.4 Robust

EduSwap aims to remain compatible with modern assistive technologies and current browsers.

Semantic HTML is used to improve accessibility and structure.

ARIA attributes may be applied where appropriate to support assistive technology.

Cross-browser and cross-device accessibility is considered as part of ongoing development.

4. Accessibility testing practices

Automated accessibility scanning may include tools such as Lighthouse and axe-core.

Manual keyboard-only navigation testing is used to assess key user flows.

Screen reader testing may include tools such as NVDA and VoiceOver.

Colour contrast and colour-blindness pattern checks are considered during review.

Accessibility checks are undertaken during feature development and significant platform updates.

5. Known limitations and roadmap

Additional ARIA labelling may continue to be introduced across interactive components.

Future improvements may include stronger support for alternative text handling in user-uploaded images.

Compatibility testing with a broader range of assistive technologies may continue over time.

Internal accessibility standards and developer awareness may continue to mature as the platform evolves.

6. Feedback and accessibility support

Users can report accessibility issues or request support by emailing support@eduswap.com.au.

Accessibility-related reports are intended to be acknowledged within 3 business days.

Where an issue is confirmed, EduSwap will aim to communicate next steps or remediation timing based on priority and complexity.

7. Compliance summary

EduSwap is designed with the goal of aligning with WCAG 2.1 Level AA principles.

The platform is intended to support Australian digital accessibility expectations, including school-sector guidance.

Accessibility improvements form part of EduSwap’s ongoing development lifecycle.