Skip forward into hiring notes
RosterAcorn

Federal hiring software accessibility: 4 Access Board rules

Federal hiring software that has a user interface or transmits information must conform to E207 and Chapter 5 of the Access Board's Revised 508 Standards. The exception covers assistive technology that supports the platform's accessibility services, which is exempt from Chapter 5 and from E207.2. Recruiters and small staffing teams can sort any applicant tracking tool against these rules, plus the Level A and AA requirements for user interface components, before they buy or approve it.

Sharp takeaways

  • Hiring software with a user interface, or software that transmits information, must conform to E207 and Chapter 5.
  • Assistive technology that supports the platform's accessibility services is exempt from Chapter 5 and from E207.2.
  • User interface components and platform content must conform to WCAG 2.0 Level A and Level AA.
  • Agency support documentation and services for ICT must conform to Chapter 6.

Chapter 5 covers software with a user interface

The first rule to check comes from the U.S. Access Board's Revised 508 Standards. The standards say that where components of information and communication technology (ICT) are software and transmit information or have a user interface, "such components shall conform to E207 and the requirements in Chapter 5" ( Revised 508 Standards and 255 Guidelines).

Read that sentence as a two-part test. Software qualifies if it transmits information, or if it has a user interface. The word "or" matters, because meeting either condition is enough. An applicant tracking tool may meet both, depending on its design. Applicants and recruiters work through screens, and resumes, application answers, and status changes move between the system and other systems the agency uses.

That makes the test useful in a vendor conversation. Ask which parts of the product have a user interface, such as an applicant portal, a recruiter dashboard, or an interview scheduler, and which parts pass information between systems. Each part that qualifies falls under the requirement to conform to E207 and Chapter 5. A vendor who answers only about the public careers page has not addressed the recruiter screens.

The trigger is what the component does. For a review, sort each module by the two triggers and record which ones apply. That gives you a list you can check against the vendor's accessibility documentation.

The assistive technology exception

The same Access Board page includes one exception that matters for hiring tools. It reads: "Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to the requirements in Chapter 5" ( Revised 508 Standards and 255 Guidelines).

The exception has two conditions, joined by "and." The software must be assistive technology, and it must support the accessibility services of the platform. Both must be true. Assistive technology is software that helps a person with a disability use a computer or device, and a screen reader is a common example. For more on how the standard reads its terms, see defined terms. The exception covers software that serves the platform's accessibility services. It does not cover a hiring system that simply runs on the same platform.

A common error in reviews is treating the exception as a general accessibility pass. An applicant tracking tool that works well with a screen reader is still not assistive technology. Its job is to manage applications, not to help a person read the screen. Accessibility features built into the hiring tool itself therefore remain under Chapter 5.

For a recruiter, the question is narrow. When a vendor says its product is exempt because it is accessible, ask whether the product is the assistive software itself or a hiring system that works with assistive software. Only the first fits the exception. The second must meet Chapter 5 for its own user interface, and the exception provides no shelter for it.

Comparison table: which rule applies to which tool

The table lists the four provisions covered above, using the Revised 508 Standards and 255 Guidelines as the source.

Software or supportWhat the Access Board requires
Hiring software with a user interface or that transmits informationConformance to E207 and Chapter 5
Assistive technology that supports platform accessibility servicesExempt from Chapter 5 and from E207.2
User interface components and the content of platforms and applicationsConformance to WCAG 2.0 Level A and Level AA
Agency-provided support documentation or services for ICTConformance to Chapter 6

Read the first row first. Hiring software is covered by Chapter 5 and by E207, and its user interface and content also fall under the WCAG 2.0 Level A and AA requirement. The second row shows that the exception is narrow. Assistive technology is exempt from Chapter 5 and from E207.2 only, so the rest of E207 still applies.

The fourth row is a different kind of requirement. Agency support documentation and services fall under Chapter 6, which has its own section below. Keeping the rows separate prevents a common mix-up, in which a vendor's exemption for one product is treated as an exemption for the whole package.

Level A and AA criteria in WCAG 2.0

The second half of the standard sets a content requirement. It reads: "User interface components, as well as the content of platforms and applications, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1)" ( Revised 508 Standards and 255 Guidelines).

The sentence covers two things. The first is user interface components, meaning the parts of a screen that people operate, such as forms, menus, and buttons. The second is the content of platforms and applications, which in a hiring setting includes job postings and application questions published through the system. Both fall under the same requirement.

The sentence names both Level A and Level AA. Meeting only Level A does not satisfy it. A vendor that offers a statement covering Level A alone has not answered the requirement. Ask for a conformance statement that names both levels.

The phrase "incorporated by reference" explains how the standard works. Rather than copying the full WCAG 2.0 text into the Access Board's rules, the standard points to it, and the reference is made at section 702.10.1. When you read a vendor's report, the success criteria it cites are the WCAG 2.0 criteria at those two levels. Reports that cite other criteria or a different structure need to be matched back to these levels before you can rely on them.

Why later WCAG versions keep existing criteria

Vendors often describe their products as meeting WCAG without naming a version, and newer versions of the guidelines appear over time. The World Wide Web Consortium's overview addresses how those versions relate to one another. It says: "Later versions add new success criteria, and do not change existing success criteria" ( WCAG 2 Overview).

That sentence has a direct effect on how you read a conformance claim. A success criterion from WCAG 2.0 keeps its meaning in later versions, because existing criteria are not changed. Newer versions add to the list rather than rewriting it. The 2.0 Level A and AA criteria that the Access Board names are not changed in a newer version, which only adds new criteria.

In a review, this means a claim of conformance to a newer version still needs to be tested against the 2.0 criteria. Ask which version the vendor tested against, and whether its report lists the 2.0 Level A and AA criteria by name. A report that says "meets WCAG" with no version or level gives you nothing to check against the Access Board's requirement. A report that names the criteria gives you a list you can match to the WCAG 2.0 Level A and AA criteria by number.

The E207.2 reference for assistive software

The Access Board's standard includes a second exemption that is worded separately from the first. It reads: "Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to E207.2" ( Revised 508 Standards and 255 Guidelines).

The two exemptions point to different provisions. The Chapter 5 exemption covers the chapter as a whole. The E207.2 exemption names one specific section. Both apply only to assistive technology that supports the platform's accessibility services, so the conditions are the same, and the reach is different. Read the two together and you see that the exemption is specific by section number.

Because the exemption names E207.2 by number, the rest of E207 is not waived. This is why the comparison table lists E207 as required for assistive technology with the single exception of E207.2. Any vendor statement that a product is exempt from accessibility standards needs to be matched against the named sections. A general claim of exemption does not correspond to either exemption in the standard.

Support documentation must meet Chapter 6

The Revised 508 Standards also reach the material around the software, not only the screens. The Access Board's text says: "Where an agency provides support documentation or services for ICT, such documentation and services shall conform to the requirements in Chapter 6" ( Revised 508 Standards and 255 Guidelines).

The trigger is the agency's own action. The sentence applies when an agency provides support documentation or services for information and communication technology. In a federal hiring process, that can include the user guide a hiring manager gives to panel members, the instructions posted for applicants, the help line the agency staffs, and any training the agency runs on the tool. If the agency produces or delivers these materials, they fall under Chapter 6.

Vendor documentation raises a related question. The quoted sentence speaks to what the agency provides. Ask the vendor which documents it would supply, and confirm with your agency which ones it will hand to users.

The sentence above requires agency-provided support material to conform to Chapter 6, so read the chapter itself before you test anything. For a review, list every document and service the agency will provide with the tool, and check each item against the chapter. A hiring interface can meet its requirements while the applicant help page does not, so the list is worth making.

Error alerts that tell users how to fix errors

Hiring forms produce errors constantly: a date typed in the wrong format, a required field left blank, a file of the wrong type. The U.S. Department of Justice's guidance on web accessibility and the ADA addresses how these errors should be handled. It says the guidance includes "clearly identifying what the error is and how to resolve it (such as an automatic alert telling the user that a date was entered in the wrong format)" ( Guidance on Web Accessibility and the ADA).

The sentence names two parts of a useful error message. The first tells the user what went wrong. The second tells the user how to fix it. A message that only says "invalid entry" addresses neither part clearly. The example is a date entered in the wrong format, reported by an automatic alert. That example suits applicant forms well, because date fields for work history and availability are common.

ElementCountExample in the guidance
Parts of an error message the guidance names2What the error is; how to resolve it
Example alert given1 Date entered in the wrong format

This is Department of Justice guidance, so read it as an explanation of what clear error handling includes. For an applicant portal, test it directly. Submit deliberate errors on each form type, such as a wrong date format and an empty required field. Then check whether each message names the problem and the fix, and whether the alert appears when the error occurs, as the example describes. For more on form checks, see accessible job application forms.

Which one should you pick?

When two or three tools look similar, choose the one whose vendor can show evidence against the rules in this post. A longer feature list does not answer the accessibility question. The rules give you a short list of things to compare, and each vendor should be able to answer all of them.

The most useful evidence is a conformance statement that names the criteria. The Access Board requires user interface components and content to meet WCAG 2.0 Level A and Level AA ( Revised 508 Standards and 255 Guidelines). A vendor whose report says only "WCAG compliant" leaves you nothing to verify. A report tested against a newer version should still list the 2.0 criteria by number. For a fuller set of vendor checks, see vendor hiring-tool claims.

Question to settle before choosingFigure from the quoted rulesBasis
Conformance levels the user interface and content must meet2 (Level A and Level AA)Access Board, WCAG 2.0 reference
Conditions an assistive software exemption must meet2 (assistive technology, and support for platform accessibility services)Access Board exception
Chapter governing agency-provided support documentation1 (Chapter 6)Access Board

Choose the tool that answers all three questions with specific evidence. If two tools both pass, use the error-message test from the previous section. Submit deliberate errors and compare how each tool explains the problem and the fix. The tool whose messages do both is the stronger choice for applicants who make mistakes on their first attempt.

Checklist for reviewing an applicant tracking tool

Work through these steps with the vendor's documents in front of you.

  1. Sort each module by the two triggers. If a component has a user interface or transmits information, it must conform to E207 and Chapter 5. Record which modules qualify.
  2. Test any exemption claim. Assistive technology is exempt only if it is assistive software that supports the platform's accessibility services, and both conditions must hold. A hiring system that merely runs on an accessible platform does not qualify ( Revised 508 Standards and 255 Guidelines).
  3. Request a named conformance statement. Ask for Level A and Level AA results for the user interface and content, with WCAG 2.0 criteria listed by number. A report that cites only "WCAG" with no version or level gives you nothing to check against that requirement.
  4. List the agency-provided documents and services. Check each one against Chapter 6.
  5. Test error handling directly. Enter deliberate errors on each form, then confirm that the message identifies the error and explains how to fix it ( Guidance on Web Accessibility and the ADA).
  6. Write down what you checked. Note the version of each vendor report, the date it was issued, and which modules and documents it covers.

Next step today: take the vendor documents you already have and run checklist steps 1 and 2 on them before your next meeting.

Related guides: 3 federal rules for immigration-related hiring charges · Age discrimination: 8 hiring and benefits rules · California fair chance hiring: 3 rules to check.

Reader questions

Does a vendor's claim of a newer WCAG version satisfy the Access Board's requirement? Only if its report also shows the WCAG 2.0 Level A and Level AA criteria by name. The Access Board names WCAG 2.0, and the World Wide Web Consortium says later versions add criteria without changing existing ones ( WCAG 2 Overview).

Is "WCAG compliant" enough on a vendor's sales sheet? Not for a review. A claim with no version and no level cannot be checked against the 2.0 Level A and AA requirement. Ask for the criteria by number.

Does an error message need to say how to fix the problem? Yes. The Department of Justice guidance describes clear error handling as naming the error and how to resolve it ( Guidance on Web Accessibility and the ADA). A message that names only the problem leaves out the second part.

How can I test error messages without relying on the vendor's word? Enter deliberate errors in each form, such as a wrong date format and an empty required field. Check whether each message says what went wrong and how to fix it ( Guidance on Web Accessibility and the ADA).

Does the error guidance apply only to dates? No. The example in the guidance is a date, but the sentence describes errors in general terms. Apply the same test to every required field and upload ( Guidance on Web Accessibility and the ADA).

Sources