Skip to main content
Built for everyone

Accessibility at FindDevs.

We aim for FindDevs to work for everyone, regardless of ability, device, or assistive technology. Here's the standard we hold ourselves to and how to report something that doesn't quite work.

Last updated: 2 May 2026
Standard
WCAG 2.1 AA
Web Content Accessibility Guidelines, level AA conformance target.
Last full audit
2 May 2026
Internal review covering keyboard, screen-reader and contrast tests.
Open issues
0 critical
No known critical barriers. Outstanding minor items are listed below.

1. Our commitment

FindDevs is committed to digital accessibility. We design and build the Service with the goal that every Australian, including people who use screen readers, voice control, switch devices, or who have low vision, motor, or cognitive differences, can compare developer quotes without barriers.

We use the Web Content Accessibility Guidelines (WCAG) 2.1 at conformance level AA as our baseline standard. Where we're not yet there, this page tells you so honestly.

2. What we do today

2.1 Standards we follow

  • WCAG 2.1 AA across all public pages.
  • Semantic HTML5 with proper landmark roles (main, nav, footer, etc.).
  • Australian Disability Discrimination Act 1992 obligations.
  • WAI-ARIA only where native HTML is not sufficient.

2.2 Specific features

  • Keyboard navigation. Every interactive element, links, buttons, the navigation menu, the quote modal, FAQ accordions, is reachable and operable using Tab, Shift+Tab, Enter and Space.
  • Skip link. The first focusable element on every page is a "Skip to main content" link.
  • Focus indicators. A visible focus ring is shown on every focusable element.
  • Screen reader support. Tested with VoiceOver (macOS, iOS) and NVDA (Windows). Form labels are programmatically associated, and every icon has an accessible name where it carries meaning (or aria-hidden="true" where it's decorative).
  • Reduced motion. If your operating system requests reduced motion, we honour it, marquee animations stop, parallax is disabled, and reveal animations show content immediately.
  • Colour contrast. Body text meets at least 4.5:1 contrast against its background; large headings meet at least 3:1.
  • Resizable text. The site is fully usable when text is zoomed to 200% in any modern browser, and reflows down to 320px wide without horizontal scroll.
  • Forms. Every input has a visible label, error messages are announced to screen readers, and required fields are marked both visually and programmatically.
  • Document language. Every page declares lang="en-AU".
  • Alt text. Every meaningful image has a descriptive alt attribute. Decorative images use alt="".

3. Known limitations

We're being honest. The following items are on our backlog and we're working on them:

  • Marketing illustrations. The "How it works" illustrations are decorative; we're working on adding richer text alternatives that describe the steps in more detail.
  • Cookie table. On very narrow screens (under 360px), the cookies table requires horizontal scroll. We're redesigning it as a stacked card layout.
  • Third-party fonts. Google Fonts are loaded from a third-party domain. If that domain is blocked, the page falls back to system fonts, which works, but visually differs from the design.

If you've hit something that isn't in this list, please tell us, see Section 5.

4. How we test

Accessibility testing is part of every release we ship. Specifically:

  • Automated audits with axe DevTools and Lighthouse on every page change.
  • Manual keyboard-only walk-throughs of new flows.
  • Manual screen-reader walk-throughs (VoiceOver and NVDA) at minimum quarterly.
  • Colour contrast checks using the WCAG contrast formula on every new design token.
  • Mobile accessibility checks (iOS VoiceOver, Android TalkBack) on the quote modal at minimum quarterly.

We don't pretend automation finds everything. The judgement calls, focus order, alt-text quality, error-message clarity, get human review.

5. Report a barrier

If you've encountered a part of FindDevs that doesn't work for you, please tell us. We treat accessibility issues as priority bugs, most are fixed in the next deploy.

Email accessibility issues
Helpful to include: the page URL, what you were trying to do, what happened, your browser and assistive technology (if any). We'll acknowledge within 2 business days and aim to fix critical issues within 7 days.

6. Alternative formats

If a page on FindDevs isn't accessible to you and you need the information urgently, email us at hello@finddevs.com.au and we'll send you the same content in a format that works, plain-text email, a phone call, or whatever you need.

7. Accessibility in the network

We ask the developers in the FindDevs network to consider accessibility in the work they quote on, and we encourage clients to make it a stated requirement of new builds. We're happy to suggest network developers with documented experience in WCAG conformance, just mention it in your brief.

8. Changes to this statement

We update this statement whenever we ship significant accessibility improvements or discover new known issues. The "Last updated" date at the top reflects the most recent change.

9. External resources

If you'd like to learn more about web accessibility:

Joshua from Logan City just received three quotes for Mobile App development. Get your 3 quotes now
7 minutes ago