Notes for using an Accessibility Statement Generator

The accessibility statement for your website can be as simple as you’d like.

If you don’t know where to start, an accessibility statement generator can be helpful. If you’re using a statement generator like Siteimprove.com, here are some notes to help you fill out that form.

We are NOT accessibility law experts. We implement best practices based on our knowledge and depend highly on our assessment tools. Always seek legal advice from an expert and decide internally how to answer each of the form’s questions.

A survey question asks about the accessibility standard a site adheres to, with options: WCAG 2.1 level AA, WCAG 2.0 level AA, Unknown, and a fill-in-the-blank "Other" option.

Answer notes

Orbit takes a realistic, accessibility-first approach to web design and development, with the goal of building a site that is tested for WCAG 2.2 AA compliance.

You may have requested another level of accessibility. This would go into the “Other” category.

Accessibility conformance status with options. "Partially conformant" is selected, indicating some content does not fully meet accessibility standards. Other options are "Fully," "Non," and "Unknown.

Answer notes

Choose the option that best aligns with your assessment of the new website’s accessibility conformance.

This is often “Partially conformant” because Orbit only tests a short list of key pages and features.

To be fully conformant, every URL on your website would need to be scanned and tested by a testing tool.

Screenshot of an accessibility issues form with fields for the title and description of the issue. There's a button labeled "Add another issue" at the bottom.

Answer notes

As we’ve guided you throughout the process, we’ve given you insight into what accessibility risks are possible for the pages we test and for unique features and functionality. Use those notes to complete this answer. Submit all issues individually.

Input field for listing compatible browsers, with an example showing Internet Explorer (Windows) versions 7.0 to 9.0. There is an option to add another browser.

Answer notes

We test your website on multiple browsers, devices, and screen sizes. Currently, Chrome, Safari and Edge are the most popular browsers. We test on the most recent versions of these browsers.

However, we test based on what your users use to access your website, and we gather this information from Google Analytics.

We document browser and device traffic in the Content Workbook so we know what to test when it comes time to test.

Form field for listing tested assistive technologies, with an example given and an option to add another technology.

Answer notes

We test with one or more of the following assistive technologies:

  • VoiceOver
  • NVDA
  • TalkBack
Form with checkboxes for technologies: HTML, WAI-ARIA, CSS, Javascript, SMIL. Includes a text field labeled "Other technology 1" and a button to "Add another technology".

Answer notes

Orbit builds sites with the following technologies:

  • HTML
  • WAI-ARIA
  • CSS
  • Javascript

However, your 3rd party resources and embedded tools may use other technologies. It is recommended that you gather details from your vendors and include them in your answer.

Form displaying assessment method options for site evaluation: self-evaluation, external evaluation, and an option to add another method in a text field.

Answer notes

Orbit plans, designs, develops, and conducts the accessibility audit for the key page templates.

Your team is responsible for conducting accessibility tests and assuring all pages meet the desired accessibility criterion.

If you plan to hire a 3rd party to conduct further testing, check all applicable boxes.

Text box requesting a link to any recent accessibility evaluation reports with an example URL provided.

Answer notes

This depends on the tools you used for testing (i.e., siteimprove.com or accessibleweb.com) and how comfortable you are with sharing the results of your evaluations.