The fastest way to show I can do this brief is to do a slice of it. Here's a content design engine — a real before/after plain-language rewrite of a dense, tax-style passage, an accessibility & readability pass applied line by line, a reusable content component, and the same content structured to be found and trusted by AI search.
"Where an entity has a liability that remains unsatisfied beyond the prescribed period, the Commissioner may, at his or her discretion, impose an administrative penalty calculated in accordance with the relevant rate, notwithstanding any prior arrangement entered into, unless the entity can demonstrate that the failure to remit was attributable to circumstances beyond its reasonable control."
"If you don't pay on time, you may get a penalty. We work out the penalty using the standard rate.
You may not have to pay it if something outside your control stopped you from paying — for example, a serious illness or a natural disaster. You'll need to show us what happened."
Grade 7 or lower for public-facing content — checked, not guessed.h1 → h2 → h3 order so screen-reader and AI parsing both follow the page."click here" — for keyboard and screen-reader users.Honest note: this is content-side accessibility — the part a content designer owns. Formal WCAG conformance auditing (colour contrast tooling, full assistive-tech testing) is where I'd work with the team's accessibility specialists rather than sign it off alone.
One accessible, plain-language pattern → reused across hundreds of "how to" pages → quality lifts everywhere at once.
The brief asks for content that's "discoverable, trusted, and aligned" across AI-enabled platforms and search. That's a content-design problem before it's a technical one — and it's exactly where my writing craft and AI workflow meet.