How I am trying to make this site work for everyone, where I am still falling short, and how to tell me when something is broken for you.
The full statement is below. Here is the gist if you are short on time.
I want this site to work for everyone, including people who use assistive technology.
It aims for WCAG 2.1 Level AA. The formal audit is still in progress.
Some areas are not perfect yet. Known issues are listed openly below.
Hit a barrier? Tell me. I will fix it or offer an alternative way to access the content.
This statement is reviewed and updated when I make material accessibility changes.
I want this site to work for everyone, not just people who browse the way I do. Accessibility is part of professional craft. If something here is broken for you, that is my problem to fix, not yours to work around.
This statement covers victorijomah.com. The blog at blog.victorijomah.com runs on a separate system and is in its own review cycle (see Known issues below).
I take this seriously. If you report a problem and I cannot fix it immediately, I will find a way to give you the content in another form while I work on a proper fix.
This site aims to meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA . WCAG is the international standard for accessible web content, covering four core principles: content should be perceivable, operable, understandable, and robust.
I am not claiming full conformance yet. A formal third-party audit is still on the roadmap. What I am claiming is that I have built the site with these principles in mind from the start, and that I will keep narrowing the gap.
The following accessibility features are built in across the main pages:
Semantic HTML structure
Pages use proper landmark elements so screen readers can navigate sections easily.
Keyboard navigation
Every interactive element is reachable and operable using only a keyboard.
Sufficient colour contrast
Primary text meets or exceeds WCAG 2.1 Level AA contrast ratios against its background.
Descriptive labels
Icon-only buttons have ARIA labels. Form fields have visible labels. Images have alt text where they carry meaning.
Responsive across screen sizes
Layouts adapt from small phones to large desktops without horizontal scrolling or content loss.
Visible focus indicators
Tab focus is visually distinct so keyboard users always know where they are on the page.
Listing known issues openly is more useful than pretending the site is perfect. These are the gaps I am aware of right now.
Formal accessibility audit not yet complete
I have built with accessibility in mind, but a full third-party audit against WCAG 2.1 AA is still on the roadmap.
Some interactive widgets need testing
The calendar widget on the contact and hire pages, and any cookie banner once installed, have not been verified against a full range of assistive technology.
Animations and motion
Some hover and entrance animations do not yet respect the prefers-reduced-motion browser setting. Working on it.
Hosted blog at blog.victorijomah.com
The blog runs on a separate WordPress install. Its accessibility depends on the theme and plugins used there. I am reviewing those separately.
This list is not exhaustive. There are almost certainly issues I have not spotted yet, particularly ones that only appear with specific assistive technology setups. If you find one, please tell me.
The most useful way to flag an accessibility problem is by email. The link below opens a new message with a few prompts pre-filled to make it quick.
Please include, if you can:
If email is not convenient, message me on any of the social channels in the footer.
When you report an issue, you can expect:
If for some reason I cannot fix the underlying problem (for example, a third-party widget I do not control), I will say so plainly and we can talk about alternatives.
If a specific piece of content on this site is not accessible to you in its current form, ask and I will provide it in an alternative format wherever I reasonably can. That might mean:
This is the kind of thing where it is much easier to act on a specific request than to anticipate every need. Reach out and we will figure it out.
I review this statement when I make material changes to the site, when a formal audit completes, or at least once a year. The “Last updated” date at the top reflects the most recent revision.
If you want to know what specifically changed between versions, email me and I will tell you.