Accessibility statement

bumfuzzledjane.com should work with a keyboard, a screen reader, a magnifier, a phone held in bright sunlight, or a slow connection in a house that is currently a building site. Where it does not, that is a defect and we would like to hear about it.

The commitment

Accessibility is treated here as part of the build rather than a widget bolted on afterward. We use no accessibility overlay: overlays interfere with the assistive technology people have already configured to their liking, and they fix the audit rather than the site.

If something here keeps you from the information you came for, say so and you will get it by another route the same week. That offer does not depend on us agreeing it is a bug.

The standard we aim at

We target WCAG 2.2 Level AA, the version of the Web Content Accessibility Guidelines most commonly referenced in US practice. The site is built and hand-tested against it. It has not been independently audited or certified, and we would rather say so than imply an accreditation that does not exist.

What has been built in

• Semantic HTML. Headings in order, real lists and landmarks, one h1 per page, and a skip-to-content link as the first focusable element.
• Keyboard navigation. Every link, button, field and accordion works without a mouse, in a sensible order, with no traps. The FAQ accordions are native disclosure elements, so they behave the way your screen reader already expects.
• Visible focus. A two-pixel clay outline with three pixels of offset, never removed for the sake of appearances.
• Color contrast. Body text runs near-black on warm cream, comfortably past 4.5:1, with interface elements checked against 3:1. Color is never the only carrier of meaning.
• Descriptive alt text. Every photograph describes the actual room rather than repeating a file name. Decorative gradients are hidden from assistive technology.
• Reduced motion. With prefers-reduced-motion on, the scroll reveals and smooth scrolling switch off entirely rather than merely shorten.
• Text sizing and reflow. Type scales with your browser setting, pages reflow from 320 pixels up without horizontal scrolling, and nothing is lost at 200 percent zoom.
• Forms. Every field on the contact form has a real label, required fields are marked in text and in code, and nothing relies on placeholder text alone.
• Target size. Controls meet the 24 by 24 pixel minimum, and most buttons are considerably larger.

Where it currently falls short

Stated plainly, because a statement claiming perfection is not worth reading:

• Alt text on project photographs describes each room, but cannot convey everything a designer would notice standing in it. If a particular image matters, ask and we will describe it in writing.
• The consent checkbox on the contact form has a longer label than is ideal for magnifier users at high zoom.
• Typefaces load from a third-party font service, so a very slow connection shows a brief flash of fallback type.
• Video calling, scheduling and invoicing are third-party tools whose accessibility we do not control. If one is a barrier, say so and we will use a different route.
• Testing covers VoiceOver with Safari, NVDA with Firefox and keyboard-only use, not every possible combination.

Working with us if you have access needs

Deliverables are adapted at no extra charge, as a scheduling note rather than a negotiation. Regularly, we:

• issue plans and schedules as tagged, screen-reader-readable PDFs, or as plain-text and spreadsheet versions where a PDF is awkward
• set documents in 18 point or larger, with high-contrast versions of palettes and drawings
• turn on live captions for video calls, run the call by phone, or work entirely in writing
• split a 90-minute direction call into two 45-minute sessions, for the same fee
• mail physical paint and material samples rather than relying on on-screen color judgment, which is the better answer for a great many people regardless of vision
• write recaps as short numbered decisions instead of prose, and describe reference images aloud during a call

Mention what works for you in your first message and it becomes how your project runs. Scope for each engagement is on the services page.

Reporting a problem

Email hello@bumsfuzzledjane.com with “Accessibility” in the subject line, or call +1 (503) 555-0148. Include the page address, what you were trying to do, and the browser and assistive technology you were using.

We acknowledge every report within two working days and aim to fix it or give you a dated plan within ten. Either way the information you wanted reaches you immediately, by whatever route suits. The form is on the contact page, and the rest of the small print is in the privacy policy, the terms of service and the disclaimer.