Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DTabindex Anti-PatternsAction0 positive, 29 -1-on-focusableFIX
F404 Error PageActionHTTP 508, bare pageFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
CLandmark StructureAction7 landmarksREVIEW
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Learn more ▾ ▴
The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.
Source: WAI-ARIA / WCAG 2.4.1
Multiple navigations need aria-label to distinguish them for screen readers.
Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.
Learn more ▾ ▴
When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.
Source: WAI-ARIA Authoring Practices
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.
Learn more ▾ ▴
Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.
Source: WCAG 2.1 SC 2.4.1
BForm Accessibility2 of 10 controls have issuesREVIEW
| Control | Type | Label | Method |
|---|---|---|---|
| #input_1_8 | text | for/id | |
| #input_1_1 | text | Name* | for/id |
| #input_1_2 | Email* | for/id | |
| #input_1_3 | tel | Phone* | for/id |
| #input_1_7 | text | What is the name of the other party? | for/id |
| #input_1_6 | textarea | Brief description of your legal issue* | for/id |
| #input_1_4_1 | checkbox | I agree to the disclaimer and privacy policy.* | for/id |
| ak_hp_textarea | textarea | Δ | none |
| #gform_submit_button_1 | submit | (none) | none |
| #g-recaptcha-response-100000 | textarea | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit" id="gform_submit_button_1">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
Source: WCAG 2.1 SC 3.3.2
CLink & Button QualityAction3 issue(s) across 71 links and 1 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| / | (empty) | empty | Add link text or aria-label |
| tel:503-594-7027 | (empty) | empty | Add link text or aria-label |
| tel:503-610-4261 | 503-610-4261 | new tab | Add '(opens in new tab)' to text |
| / | (empty) | empty | Add link text or aria-label |
| https://google.com/maps?q=Regele%20Law,%… | Regele Law, LLC <br> 1415 Comm… | new tab | Add '(opens in new tab)' to text |
| https://google.com/maps?q=Regele%20Law,%… | Regele Law, LLC 1415 Commerci… | new tab | Add '(opens in new tab)' to text |
| /salem-divorce-office/ | Salem Office Location | new tab | Add '(opens in new tab)' to text |
| /salem-divorce-office/ | Salem Office Location | new tab | Add '(opens in new tab)' to text |
| https://get310.com/ | Digital Marketing by Agency 31… | new tab | Add '(opens in new tab)' to text |
Links without text are announced as raw URLs by screen readers.
/; tel:503-594-7027; /
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
tel:503-610-4261; https://google.com/maps?q=Regele%20Law,%20LLC%20%201415%20Commercial%20St%20S…; https://google.com/maps?q=Regele%20Law,%20LLC%20%201415%20Commercial%20St%20S…; /salem-divorce-office/; /salem-divorce-office/; https://get310.com/
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
CFavicon & BrandingAction3 icon(s) detectedREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 11 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Our Practice Focuses… | 17.53:1 | 3.0:1 | #000000 | #EFEAE1 | Pass |
| h2 We're About More Tha… | 17.53:1 | 3.0:1 | #000000 | #EFEAE1 | Pass |
| h2 For The Good of Your… | 17.53:1 | 3.0:1 | #000000 | #EFEAE1 | Pass |
| h2 Practice Areas | 17.53:1 | 3.0:1 | #000000 | #EFEAE1 | Pass |
| h2 Full-Service Attorne… | 17.53:1 | 3.0:1 | #000000 | #EFEAE1 | Pass |
| h2 Welcome LGBTQ And Ot… | 17.53:1 | 3.0:1 | #000000 | #EFEAE1 | Pass |
| h2 Bring Your Questions | 17.53:1 | 3.0:1 | #000000 | #EFEAE1 | Pass |
| h2 What Our Clients Say | 17.53:1 | 3.0:1 | #000000 | #EFEAE1 | Pass |
| h2 Arrange Your Consult… | 17.53:1 | 3.0:1 | #000000 | #EFEAE1 | Pass |
| title Divorce & Family Law… | 1.19:1 | 4.5:1 | #000000 | #0F1927 | Fail |
| a Skip to content | 1.20:1 | 4.5:1 | #000000 | #101A28 | Fail |
| a Divorce | 1.39:1 | 4.5:1 | #000000 | #1F2731 | Fail |
| a Cooperative Divorce | 2.00:1 | 4.5:1 | #000000 | #3A4045 | Fail |
| a Same-Sex Divorce | 2.74:1 | 4.5:1 | #000000 | #505454 | Fail |
| a Spousal Support | 2.84:1 | 4.5:1 | #000000 | #545656 | Fail |
| a Property Division | 1.79:1 | 4.5:1 | #000000 | #453525 | Fail |
| a Property Division FA… | 2.42:1 | 4.5:1 | #000000 | #59492E | Fail |
| a Child Custody | 1.53:1 | 4.5:1 | #000000 | #40271D | Fail |
| a Oregon Child Custody… | 1.50:1 | 4.5:1 | #000000 | #40251A | Fail |
| a Fathers’ Rights | 1.44:1 | 4.5:1 | #000000 | #392416 | Fail |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
A+Heading Hierarchy17 headingsPASS
- H2 We're About More Than Divorce
- H1 Our Practice Focuses On Your Family.
- H2 For The Good of Your Family
- H2 Practice Areas
- H3 Family Law
- H3 Divorce
- H3 Child Custody & Parenting Time
- H2 Full-Service Attorneys For Your Family Law Needs
- H2 Welcome LGBTQ And Other Diverse Families!
- H2 Bring Your Questions
- H2 What Our Clients Say
- H2 Arrange Your Consultation Today!
- H3 Regele Law, LLC 1415 Commercial St SE Salem, OR 97302
- H3 Salem Office Location
- H3 Phone: 503-610-4261
- H3 Fax: 503-217-7552
- H2 Digital Marketing by Agency 310
A+Heading Text QualityAll 17 heading(s) have substantive, well-formed textPASS
A+Alt Text QualityAll 13 images OKPASS
A+Form Input Types10 form control(s) checked, no type mismatchesPASS
A+Form Input Quality10 form control(s) checked, no input-semantic issuesPASS
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
A+Document LanguageLang attribute set to "en-US"PASS
AIframe Accessibility1/3 iframe(s) missing title; 0 placeholder(s)PASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A+Mobile-Readable Font SizesAll 71 visible text node(s) render at >= 12 CSS pixelsPASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
ALighthouse Accessibility AuditsScore 90/100 — 4 failing, 24 passedPASS
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Contrast
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
CONTACT US div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text |
div#gform_wrapper_1 > form#gform_1 > div.gform-footer > input#gform_submit_button_1 div#gform_wrapper_1 > form#gform_1 > div.gform-footer > input#gform_submit_button_1 |
These are opportunities to improve the legibility of your content.
Names and labels
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a |
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon |
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a |
Including a skip link can help users skip to the main content to save time. Learn more about skip links.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Skip to content body.home > a.skip-link |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Best practices
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.crjs html.crjs |
These items highlight common accessibility best practices.