TL;DR: The 21st Century Integrated Digital Experience Act (21st Century IDEA), signed into law in December 2018, requires federal agencies to modernize public-facing websites, make them mobile-friendly and accessible, digitize paper-based forms, provide e-signature options where possible, and meet standards set by OMB. It works alongside Section 508 (accessibility) and Federal Acquisition Regulation requirements. OMB’s M-23-22 memorandum in 2023 reinforced and expanded these requirements. Implementation has been uneven across agencies, but the legal obligations are real and active.
The 21st Century Integrated Digital Experience Act - usually shortened to “21st Century IDEA” or “the IDEA Act” - is the closest thing the federal government has to a master statute governing the design and operation of agency websites. It was signed into law on December 20, 2018, with bipartisan support, and it is short by federal-legislation standards - barely four pages of text.
But its scope is wide, and its effect on how federal agencies have to think about their digital presence is significant. This post walks through what the law actually says, how it interacts with Section 508 and other federal requirements, what OMB has said about implementation, and what agencies still need to do.
What the Law Actually Requires
The IDEA Act contains a set of requirements that fall on every federal “executive branch agency” - which covers Cabinet departments, independent agencies, and most agencies most people interact with. The core requirements are:
1. Modernized Public-Facing Websites
Within 180 days of enactment, and ongoing, each agency must ensure that any new website or major redesign of a public-facing website:
- Is accessible to individuals with disabilities, in accordance with Section 508.
- Has a consistent appearance.
- Does not overlap with or duplicate the legitimate purposes of an existing site.
- Contains a search function.
- Uses an industry standard secure connection (HTTPS).
- Is designed around user needs with data-driven analysis.
- Provides users with the ability to provide feedback and follow up on their feedback.
- Is mobile-friendly.
That list essentially codifies a decade of digital service best practices into binding statute. Several of these (HTTPS, accessibility) were already required separately; the IDEA Act ties them together.
2. Digitization of Paper Forms
The Act requires agencies, in consultation with the Administrator of General Services and the Office of Management and Budget, to make all paper-based forms that are used for collecting information from the public available in a digital format. The goal is straightforward: nobody should have to print, fill out, and mail a form because the agency has not bothered to digitize it.
3. E-Signature Standards
The Act requires agencies to accept electronic signatures from the public, where possible, in accordance with the Electronic Signatures in Global and National Commerce Act (“E-Sign Act”) and the Government Paperwork Elimination Act.
4. Improvement of Digital Services
Each agency must make a plan to “accelerate the use of electronic signatures” and “improve the digital experience” for the public, including by upgrading systems and processes.
5. Reports to Congress
Agencies are required to report regularly to Congress on their implementation progress, including the number of forms digitized, the number of e-signatures accepted, and the percentage of public-facing websites that meet the Act’s standards.
How IDEA Interacts with Section 508
The IDEA Act references Section 508 of the Rehabilitation Act explicitly. Section 508, originally enacted in 1973 and most recently updated in the 2017 Section 508 Refresh, requires federal agencies (and federal contractors) to make their electronic and information technology accessible to people with disabilities. The Refresh harmonized Section 508 with WCAG 2.0 Level AA.
IDEA does not replace Section 508; it incorporates it as a baseline and adds requirements on top. A federal site that conforms to Section 508 is partway toward IDEA compliance but still needs to meet IDEA’s additional requirements for search, mobile-friendliness, user-centered design, feedback, HTTPS, and consistency.
A federal site that does not conform to Section 508 fails both. See our Section 508 vs. ADA Title II explainer for the relationship between Section 508 and the more recent ADA Title II rule for state and local government.
OMB Guidance
The IDEA Act assigns OMB a central coordinating role. OMB has issued several rounds of implementation guidance, including:
M-17-06 and M-19-21
These earlier memoranda predate IDEA but cover related ground - records management and digital service modernization. They remain in force.
M-23-22: Delivering a Digital-First Public Experience (2023)
This is the most important guidance to date. OMB Memorandum M-23-22, issued in September 2023, directly implements IDEA and sets concrete expectations:
- A redesigned, agency-wide approach to digital experience.
- Federal websites must meet standards around accessibility, mobile use, security, search, analytics, and user research.
- Forms must be available in digital format, with paper preserved only where required by law.
- E-signatures must be accepted unless a statute specifically prohibits it.
- Agencies must use the U.S. Web Design System or an equivalent design system that meets the same standards.
- Agencies must publish a list of their most important customer journeys and digitally enable them.
M-23-22 sets implementation deadlines that extend through 2025 and beyond and ties IDEA implementation into the President’s Management Agenda customer experience priority.
USWDS
The U.S. Web Design System (designstd.18f.gsa.gov) is the de facto reference implementation for IDEA-compliant federal websites. It provides accessible, responsive, Section 508-conformant components that agencies can adopt without rebuilding from scratch. M-23-22 effectively makes USWDS (or an equivalent) the standard.
How Implementation Has Gone
Honest answer: it has been uneven. A 2023 GAO report and subsequent reviews found that:
- Most agencies had made progress on HTTPS and basic accessibility, building on pre-IDEA work.
- Many agencies had only partially digitized their forms catalog, with significant numbers of forms still available only as PDFs that had to be printed and mailed.
- E-signature acceptance varied widely. Some agencies accept it universally; others accept it only for specific transactions.
- User-centered design practices and feedback loops varied even more, with some agencies running mature digital service teams and others outsourcing wholesale to vendors.
In other words: IDEA is the law, but agency capability to implement it varies. The agencies with strong digital service teams (USDS, 18F alumni, GSA’s Technology Transformation Services) are years ahead of agencies that lack that capacity.
What Agencies Still Need to Do
If you work for a federal agency or a federal contractor, the IDEA Act and M-23-22 together imply a fairly clear to-do list.
Inventory Public-Facing Sites
Make a list of every public-facing website your agency operates. You probably have more than you think - main agency site, subagency sites, program sites, microsites for specific initiatives, legacy sites that should have been retired. Each one is covered by IDEA.
Audit for the Basics
For each site, check:
- HTTPS enforced, with HSTS where appropriate (see our security headers guide).
- Section 508 conformance, with documented audits.
- Mobile-responsiveness across viewports.
- Functional search.
- Visible user feedback mechanism.
- Consistent agency branding.
Audit Your Forms
List every form on every site. Identify those still available only on paper or as fillable PDFs that the user must print, sign, and mail. Prioritize digitization based on volume and the importance of the underlying service.
E-Signature Adoption
Identify transactions that currently require a wet signature. For each, determine whether a statute actually requires a handwritten signature or whether the practice is bureaucratic inertia. Pursue e-signature adoption for everything not legally constrained.
Adopt or Equivalent USWDS
If you are not on USWDS or another design system that meets equivalent standards, this is the time. USWDS handles much of the Section 508 and IDEA work automatically, including accessible color palettes and keyboard-accessible components.
Customer Journeys
Identify the 10 to 20 most important customer journeys for your agency - the things residents most often try to do on your site. Map each one end-to-end. Where the journey hands off to a paper form, a phone call, or an in-person visit, plan the digital alternative.
Reporting
OMB and Congress get reports. Keep a running record of what you have digitized, how many e-signatures you process, and how your sites perform against the IDEA standards.
Where IDEA Does Not Reach
IDEA covers federal executive branch agencies. It does not apply to:
- State and local governments, which are covered by ADA Title II and applicable state law.
- The legislative or judicial branches, which have their own (less stringent) standards.
- Private entities, which are covered by ADA Title III if they are “public accommodations.”
- Federal contractors directly, although Section 508 procurement requirements pull contractors in through the Federal Acquisition Regulation.
For state and local equivalents, the 2024 DOJ ADA Title II rule is now the closest analog. State agencies should treat the DOJ rule as their baseline and consult our state government ADA obligations guide for specifics.
How This Connects to ADA, Privacy, and Security
IDEA is part of a much broader compliance picture for federal sites. A typical federal .gov site has to satisfy:
- IDEA (modernization, mobile, search, feedback, e-signature).
- Section 508 (accessibility).
- The Paperwork Reduction Act and Privacy Act.
- The Federal Information Security Modernization Act (FISMA).
- CISA Binding Operational Directives (HTTPS, KEV remediation, asset inventory).
- OMB memoranda on cookies, third-party services, customer experience, and zero trust.
These overlap and reinforce each other. A site that complies with IDEA’s HTTPS and accessibility requirements is partway to FISMA compliance and to ADA Title II conformance. A site that ignores them is failing on all fronts. See our broader government website compliance checklist for an integrated view.
What’s Next
IDEA is unlikely to be amended in the near term, but OMB will continue to update its implementation guidance. Several themes to watch:
- Customer experience metrics. Future guidance is likely to push specific quantitative metrics for digital service performance.
- AI and automation. Agencies are increasingly being pushed to use AI for customer service while satisfying transparency, accessibility, and security requirements.
- Identity and authentication. Login.gov and identity proofing remain a contested area, with implications for e-signature adoption.
- State and local equivalents. Several states (California, Washington, others) have IDEA-like statutes for state agencies. Expect more.
Monitor What You Modernize
A federal site that meets IDEA on launch day is not necessarily an IDEA-compliant site six months later. A new vendor widget that breaks mobile layout, a CMS update that removes HSTS, a new form added without an accessible HTML version - any of these can quietly push a site back out of compliance.
Govzu continuously monitors federal and other government websites for the underlying requirements that IDEA depends on - accessibility, mobile-friendliness, HTTPS, security headers, search availability, and form completeness - so federal teams can prove ongoing compliance and catch regressions before OMB, GAO, or the public finds them.