fatherhoodgov.info Accessibility
fatherhoodgov.info Botability
fatherhoodgov.info Security
fatherhoodgov.info Usability
- Managed by: Department of Health and Human Services
- Status: 200
- Pages: 1 · Get full site scan
- Last scan: 6/24/2026
Grade / score
Standards
| Standards | Risk | Status |
|---|---|---|
|
Deprecated ARIA roles were not used Accessibility roles use current, supported values. |
Screen readers may not recognize deprecated roles, breaking navigation. | Active |
|
[aria-hidden="true"] is not present on the document <body> The page body is not hidden from screen readers. |
Screen readers cannot read any content on the page. | Active |
|
[role]s have all required [aria-*] attributes Accessibility roles include all required attributes so screen readers can describe the element. |
Screen readers cannot describe the state of interactive elements. | Active |
|
[role] values are valid Accessibility roles use valid, recognized values. |
Screen readers ignore invalid roles and treat elements as plain text. | Active |
|
Background and foreground colors have a sufficient contrast ratio Text and background colors meet minimum contrast ratios. |
Users with low vision cannot read your text. | Active |
|
Document has a <title> element The page has a descriptive title visible in browser tabs and search results. |
Screen reader users cannot identify or interact with elements. | Missing |
|
<frame> or <iframe> elements have a title Embedded frames have titles so screen readers can describe their content. |
Screen reader users cannot identify or interact with elements. | Active |
|
<html> element has a [lang] attribute The page declares its language so screen readers use the correct voice. |
Screen readers mispronounce content, confusing users. | Active |
|
<html> element has a valid value for its [lang] attribute The page has a valid language code so screen readers pronounce content correctly. |
Screen readers mispronounce content, confusing users. | Active |
|
Links have a discernible name Links have unique, descriptive text so users know where they go. |
Screen reader users cannot identify or interact with elements. | Active |
|
Lists contain only <li> elements and script supporting elements (<script> and <template>) Lists use correct markup so screen readers can announce them properly. |
Screen readers announce structured content incorrectly. | Active |
|
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements List items are nested inside a valid parent list element. |
Screen readers announce structured content incorrectly. | Active |
|
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5 The page allows users to zoom in on mobile devices. |
Mobile users with low vision cannot zoom in to read content. | Missing |
|
Touch targets have sufficient size and spacing Buttons and interactive elements are large enough to tap easily on touch screens. |
Users with motor disabilities struggle to tap small buttons. | Active |
|
Document has a main landmark The page has exactly one main content area so screen readers can navigate to it. |
Screen reader users cannot skip directly to main content. | Missing |
| presentation-role-conflict | Active | |
|
Image aspect ratio Images display at their intended proportions. |
Images look stretched or squished. | Active |
|
Valid doctype The page has a doctype declaration so browsers render it correctly. |
Browsers display your page wrong. | Active |
|
Character encoding The page declares its character encoding so text displays correctly. |
Special characters show up as weird symbols. | Active |
About accessibility
Meet WCAG standards so every type of user can use your website.
Why it's important
People with disabilities need equal access to information and services online.
Risks
- People with disabilities cannot use your site.
Guidance
What we use to grade accessibility:
Grades/scores
ScanGov
Grade / score
Standards
| Standards | Risk | Status |
|---|---|---|
|
Canonical Each page declares a preferred URL so search engines show the right link. |
Search rankings split across duplicate pages. | Active |
|
Link text Links use descriptive text that tells users and search engines where they go. |
Users cannot tell where links go. | Active |
|
hreflang Pages declare their language and region for international users. |
Users see pages in wrong language. | Active |
|
Crawlable The site allows search engines and AI agents to index its pages. |
Search engines cannot find your pages. | Active |
|
Content available in document The page's main content loads without requiring JavaScript. |
Bots cannot read your content. | Active |
|
GovernmentOrganization Schema.org type Homepage is marked up as an official government organization. |
Systems cannot verify you are an official government site. | Missing |
|
Robots valid The site has a robots.txt file that guides search engines. |
Search engines ignore your instructions. | Missing |
|
Sitemap XML The sitemap file uses the required XML format. |
Search engines cannot read your sitemap. | Missing |
|
Robots allowed The robots.txt file allows search engines and AI agents to crawl the site. |
Your site is blocked from search results. | Active |
|
Sitemap status The sitemap file loads and returns a successful response. |
Search engines cannot find all your pages. | Missing |
|
Sitemap in robots.txt The robots.txt file links to the sitemap. |
Search engines take longer to find your pages. | Active |
About botability
Help AI and search engines discover, crawl, and index your website.
Why it's important
Smart technology can better process and share public information, making services faster and more efficient for users.
Risks
- AI tools cannot find or understand your content.
Guidance
What we use to grade botability:
- 21st Century Integrated Digital Experience Act (IDEA)
- Memorandum (M-23-22)
- The Web Robots Pages
- Schema.org structured data
- sitemaps.org
- Google Search Central
Grades/scores
ScanGov
Grade / score
Standards
| Standards | Risk | Status |
|---|---|---|
|
Content security policy (CSP) The site has a policy that limits what external content can load on its pages. |
Hackers can inject bad code into your site. | Active |
|
HTTP Strict Transport Security (HSTS) The site forces an encrypted HTTPS connection for all users. |
Hackers can downgrade your connection and steal data. | Active |
|
Errors in the console The page loads without JavaScript or network errors. |
Site may have hidden bugs that break features. | Missing |
|
Clickjacking mitigation The site prevents other websites from embedding its pages to trick users into clicking. |
Hackers can trick users into clicking wrong things. | Active |
|
Paste preventing inputs The page lets users paste content into form fields. |
Users cannot use password managers safely. | Active |
|
Hypertext Transfer Protocol Secure (HTTPS) The site uses HTTPS to encrypt data between the server and users. |
Hackers can see and steal personal information. | Active |
|
Sponsored top-level domain (sTLD) The site uses a government-issued domain (.gov, .edu, or .mil). |
People cannot tell if your site is real government. | Missing |
|
security.txt The site has a security.txt file so researchers know how to report issues. |
Security researchers cannot report problems to you. | Missing |
|
X-Content-Type-Options The site tells browsers not to guess the type of files it serves. |
Browsers might run dangerous files by mistake. | Missing |
About security
Secure your site and protect users with proper security practices.
Why it's important
Strong defenses prevent hackers from stealing personal information and other confidential data.
Risks
- Hackers can steal private information from your site.
Guidance
What we use to grade security:
- CISA Website Security
- 21st Century Integrated Digital Experience Act (IDEA)
- CISA Cybersecurity Performance Goals
- Memorandum (M-23-22)
- RFC 9116
- OWASP Top 10
- U.S. Federal Website Standards
Grades/scores
ScanGov
Grade / score
Standards
| Standards | Risk | Status |
|---|---|---|
|
Page title The page has a unique, descriptive title shown in browser tabs and search results. |
Users cannot tell what your page is about. | Missing |
|
Page description The page has a meta description that summarizes its content for search results. |
Search results do not show what your page does. | Missing |
|
Viewport meta tag The page scales correctly on mobile devices and tablets. |
Mobile users see broken pages on their phones. | Active |
|
First Contentful Paint (FCP) The page starts displaying content within 1.8 seconds. |
Users see blank screen and think site is broken. | Missing |
|
Largest Contentful Paint (LCP) The page's main content loads within 2.5 seconds. |
Users wait too long and leave your page. | Missing |
|
Time to First Byte (TTFB) The server sends the first byte of content within 0.8 seconds. |
Slow server delays everything on your page. | Active |
|
Cumulative Layout Shift (CLS) Page content stays in place as the page loads. |
Users click wrong buttons by mistake. | Active |
|
Interaction to Next Paint (INP) The page responds to user interactions in under 0.2 seconds. |
Site feels frozen when users click things. | Active |
|
Open Graph site name The site has a name for social media and browser display. |
Site name missing in social media shares. | Missing |
|
Open Graph type The page declares its content type for social media cards. |
Social media shows wrong content type. | Missing |
|
Open Graph title The page has a title for social media previews. |
Shared links have no title on social media. | Missing |
|
Open Graph description The page has a description for social media previews. |
Shared links have no description on social media. | Missing |
|
Open Graph URL The page has a canonical URL for social media sharing. |
Shared links may point to wrong page. | Missing |
|
Open Graph image The page has a preview image for social media cards. |
Shared links have no image on social media. | Missing |
|
Open Graph image alt The social media preview image has alt text for screen readers. |
Screen readers cannot describe shared images. | Missing |
|
Readability Page content is written at a reading level most users can understand. |
People struggle to understand your content. | Active |
|
www resolution The site works whether users type www or not. |
Users get errors when typing your web address. | Active |
About usability
Optimize content structure so users quickly find what they need.
Why it's important
Well-written pages help people understand laws, services, and procedures without confusion, reducing calls and office visits.
Risks
- Users cannot understand your information.
Guidance
What we use to grade usability:
- 21st Century Integrated Digital Experience Act (IDEA)
- U.S. Federal Website Standards
- Memorandum (M-23-22)
- Automated Readability Index (ARI)
- Flesch-Kincaid (FK)
- Plain Writing Act of 2010
- Google Search Central
- Web Vitals / Core Web Vitals
- Open Graph