Accessibility Conformance Report
About this report
| Name of product and version | The cRUD Company website (thecrudcompany.com), as built on 17 October 2026: 52 canonical public pages and the 404 page. |
|---|---|
| Report date | 17 October 2026 |
| Product description | The public website of The cRUD Company: the homepage, About cRUD, Partnerships, Careers and Contact; the Overview, Workflow, Approach, Solutions and Documentation pages for cRUD Webinar, cRUD Collab and cRUD Morph; Curious cRUD with its blog, whitepapers and author pages; the Trust Center and its ten policies; the Accessibility Statement, this report and the HTML sitemap. |
| Contact information | hello@thecrudcompany.com |
| Notes | This report covers this website only. It does not cover the cRUD Webinar or cRUD Collab applications, the crudwebinar.com and crudcollab.com websites, or software that integrates cRUD Morph. The contact form sends messages to a form-handling service that has no user interface of its own. |
| Evaluation methods used | Self-assessment by The cRUD Company; not an independent third-party audit or certification. Methods are listed in the next section. |
Evaluation methods used
- Self-assessment by The cRUD Company on 17 October 2026, on the build of that date: the 52 canonical public pages listed in sitemap.xml, and the 404 page separately. Each Trust Center policy is also served at a second address with a trailing slash; those copies are identical and are not counted twice.
- Automated testing with axe-core 4.12.1, WCAG 2.0, 2.1 and 2.2 Level A and AA rules and best-practice rules, on every page at 1440 and 390 CSS pixels, with reduced motion so that animated elements were at rest.
- Text contrast measured from rendered pixels for the 26 places where axe could not decide, and focus ring contrast measured on representative pages and from pixels on dark and image backgrounds.
- Scripted keyboard traversal in Chrome of every page with the first-visit cookie banner open at 1440, 1024, 768, 390 and 320 CSS pixels, and with a cookie choice made at 1440 and 390 CSS pixels: first focus stop, a visible change at every stop, focus visible state, focus hidden behind other content, keyboard traps and console errors.
- Landmarks and heading structure on every page at 1440, 1024, 768, 390 and 320 CSS pixels: one main region, consistently grouped repeated navigation and headings beginning at H1 without skipped levels.
- Reflow at 320 and 640 CSS pixels and at a landscape phone size, WCAG text spacing on every page at 1440, 1024, 768, 390 and 320 CSS pixels, and an inventory of running animation with and without reduced motion, including what is still running five seconds after each page loads.
- The cookie banner: with no choice saved, every footer link focused in turn at 1440, 1024, 768, 390 and 320 CSS pixels; then each choice made and Cookie settings reopened, without changing the stored choice values.
- The 404 page: its story played to the end without the page leaving, and its Pause activity control operated by keyboard three times in a row, with and without reduced motion.
- Keyboard operation of the Products menu, mobile menu, site search and its announcements, the Ctrl or Cmd plus K shortcut, FAQs, the About page rows, the product section row and the resource filter.
- The contact form: labels, required fields, autocomplete purposes, hints and error messages, checked by moving through the fields. The form was not sent.
- Target size, label in name, landmarks and heading order on every page at 390 CSS pixels.
- No screen reader software was used for this report.
Applicable standards and guidelines
| Standard or guideline | Included in report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A (Yes) · Level AA (Yes) · Level AAA (No) |
| Web Content Accessibility Guidelines 2.1 | Level A (Yes) · Level AA (Yes) · Level AAA (No) |
| Web Content Accessibility Guidelines 2.2 | Level A (Yes) · Level AA (Yes) · Level AAA (No) |
Terms
| Supports | The functionality of the product has at least one method that meets the criterion without known defects or meets 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. Used only for WCAG Level AAA. |
Summary
Of 56 Level A and AA success criteria in WCAG 2.2 (with 4.1.1 reported for WCAG 2.0 and 2.1), 47 Supports, 0 Partially Supports, 0 Does Not Support and 9 Not Applicable.
Table 1. Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) | Supports | Every image has a text alternative or is marked decorative: product illustrations are described, logos are named, and decorative icons, artwork and the closing-block watermark are hidden from assistive technology. axe reported no image or alternative-text failures on any page. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Not Applicable | The website contains no prerecorded audio-only or video-only content. |
| 1.2.2 Captions (Prerecorded) (Level A) | Not Applicable | The website contains no prerecorded video with audio. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Not Applicable | The website contains no prerecorded synchronised media. |
| 1.3.1 Info and Relationships (Level A) | Supports | Every page has one banner, one main region and one content information region, and its headings start at H1 with no skipped levels. Lists, data tables with header cells and labelled form fields are marked up. The closing call-to-action block sits after the main region with its own heading. |
| 1.3.2 Meaningful Sequence (Level A) | Supports | Reading and focus order follow the visual order on every page at desktop and phone widths. |
| 1.3.3 Sensory Characteristics (Level A) | Supports | Instructions do not rely on shape, size, position or sound. |
| 1.4.1 Use of Color (Level A) | Supports | Links in running text are underlined. Contact form errors are shown in words as well as colour. |
| 1.4.2 Audio Control (Level A) | Not Applicable | No audio plays automatically. |
| 2.1.1 Keyboard (Level A) | Supports | The Products menu, mobile menu, site search, FAQs, the About page rows, the product section row, the resource filters, shelves and the contact form all work with the keyboard; each was operated by keyboard in this evaluation. |
| 2.1.2 No Keyboard Trap (Level A) | Supports | A Tab walk through every page at desktop and phone widths always reached the end of the page; menus and search close with Escape and return focus to their button. |
| 2.1.4 Character Key Shortcuts (Level A · WCAG 2.1) | Supports | Search opens with Ctrl+K or Cmd+K only. The contact topic list answers typed letters only while it has focus. |
| 2.2.1 Timing Adjustable (Level A) | Supports | No time limits are set on any page. The 404 page plays a short story and then stays where it is, with a link back to the homepage; it never leaves the page by itself. |
| 2.2.2 Pause, Stop, Hide (Level A) | Supports | Decorative animation (the hero particles on the homepage and product overviews, the cRUD Morph hero sheen, the 404 page edge pulses and other small looping details) stops within five seconds of the page loading. The auto-playing 404 story has a Pause activity control that pauses it and resumes it where it left off; nothing new appears while it is paused. All motion also stops when the visitor turns on the reduced motion setting of their operating system. |
| 2.3.1 Three Flashes or Below Threshold (Level A) | Supports | Nothing flashes more than three times in any one second. |
| 2.4.1 Bypass Blocks (Level A) | Supports | Each page uses a single main region, consistent landmarks and a clear heading structure. These mechanisms allow assistive technology to bypass repeated navigation and move directly to the page content. They were checked on every page at desktop and phone widths. |
| 2.4.2 Page Titled (Level A) | Supports | Every page has a unique, descriptive title. |
| 2.4.3 Focus Order (Level A) | Supports | Focus order is logical on every page; closed menus, search and filters are out of the tab order. |
| 2.4.4 Link Purpose (In Context) (Level A) | Supports | Link text, or text with its context, describes the destination; links that open a new tab say so. |
| 2.5.1 Pointer Gestures (Level A · WCAG 2.1) | Supports | Shelves that can be dragged or swiped also have previous and next buttons and scroll normally. No function needs a path-based gesture. |
| 2.5.2 Pointer Cancellation (Level A · WCAG 2.1) | Supports | Actions run on release (a standard click), not on press. |
| 2.5.3 Label in Name (Level A · WCAG 2.1) | Supports | Accessible names contain the visible label; contact desk links begin with their visible label. The Follow on LinkedIn button on the cRUD Research Team page was corrected during this evaluation. |
| 2.5.4 Motion Actuation (Level A · WCAG 2.1) | Not Applicable | No function is triggered by device motion. |
| 3.1.1 Language of Page (Level A) | Supports | Every page declares lang="en-GB". |
| 3.2.1 On Focus (Level A) | Supports | Receiving focus does not change context. |
| 3.2.2 On Input (Level A) | Supports | Changing a control (the contact topic, the resource filters) updates content in place without a change of context. |
| 3.2.6 Consistent Help (Level A · WCAG 2.2) | Supports | The Contact us button appears in the same place in the header of every page, and the footer carries the same contact and policy links in the same order. |
| 3.3.1 Error Identification (Level A) | Supports | A field left empty or invalid shows a written message linked to the field and is marked invalid; the message clears when the entry is corrected. Checked on the contact form without sending it. |
| 3.3.2 Labels or Instructions (Level A) | Supports | All form fields have visible labels; required fields are marked, and the email format and minimum message length are stated. |
| 3.3.7 Redundant Entry (Level A · WCAG 2.2) | Not Applicable | There is no multi-step process that asks for the same information twice. |
| 4.1.1 Parsing (Level A) | Supports | For WCAG 2.0 and 2.1 this criterion is always satisfied for HTML under the W3C errata. It is obsolete and removed in WCAG 2.2. |
| 4.1.2 Name, Role, Value (Level A) | Supports | Buttons, menus, disclosure widgets, filters and form fields expose name, role and state; axe reported no name, role or value failures, and menu and row states were checked by keyboard. |
Table 2. Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Not Applicable | The website has no live audio or video. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Not Applicable | The website contains no prerecorded video. |
| 1.3.4 Orientation (Level AA · WCAG 2.1) | Supports | Content works in portrait and landscape; a landscape phone width showed no loss of content or sideways scrolling. |
| 1.3.5 Identify Input Purpose (Level AA · WCAG 2.1) | Supports | The name and email fields declare their autocomplete purposes. |
| 1.4.3 Contrast (Minimum) (Level AA) | Supports | Text meets 4.5:1 (3:1 for large text). axe reported no text contrast failure apart from the large decorative "cRUD" watermark in the closing block, which is exempt. The 26 places where axe could not decide (text over gradients, images and decorative underlines) were measured from rendered pixels and all pass. |
| 1.4.4 Resize Text (Level AA) | Supports | Text resizes to 200% with browser zoom without loss of content; at 640 CSS pixels, the width of a 1280-pixel window at 200%, no page scrolls sideways. |
| 1.4.5 Images of Text (Level AA) | Supports | Images of text are limited to logos and product illustrations whose text is part of the interface they depict; each illustration is described in text. |
| 1.4.10 Reflow (Level AA · WCAG 2.1) | Supports | Every page reflows at 320 CSS pixels without scrolling in two directions; data tables scroll within their own region. |
| 1.4.11 Non-text Contrast (Level AA · WCAG 2.1) | Supports | Form field borders reach 3.6:1. The focus ring is solid Mineral Teal (5.4:1 or more on light grounds) or the lighter on-dark teal on dark grounds (8.9:1 or more); buttons and floating controls carry a two-tone ring so one tone always contrasts with what is beside it. Set during this evaluation. |
| 1.4.12 Text Spacing (Level AA · WCAG 2.1) | Supports | With WCAG text spacing applied at 1440, 1024, 768, 390 and 320 CSS pixels, no text is cut off and no page scrolls sideways. Resource card titles, the current item in the breadcrumb and the section titles in the legal "On this page" lists wrap onto further lines rather than being cut off. |
| 1.4.13 Content on Hover or Focus (Level AA · WCAG 2.1) | Supports | The Products menu and the search results stay open while hovered or focused and close with Escape. |
| 2.4.5 Multiple Ways (Level AA) | Supports | Every page can be reached from the navigation, the site search on every page and the HTML sitemap. |
| 2.4.6 Headings and Labels (Level AA) | Supports | Headings and labels describe their topic or purpose. |
| 2.4.7 Focus Visible (Level AA) | Supports | Every focus stop on every page, at desktop and phone widths, shows a visible focus indicator. Buttons previously showed none; fixed during this evaluation. |
| 2.4.11 Focus Not Obscured (Minimum) (Level AA · WCAG 2.2) | Supports | No focused element is hidden on any page at 1440, 1024, 768, 390 or 320 CSS pixels while the first-visit cookie banner is open, or at 1440 and 390 CSS pixels after a choice. While the banner is open, the page keeps clear space at its foot equal to the banner's height, so the last links on a page, such as the footer policy links, scroll clear of it when they receive focus. The space is removed once a choice is made and returns if Cookie settings is reopened. At 320 CSS pixels the open banner fills most of a short window, so a focused element taller than the space left, such as a scrollable table, is partly covered but stays in view. |
| 2.5.7 Dragging Movements (Level AA · WCAG 2.2) | Supports | Anything that can be dragged also has single-pointer previous and next buttons. |
| 2.5.8 Target Size (Minimum) (Level AA · WCAG 2.2) | Supports | Targets are at least 24 by 24 CSS pixels or have enough space around them. The consent checkbox on the contact form is smaller, but its whole label is a larger target for the same action; links inside sentences are exempt. |
| 3.1.2 Language of Parts (Level AA) | Supports | Content is in English; there are no passages in other languages. |
| 3.2.3 Consistent Navigation (Level AA) | Supports | The shared header and footer remain in the same relative order on every page. Product navigation remains in the same relative order across the pages where it appears. |
| 3.2.4 Consistent Identification (Level AA) | Supports | Components with the same function have the same names across pages. |
| 3.3.3 Error Suggestion (Level AA) | Supports | Error messages say how to fix the field, for example the email address format or the minimum message length. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Supports | The website takes no purchases or payments. The contact form, which includes agreement to the Terms of Service, checks every field and lets the visitor correct it before anything is sent. |
| 3.3.8 Accessible Authentication (Minimum) (Level AA · WCAG 2.2) | Not Applicable | The website has no sign-in. |
| 4.1.3 Status Messages (Level AA · WCAG 2.1) | Supports | Search result counts and the resource filter counts are announced without moving focus, through status regions. |
Table 3. Success Criteria, Level AAA
Level AAA was not evaluated.
Issues fixed during this evaluation
| Issue | WCAG | Fix |
|---|---|---|
| Buttons showed no visible keyboard focus, because their own shadows replaced the focus ring | 2.4.7 | Every button carries a two-tone focus ring that no variant, hover or pressed state can remove. |
| The shared focus ring was translucent, at 1.4:1 to 1.8:1 against the page | 1.4.11 | The ring is solid Mineral Teal, the lighter on-dark teal on dark bands, and two-tone on the floating Summarise with AI and Back to top controls. |
| The Follow on LinkedIn button's name did not contain its visible label | 2.5.3 | The name now begins with "Follow on LinkedIn". |
| The 404 page returned to the homepage after a five-second countdown, with no option to stay | 2.2.1 | The page stays where it is at the end of the story, with its link back to the homepage, and never leaves by itself. |
| Looping decorative animation and the auto-playing 404 story had no way to pause them | 2.2.2 | Decorative loops stop within five seconds of the page loading, and the 404 story has a Pause activity control. |
| With text spacing increased, card titles, the current breadcrumb item and legal "On this page" labels were cut off with an ellipsis, and at the narrowest widths some button labels and one long policy heading ran out of their space | 1.4.12 | They wrap onto further lines; the breadcrumb moves into the page when the space beside the header is too narrow to show it in full. |
| Until a cookie choice was made, the cookie banner could cover the last links on a page when they received focus | 2.4.11 | While the banner is open the page keeps clear space at its foot equal to the banner's height; the Back to top control and the sticky contents lists also stay clear of it. |
| On the homepage between tablet and small laptop widths, the FAQ topic selector hid its last topic past its edge, where it could not be seen when focused | 2.4.11 | The topics wrap onto a second row whenever they do not fit. |
Known limitations and next checks
- No screen reader software was used; names, roles and states were verified programmatically and by keyboard. A screen reader pass (NVDA or VoiceOver) is the next check.
- Best practice, not a WCAG failure: the closing call-to-action block sits outside the page landmarks, and the 404 page has two landmarks with the same name.
- Separate reports are needed for the cRUD Webinar and cRUD Collab applications; this report covers the website only.
Legal disclaimer
This report describes the accessibility of the website as built on the report date, as assessed by The cRUD Company. It is provided for information and is not a warranty or a certification. Content and conformance may change as the website changes; this report will be updated when they do.
VPAT® is a registered service mark of the Information Technology Industry Council (ITI). This report follows the structure of the VPAT® Version 2.5Rev WCAG edition.
Report a barrier to hello@thecrudcompany.com.
This page is published by CRUD INFOSYSTEMS PRIVATE LIMITED, Unit 101, Oxford Towers, 139 HAL Old Airport Road, Kodihalli, Bengaluru, Karnataka 560008, India.
Return to the Accessibility statement or the Trust Center.