Accessibility

Our commitment

Molded By Grace Business Group builds this website so that it can be used by people who navigate with a keyboard, listen with a screen reader, magnify the page, override its colours or its text spacing, or read it on a small screen. That is not a feature we added; it is part of what we mean when we say the work has to be done properly.

We treat an accessibility problem the same way we treat any other defect. If something here does not work for you, it is our fault and we want to know.

Our technical target

This website has been designed and tested with WCAG 2.2 Level AA as its accessibility target.

We do not claim to be certified, guaranteed compliant, fully accessible, or compliant with the law of every jurisdiction. No website can honestly claim those things, and a claim we cannot support is worth less than a defect we are open about. What we can tell you is what we aimed at, what we tested, what passed, and what is still open.

What we have done

• A skip link is the first thing keyboard focus reaches on every page, and it moves focus to the main content.
• Every page has one main heading, one banner landmark, one main landmark and one footer landmark, and a heading structure that goes in order without skipping a level.
• Each navigation region has its own name, so “Primary”, “Footer” and “Legal” are told apart rather than announced as three identical menus.
• Every interactive control is a real button or link that works with a keyboard. Expandable panels can be opened and closed with Enter or Space, closed with Escape, and focus returns to the control that opened them. The site’s navigation menu control now behaves the same way, which it did not before: we added the Escape handling and the focus return that the page builder does not provide.
• Keyboard focus is shown with a 3-pixel gold outline offset from the element, on every focusable thing including the navigation, the Contact control, the menu control, the form fields and the footer links. This was measured on each control type rather than assumed from the stylesheet.
• Body text meets or exceeds the WCAG AA contrast ratio of 4.5 to 1, and large text meets 3 to 1. Every text element on every page was measured rather than sampled.
• Meaning is never carried by colour alone. Where a distinction matters — a required field, a development status, a link inside a paragraph — it is also written in words or marked in a second way.
• Every layout reflows to a single readable column at 320 CSS pixels wide, with no two-dimensional scrolling, and holds up when text is enlarged to 200% or when text spacing is overridden.
• Decorative artwork — the ridgeline drawing, the contour lines, the hairline grid — is hidden from assistive technology and is not reachable by keyboard, so it is never read out or tabbed into.
• Motion is minimal, causes no layout shift, and is switched off entirely for a visitor whose device asks for reduced motion. Nothing flashes, and nothing moves that cannot be stopped by that setting.
• With JavaScript unavailable, every panel renders open and the whole page is readable. Nothing is hidden behind a script.
• The contact form has visible labels on every field, marks required fields in words as well as with a symbol, tells you exactly what went wrong, and moves focus to a summary of the problems rather than leaving you at the submit button.
• There are no pop-ups, no autoplaying media, no carousels, no content that appears only on hover, and no time limits.

How we tested

The pages were tested as the server actually renders them, in a real browser engine, at 320, 375, 390, 768, 1024, 1280, 1440 and 1920 pixels wide. That included an automated rule set (axe-core) across every page, a keyboard pass through the controls, contrast measured on every text element, reflow at 320 pixels, text enlarged to 200%, a text-spacing override, reduced-motion behaviour, and a pass with JavaScript switched off entirely.

Two real faults were found and fixed during the most recent round, both of which an automated pass at a single width would have missed:

• On a phone, the site identity in the header had no accessible name at all, because the visible company name had been removed to make room and the mark beside it is decorative. A screen reader would have announced “link” and nothing else. The name is now present for assistive technology at every width.
• At 320 pixels with text enlarged to 200%, the single word in one page heading was wider than the screen and forced sideways scrolling. Headings now break and hyphenate instead.

Known limitations

These are the things we know about today.

• A full screen-reader test has not been completed. Our automated and keyboard testing covers a great deal, but it is not the same as sitting down with VoiceOver, NVDA or JAWS and using the site. That test is outstanding, and until it is done we will not claim the site has passed it.
• The navigation menu has not been confirmed on a real phone. Its keyboard behaviour has been tested and corrected, but a hands-on check on an actual handset is still to come.
• The business logos are typographic placeholders. They are readable text rather than images, so nothing is lost to assistive technology, but they are not yet the real artwork.
• The website previews are placeholders. The three business websites are still being built, so each preview shows a labelled placeholder rather than a screenshot. Each one says so in words.
• Some behaviour belongs to the page builder. The navigation menu is rendered by Elementor rather than written by us. We have corrected its landmark labelling, its focus indicator, its Escape handling and its focus return; if any of its remaining behaviour causes you a problem, please tell us and we will address it.

Telling us about a problem

Email admin@mbgbusinessgroup.com and describe what happened. You do not need to know any technical terms, and you do not need to work out what caused it. “I could not get past the menu with my keyboard” is a perfectly good report.

What helps us fix it faster

• The address of the page you were on.
• What you were trying to do, and what happened instead.
• Anything you know about how you were using the site: which browser, which device, and whether you were using a screen reader, magnification, voice control, or a keyboard on its own.

Any of that is useful. None of it is required.

What we will do

We read every accessibility report and we will reply to you. If it is something we can fix, we will fix it and tell you when it is done. If it is something we cannot fix quickly, we will tell you that honestly, explain why, and describe any way around it in the meantime. Reports also get added to this page’s list of known limitations, so the next person is not left guessing.

Reviewing this page

This statement is reviewed whenever the website changes materially, and at least once a year.

Technical target

WCAG 2.2 Level AA

Last reviewed

August 5, 2026

Accessibility contact

admin@mbgbusinessgroup.com