Accessibility
The target is WCAG 2.2 Level AA. I check keyboard use, small-screen layout, contrast, reduced motion, text alternatives and gestures within the agreed scope and environment. A future environment needs separate verification.
Practice standards
Clear rules for producing and handing over content.
These rules explain how I handle accessibility, data, AI, files and rights. Your organisation’s rules take priority.
Privacy and data
I use as little data as possible. Identifiable student data is not required by default. Sensitive content stays out of the public site and unapproved tools.
Use of AI
Any use of AI follows client rules, can be traced and is checked by a person. AI output alone never approves subject content, rights or an assessment.
Files and rights
I distinguish client-provided files, files created for the project, software dependencies and third-party content. The proposal describes delivered formats, rights, credits and reuse limits.
Handover and dependencies
The proposal lists editable files, dependencies and update notes. Any dependency that cannot be avoided is disclosed before approval.
During the project
Requirements become verifiable criteria.
- List requirements, the target environment and sensitive content.
- Name the people who approve the work.
- Test the first production.
- Record problems, decisions and fixes.
- Deliver sources, dependencies and known limits.
First project