Service
Web implementation
A new website, or developing an existing one further – with accessibility from the first sketch instead of as a repair job at the end.
Saving money by thinking about accessibility from the start
Retrofitting accessibility almost always means rebuilding components, reworking colours, rearranging structure. Thought through from the start it costs hardly any extra effort, because it feeds into decisions that have to be made anyway – which element, which contrast, which order.
What is included
- Concept and information architecture
- Design, or the implementation of an existing design
- Development – from a static site to a content management system
- Integration with existing systems where that is needed
- Testing before launch: keyboard, screen reader, zoom, contrast
- Training, so the editorial team can keep the accessibility up
Technology
I work with what suits the project: WordPress or TYPO3 where an editorial team is meant to work with it, a static site generator where speed and low maintenance count. Online shops and integrations with existing systems are possible.
What I avoid: frameworks that make a site heavy for no good reason. A large share of the barriers on the web comes from tools nobody needed.
On the use of AI
AI tools take routine off my hands and make some steps faster. What they do not take off my hands: deciding whether an image description really fits, whether the keyboard order makes sense, whether an error message helps.
After launch
An accessible website only stays one if it is kept that way. So the handover includes a short guide for the editorial team – what to keep in mind with new content – and, on request, a retest after some time in operation.