Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FHeading HierarchyAction74 headings, 26 skip(s)FIX
- H2 Main navigation
- H2 Main navigation
- H1 Welcome to the State of Mississippi Citizen Portal
- H3 YOUR MISSISSIPPI STARTS HERE! skipped
- H2 Discover Citizen Resources and Opportunities.
- H2 Education & Learning
- H2 Taxpayer Access Point
- H2 Driving in Mississippi
- H2 Business in Mississippi
- H2 Your Technology
- H2 Living in Mississippi
- H3 Register To Vote
- H3 Driver License Renewal
- H3 Hunting & Fishing Licenses
- H3 MS.GOV For Kids
- H3 Mississippi Outdoors
- H3 Featured Mobile Apps
- H3 Start a Business
- H3 MS.GOV Connect
- H3 Plan Your Trip
- H3 Commissioner of Insurance
- H1 Mike Chaney duplicate H1
- H3 Governor skipped
- H1 Tate Reeves duplicate H1
- H3 Lieutenant Governor skipped
- H1 Delbert Hosemann duplicate H1
- H3 Secretary of State skipped
- H1 Michael Watson duplicate H1
- H3 Attorney General skipped
- H1 Lynn Fitch duplicate H1
- H3 State Auditor skipped
- H1 Shad White duplicate H1
- H3 State Treasurer skipped
- H1 David McRae duplicate H1
- H3 Commissioner of Agriculture skipped
- H1 Andy Gipson duplicate H1
- H3 Commissioner of Insurance skipped
- H1 Mike Chaney duplicate H1
- H3 Governor skipped
- H1 Tate Reeves duplicate H1
- H3 Lieutenant Governor skipped
- H1 Delbert Hosemann duplicate H1
- H3 Secretary of State skipped
- H1 Michael Watson duplicate H1
- H3 Attorney General skipped
- H1 Lynn Fitch duplicate H1
- H3 State Auditor skipped
- H1 Shad White duplicate H1
- H3 State Treasurer skipped
- H1 David McRae duplicate H1
- H3 Commissioner of Agriculture skipped
- H1 Andy Gipson duplicate H1
- H3 Commissioner of Insurance skipped
- H1 Mike Chaney duplicate H1
- H3 5.3 skipped
- H6 FYTD Revenue skipped
- H3 16.4
- H6 FYTD Expenditures skipped
- H3 5.5
- H6 FYTD General Fund Expenditure skipped
- H3 1,279,803
- H6 FYTD Electronic Transactions skipped
- H3 160
- H6 Procurement Opportunities skipped
- H3 30.9
- H6 Appropriated Budget skipped
- H3 547
- H6 State Contracts skipped
- H3 25
- H6 Open Meetings skipped
- H4 Help
- H4 About
- H4 Policy
- H4 Feedback
A page should have only one H1. Multiple H1s dilute the document outline.
Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.
Learn more ▾ ▴
HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.
Source: WCAG 2.4.6 / Google Search Central
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
FAlt Text QualityAction42 of 47 images have issuesFIX
| Issue | Count |
|---|---|
| missing | 36 image(s) |
| generic | 6 image(s) |
Images without alt text are invisible to screen readers.
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
Learn more ▾ ▴
WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.
Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report
An image inside a link with no alt creates an empty link.
Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.
Learn more ▾ ▴
An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.
Source: WCAG 2.1 SC 2.4.4
DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
CLandmark StructureAction9 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
CLink & Button QualityAction8 issue(s) across 165 links and 12 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://accessibe.com/blog/knowledgebase… | Accessibility Screen-Reader Gu… | new tab | Add '(opens in new tab)' to text |
| # | English | img no alt | Add alt attribute to the image |
| # | Español | img no alt | Add alt attribute to the image |
| # | Tiếng Việt | img no alt | Add alt attribute to the image |
| https://www.ms.gov/dfa/ace/W2EFTDispatch… | ACE Login | new tab | Add '(opens in new tab)' to text |
| https://web.getgov2go.com/signin | MS.GOV Login | new tab | Add '(opens in new tab)' to text |
| /ms-search | Search | img no alt | Add alt attribute to the image |
| / | (empty) | empty | Add link text or aria-label |
| / | (empty) | empty | Add link text or aria-label |
| / | (empty) | empty | Add link text or aria-label |
| / | (empty) | empty | Add link text or aria-label |
| https://uat-web.getgov2go.com/ | MS.GOV Login | new tab | Add '(opens in new tab)' to text |
| https://www.ms.gov/dfa/ace/W2EFTDispatch… | ACE Login | new tab | Add '(opens in new tab)' to text |
| https://web.getgov2go.com/signin/create-… | Create Your MS.GOV Account | new tab | Add '(opens in new tab)' to text |
| https://web.getgov2go.com/signin | Log in here | new tab | Add '(opens in new tab)' to text |
| https://www.mdek12.org/OAE/2019-Access-f… | Access for All Guide | new tab | Add '(opens in new tab)' to text |
| https://treasury.ms.gov/for-citizens/col… | College Savings Guide | new tab | Add '(opens in new tab)' to text |
| https://www.msvcc.org/ | Mississippi Virtual Community … | new tab | Add '(opens in new tab)' to text |
| https://www.mdek12.org/OETA | Teacher Center | new tab | Add '(opens in new tab)' to text |
| https://www.charterschoolboard.ms.gov/ | Mississippi Charter School Boa… | new tab | Add '(opens in new tab)' to text |
| https://maapp.msfinancialaid.org/#/appli… | Apply for Financial Aid | new tab | Add '(opens in new tab)' to text |
| http://www.mississippi.edu/ | Colleges and Universities | new tab | Add '(opens in new tab)' to text |
| http://mdek12.org/dd | Mississippi School Districts | new tab | Add '(opens in new tab)' to text |
| https://www.msfinancialaid.org/ | Mississippi Office of Student … | new tab | Add '(opens in new tab)' to text |
| https://tap.dor.ms.gov/_/#1 | Mississippi Tax | new tab | Add '(opens in new tab)' to text |
| https://tap.dor.ms.gov/_/ | Locate Your Tax Refund | new tab | Add '(opens in new tab)' to text |
| https://tap.dor.ms.gov/_/ | Register for Taxes | new tab | Add '(opens in new tab)' to text |
| https://tap.dor.ms.gov/_/ | Make an Estimated Payment | new tab | Add '(opens in new tab)' to text |
| https://tap.dor.ms.gov/ | Register to Pay Your Business … | new tab | Add '(opens in new tab)' to text |
| https://www.dor.ms.gov/business/corporat… | Corporate Income and Franchise… | new tab | Add '(opens in new tab)' to text |
| https://www.dor.ms.gov/e-services | e-File Income Taxes | new tab | Add '(opens in new tab)' to text |
| https://tap.dor.ms.gov/WebFiles/Help/TAP… | Frequently Asked Questions | new tab | Add '(opens in new tab)' to text |
| http://www.irs.gov/ | Internal Revenue Service | new tab | Add '(opens in new tab)' to text |
| https://telegov.egov.com/dps | Schedule an Appointment Online | new tab | Add '(opens in new tab)' to text |
| https://www.dor.ms.gov/tagstitles/line-t… | Car Tag Renewal | new tab | Add '(opens in new tab)' to text |
| https://www.driverservicebureau.dps.ms.g… | Driver's License Manual | new tab | Add '(opens in new tab)' to text |
| https://www.driverservicebureau.dps.ms.g… | Driver Service Bureau Website | new tab | Add '(opens in new tab)' to text |
| https://yallbusiness.sos.ms.gov/Home | Starting a Business in Mississ… | new tab | Add '(opens in new tab)' to text |
| https://mdes.ms.gov/i-need-a-job/job-sea… | Employment Interruption | new tab | Add '(opens in new tab)' to text |
| https://mdes.ms.gov/ | Department of Employment Secur… | new tab | Add '(opens in new tab)' to text |
| https://yallbusiness.sos.ms.gov/Home/Res… | Start Up Resources | new tab | Add '(opens in new tab)' to text |
| http://www.mississippi.org/ | Economic Development | new tab | Add '(opens in new tab)' to text |
| https://www.govloans.gov/categories/busi… | Search for Business Loans | new tab | Add '(opens in new tab)' to text |
| https://assistant.google.com/ | Google Assistant | new tab | Add '(opens in new tab)' to text |
| https://mdes.ms.gov/i-need-a-job/job-sea… | Job Opportunities | new tab | Add '(opens in new tab)' to text |
| https://www.hud.gov/states/mississippi | Public Housing Resources | new tab | Add '(opens in new tab)' to text |
| https://www.access.ms.gov/ | Mississippi Family Assistance | new tab | Add '(opens in new tab)' to text |
| https://www.mshomecorp.com/ | Get Help Buying a Home | new tab | Add '(opens in new tab)' to text |
| http://www.mrec.ms.gov/ | Mississippi Real Estate Commis… | new tab | Add '(opens in new tab)' to text |
| https://www.mdhs.ms.gov/child-support/ | Child Support Payments | new tab | Add '(opens in new tab)' to text |
| https://www.sos.ms.gov/yall-vote | Register To Vote | new tab | Add '(opens in new tab)' to text |
| https://www.ms.gov/dps/license_renewal | Driver License Renewal | img no alt | Add alt attribute to the image |
| https://www.ms.gov/mdwfp/licensing/login | Hunting & Fishing Licenses | img no alt | Add alt attribute to the image |
| https://www.ms.gov/msgov-kids | MS.GOV For Kids | img no alt | Add alt attribute to the image |
| https://www.mdwfp.com | Mississippi Outdoors | new tab | Add '(opens in new tab)' to text |
| https://www.ms.gov/msgov-mobile-apps | Featured Mobile Apps | img no alt | Add alt attribute to the image |
| https://ms.gov/industry | Start a Business | new tab | Add '(opens in new tab)' to text |
| https://www.ms.gov/msgov-connect | MS.GOV Connect | img no alt | Add alt attribute to the image |
| https://visitmississippi.org | Plan Your Trip | new tab | Add '(opens in new tab)' to text |
| http://www.mid.ms.gov/#&panel1-1 | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| https://governorreeves.ms.gov/ | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| https://ltgovhosemann.ms.gov/ | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| https://www.sos.ms.gov | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| https://attorneygenerallynnfitch.com/ | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| http://www.osa.ms.gov/ | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| https://www.treasury.ms.gov/Pages/defaul… | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| https://www.mdac.ms.gov/ | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| http://www.mid.ms.gov/#&panel1-1 | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| https://governorreeves.ms.gov/ | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| https://ltgovhosemann.ms.gov/ | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| https://www.sos.ms.gov | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| https://attorneygenerallynnfitch.com/ | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| http://www.osa.ms.gov/ | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| https://www.treasury.ms.gov/Pages/defaul… | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| https://www.mdac.ms.gov/ | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| http://www.mid.ms.gov/#&panel1-1 | Visit Official Website | new tab | Add '(opens in new tab)' to text |
| https://pluralpolicy.com/app/jurisdictio… | Legislation | new tab | Add '(opens in new tab)' to text |
| https://www.legislature.ms.gov/legislato… | Senators | new tab | Add '(opens in new tab)' to text |
| https://www.legislature.ms.gov/legislato… | Representatives | new tab | Add '(opens in new tab)' to text |
| https://www.lbo.ms.gov/Home/Publications | FYTD Revenue | new tab | Add '(opens in new tab)' to text |
| https://www.transparency.ms.gov/checkboo… | FYTD Expenditures | new tab | Add '(opens in new tab)' to text |
| https://www.transparency.ms.gov/checkboo… | FYTD General Fund Expenditure | new tab | Add '(opens in new tab)' to text |
| https://www.transparency.ms.gov/checkboo… | Appropriated Budget | new tab | Add '(opens in new tab)' to text |
| / | (empty) | empty | Add link text or aria-label |
| http://www.facebook.com/msdotgov | (empty) | empty | Add link text or aria-label |
| https://www.instagram.com/msdotgov | (empty) | empty | Add link text or aria-label |
| http://www.twitter.com/msdotgov | (empty) | empty | Add link text or aria-label |
| https://www.govtech.com/government-exper… | GovX 2025 Overall Winner | new tab | Add '(opens in new tab)' to text |
| http://www.transparency.ms.gov/ | Transparency MS | new tab | Add '(opens in new tab)' to text |
| https://www.surveymonkey.com/r/XCVGDZP | Take Our Survey | new tab | Add '(opens in new tab)' to text |
| https://www.research.net/r/L3KDB2G | Report Missing Content | new tab | Add '(opens in new tab)' to text |
Links without text are announced as raw URLs by screen readers.
/; /; /; /; /; http://www.facebook.com/msdotgov; https://www.instagram.com/msdotgov; http://www.twitter.com/msdotgov
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.
https://accessibe.com/blog/knowledgebase/screen-reader-guide; https://www.ms.gov/dfa/ace/W2EFTDispatcher; https://web.getgov2go.com/signin; https://uat-web.getgov2go.com/; https://www.ms.gov/dfa/ace/W2EFTDispatcher; https://web.getgov2go.com/signin/create-account; https://web.getgov2go.com/signin; https://www.mdek12.org/OAE/2019-Access-for-All-Guide; https://treasury.ms.gov/for-citizens/college-savings-mississippi/; https://www.msvcc.org/ (+64 more)
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
B404 Error PageHTTP 404, custom pageREVIEW
BFavicon & Branding27 icon(s) detectedREVIEW
CWeb ManifestActionValid manifestREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 20 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
4 contrast failures on background images/gradients
These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Welcome to the | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 State | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Mississippi | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Citizen Portal | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Mike Chaney | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Tate Reeves | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Delbert Hosemann | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Michael Watson | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Lynn Fitch | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Shad White | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 David McRae | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Andy Gipson | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Mike Chaney | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Tate Reeves | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Delbert Hosemann | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Michael Watson | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Lynn Fitch | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Shad White | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 David McRae | 2.48:1 | 3.0:1 | #000000 | #5C4848 | Fail |
| h1 Andy Gipson | 2.48:1 | 3.0:1 | #000000 | #5C4848 | 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.
BLighthouse Accessibility AuditsScore 82/100 — 6 failing, 25 passedREVIEW
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.
Names and labels
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.chat-widget > div.input-area > div.request-sender > button.send-icon div.chat-widget > div.input-area > div.request-sender > button.send-icon |
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.level-left > div.level-item > a > img.brand-image div.level-left > div.level-item > a > img.brand-image |
body.front-page-body > div.dialog-off-canvas-main-canvas > section#hero > img.hero-down-here body.front-page-body > div.dialog-off-canvas-main-canvas > section#hero > img.hero-down-here |
div#slick-slide00 > div.official-slide-card > div.official-image > img div#slick-slide00 > div.official-slide-card > div.official-image > img |
div > section#stats-section > div.text-align-center > img.star-bar div > section#stats-section > div.text-align-center > img.star-bar |
div.columns > div.column > a > img.footer-logo div.columns > div.column > a > img.footer-logo |
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.level > div.level-left > div.level-item > a div.level > div.level-left > div.level-item > a |
div.level > div.level-left > div.level-item > a div.level > div.level-left > div.level-item > a |
div.level > div.level-left > div.level-item > a div.level > div.level-left > div.level-item > a |
div.level > div.level-left > div.level-item > a div.level > div.level-left > div.level-item > a |
div.container > div.columns > div.column > a div.container > div.columns > div.column > a |
div.container > div.columns > div.column > a.button div.container > div.columns > div.column > a.button |
div.container > div.columns > div.column > a.button div.container > div.columns > div.column > a.button |
div.container > div.columns > div.column > a.button div.container > div.columns > div.column > a.button |
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.
Navigation
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
YOUR MISSISSIPPI STARTS HERE! div.container > div.columns > div.column > h3.subtitle |
5.3 div#block-msgov-homepagestatistics > div.stats-container > div.card > h3#count1 |
FYTD Revenue div#block-msgov-homepagestatistics > div.stats-container > div.card > h6 |
FYTD Expenditures div#block-msgov-homepagestatistics > div.stats-container > div.card > h6 |
FYTD General Fund Expenditure div#block-msgov-homepagestatistics > div.stats-container > div.card > h6 |
FYTD Electronic Transactions div#block-msgov-homepagestatistics > div.stats-container > div.card > h6 |
Procurement Opportunities div#block-msgov-homepagestatistics > div.stats-container > div.card > h6 |
Appropriated Budget div#block-msgov-homepagestatistics > div.stats-container > div.card > h6 |
State Contracts div#block-msgov-homepagestatistics > div.stats-container > div.card > h6 |
Open Meetings div#block-msgov-homepagestatistics > div.stats-container > div.card > h6 |
These are opportunities to improve keyboard navigation in your application.
Best practices
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.container > div.columns > div.column > a.button div.container > div.columns > div.column > a.button |
div.container > div.columns > div.column > a.button div.container > div.columns > div.column > a.button |
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.js html.js |
These items highlight common accessibility best practices.