EVOLIZE Run a free assessment

Accessibility assessment of matterofrecord.app

Automated technical assessment of 5 publicly accessible pages · Scanned 5 Sep 2026. Inspected 5 of 5 selected pages.

29findings detected
1critical + high
5pages inspected

What to fix first

  1. High Hidden elements can still receive keyboard focus
  2. Medium Touch targets are too small on mobile
  3. Medium Touch targets are too small on mobile
  4. Medium Touch targets are too small on mobile
  5. Medium Elements must only use permitted ARIA attributes

Findings

High

Hidden elements can still receive keyboard focus

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Component 5 affected pages 10 instances WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A) Ref TK1YAL
Affected pagehttps://matterofrecord.app/
Elementbody > div > header > div > nav > a:nth-of-type(1)
Accessible nameBrowse cases
Markup
<a href="/cases" class="py-1 transition-colors hover:text-masthead-fg">Browse cases</a>
How to fixTo fix this issue, ensure that hidden elements are removed from the tab order. This can be achieved by setting the 'tabindex' attribute to '-1' or by using a more robust method such as dynamically adding or removing elements from the DOM based on their visibility. For the given element <a href="/cases" class="py-1 transition-colors hover:text-masthead-fg">Browse cases</a>, consider adding 'tabindex="-1"' when it is not visible or restructure the navigation to only include visible elements in the tab order.
Medium

Touch targets are too small on mobile

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Component 5 affected pages 5 instances WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA) Ref SG5X55
Affected pagehttps://matterofrecord.app/about
Elementhtml > body > div > header > div > a
Accessible nameMatter of Record.
Markup
<a href="/" class="truncate whitespace-nowrap font-display text-base font-semibold leading-none tracking-tight text-masthead-fg sm:overflow-visible sm:text-xl">Matter of Record<span class="text-accent">.</span></a>
How to fixIncrease the touch target size of the interactive element to at least 24x24 pixels to make it easier for users to activate by touch.
Medium

Touch targets are too small on mobile

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Component 5 affected pages 37 instances WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA) Ref LQXPB0
Affected pagehttps://matterofrecord.app/privacy
Elementdiv > div:nth-of-type(1) > nav:nth-of-type(1) > ul > li:nth-of-type(1) > a
Accessible nameAll cases
Markup
<a href="/cases" class="text-masthead-muted hover:text-masthead-fg">All cases</a>
How to fixIncrease the touch target size of the interactive element to at least 24x24 pixels to make it easier for users to activate by touch.
Medium

Touch targets are too small on mobile

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Component 5 affected pages 5 instances WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA) Ref KH009P
Affected pagehttps://matterofrecord.app/about
Elementhtml > body > div > a
Accessible nameSkip to content
Markup
<a href="#main" class="sr-only layer-toast focus:not-sr-only focus:fixed focus:left-4 focus:top-4 focus:rounded-md focus:bg-background focus:px-4 focus:py-2 focus:text-sm focus:font-medium focus:text-foreground focus:shadow-lg focus:ring-2 focus:ring-ring focus:ring-offset-2">Skip to content</a>
How to fixIncrease the size of the touch target to at least 24x24px to make it easier for users to activate by touch. Consider adding padding or increasing the font size of the 'Skip to content' link to achieve this.
Medium

Elements must only use permitted ARIA attributes

Elements must only use permitted ARIA attributes

Component 1 affected page 2 instances WCAG WCAG SC 4.1.2 Ref B9Z3LY
Affected pagehttps://matterofrecord.app/
Element.py-4.px-5.justify-between > .text-micro.bg-secondary[aria-label="Convicted"]
Accessible nameConvicted
Markup
<span class="inline-flex shrink-0 items-center whitespace-nowrap rounded-full border px-2.5 py-1 text-micro font-semibold uppercase leading-none tracking-label border-graphite bg-secondary text-foreground" aria-label="Convicted">Convicted</span>
How to fixReview the use of ARIA attributes on the span element with the class 'inline-flex shrink-0 items-center whitespace-nowrap rounded-full border px-2.5 py-1 text-micro font-semibold uppercase leading-none tracking-label border-graphite bg-secondary text-foreground'. Ensure that only permitted ARIA attributes are used. Consider removing or replacing the 'aria-label' attribute if it is not necessary for the element's functionality.
Medium

Elements must only use permitted ARIA attributes

Elements must only use permitted ARIA attributes

Component 1 affected page 12 instances WCAG WCAG SC 4.1.2 Ref I15498
Affected pagehttps://matterofrecord.app/
Element.hover\:bg-paper.group.py-5:nth-child(1) > .pointer-events-none.z-10.justify-between > .min-w-0 > .flex-wrap.gap-2.items-start > .text-micro.bg-secondary[aria-label="Convicted"]
Accessible nameConvicted
Markup
<span class="inline-flex shrink-0 items-center whitespace-nowrap rounded-full border px-2.5 py-1 text-micro font-semibold uppercase leading-none tracking-label border-graphite bg-secondary text-foreground" aria-label="Convicted">Convicted</span>
How to fixReview the usage of ARIA attributes on the span element. Ensure that only permitted ARIA attributes are used. In this case, consider using a more semantic HTML element, such as a button or a link, if the span is intended to be interactive. Remove any unnecessary or prohibited ARIA attributes.
Medium

Elements must only use permitted ARIA attributes

Elements must only use permitted ARIA attributes

Component 1 affected page 2 instances WCAG WCAG SC 4.1.2 Ref SVYNFD
Affected pagehttps://matterofrecord.app/cases
Element.border-accent-ink
Accessible nameAwaiting retrial — no finding of guilt
Markup
<span class="inline-flex shrink-0 items-center whitespace-nowrap rounded-full border px-2.5 py-1 text-micro font-semibold uppercase leading-none tracking-label border-accent-ink bg-secondary text-accent-ink" aria-label="Awaiting retrial — no finding of guilt">Awaiting retrial</span>
How to fixReview the use of ARIA attributes on the span element. Ensure that only permitted ARIA attributes are used. In this case, the 'aria-label' attribute is used on a span element, which may not be necessary if the text content of the span is already descriptive. Consider removing the 'aria-label' attribute if the text content is sufficient for screen readers to announce the element's purpose.
Medium

Elements must only use permitted ARIA attributes

Elements must only use permitted ARIA attributes

Component 1 affected page 16 instances WCAG WCAG SC 4.1.2 Ref 6FYI97
Affected pagehttps://matterofrecord.app/cases
Element.group.py-5.hover\:bg-paper:nth-child(1) > .pointer-events-none.z-10.justify-between > .min-w-0 > .flex-wrap.gap-2.items-start > .text-micro.uppercase[aria-label="Convicted"]
Accessible nameConvicted
Markup
<span class="inline-flex shrink-0 items-center whitespace-nowrap rounded-full border px-2.5 py-1 text-micro font-semibold uppercase leading-none tracking-label border-graphite bg-secondary text-foreground" aria-label="Convicted">Convicted</span>
How to fixReview the usage of ARIA attributes on the span element. Ensure that only permitted ARIA attributes are used. In this case, consider using a more semantic HTML element, such as a button or a link, if the span is intended to be interactive. Remove any unnecessary or prohibited ARIA attributes.
Medium

Elements must only use permitted ARIA attributes

Elements must only use permitted ARIA attributes

Component 1 affected page 2 instances WCAG WCAG SC 4.1.2 Ref PUCJPG
Affected pagehttps://matterofrecord.app/calendar
Element.mt-10:nth-child(4) > .mt-6 > .border-t.border-border > section > .divide-y.divide-border.border-b > .group.border-l-2.hover\:bg-secondary\/60 > .pointer-events-none.z-10.grid-cols-\[4\.5rem_minmax\(0\,1fr\)\] > .min-w-0 > .gap-x-3.flex-wrap.flex > .border-graphite.text-foreground[aria-label="Convicted"]
Accessible nameConvicted
Markup
<span class="inline-flex shrink-0 items-center whitespace-nowrap rounded-full border px-2.5 py-1 text-micro font-semibold uppercase leading-none tracking-label border-graphite bg-secondary text-foreground" aria-label="Convicted">Convicted</span>
How to fixReview the usage of ARIA attributes on the span element. Ensure that only permitted ARIA attributes are used. Consider removing the aria-label attribute if the element's text content is sufficient for accessibility.
Medium

Elements must only use permitted ARIA attributes

Elements must only use permitted ARIA attributes

Component 1 affected page 2 instances WCAG WCAG SC 4.1.2 Ref M0KM04
Affected pagehttps://matterofrecord.app/calendar
Element#recent > .mt-6 > .border-t.border-border > section:nth-child(1) > .divide-y.divide-border.border-b > .group.border-l-2.hover\:bg-secondary\/60:nth-child(1) > .pointer-events-none.z-10.grid-cols-\[4\.5rem_minmax\(0\,1fr\)\] > .min-w-0 > .gap-x-3.flex-wrap.flex > .border-graphite.text-foreground[aria-label="Convicted"]
Accessible nameConvicted
Markup
<span class="inline-flex shrink-0 items-center whitespace-nowrap rounded-full border px-2.5 py-1 text-micro font-semibold uppercase leading-none tracking-label border-graphite bg-secondary text-foreground" aria-label="Convicted">Convicted</span>
How to fixRemove or replace the aria-label attribute with a permitted ARIA attribute for the given element, or ensure the attribute is used in a way that is compatible with the element's role.
Medium

Elements must only use permitted ARIA attributes

Elements must only use permitted ARIA attributes

Component 1 affected page 12 instances WCAG WCAG SC 4.1.2 Ref 9IA2TM
Affected pagehttps://matterofrecord.app/calendar
Element.group.border-l-2.hover\:bg-secondary\/60:nth-child(2) > .pointer-events-none.z-10.grid-cols-\[4\.5rem_minmax\(0\,1fr\)\] > .min-w-0 > .gap-x-3.flex-wrap.flex > .border-graphite.text-foreground[aria-label="Convicted"]
Accessible nameConvicted
Markup
<span class="inline-flex shrink-0 items-center whitespace-nowrap rounded-full border px-2.5 py-1 text-micro font-semibold uppercase leading-none tracking-label border-graphite bg-secondary text-foreground" aria-label="Convicted">Convicted</span>
How to fixTo fix this issue, remove any prohibited ARIA attributes from the span element. For example, if the span element does not have a role that requires an aria-label, consider using a regular text label instead. Ensure that the ARIA attributes used are valid and suitable for the element's role.
Medium

Elements must only use permitted ARIA attributes

Elements must only use permitted ARIA attributes

Component 1 affected page 2 instances WCAG WCAG SC 4.1.2 Ref 90J5JN
Affected pagehttps://matterofrecord.app/cases
Elementspan[aria-label="Closed"]
Accessible nameClosed
Markup
<span class="inline-flex shrink-0 items-center whitespace-nowrap rounded-full border px-2.5 py-1 text-micro font-semibold uppercase leading-none tracking-label border-graphite bg-secondary text-foreground" aria-label="Closed">Closed</span>
How to fixRemove or replace the 'aria-label' attribute with a permitted ARIA attribute for the given element, or ensure that the attribute is used in a way that is consistent with the element's role and the ARIA specification.
Medium

Elements must only use permitted ARIA attributes

Elements must only use permitted ARIA attributes

Component 1 affected page 10 instances WCAG WCAG SC 4.1.2 Ref LDL2QP
Affected pagehttps://matterofrecord.app/calendar
Elementsection:nth-child(1) > .divide-y.divide-border.border-b > .group.border-l-2.hover\:bg-secondary\/60:nth-child(3) > .pointer-events-none.z-10.grid-cols-\[4\.5rem_minmax\(0\,1fr\)\] > .min-w-0 > .gap-x-3.flex-wrap.flex > .border-graphite.text-foreground[aria-label="Convicted"]
Accessible nameConvicted
Markup
<span class="inline-flex shrink-0 items-center whitespace-nowrap rounded-full border px-2.5 py-1 text-micro font-semibold uppercase leading-none tracking-label border-graphite bg-secondary text-foreground" aria-label="Convicted">Convicted</span>
How to fixReview the usage of ARIA attributes on the span element. Ensure that only permitted ARIA attributes are used. Consider removing the aria-label attribute if the element's text content is sufficient for accessibility.
Low

Touch targets are too small on mobile

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Component 2 affected pages 2 instances WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA) Ref NREMZK
Affected pagehttps://matterofrecord.app/cases
Elementbody > div > div > div > p > a
Accessible nameHow we measure
Markup
<a href="/privacy" class="underline decoration-border underline-offset-4">How we measure</a>
How to fixTo fix this issue, increase the size of the interactive control to at least 24x24 pixels to make it easier for users to tap on mobile devices. Consider adding padding or increasing the font size of the link to achieve the minimum target size.
Low

Touch targets are too small on mobile

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Component 2 affected pages 7 instances WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA) Ref NRLF6O
Affected pagehttps://matterofrecord.app/about
Elementmain#main > div > div > ul > li:nth-of-type(1) > a
Accessible nameSourcing methodology
Markup
<a href="/sourcing" class="underline decoration-border underline-offset-4 hover:text-foreground">Sourcing methodology</a>
How to fixIncrease this <a>'s rendered area to at least 24 × 24 CSS pixels, or provide sufficient spacing from adjacent targets. Prefer increasing padding on the existing control (for example the button or link) rather than adding a separate non-interactive wrapper. Observed size: 133 × 20 CSS pixels; required minimum: 24 × 24 CSS pixels.
Low

Touch targets are too small on mobile

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Component 2 affected pages 5 instances WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA) Ref ML4J7I
Affected pagehttps://matterofrecord.app/about
Elementmain#main > div > div > p:nth-of-type(8) > a
Accessible nameRead the sourcing methodology →
Markup
<a href="/sourcing" class="underline underline-offset-4">Read the sourcing methodology →</a>
How to fixTo improve accessibility, ensure that all interactive elements, such as buttons and links, have a minimum touch target size of 24x24 pixels. Consider increasing the padding or size of the affected element to meet this requirement.
Low

Touch targets are too small on mobile

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Component 1 affected page 2 instances WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA) Ref M8I1AI
Affected pagehttps://matterofrecord.app/
Elementsection:nth-of-type(1) > div > div > div > p:nth-of-type(1) > a
Accessible nameExplore all cases
Markup
<a href="/cases" class="inline-flex items-center gap-1 text-sm text-secondary-foreground underline decoration-border underline-offset-4 hover:text-foreground">Explore all cases<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-arrow-right size-3.5" aria-hidden="true"><path d="M5 12h14"></path><path d="m12 5 7 7-7 7"></path></svg></a>
How to fixIncrease this <a>'s rendered area to at least 24 × 24 CSS pixels, or provide sufficient spacing from adjacent targets. Prefer increasing padding on the existing control (for example the button or link) rather than adding a separate non-interactive wrapper. Observed size: 114 × 20 CSS pixels; required minimum: 24 × 24 CSS pixels.
Low

Touch targets are too small on mobile

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Component 1 affected page 3 instances WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA) Ref C2A82Y
Affected pagehttps://matterofrecord.app/
Elementarticle > ol > li:nth-of-type(1) > div > div > a
Accessible nameNews report·Lawcommentary
Markup
<a href="https://www.lawcommentary.com/articles/man-accused-of-orchestrating-tupac-shakurs-murder-finally-heads-to-trial-30-years-later" target="_blank" rel="noopener noreferrer" class="inline-flex max-w-[200px] items-center gap-1 text-xs text-muted-foreground underline underline-offset-2 hover:text-foreground focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring sm:max-w-[280px]"><span class="min-w-0 truncate"><span class="inline-flex min-w-0 flex-wrap items-center gap-1.5 "><svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke…
How to fixIncrease the size of the touch target to at least 24x24 pixels to make it easier for users to activate by touch. Consider adding padding or increasing the font size of the interactive element to achieve this.
Low

Touch targets are too small on mobile

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Component 1 affected page 3 instances WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA) Ref SETR5I
Affected pagehttps://matterofrecord.app/cases
Elementbutton#radix-_R_3mopaq_
Accessible nameCountry
Markup
<button type="button" id="radix-_R_3mopaq_" aria-haspopup="menu" aria-expanded="false" data-state="closed" aria-label="Country" class="text-sm text-foreground underline underline-offset-4 outline-none hover:text-primary focus-visible:ring-2 focus-visible:ring-ring">All countries</button>
How to fixTo fix this issue, consider increasing the size of the touch target to at least 24x24 pixels. This can be achieved by adding padding or increasing the font size of the button. Additionally, ensure that the button's width and height are set to a minimum of 24 pixels to provide a larger target area for users to interact with.
Low

Text has insufficient colour contrast

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Component 2 affected pages 2 instances WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA) Ref WJI6JU
Affected pagehttps://matterofrecord.app/about
Element.text-secondary-foreground.leading-relaxed.text-sm
Accessible namePrivacy-friendly analytics, hosted in the EU. Nothing is sent unless you accept, and declining changes nothing about how the site works. How we measure
Markup
<p class="text-sm leading-relaxed text-secondary-foreground">Privacy-friendly analytics, hosted in the EU. Nothing is sent unless you accept, and declining changes nothing about how the site works. <a href="/privacy" class="underline decoration-border underline-offset-4">How we measure</a></p>
How to fixTo improve the accessibility of this element, consider adjusting the color scheme to ensure a minimum contrast ratio of 4.5:1 for normal text and 7:1 for larger text (18pt or 14pt bold). This can be achieved by changing the text color, background color, or both. For example, you can use a color contrast analyzer tool to find a suitable combination that meets the WCAG 2.1 guidelines.
Low

Text has insufficient colour contrast

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Component 1 affected page 2 instances WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA) Ref NAQMI8
Affected pagehttps://matterofrecord.app/
Element.decoration-border.underline-offset-4[href$="privacy"]
Accessible nameHow we measure
Markup
<a href="/privacy" class="underline decoration-border underline-offset-4">How we measure</a>
How to fixTo improve text legibility, consider adjusting the color scheme to meet the minimum contrast ratio of 4.5:1 for normal text. You can use online tools to calculate the contrast ratio between the text color and background color. For the affected element, try changing the class 'text-secondary-foreground' or the background color to achieve sufficient contrast.
Low

Text has insufficient colour contrast

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Component 2 affected pages 2 instances WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA) Ref M3BFBP
Affected pagehttps://matterofrecord.app/cases
Element.decoration-border
Accessible nameHow we measure
Markup
<a href="/privacy" class="underline decoration-border underline-offset-4">How we measure</a>
How to fixTo improve text legibility, consider adjusting the color scheme to meet the minimum contrast ratio of 4.5:1 for normal text. You can use online tools to calculate the contrast ratio between the text color and background color. For the affected element, try changing the class 'text-secondary-foreground' or the background color to achieve sufficient contrast.
Low

Touch targets are too small on mobile

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Component 1 affected page 1 instance WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA) Ref KITEHH
Affected pagehttps://matterofrecord.app/
Elementdiv > article > div:nth-of-type(1) > div > h2 > a
Accessible nameMurder of Tupac Shakur
Markup
<a href="/case/murder-of-tupac-shakur" class="text-foreground transition-colors hover:underline focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring">Murder of Tupac Shakur</a>
How to fixTo fix this issue, increase the size of the touch target to at least 24x24 pixels. This can be achieved by adding padding to the element or increasing its font size.
Low

Touch targets are too small on mobile

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Component 1 affected page 1 instance WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA) Ref NUUXJP
Affected pagehttps://matterofrecord.app/
Elementmain#main > div > section:nth-of-type(3) > div > div:nth-of-type(1) > a
Accessible nameFull calendar
Markup
<a href="/calendar" class="group inline-flex items-center gap-2 text-sm text-secondary-foreground underline decoration-border underline-offset-4 transition-colors hover:text-foreground">Full calendar<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-arrow-right h-3.5 w-3.5 transition-transform group-hover:translate-x-0.5" aria-hidden="true"><path d="M5 12h14"></path><path d="m12 5 7 7-7 7"></path></svg></a>
How to fixTo improve accessibility, increase the size of the touch target for the 'Full calendar' link to at least 24x24 pixels. This can be achieved by adjusting the CSS styles for the element, such as setting a minimum width and height for the link or its container.
Low

Touch targets are too small on mobile

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Component 1 affected page 1 instance WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA) Ref INC5IC
Affected pagehttps://matterofrecord.app/privacy
Elementmain#main > div > div > nav > a
Accessible nameAbout
Markup
<a href="/about" class="underline decoration-border underline-offset-4 hover:text-foreground">About</a>
How to fixTo fix this issue, ensure that all interactive controls, such as buttons and links, have a minimum touch target size of 24x24 pixels. Consider increasing the size of the 'About' link or wrapping it in a larger clickable area to make it easier to tap on mobile devices.
Low

Text has insufficient colour contrast

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Component 1 affected page 1 instance WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA) Ref UY1259
Affected pagehttps://matterofrecord.app/
Element.max-w-5xl > .text-secondary-foreground.leading-relaxed.text-sm
Accessible namePrivacy-friendly analytics, hosted in the EU. Nothing is sent unless you accept, and declining changes nothing about how the site works. How we measure
Markup
<p class="text-sm leading-relaxed text-secondary-foreground">Privacy-friendly analytics, hosted in the EU. Nothing is sent unless you accept, and declining changes nothing about how the site works. <a href="/privacy" class="underline decoration-border underline-offset-4">How we measure</a></p>
How to fixTo improve the accessibility of the text, consider increasing the contrast between the text color and the background color. This can be achieved by adjusting the CSS styles for the 'text-secondary-foreground' class to use a color with sufficient contrast to the background.
Low

Text has insufficient colour contrast

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Component 1 affected page 1 instance WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA) Ref AXLQK7
Affected pagehttps://matterofrecord.app/cases
Element.text-secondary-foreground.leading-relaxed
Accessible namePrivacy-friendly analytics, hosted in the EU. Nothing is sent unless you accept, and declining changes nothing about how the site works. How we measure
Markup
<p class="text-sm leading-relaxed text-secondary-foreground">Privacy-friendly analytics, hosted in the EU. Nothing is sent unless you accept, and declining changes nothing about how the site works. <a href="/privacy" class="underline decoration-border underline-offset-4">How we measure</a></p>
How to fixTo improve the accessibility of the text, consider increasing the contrast between the text color and the background color. This can be achieved by adjusting the CSS styles for the 'text-secondary-foreground' class to use a color with sufficient contrast to the background.
Low

Text has insufficient colour contrast

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Component 1 affected page 1 instance WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA) Ref CX3RV6
Affected pagehttps://matterofrecord.app/about
Element.text-secondary-foreground.leading-relaxed.text-sm > .decoration-border.underline[href$="privacy"]
Accessible nameHow we measure
Markup
<a href="/privacy" class="underline decoration-border underline-offset-4">How we measure</a>
How to fixConsider adjusting the color scheme to improve contrast between the text and background. A contrast ratio of at least 4.5:1 for normal text is recommended.
Low

Text has insufficient colour contrast

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Component 1 affected page 1 instance WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA) Ref YC7URS
Affected pagehttps://matterofrecord.app/privacy
Element.text-sm.leading-relaxed > .active[href$="privacy"][data-status="active"]
Accessible nameHow we measure
Markup
<a class="underline decoration-border underline-offset-4 active" href="/privacy" data-status="active" aria-current="page">How we measure</a>
How to fixTo improve the legibility of the text, consider adjusting the background color or the text color to meet the minimum contrast ratio of 4.5:1 for normal text. You can use online tools to help determine the contrast ratio and select colors that meet the accessibility guidelines.

Keep matterofrecord.app monitored

This is a point-in-time assessment. Evolize monitoring re-scans the site on a schedule, flags new and recurring issues, tracks changes over time, and verifies fixes after you make them.

Start monitoring
About this assessment.
  • Automated technical analysis of publicly accessible website surfaces only — no credentials, private systems, or source-code access.
  • Findings apply to the pages and states successfully inspected; automated analysis may not detect every accessibility issue.
  • Results reflect the site at the scan date and may have changed since.
  • This is technical information, not legal advice.

Request a correction or removal · How Evolize scans