A
90%
| Standards | Risk | Status |
|---|---|---|
|
[aria-*] attributes match their roles Accessibility attributes are only used where they are supported. |
Screen readers ignore attributes that don't match the element's role. | Active |
|
ARIA attributes are used as specified for the element's role Accessibility attributes are only used when the element's role allows them. |
Screen readers ignore attributes used outside their allowed conditions. | Active |
|
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 |
|
[aria-hidden="true"] elements do not contain focusable descendents Interactive elements are not hidden from screen reader users. |
Keyboard users can focus elements that screen readers cannot announce. | Active |
|
Elements use only permitted ARIA attributes Accessibility attributes are not used where they are prohibited. |
Screen readers ignore prohibited attributes, hiding important information. | 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 |
|
Elements with an ARIA [role] that require children to contain a specific [role] have all required children Interactive groups contain all the child elements they need to work correctly. |
Screen readers cannot navigate grouped elements like menus or lists. | Missing |
|
[role]s are contained by their required parent element Interactive elements are nested inside the correct parent container. |
Screen readers cannot interpret elements outside their required container. | Active |
|
[role] values are valid Accessibility roles use valid, recognized values. |
Screen readers ignore invalid roles and treat elements as plain text. | Active |
|
[aria-*] attributes have valid values Accessibility attributes use valid values so screen readers can interpret them. |
Screen readers cannot interpret attributes with unrecognized values. | Active |
|
[aria-*] attributes are valid and not misspelled Accessibility attributes use valid, recognized names. |
Screen readers ignore misspelled or unrecognized attribute names. | Active |
|
Buttons have an accessible name Buttons have labels so screen readers can describe their action. |
Screen reader users cannot identify or interact with elements. | 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. | Active |
|
Heading elements appear in a sequentially-descending order Page headings follow a logical order without skipping levels. |
Keyboard users cannot efficiently navigate your site. | 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. | Missing |
|
Image elements have [alt] attributes Images have descriptive alt text or are marked as decorative. |
Screen reader users cannot identify or interact with elements. | Missing |
|
Form elements have associated labels Form fields have labels so screen readers can identify them. |
Screen reader users cannot identify or interact with elements. | Active |
|
Links are distinguishable without relying on color Links in body text are visually distinct from surrounding text, not by color alone. |
Users with low vision cannot read your text. | 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. | Active |
|
No element has a [tabindex] value greater than 0 The page uses natural keyboard tab order without manual overrides. |
Keyboard users cannot efficiently navigate your site. | Active |
|
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. | Active |
| autocomplete-valid | Active | |
| presentation-role-conflict | Active | |
|
Elements with visible text labels have matching accessible names A button or link's visible label matches what screen readers announce. |
Voice control users cannot activate elements by their visible label. | 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 |
D
63%
| 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. | Active |
|
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. | Missing |
D
66%
| 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. | Active |
|
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 |
C
70%
| 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. | Active |
|
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 |
|
Open Graph site name The site has a name for social media and browser display. |
Site name missing in social media shares. | Active |
|
Open Graph type The page declares its content type for social media cards. |
Social media shows wrong content type. | Active |
|
Open Graph title The page has a title for social media previews. |
Shared links have no title on social media. | Active |
|
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. | Active |
|
Open Graph image The page has a preview image for social media cards. |
Shared links have no image on social media. | Active |
|
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. | Missing |
|
First Contentful Paint (FCP) The page starts displaying content within 1.8 seconds. |
Users see blank screen and think site is broken. | Active |
|
Largest Contentful Paint (LCP) The page's main content loads within 2.5 seconds. |
Users wait too long and leave your page. | Active |
|
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 |
|
www resolution The site works whether users type www or not. |
Users get errors when typing your web address. | Missing |
8/22/2025