Accessibility Conformance Report
WCAG Edition — based on VPAT® 2.5
Name of Product/Version: multihousingdepot.com (public website), as at 8 September 2026 Report Date: 8 September 2026 Product Description: Public marketing and e-commerce website for Multi-Housing Depot, a supplier of cabinetry, countertops, appliances and related products to the multifamily housing industry. Contact Information: sales@gomhd.com · 800.253.3855 Notes: This report covers the ten pages listed under Scope below. It does not cover linked PDF documents, third-party content served in iframes, or pages outside that set. Evaluation Methods Used: See Evaluation Methods below.
Applicable Standards / Guidelines
| Standard / Guideline | Included in Report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A — Yes; Level AA — Yes |
| Web Content Accessibility Guidelines 2.1 | Level A — Yes; Level AA — Yes |
| Web Content Accessibility Guidelines 2.2 | Level A — Yes; Level AA — Yes |
Level AAA criteria are out of scope and are not reported.
WCAG 2.2 removed success criterion 4.1.1 Parsing. It is therefore not evaluated and does not appear in the tables below.
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports — the functionality of the product has at least one method that meets the criterion without known defects, or meets the criterion with equivalent facilitation.
- Partially Supports — some functionality of the product does not meet the criterion.
- Does Not Support — the majority of product functionality does not meet the criterion.
- Not Applicable — the criterion is not relevant to the product.
- Not Evaluated — the product has not been evaluated against the criterion.
Scope
Ten pages were evaluated, selected to cover each distinct page type:
Home · Products · Products › Cabinets · Request a Quote · Vanity Program · Insights · FAQ · About Us · Shop · My Account
Not covered by this report: individual product detail pages, the photo gallery, Careers, the WooCommerce cart and checkout flow beyond the account page, and any linked PDF documents. Where a criterion's rating depends on untested functionality, this is stated in the Remarks.
Evaluation Methods
Automated testing. axe-core 4.10.3, executed via Deque Systems' @axe-core/cli in headless Chrome, against the wcag2a, wcag2aa, wcag21aa and wcag22aa rule sets. All ten pages in scope. Result: 63 findings, all of them color-contrast; four pages returned no findings.
Manual testing. Keyboard-only walkthrough including tab order, skip link operation and both enquiry forms; verification that a focus indicator is present and visible on interactive controls; measurement of touch target sizes and centre-to-centre spacing at 390 px width; reflow at 320 px width; application of the WCAG text-spacing override; inspection of rendered markup for landmark, heading, table and form semantics; visual inspection of every image carrying an empty alt attribute to determine whether it is decorative.
Not yet performed. Screen reader testing with NVDA and VoiceOver, and submission testing of the enquiry forms to confirm error-message behaviour. Criteria whose rating depends on this are marked Partially Supports with the reason stated, rather than being claimed.
Table 1: Success Criteria, Level A
| Criterion | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | All informative images have text alternatives. Each image carrying an empty alt was inspected individually; those left empty are decorative (feature icons that sit directly above their own heading and body text, quotation marks, spacers) or are thumbnails whose adjacent titled link conveys the destination. Certification badges, partner logos and product photography are described. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | No prerecorded audio-only or video-only content is present on any page in scope. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | No prerecorded synchronised media is present. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | No prerecorded synchronised media is present. |
| 1.3.1 Info and Relationships | Supports | Each page exposes a single <main> landmark and one top-level heading. Form controls have programmatically associated labels, including the twelve quantity fields in the vanity order table. That table uses scope="col" headers and a caption. Post grids no longer apply invalid role="list" / role="listitem" to <article> elements. |
| 1.3.2 Meaningful Sequence | Supports | Reading order follows DOM order. Verified by keyboard traversal and by reflow at 320 px, where content order is preserved. |
| 1.3.3 Sensory Characteristics | Supports | No instructions rely on shape, size, visual location or sound alone. |
| 1.4.1 Use of Color | Supports | Links within blocks of running text, breadcrumbs and pagination are underlined in addition to being coloured. Confirmed on the cached page as served to visitors. |
| 1.4.2 Audio Control | Not Applicable | No audio plays automatically. |
| 2.1.1 Keyboard | Partially Supports | All content reached during keyboard testing was operable, and no keyboard traps were found. The desktop mega-menu submenus open on hover and their aria-controls references could not be resolved by automated tooling; keyboard operation of those submenus has not yet been confirmed with a screen reader. |
| 2.1.2 No Keyboard Trap | Supports | No traps found. Hidden dropdown containers are display: none, so no focusable content is stranded inside a hidden region. |
| 2.1.4 Character Key Shortcuts | Not Applicable | No single-character key shortcuts are implemented. |
| 2.2.1 Timing Adjustable | Not Applicable | No time limits are imposed on any process. |
| 2.2.2 Pause, Stop, Hide | Supports | The homepage slideshow advances automatically and provides a persistent pause/play control, positioned before the slides in the keyboard order. It also pauses automatically when keyboard focus enters the carousel, and starts paused when the operating system requests reduced motion. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No flashing content. |
| 2.4.1 Bypass Blocks | Supports | A "Skip to content" link is the first focusable element on every page and moves focus to the <main> landmark. Previously the link target did not exist; this was corrected. |
| 2.4.2 Page Titled | Supports | Every page in scope has a unique, descriptive <title>. |
| 2.4.3 Focus Order | Supports | Focus order follows a logical sequence. Anti-spam decoy fields that previously carried tabindex="1000" and preceded all real content in the tab order are now removed from the tab order and from the accessibility tree. |
| 2.4.4 Link Purpose (In Context) | Supports | Link text, or its immediate context, describes the destination. Empty thumbnail links adjacent to a titled link to the same destination are hidden from assistive technology to avoid duplicate unnamed links. |
| 2.5.1 Pointer Gestures | Supports | No path-based or multipoint gestures are required. Carousels expose previous/next controls. |
| 2.5.2 Pointer Cancellation | Supports | No functionality is triggered on down-event. |
| 2.5.3 Label in Name | Supports | Accessible names contain the visible label text for controls inspected. |
| 2.5.4 Motion Actuation | Not Applicable | No functionality is operated by device or user motion. |
| 3.1.1 Language of Page | Supports | Every page declares lang="en-US". |
| 3.2.1 On Focus | Supports | Receiving focus does not initiate a change of context. |
| 3.2.2 On Input | Supports | Changing a form control value does not automatically submit or change context. |
| 3.2.6 Consistent Help | Supports | The "Contact Us" control appears in the same relative position within the header on every page. |
| 3.3.1 Error Identification | Partially Supports | Both enquiry forms output a live region (role="status", aria-live="polite") for validation messages, and invalid fields are marked aria-invalid. Per-field association between an error message and its control has not been confirmed by submitting the forms; this is scheduled with the screen reader testing. |
| 3.3.2 Labels or Instructions | Supports | Every user input has a visible or programmatically associated label. |
| 3.3.7 Redundant Entry | Supports | No process re-requests information already provided in the same session. |
| 4.1.2 Name, Role, Value | Partially Supports | Site controls expose correct name, role and value; the previously unnamed quantity fields and post-thumbnail links were corrected. The third-party cookie consent banner presents as a blocking overlay without role="dialog", aria-modal or an accessible name. Accessible names have been supplied for its category toggles; the dialog semantics remain outstanding with the plugin vendor. |
Table 2: Success Criteria, Level AA
| Criterion | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | No live synchronised media. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | No prerecorded synchronised media. |
| 1.3.4 Orientation | Supports | Content is not restricted to a single display orientation. |
| 1.3.5 Identify Input Purpose | Supports | Fields collecting information about the user carry the appropriate autocomplete tokens (name, email, tel, organization, street-address, address-line2, address-level1, address-level2, postal-code). |
| 1.4.3 Contrast (Minimum) | Partially Supports | Most text meets the 4.5:1 minimum. Text and controls that combine the brand blue #1CA9E1 with white — and, in a small number of cases, brand blue on light grey — fall below it. 63 instances across the pages in scope. A revised approach to how the brand colours are combined is in progress; the two existing brand colours meet the requirement against one another. |
| 1.4.4 Resize Text | Supports | Content and functionality remain available when text is enlarged. Verified indirectly by the reflow test at 320 px CSS width, which is a more demanding condition than 200 % text resize, with no loss of content or functionality. |
| 1.4.5 Images of Text | Partially Supports | Body content uses real text. A small number of promotional graphics render text as part of the image — most notably a homepage badge reading "Up to $500 savings". These now carry text alternatives conveying the same information, but the text itself is not resizable or restyleable by the user. Logotypes are exempt under this criterion. |
| 1.4.10 Reflow | Supports | No horizontal scrolling or content loss at 320 px CSS width on any page in scope. |
| 1.4.11 Non-text Contrast | Partially Supports | Focus indicators and most interface boundaries meet 3:1. Some brand-blue interface elements against white do not. Same root cause as 1.4.3 and addressed by the same work. |
| 1.4.12 Text Spacing | Supports | With line height 1.5×, paragraph spacing 2×, letter spacing 0.12em and word spacing 0.16em applied, no content is clipped, overlapped or lost. |
| 1.4.13 Content on Hover or Focus | Partially Supports | Desktop navigation submenus appear on hover. Whether they are dismissible, hoverable and persistent as required has not been fully verified; this is scheduled with the screen reader testing. |
| 2.4.5 Multiple Ways | Supports | More than one route to content: site navigation menus and a search facility. |
| 2.4.6 Headings and Labels | Supports | Headings and labels describe their topic or purpose. Pages that previously had no <h1>, or two, now have exactly one. |
| 2.4.7 Focus Visible | Supports | A consistent focus indicator is applied site-wide: a three-pixel outline with an offset and a contrasting inner band, so that it remains visible on light, navy and brand-blue surfaces. Previously several controls showed no visible focus change. |
| 2.4.11 Focus Not Obscured (Minimum) | Partially Supports | Focused controls are not obscured by site content. While the cookie consent banner is displayed, it can cover a focused element in the lower portion of the viewport. The banner is third-party and is being addressed with the vendor. |
| 2.5.7 Dragging Movements | Supports | No functionality requires a dragging movement; carousels provide button alternatives. |
| 2.5.8 Target Size (Minimum) | Supports | Interactive targets meet the 24 × 24 CSS pixel minimum, or the spacing exception. Carousel pagination controls and the account page's password-reveal control were enlarged to meet it. |
| 3.1.2 Language of Parts | Not Applicable | No passages occur in a language other than the page language. |
| 3.2.3 Consistent Navigation | Supports | Navigation is presented in the same relative order on every page. |
| 3.2.4 Consistent Identification | Supports | Components with the same function are identified consistently. |
| 3.3.3 Error Suggestion | Partially Supports | Validation messages describe the problem and, for format errors, the expected format. As with 3.3.1, per-field behaviour has not been confirmed by submitting the forms. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Partially Supports | The vanity order form is an enquiry rather than a completed financial transaction, and submissions are reversible by contacting the company. The WooCommerce checkout flow, which does involve a financial commitment, is outside the scope of this report and has not been evaluated against this criterion. |
| 3.3.8 Accessible Authentication (Minimum) | Supports | The account login accepts pasted credentials, supports password managers via autocomplete="current-password", and imposes no cognitive function test. |
| 4.1.3 Status Messages | Supports | Form status and validation messages are exposed through a live region (role="status", aria-live="polite", aria-atomic="true") without moving focus. |
Summary
Across the 55 Level A and AA success criteria evaluated (31 at Level A, 24 at Level AA):
| Rating | Count |
|---|---|
| Supports | 35 |
| Partially Supports | 10 |
| Does Not Support | 0 |
| Not Applicable | 10 |
No criterion fails outright. Every Partially Supports rating traces to one of four causes:
- Colour contrast involving the brand palette — 1.4.3, 1.4.5, 1.4.11.
Remediation in progress. The two existing brand colours meet the contrast requirement against one another, so this is a question of how they are combined rather than of replacing them.
- The third-party cookie consent banner — 2.4.11, 4.1.2. Being addressed
with the plugin vendor.
- Behaviour not yet confirmed by screen reader or form-submission testing —
2.1.1, 1.4.13, 3.3.1, 3.3.3. Testing is scheduled. These are reported as unconfirmed rather than claimed as conforming.
- Functionality outside the evaluated scope — 3.3.4, where the WooCommerce
checkout flow has not been evaluated.
Legal Disclaimer
This report represents Multi-Housing Depot's good-faith assessment of the accessibility of the pages listed under Scope, using the methods described under Evaluation Methods, as at the report date. It is a statement of conformance made by the organisation; it is not a certification, and no certification of WCAG conformance exists or is issued by any body. Automated testing tools detect a subset of accessibility barriers and cannot establish conformance on their own, which is why manual evaluation is included and why criteria dependent on unfinished testing are marked as only partially supported.
Website content changes over time. This report will be reviewed and reissued when significant changes are made, and in any event no less than annually.