Portfolio piece: a sample Canvas course built on a custom theme I designed and coded (WCAG 2.2 AA).

1. Starting point and standard

Starting point

Two earlier builds were audited before a line of this theme was written.

The program is delivered in Canvas LMS, consistent with the other recent builds in the same portfolio. The university's own visual guidelines were reviewed for brand reference only. They don't govern structure, because the deliverable is a Canvas theme rather than a page on the university's website.

The two reference builds had very different strengths:

The two reference builds compared
 Reference build AReference build B
SelectorsScoped to authored contentGlobal and unscoped
ColoursTaken verbatim from the client's published brand siteApproximated from the logo colour
AccessibilityFull focus, keyboard, screen reader and reflow layerMinimal scaffolding

The decision was to build on the structural pattern of build A, and to record what was rejected from build B, and why.

No need to approximate from a logo; the documented palette is used directly.

Style sheet decisions, section 7

What wasn't carried over

Theming off the most visible brand colour

This university publishes exact hex values and a WCAG AA colour table. There was no need to work from a logo; the documented palette is used directly.

Global, unscoped element selectors

Styling bare headings, paragraphs and tables everywhere risks leaking into Canvas's own navigation and admin screens. Every content rule is scoped to authored content instead.

Minimal accessibility scaffolding

Replaced with the full focus, keyboard, screen reader and reflow layer from build A, which is structural engineering that works independently of any palette.

Why build B looked the way it did

Build B's looseness appears partly forced. That client's brand portal was staff-login-only, so the original author most likely couldn't reach the exact hex values and worked from the visible logo colour instead.

This build wasn't in that position. The guidelines were in hand, so it follows the fidelity pattern of build A, even though the program is organisationally modelled on build B.

The standard: WCAG 2.2 AA

The theme targets WCAG 2.2 AA. AA is the universal baseline for web services; AAA is aspirational and not expected wholesale. Version 2.2 is a superset of 2.1 and adds focus-appearance and target-size criteria that a stylesheet directly controls, so authoring to it future-proofs the build at near-zero cost.

Note

Why documented conformance matters

The university's own digital guidelines reference AA. In the current higher-education climate, legal floors cite 2.1 AA while field guidance advises 2.2 AA, so documented AA conformance is valuable to have on record.