Skip to main content
Skip table of contents

Request support from the VA Section 508 Office

The VA Section 508 Office validates compliance with federal law mandating accessible information and communication technology.

For VFS teams working on, that means they review documents and audit your product when you’re ready for launch. Product teams working on authenticated pages and applications are required to submit a VA Section 508 Office Audit Request. We prefer that you submit your request before launch, but you may still launch while you wait for the results of your audit. If you launch before submitting your audit request, please submit one as soon as possible.

Document Review

Do you have a document (PDF, Word, etc.) that needs to be reviewed for accessibility? This work is out of scope for Platform, however the VA 508 Office can help you out. Follow the below steps.

  1. On the VA Network, click on the YourIT! shortcut. Should open a browser and land on the home page.

  2. In the search box, enter "508 audit request" and click on the top result. Top result should be "508 Accessibility Audit Request"

  3. You'll get an input form to enter relevant data. At the bottom select "Documents" from the Product Type dropdown

  4. Enter your 508 office contact. If you do not have a regular contact, ask the Product Support Team for a reference.

  5. Upload the document from your machine. (May have to download it from the web first)

  6. You should receive a confirmation email with your ticket number linked

Audit Request

All VFS teams are required to submit a VA 508 Office Audit Request, whether accessibility issues were found during the Collaboration Cycle Staging Review or not.

Follow the steps below to send your product to the VA 508 office for review: 

  1. Sign in to the VA network. This ensures that your service request is linked to your VA email and credentials.

  2. From your VA desktop, navigate to the VA Service Portal at

  3. Select “Submit a Request” option.

    Heading that says Welcome to yourIT Service Portal and two large buttons. The first button says Is something broken Report an Issue. The second button says Need something new Submit a Request.

    Call-to-action options in the VA Service Portal landing page.

  4. On the next screen, under Technical Services Catalog menu (left hand side), select 508 Accessibility. If you see the Standard Services Catalog instead of the Technical Services Catalog, use the Technical Catalog toggle beneath the catalog menu to switch to the correct menu.

    Technical Services Catalog list. 508 Accessibility is highlighted as the first item in the list.

    Navigation menu for items in the Technical Services Catalog.

  5. On the next screen, select the option for 508 Accessibility Audit Request.

    Heading that says 508 Accessibility, followed by a service option labeled 508 Accessibility Audit R. The rest of the text is cut off. A description for this option says Audit your sites and applications to be 508 accessibility compliant.

    Catalog listing for 508 Accessibility Audit Request.

  6. Fill out the form with the relevant data for your request.

    1. In the “Are you submitting this request on behalf of someone else?” field, select Yes.

    2. In the “Requested For” field, select the name of the OCTO Accessibility Lead, Martha Wilkes.

    3. In the “Requested For Phone Number” field, enter Martha’s phone number. You can find this on her Slack profile.

    4. In the “Requested For Location” field, enter “VACO.”

    5. In the “Name of Item” field, enter the name of your product.

    6. In the “VA Organization” field, select the organization where your VA product owner lives.

    7. In the “VA Project Manager” field, select your VA product owner.

    8. In the “Description of item to be audited” field, provide:

      1. A brief description of your product.

      2. A description of the scope of what should be reviewed. Indicate the URL(s) they should start from when testing your product, and what sections of the product have changed as part of this work (if applicable).

      3. A statement that automated testing was completed using axe DevTools and either:

        1. State that no issues were detected within the scope of your product, or that all detected issues were resolved.

        2. If issues remain unresolved, copy the issue descriptions provided by axe DevTools and provide any other relevant information.

      4. Links to any accessibility testing artifacts submitted as part of your most recent Staging Review.

      5. Links to any open accessibility feedback issues created for your product as part of Staging Reviews. These GitHub issues will have a label a11y-defect-# where # is a number from 0 to 4.

    9. In the “Did the product team do any documented 508 testing of the product for this release?” field, select Yes.

    10. In the “Product Type” field, select Web Hosted Applications.

    11. In the “URL for auditing” field, enter either a or URL.

    12. In the “Is this a re-audit?” field:

      1. Select Yes if this is an update to an existing product that has previously been audited by the Section 508 Office.

      2. Select No if this is a new product that has never been audited by the Section 508 Office.

    13. In the “Is this a COTS Product?” field, select No.

    14. In the “Please describe the access requirements for auditors” field, provide any test user credentials or user requirements for reviewing the product.

  7. Submit your request by clicking the “Order Now” button. This will put your request into the VA 508 ticket queue and routed to the appropriate person for that product.

After your request

The Section 508 Office will follow up with you to request any additional information needed to complete their audit. They will reply via email with the results of the audit once their work is complete. Their findings will be categorized into severity levels that are consistent with Platform’s accessibility defect severity rubric.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.