Accessibility

♿

Working toward WCAG 2.1 Level AA conformance

Last updated: July 2026 · Accessibility is an ongoing effort

Postopcare.info is committed to making post-surgery recovery information accessible to all patients, regardless of ability. We believe that recovery guidance should be available to everyone, and we work toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.

Our commitment

Surgery recovery is stressful enough without struggling to use a website. We are committed to ensuring that every patient — including those who use assistive technologies, have low vision, limited dexterity, or cognitive difficulties; can access the information they need to recover safely at home.

We continuously review and improve the accessibility of our site. Where we fall short, we want to know about it so we can fix it.

What we do

The following accessibility features are implemented across Postopcare.info:

🌐

Language declaration

lang="en" is set on all 205 pages, ensuring screen readers use the correct pronunciation. Google Translate integration is available on every page for patients who speak other languages.

📱

Responsive design

Every page includes a viewport meta tag and is tested on mobile, tablet, and desktop screen sizes. Content reflows without horizontal scrolling at up to 400% zoom.

📄

Semantic HTML

Pages use proper semantic elements: <main>, <header>, <footer>, <nav> — with a logical heading hierarchy so assistive technologies can navigate content structure.

🎛

ARIA attributes

Interactive elements across 167 pages include aria-label attributes, and modal dialogs use role="dialog", aria-modal, and aria-labelledby for proper screen reader announcements.

⌨

Keyboard navigation

All interactive elements (buttons, links, modals, search overlays) are reachable and operable by keyboard. Focus indicators are visible on all focusable elements.

◑

High contrast

Text meets WCAG AA contrast ratios throughout the site. Dark text on an ivory background ensures readability. Interactive elements maintain sufficient contrast in all states.

🖨

Print-friendly

Every page includes a dedicated print stylesheet that strips navigation chrome, reformats coloured boxes to bordered outlines, and adds source attribution, so patients can print guides for offline use.

🔓

No login required

All content is accessible without creating an account, entering an email address, or completing any registration form. There are no authentication barriers to any recovery guide.

🔒

Privacy-first architecture

All patient data (checklists, symptom logs, medication schedules) is stored locally on the patient's own device using browser localStorage. No server dependency means no risk of data being inaccessible due to account lockout.

Known limitations

We are honest about where our accessibility work is incomplete. The following limitations are known:

Some interactive tools (pain tracker, wound photo journal, medication schedule builder) use browser localStorage and require JavaScript to be enabled. These tools do not function without JavaScript.
Automated accessibility testing (such as axe-core or Lighthouse audits) has not been completed across all pages. A formal accessibility audit is planned.
Some older pages may have inconsistent heading hierarchy where headings skip levels (for example, jumping from <h2> to <h4>).

We are actively working to address these limitations. As pages are reviewed and updated, accessibility improvements are included in each release.

Feedback

We welcome accessibility feedback from patients, carers, clinicians, and accessibility professionals. If you encounter any barriers using this site: content you cannot access, features that do not work with your assistive technology, or anything that makes the site harder to use — please let us know.

You can contact us through askmygp.com.au. We take all accessibility reports seriously and will work to resolve issues promptly.

When reporting an accessibility issue, it helps if you can describe which page you were on, what you were trying to do, and what assistive technology (if any) you were using.

Standards reference

This accessibility statement references the Web Content Accessibility Guidelines (WCAG) 2.1, published by the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI). WCAG 2.1 Level AA is the internationally recognised benchmark for web accessibility.

📖 WCAG 2.1 specification at w3.org ↗