Security, accessibility, and performance
The checks that keep a small staff from inheriting a site they cannot safely edit, or one the public cannot use.
Where it goes wrong
On a small organization's site, security problems are mostly ordinary: a shared password, an administrator account from the original install, plugins two years behind. Accessibility problems are ordinary too: a form that cannot be finished from the keyboard, gray text on a gray background, a PDF that a screen reader cannot read. Slow pages lose people on phones.
What we do
- Review accounts and permissions, and remove what nobody uses.
- Apply updates and record what changed.
- Test keyboard use, labels, contrast, and the phone layout against WCAG 2.2 AA, by hand as well as with tools.
- Find the pages that load slowly and fix the cause.
How it runs
For a site we build, this is part of the build. For a site we did not build, a review can be scoped on its own. It produces a written list in the order we would fix things, with risks separated from items that are only untidy. The standard and the legal question are on the accessibility page.