Accessibility Statement
Codegevity should be usable by as many people as possible — including anyone browsing with a keyboard, a screen reader, at high zoom, or with motion reduced. This page records where the site actually stands, including the parts that do not yet meet the standard.
The target
We aim for WCAG 2.2 Level AA.
The site is partially conformant. Most of the standard is met. Some of it is not, and some of it has been verified with only one screen reader. Both are listed below rather than left out.
What was reviewed
A full accessibility review was carried out in August 2026, covering keyboard operation of both forms and the mobile menu, visible focus, heading order and landmark structure, form labelling and error messaging, colour contrast in both the light and dark themes, reduced-motion support, and alternative text on images.
Changes made as a result:
- Visible focus indicators on every interactive element, in both themes. Previously focus was only styled on form fields, and was close to invisible.
- A “skip to content” link for keyboard and screen reader users.
- Page headings moved inside the main landmark, so the structure of each page is announced correctly.
- Form fields now identify themselves as required, and error messages are tied to the field they describe rather than sitting loose beside it.
- Errors are signalled by more than colour alone.
- After a form is sent, focus moves to the confirmation so the outcome is not silently missed.
- Navigation menus and pagination carry proper names, and the current page is marked as such.
- Animation and page-scrolling now respect the operating system’s “reduce motion” setting throughout.
- Portfolio screenshots are real images with alternative text. They were previously background graphics, invisible to screen readers.
- Text and control colours were re-measured against every surface they appear on, in both themes, and adjusted where they fell short. Small print, the green accent used as text, buttons, and input borders all now meet the minimum.
- Anything reached by an in-page link or by tabbing now scrolls clear of the sticky header instead of landing underneath it.
- The site was tested at 320px wide, at 200% zoom, and with increased line, letter, and word spacing applied. Two layout faults were found and fixed; no content is cut off or forced into horizontal scrolling under any of those conditions.
- Comments are now styled and use the site’s own markup. They previously fell back to a deprecated WordPress template whose heading structure skipped a level.
Testing with a screen reader
On 11 September 2026 the site was tested with VoiceOver — on macOS with both Safari and Chrome, and on iOS with Safari. This was a scripted run of twelve checks covering focus visibility, the skip link, heading structure, both forms, the mobile menu, the expanding navigation menus, site search, the questions accordion, dark mode, and reduced motion.
Nine checks passed. One passed in part, one was set aside, and one could not be run. All three are described under “Known limitations” below.
Four faults were found and fixed the same day:
- Keyboard focus was lost when the mobile menu closed because the window widened — which is what happens when a phone is rotated with the menu open. Focus fell back to the top of the page instead of returning to the menu button.
- The “CASE STUDY” label on the home page was white text placed over whatever image had been uploaded behind it. Over a light image it was effectively invisible. It now has its own background and is readable regardless of the image.
- One colour used for code comments fell below the minimum contrast. It has been adjusted.
- Opening site search announced nothing to VoiceOver. Typing worked, but no feedback was spoken until the user tabbed away and back. The search panel now announces itself when it opens.
None of these would have been found by reviewing the code. Each one depended on how the page behaved in use — at a particular window width, with a particular uploaded image, or with a screen reader running.
Built after the August review
Five parts of the site were added after the August 2026 review. Four of them have now been through the screen reader testing described above: the expanding Services and Work menus, site search, the questions accordion, and the anti-spam check on both forms.
The recommended tools page has not been tested, because it has no published content yet. It is listed here rather than left out.
Known limitations
Only one screen reader has been used
All testing to date has been with VoiceOver. NVDA and JAWS — the screen readers most Windows users run — have not been used on this site at all.
Screen readers differ, and some of the patterns on this site are supported inconsistently between them. One specific question is open: the confirmation panel shown after sending a form is both announced automatically and given keyboard focus. VoiceOver reads it once, which is correct. Another screen reader may read it twice. That has not been checked.
Testing with NVDA is planned, and this page will be updated with the results.
The recommended tools page is untested
It has no published entries, so nothing on it — including the affiliate disclosure — has been read by a screen reader. An affiliate label that no screen reader reaches is not a disclosure, so this is recorded as a real gap rather than a formality.
The multi-step project request form does not announce which step you are on
Pressing “Next” moves keyboard focus correctly to the first field of the new step, and the step is labelled in the page. But VoiceOver does not read that label aloud when focus moves there, so the field is announced without the context around it.
The two available remedies each cost more than they return — one would make the form announce itself repeatedly while typing, the other would add a step everyone has to tab past. The behaviour is recorded here instead.
The forms require JavaScript
Both forms previously worked with JavaScript turned off. The anti-spam check added in September 2026 needs it, so they no longer do. Where JavaScript is unavailable the form is replaced by our email address, which reaches the same place — but it is a step backwards and is recorded here as one.
The site administration area has not been tested
This statement describes the public site. The WordPress administration area behind the login has not been tested with a screen reader. It has one user and is not public, but it is not covered by anything above.
Third-party content
Policy pages such as the Privacy Policy are supplied by a third-party service and embedded here.
The anti-spam check on the contact and project request forms is supplied by Cloudflare and runs inside the form itself. It has to be completed before a message can be sent, which makes it more consequential than an embedded page. It can be reached by keyboard, but it usually resolves without asking anything, so we have not been able to observe what happens when it does present a challenge. Whether that challenge can be completed by keyboard alone, or with a screen reader, is unverified.
In both cases the markup is outside our control and its accessibility has not been assessed by us. If either is a barrier for you, the email address below reaches the same place as the form.
Reporting a problem
If any part of this site is hard or impossible to use, please say so — it is treated as a bug, not a feature request. Email info@codegevity.com and describe what you were trying to do, which page you were on, and what got in the way. Mentioning the browser and any assistive technology you use helps, but is not required.
Replies land within one business day.
About this statement
This statement covers codegevity.com. It was prepared on 8 August 2026, following the review described above, and is based on a self-assessment carried out in-house rather than an independent audit.
It was last revised on 11 September 2026, after the screen reader testing described above.
It will be reviewed whenever the site changes materially, and revised as the limitations above are closed.