Accessibility Remediation Report
A complete record of what was tested, what was found, and what was changed.
This page accompanies our Accessibility Statement. The statement describes our commitment and how to reach us; this page is the detailed engineering record behind it. It is published openly because a claim of accessibility is only as good as the evidence supporting it.
1. What was tested
Public pages: the homepage (including the contact form and eight product dialogs), the products page, the client login page, and the accessibility pages.
Client area (added 11 August 2026): the client landing page, the diamond inventory listing and the reserved-diamonds page — all three now audited and corrected.
Not covered: the third-party product catalogue embedded on the products page, which is not under our control. See section 6.
2. How it was tested
- Automated structural analysis of every page against Level A and AA success criteria.
- Arithmetic contrast measurement of every colour pairing in the site's stylesheets, calculated rather than judged by eye.
- Manual source review for malformed elements, placeholder-as-label patterns, and dead controls.
- Rendered visual comparison of every changed page against its pre-remediation version, to confirm corrections introduced no visual regressions.
- Live browser testing driving a real browser: walking the actual keyboard tab order, confirming the focus indicator renders on real keyboard focus, checking no focused element is hidden behind the fixed header, measuring rendered target sizes, and reading the accessibility tree the browser hands to screen readers.
- Mobile and reflow testing at a 320-pixel viewport, verifying no page requires horizontal scrolling.
Keyboard operation, focus behaviour, target sizes, mobile reflow and the browser's accessibility tree were all tested in a real browser. However, this audit did not include listening to the site with screen-reader software (JAWS, NVDA, VoiceOver) or testing with disabled users. Verifying the accessibility tree confirms the information screen readers receive is correct, but it does not prove the resulting experience is a good one. Those methods find issues this approach cannot, and remain our recommended next step. We state this plainly rather than imply a level of verification we have not performed.
3. Corrections applied
Keyboard access
| Criterion | Problem | Correction | Status |
|---|---|---|---|
| 2.4.7 | No visible focus indicator anywhere on the site. The stylesheets removed the browser's focus outline from every link and button without replacing it, so keyboard users could not see what they had selected. | High-visibility focus ring restored site-wide, with a contrasting halo so it remains visible on light, gold and dark backgrounds. | Fixed |
| 2.1.1 | Product dialogs could not be closed with a keyboard — the close control was a plain container element with no keyboard support. | Converted to real buttons with accessible names. | Fixed |
| 2.4.1 | No way to skip past the navigation menu, forcing keyboard users through every menu item on every page. | "Skip to main content" link added, with a proper main content landmark as its target. | Fixed |
| 2.4.4 | Dead links occupied the keyboard tab order — four links that led nowhere, plus empty navigation anchors. | Dead links removed; structural-only anchors hidden from assistive technology and the tab order. | Fixed |
| 2.4.11 | New in WCAG 2.2. The fixed navigation bar could completely cover an element that had just received keyboard focus, hiding it from view. | Scroll offset reserved on all focusable elements so focus always lands below the bar. | Fixed |
Vision and contrast
| Criterion | Problem | Correction | Status |
|---|---|---|---|
| 1.4.3 | Every interactive colour failed the minimum contrast ratio. Link text measured 1.46:1 against a required 4.5:1; button labels the same; helper text and error text also failed. | Link colour darkened and button labels flipped to near-black. The brand gold is retained as a background, where it passes comfortably. Full measurements in section 4. | Fixed |
| 1.4.1 | Links were distinguished from body text by colour alone, invisible to users with colour blindness. | Body links underlined. | Fixed |
| 1.4.10 1.4.12 | No protection against content being clipped when users zoom or increase text spacing. | Reflow and text-spacing safeguards added. | Fixed |
Screen reader access
| Criterion | Problem | Correction | Status |
|---|---|---|---|
| 1.1.1 | Informative images — staff and customer photographs — had no alternative text, so their content was unavailable to screen reader users. | Descriptive alternative text added. Genuinely decorative images explicitly marked as decorative so they are skipped deliberately rather than by accident. | Fixed |
| 2.4.4 4.1.2 | Eight product tiles were links with no name — a screen reader announced eight consecutive "link" items with no indication of where each led. Social media links had the same problem. | Descriptive names supplied to every link. | Fixed |
| 4.1.2 | The contact and login submit buttons were built from malformed markup and carried no name. The login button had no label at all. | Rebuilt as valid buttons labelled "Send Message" and "Log In". | Fixed |
| 1.3.1 2.4.6 | No page had a top-level heading, and the heading outline began part-way down the hierarchy — breaking the heading navigation screen reader users rely on. | A single top-level heading added per page and heading order corrected. | Fixed |
| 4.1.2 | The embedded product catalogue had no title, so its contents were unidentifiable before entering it. | Descriptive frame title added. | Fixed |
Forms
| Criterion | Problem | Correction | Status |
|---|---|---|---|
| 1.3.1 3.3.2 | All six form fields relied on placeholder text instead of labels. Placeholders disappear as soon as you type and are inconsistently announced, so users could not confirm what a field wanted or check what they had entered. | Proper labels bound to every field, plus autofill hints. The visual design is unchanged. | Fixed |
| 3.3.1 4.1.3 | Success and error messages appeared visually with no announcement to assistive technology — a blind user submitting the contact form received no confirmation it had worked. | Status messages now announced automatically without stealing keyboard focus. | Fixed |
| 3.3.8 | New in WCAG 2.2. Authentication must not require memorisation or puzzle-solving, which means login fields must work with password managers. | Login fields marked for password manager and autofill support. No CAPTCHA is present on the login form. | Fixed |
Motion, targets and reliability
| Criterion | Problem | Correction | Status |
|---|---|---|---|
| 2.3.3 2.2.2 | Page animations ran regardless of the user's system preference, a problem for people with vestibular disorders. | Animation now honours the operating system "reduce motion" setting. | Fixed |
| 2.5.8 | New in WCAG 2.2. Interactive targets must be at least 24×24 pixels. Icon-only social links were roughly 14 pixels. | Raised to 44×44; minimum size floors applied to all controls. | Fixed |
| 3.3.1 2.4.6 | The contact page returned a server error to anyone who reached it directly from a bookmark, search result or shared link — a dead end with no navigation and no explanation. | Corrected; the page now returns visitors to the contact form. | Fixed |
| — | Five insecure resources were being blocked by browsers, producing errors on every page load. | Dead and duplicate resources removed; the remaining one secured. | Fixed |
Client area (added 11 August 2026)
| Criterion | Problem | Correction | Status |
|---|---|---|---|
| — | Clients with an expired session hit a dead end. Anyone whose login had lapsed, or who followed a bookmark into the client area, was redirected to a page that did not exist and received a bare "not found" error with no navigation and no way to sign back in. | Login redirect corrected; users are now returned to the login page and then on to the page they originally requested. | Fixed |
| 1.3.1 | The diamond inventory tables had column headings that were not programmatically linked to their columns, and no description. A screen reader read the figures without saying which column each belonged to. | Headings associated with their columns; both tables given descriptive captions. | Fixed |
| 2.4.4 1.1.1 | All ten diamond shape tiles were links with no name. | Each now names its shape. | Fixed |
| 1.3.1 3.3.2 | The enquiry form on the client pages repeated the placeholder-instead-of-label problem, and its submit button carried no name. | Real labels added; submit button rebuilt and named. | Fixed |
| 2.4.7 2.4.1 1.3.1 | The client pages lacked the focus indicator, skip link, landmarks and headings already added to the public pages. | All applied. | Fixed |
Verified in a live browser
| Test | What was checked | Result |
|---|---|---|
| Keyboard focus | Real keyboard navigation across every page; confirmed the focus indicator actually renders. | Pass Visible ring on every stop. |
| Focus not hidden | Whether the fixed header ever covers the focused element. | Pass No page, no viewport. |
| Accessibility tree | The names and roles the browser passes to screen readers. | Pass No unnamed elements on any page. |
| Target sizes | Rendered size of every control. | Pass Footer links were 18px tall and were corrected. |
| Mobile reflow | Every page at a 320-pixel viewport. | Pass No horizontal scrolling anywhere. |
4. Contrast, measured
Level AA requires a ratio of at least 4.5:1 for normal text. Every pairing below failed before this work.
| Element | Before | After | Result |
|---|---|---|---|
| Links | 1.46:1 | 5.02:1 | Pass |
| Link hover & focus | 1.59:1 | 7.34:1 | Pass |
| Button labels | 1.46:1 | 11.92:1 | Pass |
| Helper text | 4.48:1 | 5.02:1 | Pass |
| Error text | 3.82:1 | 5.62:1 | Pass |
5. Criteria that do not apply
Recorded so the absence of a finding is not mistaken for an oversight:
| Criterion | Why it does not apply |
|---|---|
| 1.2.1 – 1.2.5 | The site contains no audio or video, so captions, transcripts and audio description are not required. N/A |
| 2.5.7 | No drag-and-drop interaction exists anywhere on the site. N/A |
| 3.3.7 | No process asks a user for the same information twice. N/A |
| 2.2.1 | No session or interaction is under a time limit. N/A |
| 2.3.1 | No content flashes. N/A |
| — | No PDFs or downloadable documents are published, so document accessibility is not in scope. N/A |
6. What is still outstanding
Listed openly. A report claiming nothing is left undone invites exactly one question, and answers it badly.
| Item | Detail | Status |
|---|---|---|
| Client login area | Audited and corrected on 11 August 2026. Because these pages require a login, corrections were verified against the page templates and the shared stylesheet rather than by signing in as a client. | Resolved |
| Screen-reader listening test | Keyboard operation and the browser accessibility tree are now verified in a live browser. Listening to the site with JAWS, NVDA or VoiceOver, and testing with disabled users, has still not been done and remains the highest-value next step. | Open |
| Product catalogue | Operated by a third-party vendor whose code we cannot modify. We tested it on 11 August 2026 and identified specific failures — a missing page language setting, an unnamed search button, an unlabelled form field and no way to skip repeated content — and have put these to the vendor in writing with a request for their conformance report and a remediation timeline. An accessible alternative route to the same information (telephone, email, in person) is published directly beneath the catalogue. | Mitigated & escalated |
| Contact form security check | The CAPTCHA guarding our contact form offers an audio alternative, but remains difficult for some users. Direct email and telephone alternatives are published on our accessibility statement. | Mitigated |
| Mobile testing | Every page verified at a 320-pixel viewport with no horizontal scrolling. Testing on physical handsets is still outstanding. | Largely resolved |
Please tell us — we treat accessibility problems as faults to be fixed. Email caryhud@aol.com or use our contact form. We aim to respond within five business days, and if you need information from this site that you cannot access, we will provide it directly in a format that works for you at no charge.
Report published 11 August 2026 by Websites By Daniel LLC. Standard applied: Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. This report describes technical conformance work and is not a legal certification. · Accessibility Statement · Return to homepage