Blossom Care Disability Services
Site tested blossomcds.com.au
Standard WCAG 2.2 Level AA
Date of test 7 August 2026
Pages tested 12
Tested by Vasilii Aldukhov, Founder and Developer, Web Ways Tech
Report status Point-in-time measurement. No re-test is scheduled.
This report records what we tested, how we tested it, and what we found. It is published in full, including the sections on what was not tested and what was not fixed.
1. Scope
Pages
All twelve routes in the application were tested in full.
| Page | |
|---|---|
| 1 | / |
| 2 | /about-us |
| 3 | /ndis |
| 4 | /blog |
| 5 | /contact-us |
| 6 | /services/support-coordination |
| 7 | /services/community-participation |
| 8 | /services/community-nursing-care |
| 9 | /services/independent-living |
| 10 | /services/individualised-living-options |
| 11 | /services/dissability-accommodation |
| 12 | /services/transport |
Processes
The enquiry form was tested from first field to submitted state, including validation behaviour and the message returned after submission.
Outbound form submissions were intercepted at the browser during testing, so no test messages were delivered to the business.
Viewports
Desktop at 1280 by 900. Mobile at 375 by 812. Reflow tested at 320 CSS pixels.
2. Tools
| Tool | Version |
|---|---|
| axe-core | 4.10.2 |
| Chromium | 149.0.7827.55 |
| Playwright driver | Python 3.11.9 |
| Chrome DevTools Protocol, Accessibility domain | accessible name and role verification |
3. What was not tested
Automated testing finds a minority of accessibility barriers. The checks below were not run, and the passes in section 5 cover only the checks that were.
- NVDA was not run. There is no desktop screen reader pass in this test.
- VoiceOver on iOS was not run. There is no mobile screen reader pass.
- Colour Contrast Analyser was not used manually. Contrast ratios were read by axe-core from computed styles. Text sitting on background photographs was returned as incomplete by axe and remains unmeasured. This affects six elements on the home page, including the H1, and two to four elements on other pages.
- Focus indicator contrast (1.4.11) was not measured.
- No users of assistive technology took part in this test.
4. Findings
Five criteria did not pass. Severity follows the axe-core classification.
4.1 Contrast (Minimum), 1.4.3, Level AA
Serious. Present on all twelve pages.
Normal body text requires a contrast ratio of at least 4.5 to 1. Five colour pairs fall below it. All five are set in the site theme, so they repeat on every page.
| Element | Foreground | Background | Measured | Required |
|---|---|---|---|---|
| Active navigation link, header | #f11d7c | #ffffff | 4.03:1 | 4.5:1 |
| Active navigation link, footer | #f11d7c | #fff8f5 | 3.84:1 | 4.5:1 |
| Green action buttons, all pages | #fafbfc | #00ca89 | 2.06:1 | 4.5:1 |
Pink Learn more button, home | #ffffff | #f791b2 | 2.17:1 | 4.5:1 |
External NDIS links, /ndis, six instances | #00ca89 | #ffffff | 2.14:1 | 4.5:1 |
The green action buttons carry the primary call to action on every page, including Send Message on the enquiry form. At 2.06 to 1 they sit below half the required ratio.
4.2 Status Messages, 4.1.3, Level AA
Serious. Enquiry form, present on ten pages.
After the enquiry form is submitted, a message reporting the result is inserted into the page. It has no role="alert" and no aria-live attribute.
Measured on the form: live regions zero, elements with role="alert" zero, aria-invalid not set on any field.
A person using a screen reader submits the form and receives no announcement of whether it was sent.
4.3 Identify Input Purpose, 1.3.5, Level AA
Moderate. Enquiry form, present on ten pages.
No field on the form has an autocomplete attribute.
| Field | Declared type | autocomplete | Expected |
|---|---|---|---|
| Name | text | absent | name |
text | absent | email | |
| Phone | text | absent | tel |
| Message | textarea | absent | not required |
The email and phone fields are declared as type="text". We entered a value that was not an email address, and the form accepted it and submitted. Format validation is absent. That last point is not a WCAG criterion. It is recorded here because the same pass found it.
4.4 Non-text Content, 1.1.1, Level A
Moderate. Three confirmed instances.
Images that carry no meaning should have an empty alt attribute so assistive technology can skip them. Three decorative images hold text that is announced instead. Each was confirmed in the accessibility tree, not just in the markup.
| Page | alt value | Image |
|---|---|---|
/ | kid | photograph in a content block |
/services/* | waves | decorative divider |
/about-us | sectiob | decorative image, value appears to be a typing error |
Repeated alt values of icon, checkmark, logo and ndis also appear in the markup. They were not confirmed in the accessibility tree and are not counted as findings here.
Photographs that do carry meaning are described well across the site, for example a boy with down syndrome holding a dog and Social inclusion - man with down syndrome working in garden.
4.5 Info and Relationships, 1.3.1, Level A
Serious. One page.
On /services/dissability-accommodation, a <ul> element has <p> elements as direct children. A list may contain only <li>, <script> or <template> as direct children.
4.6 Bypass Blocks, 2.4.1, Level A: recorded as unresolved
The site has no Skip to main content link. The first keyboard stop on every page is the logo, followed by eight stops through the header.
The site does provide landmark regions, one each of main, nav, header and footer, on every page. W3C technique ARIA11 accepts landmark regions as a sufficient technique for this criterion, so conformance is arguable.
A sighted person using a keyboard without a screen reader does not use landmark navigation. For that person the header is passed in full on every page.
5. Criteria tested and passed
The six criteria new in WCAG 2.2
| Criterion | Level | Result | Evidence |
|---|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | Pass | 39 keyboard stops walked against a fixed header 80 pixels high at z-index 10000. No focused element was obscured. |
| 2.5.8 Target Size (Minimum) | AA | Pass | The only targets under 24 pixels are seven inline links on /ndis at 22 pixels high. Centre to centre spacing is 48 pixels, so the spacing exception applies. |
| 2.5.7 Dragging Movements | AA | Not applicable | No sliders, carousels or draggable elements. |
| 3.2.6 Consistent Help | A | Pass | The phone number and the contact link appear in the same position in the header and footer on all twelve pages. |
| 3.3.7 Redundant Entry | A | Not applicable | The form is a single step. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Not applicable | The site has no login. |
Other criteria checked
| Criterion | Level | Result | Evidence |
|---|---|---|---|
| 1.4.10 Reflow | AA | Pass | No horizontal scrolling at 320 CSS pixels on any of the twelve pages. |
| 2.4.7 Focus Visible | AA | Pass | A focus indicator is present at every keyboard stop. See the note below. |
| 3.3.2 Labels or Instructions | A | Pass | All four form fields are wrapped in a <label> element with visible text. |
| 2.4.4 Link Purpose (In Context) | A | Pass | Service cards on the home page return correct accessible names, for example Supported Independent Living and Specialist Disability Accommodation. |
| 1.3.1 Info and Relationships, headings | A | Pass | No heading level is skipped on any of the twelve pages. |
| 3.1.1 Language of Page | A | Pass | lang="en" is set. |
| 1.1.1 Non-text Content, missing alt | A | Pass | Zero images without an alt attribute across all twelve pages. |
Note on 2.4.7. The focus indicator is the browser default, outline: auto 1px rgb(16,16,16). No custom focus style is set, and its contrast was not measured (see section 3), so this is a pass on presence only.
6. What was fixed
Nothing was fixed.
7. What was not fixed, and why
The site is under the control of its owner. This engagement measured the site as it stood, and did not include remediation work. No changes were made to the site in the course of it.
8. Conformance
This report does not state that blossomcds.com.au conforms to WCAG 2.2 Level AA, and it cannot. A conformance claim under the W3C method requires full pages and full processes with no exceptions, verified against every criterion.
What this report states is narrower and checkable: the site was tested against WCAG 2.2 Level AA on the date shown, using the tools and the scope listed above. Specific failures were found and are listed. The absence of other failures is not demonstrated.
9. Report your own barrier
If you use this site and hit something this report does not cover, we want to know. Email info@webwaystech.com.au with the page address and what happened.
Who ran this test
Vasilii Aldukhov Founder and Developer, Web Ways Tech linkedin.com/in/vasilii-aldukhov
Vasilii Aldukhov has been building websites for ten years and runs Web Ways Tech from Kogarah in Sydney. He works mostly in WordPress, and he built the Blossom Care site. He ran this test himself, so the person who wrote the code is the person reporting on it.
Web Ways Tech 5 Blake St, Kogarah NSW 2217 (02) 8313 5438 info@webwaystech.com.au ABN 78 494 398 487
Date of report 7 August 2026
Method How we test accessibility