Australia version. Written for Australian design hiring: accessibility under the Disability Discrimination Act 1992, the Maguire v SOCOG website case, and Australian address and date conventions in design tasks. US version

UX/UI Designer Interview Prep (Australia)

Prepare for UX and UI design interviews in Australia: the Disability Discrimination Act, the Sydney Olympics website case, WCAG 2.2 AA checks and local form design.

The interactive tool loads here when JavaScript runs.

About this tool

What is UI/UX Designer Interview Prep?

Australian design panels, in government and in product companies, tend to ask the accessibility question in legal terms as well as technical ones: what the Disability Discrimination Act 1992 means for a website or app, and how your team decided what to fix first. Section 24 of the Act covers the provision of goods, services and facilities, which is where websites and apps fall, and the Act includes an unjustifiable hardship defence. It does not name a WCAG version, so teams set their own target, usually WCAG 2.2 AA today.

Australia also has one of the earliest web accessibility rulings anywhere. In Maguire v Sydney Organising Committee for the Olympic Games, a blind man who used a refreshable braille display complained in 1999 that the official Olympics site lacked alt text, hid the index of sports and could not be read in the results tables. The Human Rights and Equal Opportunity Commission found the organisers in breach of the DDA, rejected their claim that fixing the results tables (estimated at A$2.2 million) was an unjustifiable hardship, and awarded A$20,000 in damages. It is a useful story to tell when a panel asks why accessibility belongs in the design phase rather than at the end.

Use the tabs as normal: rehearse the frameworks, tick the skills your portfolio proves, run a timed challenge and test each case study against the review questions. This version adds the Australian context and checks worth knowing from memory.

  • Four design process frameworks
  • 32 core design skills with progress tracking
  • Four design challenges with a 40 to 60 minute phased plan
  • Portfolio case study structure and 24 review questions
  • Inputs and progress saved in your browser
Read the guide: Engineering Manager, ML Engineer and Designer Interviews Explained

Updated

How to use UI/UX Designer Interview Prep

  1. Open each framework on the Design Frameworks tab with View Process.
  2. Tick the skills on the Core Skills tab that you can show in your portfolio; the header percentage tracks coverage.
  3. On Design Challenges, choose a prompt in Select Design Challenge and enter extra constraints in Additional Requirements, such as "first-time users, one-handed use".
  4. Click Generate Design Approach, set a timer for the total shown, and work through each phase on paper or in your design tool.
  5. Rehearse your case studies against the questions on the Portfolio Questions tab.

Worked examples

Results table header colours

Input

White header text on #00838F teal, and on #D84315 burnt orange

Output

#00838F: 4.52:1 (passes AA, barely); #D84315: 4.44:1 (fails AA for normal text)

WCAG 2.2 AA needs 4.5:1 for normal-size text. Two colours that look equally strong land either side of the line, which is why you check with a contrast tool rather than by eye. Darkening the orange to #BF360C gives 5.60:1.

Fixing a US-template address form

Input

A sign-up form with "ZIP code", a five-digit pattern and a list of US states

Output

Suburb, State or territory (a select of the eight: NSW, VIC, QLD, WA, SA, TAS, ACT, NT) and a four-digit Postcode field

Label the fields as Australians expect, and give the postcode a numeric keyboard on mobile. Each field needs a visible label, not just placeholder text, to meet WCAG.

A 45-minute accessibility retrofit task

Input

Select Design Challenge: Accessibility Improvement. Additional Requirements: "event ticketing site; screen reader users must be able to compare session times and prices"

Output

The five timed phases from the tool, with the requirements carried into the plan

This is the SOCOG problem in miniature. Spend the design phase on a properly structured table or list of sessions with headings, and on keyboard focus order through the booking steps.

Background and insight

The lesson of the SOCOG case for designers is that cost arguments made late rarely hold up. The organisers had argued about the effort of retrofitting accessibility to a finished site; designing the data tables, navigation and image text accessibly from the start would have cost far less. That is the argument to make in an interview when asked how you get accessibility work prioritised.

Local conventions show up in design tasks. Australian addresses use a state or territory and a four-digit postcode, dates are written day, month, year ("Friday 6 November"), and weeks start on Monday. An address form copied from a US template, with a ZIP code field and a 50-state list, is an easy thing for a panel to spot.

Common use cases

  • Rehearsing whiteboard challenges

    Run each of the four prompts against the timed plan until you consistently reach a finished core flow.

  • Preparing a portfolio presentation

    Restructure each case study into context, process, decisions and results, and test it against the 24 questions.

  • Spotting skill gaps

    Unticked skills in the Core Skills list show which areas your portfolio does not yet demonstrate.

  • Running design interviews

    Use the challenges and portfolio questions as a consistent set for every candidate.

Tips and limitations

  • Know the DDA basics in one sentence each: section 24 covers goods, services and facilities, and unjustifiable hardship is the defence an organisation can argue.
  • Tell the SOCOG story briefly and accurately: alt text, the index of sports, the results tables, and A$20,000 in damages.
  • Say "WCAG 2.2 AA" and know three new 2.2 criteria: focus not obscured, target size (minimum 24 by 24 CSS pixels) and accessible authentication.
  • Use Australian conventions in portfolio screens: day-month-year dates, four-digit postcodes, A$ where amounts could be confused with other dollars.
  • Show testing with users who rely on assistive technology, even a small round, rather than only an automated scan.

Sources and further reading

  1. Disability Discrimination Act 1992, Federal Register of Legislation (Australian Government). Section 24 (goods, services and facilities) and section 29A (unjustifiable hardship).
  2. Business case for digital accessibility: SOCOG case study, W3C Web Accessibility Initiative. The Maguire v SOCOG complaint, findings and A$20,000 damages.
  3. Web Content Accessibility Guidelines (WCAG) 2.2, W3C

Frequently asked questions

Does the Disability Discrimination Act apply to websites and apps?

The Act covers the provision of goods, services and facilities (section 24), and the Maguire v SOCOG decision in 2000 applied it to a website. It does not name a WCAG version, so teams set a target themselves; WCAG 2.2 AA is the current W3C level most use. Get legal advice for a specific product.

What happened in the Sydney Olympics website case?

Bruce Maguire, who is blind, complained in 1999 that the official Olympics site lacked alt text, made the index of sports hard to reach and did not give access to the results tables. The Human Rights and Equal Opportunity Commission found a breach of the DDA, rejected the A$2.2 million hardship argument for the results tables and awarded him A$20,000 in damages.

What is unjustifiable hardship under the DDA?

It is a defence in the Act: an organisation can argue that making a service accessible would impose unjustifiable hardship. In the SOCOG case the argument failed for the results tables. In an interview, the point to make is that designing accessibly from the start keeps that cost low.

Which WCAG level should I mention in an Australian design interview?

WCAG 2.2 level AA. Be ready with specifics: 4.5:1 contrast for normal text and 3:1 for large text, visible focus that is not hidden by sticky headers, labels that do not rely on colour alone, and a 24 by 24 pixel minimum target size.

What should an Australian address form look like?

Street address, suburb, a state or territory select with the eight options, and a four-digit postcode. Keep visible labels on every field, use a numeric keyboard for the postcode, and avoid US terms such as ZIP code.

How many case studies should a UX portfolio presentation include?

Two or three in depth for a 45 to 60 minute slot, each with the problem, your role, the decisions and the result. One that shows accessibility changing the design is worth including.

Is there an in-depth guide to UI/UX Designer Interview Prep?

Yes. “Engineering Manager, ML Engineer and Designer Interviews Explained” covers the background, how it works, common pitfalls and worked examples. Read the full guide.