When Federal Privacy Meets Accessibility: The NLRB's SORN Problem

Jamie
section 508federal accessibilitywcag 2.1public comment accesstitle ii

Jamie · AI Research Engine

Analytical lens: Strategic Alignment

Small business, Title III, retail/hospitality

AI-assisted · Source-linked · Editorially reviewed · Methodology

Trust note

This article was drafted with AI assistance, reviewed against accessibility.chat editorial standards, and should be treated as research and education rather than legal advice. We prioritize primary sources and correct material errors.

Bright and stylish modern office interior featuring wooden partitions and elegant decor.
Photo by Capture Crew on Pexels

The Federal Register's comment portal has twelve input fields, multiple dropdowns, a file upload mechanism, and a comment submission form that serves as the public's primary channel for responding to federal rulemaking. On November 23, 2026, the National Labor Relations Board published a Privacy Act System of Records Notice — a document that directly governs how worker complaint data, labor dispute records, and personally identifiable information gets collected, stored, and used by a federal agency with significant power over the lives of working people.

The question worth sitting with: how many of those workers could actually read it, comment on it, or meaningfully participate in the public comment process?

The Access Problem Hidden Inside a Privacy Notice

Privacy Act System of Records Notices (SORNs) are required under 5 U.S.C. § 552a (opens in new window) to be published in the Federal Register, giving the public 30 days to comment before a new records system goes live. The NLRB's November 2026 notice follows this standard process. What's less standard — and what rarely gets examined — is whether the comment infrastructure itself meets federal accessibility requirements.

The FederalRegister.gov platform is a federal digital service. That means it's governed by Section 508 of the Rehabilitation Act (opens in new window), which requires federal electronic and information technology to be accessible to people with disabilities. The comment form described in this notice — with its multi-field structure, dropdown state selectors, file upload functionality, and character-count approximation — represents exactly the kind of interactive web application where accessibility failures concentrate.

This isn't a hypothetical concern. Research consistently shows that automated testing catches at most 37% of real accessibility barriers in complex web applications. A form that passes automated scans can still fail a screen reader user at the file upload button, a keyboard-only user at the state dropdown, or a cognitive disability user at the character-count approximation that provides no real-time feedback.

Who Files Comments with the NLRB?

The community dimension here matters more than it might first appear. The NLRB handles unfair labor practice charges, union election disputes, and worker retaliation claims. The workers most likely to be directly affected by NLRB data systems — and therefore most interested in commenting on a SORN — include:

  • Workers in physically demanding industries (construction, agriculture, manufacturing) with higher rates of occupational disability and injury
  • Workers with limited English proficiency who may also rely on assistive technologies or accessible formatting
  • Older workers who are disproportionately represented in labor disputes and also more likely to use accessibility features
  • Workers who have experienced retaliation and may be navigating the comment process under stress, making cognitive accessibility features more critical, not less

The ADA's Title II requirements (opens in new window) apply to federal agencies through Section 504 of the Rehabilitation Act and Section 508. When a federal agency publishes a notice inviting public comment, that invitation carries an implicit obligation: the mechanism for responding must be accessible to the people being invited.

The Structural Tension in Federal Digital Publishing

FederalRegister.gov itself acknowledges a layered complexity. The site describes itself as a "prototype" of a Web 2.0 Federal Register — not an official legal edition, pending ACFR sanction. Official legal status still resides with the PDF version on govinfo.gov. This creates an interesting accessibility split: the interactive, comment-enabled platform (FederalRegister.gov) may have different accessibility characteristics than the official PDF record on govinfo.gov.

PDFs present their own well-documented accessibility challenges. An untagged or improperly structured PDF — even one that is the official legal record — may be completely inaccessible to a screen reader user. The PDF/UA standard (ISO 14289) (opens in new window) exists precisely to address this, but federal agency PDFs vary enormously in their implementation of accessible tagging, reading order, and form field labeling.

This is the kind of multi-standard compliance challenge that creates real organizational paralysis: Section 508 governs the digital platform, WCAG 2.1 success criteria govern specific technical requirements, PDF/UA governs document accessibility, and the Administrative Procedure Act governs the comment process itself. No single office owns all of these simultaneously.

What Section 508 Actually Requires Here

For practitioners advising federal agencies or commenting on federal digital infrastructure, the specific obligations are worth mapping clearly:

RequirementGoverning StandardSpecific ObligationPrimary Citation
Comment form accessibilitySection 508 / WCAG 2.1 AAAll form inputs must have programmatic labels; error messages must be descriptiveWCAG 1.3.1, 3.3.1 (opens in new window)
File upload functionalityWCAG 2.1 AAUpload controls must be keyboard operable and screen-reader compatibleWCAG 2.1.1, 4.1.2 (opens in new window)
Character count feedbackWCAG 2.1 AAStatus messages must be programmatically determinable without focus changeWCAG 4.1.3 (opens in new window)
PDF legal documentsSection 508 E205Electronic documents must conform to PDF/UA where applicable36 CFR Part 1194 (opens in new window)
Dropdown state selectorsWCAG 2.1 AASelect elements must have accessible names and keyboard operabilityWCAG 1.3.1, 2.1.1 (opens in new window)
Alternative comment channelsSection 504 / ADA Title IIReasonable accommodations must be available for inaccessible digital processes29 U.S.C. § 794 (opens in new window)

The NLRB notice does reference Regulations.gov as an alternative comment channel — a meaningful accommodation signal, though only if that platform itself is accessible.

The Broader Pattern

What this NLRB notice illustrates is a systemic gap that runs through federal digital infrastructure: the obligation to publish is treated as separate from the obligation to ensure equal access to what's published. Agencies invest in regulatory compliance (publishing the SORN on time, following APA notice requirements) while the accessibility of the publication mechanism gets treated as an IT infrastructure problem owned by someone else.

This separation matters because settlement agreements and compliance mandates that focus narrowly on one layer of the problem — say, the website's homepage — often miss the transactional forms where real participation happens. A federal agency's homepage might be fully accessible while its comment submission form fails keyboard users at step three of five.

For accessibility professionals working in the federal space, this NLRB SORN is a useful case study in where to focus evaluation energy: not on the static informational pages, but on the interactive comment infrastructure that determines whether public participation is genuinely equal or nominally open.

What Practitioners Should Do With This

If you're advising federal agencies on Section 508 compliance, the NLRB situation points toward three concrete areas:

Audit comment and participation forms specifically. Generic site audits miss transactional forms. The manual testing methods that catch barriers automated tools miss are essential for multi-step submission workflows.

Map your alternative channels. Section 504 requires that inaccessible processes have accessible alternatives. If your digital comment form has barriers, the alternative (phone, mail, in-person) must be genuinely available and not buried in fine print.

Treat document accessibility as part of the notice obligation. If you're publishing a legal notice that affects people's rights, the PDF that constitutes the official record needs accessible tagging. This is not a separate project from regulatory compliance — it is regulatory compliance.

The 30-day comment window on the NLRB's SORN closes December 23, 2026. That deadline is the same for everyone. The question is whether the path to meeting it is equally open.

About the Jamie lens

A strategy lens for small business and Title III. Frames findings around cost, sequencing, and what a retail or hospitality operator can realistically act on first.

Jamie is an AI analyst lens, not a human staff member. It helps frame this article through a consistent accessibility perspective.

Specialization: Small business, Title III, retail/hospitality

View all articles using this lens →

Transparency Disclosure

This article was drafted with AI assistance and reviewed against our editorial methodology. We disclose that process so readers can judge the work clearly.