Accessibility Statement for orsgroup.com.au
-
WCAG 2.2 Level AA
-
EN 301 549 v3.2.1 (European standard)
-
Section 508 of the Rehabilitation Act (United States)
-
Title II and III of the Americans with Disabilities Act (ADA)
- Weekly automated scans identify all critical, machine-detectable issues across pages using WCAG logic
- A defined set of 17 manual checks is conducted internally by our team based on guided instructions from the platform
- Ongoing issue tracking automatically detects regressions and recognizes resolved items between scans
| WCAG Criterion | Issue Description | Source |
|---|---|---|
| 1.4.3: Contrast (Minimum) | Ensures the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds | Automated |
| 4.1.2: Name, Role, Value | Ensure ARIA Input Fields Have Accessible Names | Automated |
| 2.4.4: Link Purpose (In Context) | Ensures links have discernible text | Automated |
| 3.1.3 Unusual Words (AAA), 3.1.4 Abbreviations (AAA), 3.1.5 Reading Level (AAA), 3.1.6 Pronunciation (AAA) | Content Clarity and Linguistic Support | Manual |
| 1.3.6 Identify Purpose (AAA) | Identify Purpose of Components and Regions | Manual |
| 2.5.5 Target Size (AAA) | Interactive Element Sizing | Manual |
| 3.2.5 Change on Request (AAA), 3.3.5 Help (AAA), 2.2.4 Interruptions (AAA), 2.2.6 Timeouts (AAA) | User Control, Interruptions, and Data Preservation | Manual |
| 2.4.8 Location (AAA) | User Location and Orientation | Manual |
| WCAG Criterion | Issue Description | Pages Affected |
|---|---|---|
| Best Practice | Ensure ARIA Attributes Are Allowed for Each Role | 6 |
| Best Practice | Ensure ARIA Input Fields Have Accessible Names | 6 |
| Best Practice | Ensure ARIA Parent Elements Have Required Child Elements | 6 |
| Best Practice | Ensures the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds | 9 |
-
Automated Testing:
Conducted weekly using the AccessibilityChecker.org testing platform, covering both mobile and desktop interfaces to identify machine-detectable issues. -
Manual Testing:
A set of 17 essential manual tests is performed to assess aspects that require human judgment, using popular browsers (Chrome, Firefox, Safari) on both desktop and mobile devices. -
Interactive Element Testing (User-Performed):
Interactive components (such as forms, menus, dialogs, and dynamic content) are evaluated through user testing using the AccessibilityChecker browser extension. -
Assistive Technology Compatibility:
Tested with major screen readers (e.g., NVDA, JAWS, VoiceOver) and across popular browsers (Chrome, Firefox, Safari) on both desktop and mobile devices.
AccessibilityChecker provides automated testing results and supports manual and interactive testing; however, completion of all manual and interactive tests remains the sole responsibility of the customer. The customer is also fully responsible for implementing any recommended corrections or remediation actions.
This tool is not all inclusive, and does not constitute legal advice, a legal guarantee, or certification of compliance with any accessibility laws, regulations, or standards. Accessibility requirements may change over time, and compliance depends on ongoing maintenance and review. The customer is solely responsible for ensuring the contemplated domain is reviewed periodically and remains compliant with applicable accessibility requirements.