Accessibility
Accessibility at Marcella
This site targets WCAG 2.1 Level AA. This page states what that covers, what is verified in code on every build, what is known to fall short, and how to tell us about a barrier so it gets fixed.
Statement reviewed 2026-10-20 · Applies to marcellalegal.com
Standard · WCAG 2.1 AA
Conformance is checked in code on every build. Colour contrast is computed, heading structure is parsed, and control sizes are measured in a real browser at 375, 768 and 1280 pixels wide. A failing check blocks the release.
-
Conformance target and status
Target standard: Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. Status: partially conformant. Partially conformant means most of the site meets the standard and the exceptions are named below rather than left for a visitor to discover.
Conformance is checked in code on every build, not asserted. Colour contrast is computed rather than estimated, heading structure is parsed, and control sizes are measured in a real browser at 375, 768 and 1280 pixels wide.
WCAG 2.1 AA is the baseline the Department of Justice and the federal courts apply to public accommodations
-
Vision: what is supported
Text contrast is at least 4.5 to 1 against its background in both the paper and the dark theme, and interface borders are at least 3 to 1. Every pair is computed at build time and a failing pair blocks the release.
Colour never carries meaning alone. Green, yellow and red triage states always carry a text label, so the meaning survives greyscale and the common forms of colour vision deficiency.
Pages use one level-one heading and an unbroken heading tree, so screen reader users can navigate by heading. Decorative icons are hidden from assistive technology. Meaningful graphics carry a text alternative. A skip link is the first focusable element on every page, and the main region is a focus target.
Text resizes to 200 percent without loss of content or function, and the layout reflows to a single column without horizontal scrolling. A paper and a dark theme are both available from the masthead and the choice is remembered.
WCAG 1.4.3, 1.4.11, 1.4.1, 1.3.1, 2.4.1, 1.4.4, 1.4.10
-
Hearing: what is supported
This site publishes no audio and no video. Every claim on it is available as text, so nothing here depends on hearing. There is no auto-playing sound anywhere on the site.
If audio or video is added later, captions and a text transcript ship with it in the same release. That is a release condition, not an intention: the build check fails on a media element that carries no caption track.
Support is reachable in writing. You never have to make a phone call to get help or to ask a question about the product.
WCAG 1.2.1, 1.2.2, 1.2.3, 1.4.2
-
Motor and input: what is supported
Everything on the site works from the keyboard alone, in a logical order, with a visible focus outline on every control. There are no keyboard traps. Menus and dialogs close with the Escape key and return focus to the control that opened them.
Interactive controls are at least 44 by 44 pixels, measured in a real browser rather than assumed from the stylesheet. Links inside a sentence are exempt from that minimum under the standard, because enlarging them would break the line.
No feature requires a drag, a swipe, a pinch, a timed response, or a device motion gesture.
WCAG 2.1.1, 2.1.2, 2.4.7, 2.5.1, 2.5.5, 2.5.8, 2.2.1
-
Cognitive and vestibular: what is supported
This site has no animation. No content fades in, slides, parallaxes or moves on scroll, so there is nothing to trigger a vestibular response and nothing to wait for before reading. Nothing flashes.
Language is plain, paragraphs are short, and every page states its subject in the first sentence. Error messages name the problem and the fix rather than reporting that something is invalid.
WCAG 2.3.1, 2.2.2, 3.1.5, 3.3.1, 3.3.3
-
Known limitations
Site search and the theme switch need JavaScript. Every page, every link in the masthead and the colophon, and all of the content work without it.
Wide comparison tables scroll horizontally inside their own container on a narrow screen. The page itself never scrolls sideways.
Automated checks catch roughly half of structural accessibility issues. They do not replace testing with a real screen reader, and we do not claim otherwise. If something here does not work with your assistive technology, that is a defect and we want to hear about it.
Last full review 2026-10-20
-
Third-party content
Forms on this site post to Formsubmit, and analytics load only if you accept them. Technology Outlaws does not control the accessibility of those third-party services. If one of them blocks you, write to us and we will take your information by email instead.
See the privacy policy for what each processor receives
Report a barrier
Write to support@technologyoutlaws.com. Tell us the page, what you were trying to do, and the assistive technology and browser you were using. You will get a reply from a person within five business days with either a fix or a date for one.
Email an accessibility reportTechnology Outlaws LLC · Mesa, Arizona
