1. Understand TASA
Open the homepage and Start here. Can you explain what TASA is and identify a useful next step?
Open the homepageCommittee review guide
Explore the proposed visitor experience, then review how each audit recommendation has been addressed.
Working proposal. This is a separate copy of the national site. The live site’s visitor experience has not been replaced. Visitor pages open without login for review. Forms demonstrate the experience without sending messages or creating subscriptions.
A short phone walkthrough
Try these journeys as someone who has just scanned a flyer’s QR code.
2. Find local connection
Search for Sunshine Coast, Noosa and the Western Australis Assemblies. Open an enquiry with the Assembly selected.
Try the Assembly list3. Find a gathering
Try Online and In person, check a date and open the details. Try the contact form with example details.
All 36 recommendations
“In preview” means a proposed implementation is available to try. It does not mean the committee has approved it or that every production check has passed.
27Proposed implementations
to explore in the preview
to explore in the preview
4Items with content-owner
confirmation still needed
confirmation still needed
5Items needing release,
hosting or real-user evidence
hosting or real-user evidence
F01Explain TASA before the structureIn preview
What is proposed here
The homepage gives a short TASA explanation and a dedicated Start here route before the detailed structure. Event and news feeds are omitted from the homepage at Sharon’s request; their dedicated sections remain available.
Original recommendation
Add a concise “What is TASA?” explanation and a separate Start here introduction. Answer what TASA does, why it matters to everyday life, what a Local Assembly is and what a newcomer can do today. Explain unfamiliar terms when first used. Link to the full structure for deeper study.
Acceptance check
A first-time visitor can describe TASA in their own words and identify a next step after a brief look at the first screen.
Suggested lead: Assembly Connect · P1
F02Bring the first action into viewIn preview
What is proposed here
The first actions sit beside the introduction. Narrow previews and enlarged text still need the final release checks.
Original recommendation
Shorten the hero to one clear heading, a short definition and two actions. Aim to make the first useful action visible in a common phone portrait view. Reduce repeated value statements and repeated calls to action lower down.
Acceptance check
At 360-430 px phone widths, people can see the primary action without a long introductory scroll; at 320 px it remains easy to reach with enlarged text.
Suggested lead: Web team · P1
F03Protect the first reading momentIn preview
What is proposed here
The automatic newsletter overlay is removed from the proposed presentation. Subscription is a deliberate inline task.
Original recommendation
Use a calm inline newsletter invitation after the introduction. If a pop-up is retained, trigger it after a deliberate visitor action and provide complete dialog behaviour. Keep the first visit focused on understanding, learning and local connection.
Acceptance check
A fresh visit can complete the introduction without an automatic overlay interrupting reading. Any dialog has a clear close control and predictable keyboard focus.
Suggested lead: Assembly Connect and web team · P1
F04Group the 11 top-level choicesIn preview
What is proposed here
Six main destinations are shown: Start here, Find an Assembly, Events, Learn, About TASA and Shop. Contact, Support and Shop have visible footer links; the existing external store is retained.
Original recommendation
Use five main choices: Start here, Find an Assembly, Events, Learn, and About TASA. Keep Contact easy to find. Put news, resources, Anna’s articles and work underway within clear landing pages and secondary navigation.
Acceptance check
The principal choices are visible together on a common phone. Five new visitors can each choose where to learn, connect or attend without coaching.
Suggested lead: Assembly Connect and web team · P1
F05Make labels match the destinationIn preview
What is proposed here
Meeting links lead to gatherings, old internal development links are normalised and Records and reports has its own clear landing page.
Original recommendation
Send meeting labels to Events, contact labels to contact routes and transparency labels to actual reports or a clearly titled reporting index. Replace the About page’s old home/resources destination with the intended current national destination.
Acceptance check
Each label accurately describes the page reached. Test the links in a signed-out phone browser, including the Back action.
Suggested lead: Content editors · P1
F06Improve search for newcomer questionsIn preview
What is proposed here
Search includes direct routes for Shop, news and newsletters, documents, FAQs and glossary, alongside beginner/subject routes and public news/group results. Ten visitor queries reached the relevant destination in the first two results. No-results help points to Start here and Contact.
Original recommendation
Review search indexing and ranking, add helpful synonyms such as “new”, “start”, “near me” and “reconveyance”, and give the beginner introduction a prominent result. Add an obvious search entry in the mobile menu.
Acceptance check
The ten most likely newcomer questions return a useful page in the first few results. A no-results state offers Start here and Contact.
Suggested lead: Web team and editors · P2
F07Add a list alongside the mapIn preview
What is proposed here
A native Assembly selector leads on smaller screens. On screens at least 1,000 CSS pixels wide, the existing map is visible with 44-pixel icon targets, zoom and full screen. Contact/event links and the searchable directory remain available.
Original recommendation
Put an accessible, searchable text directory first on phones, with Assembly name, region and contact action. Keep the map as a second view. Support area/name search and region filters without requiring location permission.
Acceptance check
Visitors can locate Sunshine Coast, Noosa and each Western Australis Assembly using text alone. The list and map use the same maintained roster.
Suggested lead: Web team · P1
F08Give enquiries a full-width routeIn preview
What is proposed here
Assembly enquiries open as a full-width page with the chosen Assembly selected. The preview form demonstrates validation without sending.
Original recommendation
Open a dedicated enquiry page or a full-width mobile sheet with the Assembly already selected. Keep required fields minimal, use 16 px or larger input text, and show clear success, error and retry states. Preserve the existing private routing.
Acceptance check
A user can complete the form without scrolling a small panel inside the map. Test recipient routing and delivery with an authorised test enquiry.
Suggested lead: Web team · P1
F09Reconcile the public Assembly rosterNeeds confirmation
What is proposed here
The copied roster is retained for demonstration. Coordinators must confirm status and consistency, including Torquay and the separate Western Australis entries.
Original recommendation
Have the responsible coordinators verify every public entry, status, contact route and region. Resolve Torquay from the authoritative roster. Maintain the three distinct Western Australis entries. Label forming or inactive groups explicitly where appropriate.
Acceptance check
Map, directory, enquiry selector and event filters agree with the approved roster and have a named editor and review date.
Suggested lead: Assembly coordinators · P1
F10Correct conflicting event detailsNeeds confirmation
What is proposed here
Labels use the stored online choice. Each recurring gathering appears once. Captain Creek’s copied June synopsis is flagged rather than replaced with an assumed topic.
Original recommendation
Reconcile date, recurrence, online/in-person status, location and the description at the source. Add a simple editorial preview before recurrence updates and a visible “last confirmed” cue where useful. Confirm changing venues before people travel.
Acceptance check
The listing, detail page and coordinator source agree for each upcoming event. A recurring event’s selected occurrence remains clear on its detail page.
Suggested lead: Local event editors · P1
F11Shorten the feed and rescue empty resultsIn preview
What is proposed here
The calendar groups recurring dates, limits the visible results and provides clear no-results routes.
Original recommendation
Show a shorter initial set with month/date grouping and Load more or pagination. Make filters compact and easy to reset. When there are no events, offer “Contact this Assembly”, nearby gatherings and suitable online introductions.
Acceptance check
A visitor can find the next relevant gathering without traversing a two-month wall of cards. Empty results always offer a useful alternative.
Suggested lead: Web team · P1
F12Put newcomer logistics before long messagesIn preview
What is proposed here
Start here provides the short learning path. The complete structure reference is visible on its dedicated pages, using the original section navigation without repeated introductory cards.
Original recommendation
Feature a newcomer-friendly event category. At the top of each detail show date, duration, time zone, venue or join action, who it is for, any requirements and a contact. Keep the full organiser message below. Consider calendar export, directions and optional viewer-local time.
Acceptance check
A newcomer can establish suitability and find the next action within the opening section. Changing the date or format cannot leave contradictory text behind.
Suggested lead: Event editors and web team · P2
F13Separate the introduction from detailed structureIn preview
What is proposed here
Useful-word definitions are included in Start here. All new wording is proposed for committee review, including the reconveyance description.
Original recommendation
Keep the reference material available and create a shorter introductory page before it. Use a short contents list, expandable detail where appropriate and mobile summaries for comparisons. Explain the General, Business, Jural and Guardianage pillars with practical examples and links.
Acceptance check
Newcomers can learn the basic relationship between local activity and the wider structure without reading every office description. Deep links still reach the full material.
Suggested lead: Assembly Connect and subject editors · P1
F14Turn the Resources directory into a learning hubIn preview
What is proposed here
Learn separates the introduction, structure and source material into three clear steps.
Original recommendation
Provide a genuine beginner guide, short FAQ and glossary, then a sequenced reading path. Label documents by topic, audience, format, date and size. Prefer mobile HTML summaries with optional accessible downloads. Keep superseded material clearly identified.
Acceptance check
Each resource answers the question suggested by its label. A newcomer can choose an appropriate next lesson without asking for a document first.
Suggested lead: Education and Assembly Connect · P2
F15Give Anna’s work context and useful discoveryIn preview
What is proposed here
Anna’s article library and original source links are retained in the shared reading layout.
Original recommendation
Keep Anna’s work prominent within Learn, with a short explanation of why it matters to TASA, a curated introductory sequence and topic search. Maintain original wording and source attribution. Add consistent reading navigation, related learning and a way back to the article collection.
Acceptance check
Readers can move from the introduction to a suitable article, then back to the learning path. Source notices and original links remain clear.
Suggested lead: Education editors · P2
F16Distinguish learning, attending and contributingIn preview
What is proposed here
Learning, attending, contributing and supporting have separate routes. The action-group reconveyance requirement is explicit.
Original recommendation
Start with learn, ask a question and connect locally. Explain action-group participation requirements at the point people consider contributing, including the established reconveyance requirement. Keep self-directed learning and appropriate public introductory gatherings welcoming.
Acceptance check
Visitors understand which first steps are open to newcomers and which roles have prerequisites. Group enquiries do not create an expectation of immediate eligibility.
Suggested lead: Assembly Connect and group leads · P1
F17Standardise the action-group overviewIn preview
What is proposed here
Group pages retain the full source description once, with current work, outputs, jurisdiction and pillar connections, published chair details, authorisation context and a contact route. The repeated purpose excerpts are removed.
Original recommendation
Give each group the same opening summary: purpose, current work, skills needed, participation requirements, contact route and meeting time with time zone where public. Place detailed working documents below and distinguish drafts from authorised outputs.
Acceptance check
A prospective contributor can answer “What does this group do?” and “What is my next step?” without interpreting a charter or internal working note.
Suggested lead: Action-group leads · P2
F18Explain contact and data handling clearlyNeeds confirmation
What is proposed here
Contact and newsletter forms link to a clearly marked privacy draft. Recipients, retention, providers and response expectations need confirmation before release.
Original recommendation
Publish accurate, approved privacy information covering enquiries, newsletter subscriptions, analytics and service providers. Link it at forms and in the footer. Explain who receives an enquiry, what happens next and a realistic response expectation. Simplify fields where practical.
Acceptance check
People can understand how their information is used before submitting. Confirmation and delivery are tested with consent. This recommendation is a transparency improvement, not a legal-compliance finding.
Suggested lead: Site owner and web team · P1
F19Use a compact news indexIn preview
What is proposed here
News uses readable summaries, dates and pagination, with events kept in the calendar.
Original recommendation
Use short excerpts, a clear date and category, consistent image crops and a limited first set. Add useful topic filters or pagination. On the homepage show only a small current selection after the introductory and local-connection sections.
Acceptance check
Readers can scan current items and reach older issues without scrolling through oversized cards. Stale announcements are archived or marked appropriately.
Suggested lead: Assembly Connect and web team · P2
F20Polish the newsletter reading routeIn preview
What is proposed here
Existing newsletter content and document links are retained. Final PDF download labels, file sizes and real-phone reading need a release pass.
Original recommendation
Retain the HTML summary and optional PDF. Add download size, clear issue navigation and an accessible full-text option where feasible. Check PDF reading order, selectable text, image descriptions and phone legibility. Keep the archive complete and consistently labelled.
Acceptance check
A visitor can understand the issue’s main content on the page and decide whether to download. Previous and next issues are easy to locate.
Suggested lead: Newsletter editors · P3
F21Make subscription a calm, complete taskIn preview
What is proposed here
Subscription retains first name and email, adds a deliberate consent choice and links to one privacy page that also retains the current national agreement. The form remains a demonstration.
Original recommendation
State the type and approximate frequency of updates, what confirmation to expect and how to unsubscribe. Keep sign-up optional and inline. Validate errors, confirmation, welcome delivery and preference links through an authorised end-to-end test.
Acceptance check
A subscriber knows whether sign-up succeeded and receives the expected confirmation or welcome. Unsubscribe and preference links work on phones without a confusing generic dead end.
Suggested lead: Newsletter and web team · P2
F22Reduce decorative height on task pagesIn preview
What is proposed here
Utility pages use compact introductions so the task begins sooner on a phone.
Original recommendation
Use a compact title-and-description treatment for Finder, Events, Contact and Resources. Reserve larger visual storytelling for the homepage and selected introduction pages. Standardise mobile spacing and responsive heading sizes.
Acceptance check
The first useful control appears quickly on task pages, while headings remain readable at enlarged text sizes. Essential instructions are never hidden to save space.
Suggested lead: Design and web team · P2
F23Simplify visual competition and long footersIn preview
What is proposed here
One shared type, colour, spacing, card and button system runs through the preview. The current master logo is used consistently.
Original recommendation
Create a small shared style system for headings, body copy, cards, buttons and spacing. Use the approved TASA identity consistently, high contrast text areas and restrained imagery. Group secondary footer links under clear headings and retain contact and privacy visibility.
Acceptance check
The same action looks and behaves consistently across templates. All text remains legible outdoors and with larger system text.
Suggested lead: Design and editors · P2
F24Keep tables and small controls usableIn preview
What is proposed here
Important controls are generously sized. Wide reference tables get a focusable scroll region and a reading cue. The earlier SEOPress beacon finding was corrected.
Original recommendation
Use 44-48 px tap areas for important controls. Offer phone-friendly comparison summaries and a visible horizontal-scroll cue for the full table. Preserve keyboard access. No public accessibility-widget change is supported by the beacon observation.
Acceptance check
Tables remain readable without forcing whole-page horizontal scrolling. Important phone controls remain easy to activate without covering content.
Suggested lead: Web team · P2
F25Give controls meaningful accessible namesIn preview
What is proposed here
Directory, search and event filters have explicit labels. The text directory offers an alternative to anonymous map markers.
Original recommendation
Name each marker by Assembly and action. Give each filter one short programmatic label with an explicit field association. Use the accessible text directory as an equivalent way to find and contact an Assembly.
Acceptance check
A screen reader announces “Sunshine Coast Assembly” and concise filter names. Keyboard users can locate a result and activate its contact route.
Suggested lead: Web team · P1
F26Complete dialog and keyboard behaviourIn preview
What is proposed here
The menu and search support Escape and focus return; the main content has a skip link. Contact and support use full pages rather than small nested dialogs.
Original recommendation
Add a skip link and consistent main landmark. Review focus entry, focus containment, Escape and focus return for every overlay. Ensure visible focus and logical order through the menu, map alternative, search and forms.
Acceptance check
A keyboard-only visitor can complete the principal journeys and always knows where focus is. Screen readers identify overlays and page content predictably.
Suggested lead: Web team · P1
F27Validate reading and error recovery manuallyRelease evidence
What is proposed here
Keyboard and reflow checks can be performed here. VoiceOver, TalkBack, contrast review, real hardware and larger-text checks remain release evidence.
Original recommendation
Review every shared template at 200% text and 400% browser zoom, contrast, heading order, meaningful image descriptions, diagram explanations, reduced motion, screen-reader reading order and field errors. Use native accessibility throughout the site.
Acceptance check
A representative iPhone VoiceOver and Android TalkBack user can read, navigate and recover from a deliberate form error. Complete a documented manual review before claiming accessibility conformance.
Suggested lead: Web team and volunteer testers · P2
F28Deliver appropriately sized imagesIn preview
What is proposed here
Images use WordPress-generated sizes where available, dimensions, lazy loading and restrained placement. Recheck sharpness and actual transferred bytes.
Original recommendation
Size logo/photo variants appropriately, add responsive images and explicit dimensions. Keep below-fold lazy loading; prioritise the LCP image.
Acceptance check
Compare bytes and rendering in a repeat test. Verify sharpness on high-density phones.
Suggested lead: Web team · P2
F29Reduce blocking styles safelyIn preview
What is proposed here
The proposed presentation uses a small shared stylesheet, system fonts and a focused script instead of rendering the original builder assets on these views.
Original recommendation
Review unused styles, critical CSS, compression and caching. Change one layer at a time; recheck menus, maps and forms.
Acceptance check
Repeatable improvement with no missing styles or interaction regression.
Suggested lead: Web team · P2
F30Measure actual loading and interactionRelease evidence
What is proposed here
A field-measurement plan remains necessary. The staging preview cannot establish real visitor loading or interaction percentiles.
Original recommendation
Track field loading and interaction where feasible. Aim for LCP ≤2.5 s, INP ≤200 ms and CLS ≤0.1 at the 75th percentile. [S4]
Acceptance check
Separate lab and field data, split devices and entry routes, and acknowledge small samples.
Suggested lead: Web and analytics leads · P2
F31Resolve the short-domain redirect discrepancyRelease evidence
What is proposed here
The public short-domain and printed QR destinations must be checked with the host and actual artwork. This preview does not change public domain routing.
Original recommendation
Inspect host/domain/path redirects, canonical settings and query preservation. Verify the exact URLs encoded on the actual flyers and banners, on real devices and different connections. Keep printed destinations stable under TASA control.
Acceptance check
QR scans, typed short-domain visits and test crawlers reach the intended public page with a short, consistent redirect chain. No claim is made that ordinary visitors currently all reach the 404.
Suggested lead: Judgie and hosting lead · P1
F32Retire obsolete public templates carefullyIn preview
What is proposed here
Legacy template paths are mapped to useful preview destinations with reversible redirects. Source records have been preserved.
Original recommendation
Map each obsolete route to a useful current destination or an intentional archive. Check links and dependencies before redirecting, unpublishing or removing anything. Consolidate the FAQ and old navigation. Raw shop shortcodes do not establish that WooCommerce is installed.
Acceptance check
Public visitors and search results no longer lead into empty development screens. Important historical links still resolve sensibly; the legacy statistics Honey Pot page is reviewed separately before any removal.
Suggested lead: Web team and content owner · P1
F33Align search and sharing with the intended siteIn preview
What is proposed here
Preview pages have specific titles, descriptions, canonical links and useful breadcrumbs. The preview is noindex; live indexing and sharing require release checks.
Original recommendation
Choose and document the preferred public URL policy, then align internal links, canonical tags, sitemap entries and social previews. Give priority pages specific titles and descriptions. Validate event data and breadcrumbs where supported. Review indexing and 404 recovery using appropriate webmaster access.
Acceptance check
A searcher sees one intended current destination for each key page, and shared links show the approved identity and a useful preview.
Suggested lead: Web team and editors · P2
F34Measure the outreach journey responsiblyRelease evidence
What is proposed here
WP Statistics is already available. Additional click and section-engagement measurement remains a configuration and privacy decision; no new analytics product is installed.
Original recommendation
Confirm the analytics setup with Judgie before adding anything, including licence, hosting resources, retention and ongoing maintenance costs. Use a stable TASA-controlled QR URL and distinct campaign tags for each outreach asset. Record Start here, Assembly search, contact, event and learning actions; keep personal form contents out of analytics.
Acceptance check
A test QR visit is attributed correctly and key actions appear once. Definitions for engaged time and conversions are documented. Heatmaps or recordings, if chosen, are separately justified and configured to protect input data.
Suggested lead: Analytics and hosting leads · P2
F35Give each content type an ownerNeeds confirmation
What is proposed here
The maintenance responsibilities and outstanding confirmations are listed below for agreement with the content owners.
Original recommendation
Assign owners for the Assembly roster, recurring events, learning, group summaries, news and documents. Use one source of truth for shared facts. Set review dates, archive rules and a short publication checklist covering phone preview, dates, links, status and contact ownership.
Acceptance check
Every active listing has an owner and a next review point. Event changes update all affected views. Old drafts are distinguishable from current authorised information.
Suggested lead: Assembly Connect and coordinators · P2
F36Test understanding with actual newcomersRelease evidence
What is proposed here
The phone walkthrough below turns the audit into practical tasks for five newcomers. No participant results have been claimed.
Original recommendation
Ask five people unfamiliar with TASA to scan a sample QR on their own phones. Ask them to explain TASA, find their nearest Assembly, locate a suitable event and ask a question. Observe without coaching, note hesitations and refine the page order and wording.
Acceptance check
Record completion, time, wrong turns and the words people use. Treat five participants as a useful formative test, not a statistically representative conversion study.
Suggested lead: Assembly Connect · P1 before sign-off
Check the screen sizes
Compare the proposed pages at phone, tablet and desktop widths.
Open responsive previewConfirm before release
Assembly and event owners
- Confirm the Assembly roster and status across map, list, enquiry routes and event filters.
- Confirm Captain Creek’s next workshop topic and current details.
- Agree who maintains recurring events and when they are reviewed.
- Confirm contact routing and a realistic response expectation.
Committee and hosting review
- Approve the visitor wording, learning path, menu and page hierarchy.
- Confirm privacy, newsletter and statistics settings.
- Check actual printed QR destinations and host redirects.
- Complete real-phone, screen-reader, delivery and performance checks.
Test understanding with five newcomers
Ask each person to scan a sample QR on their own phone, explain TASA, find their Local Assembly, locate a suitable gathering and ask a question. Observe without coaching. Record completion, wrong turns, hesitations and the words they use.
Use the findings to refine the proposal, then take the final pages and remaining decisions to Assembly Connect for approval.
A careful path to the public site
Approve the proposed pages and the supporting facts first. Transfer the agreed changes with a current backup, preserving new live events, enquiries and subscriptions. Recheck the public visitor journeys after release.