This site has been designed with the aim of meeting, and in some cases exceeding, the success criteria of the WCAG 2.2 AA. In some instances, the Google Site CMS has areas of poor or missing accessibility support. Those areas of non-conformance are listed here along with any known workarounds.
Google Sites only allows H1, H2, and H3 headings. There is no support for H4, H5, and H6.
The most appropriate heading is used throughout the site that Google Sites allows. In this section, for example, the accordion header is H3, and topics inside have headings that are also H3. It would be conforming to have the headings inside the accordion at H4, but the CMS will not allow for this. As of November 15, 2025, a ticket has not yet been raised with Google regarding this matter.
When using iFrame components, such as Slides, Sheets, Forms, Charts, Maps, Calendars, YouTube, and the Embed from the Web feature, Google Sites does not add the <title> attribute to the iFrame.
Headings are used prior to the insertion of any iFrame that describes the purpose and content of the iFrame.
The image carousel component assigns an aria-label to a <div>, which is not permitted according to the WAI-ARIA implementation guidelines.
Some screen readers may not read the description of "image carousel" when encountering the image carousel due to a lack of support for reading aria-labels on non-interactive elements. The presence of a next and previous button should provide the necessary context for screen reader users, though.
Google Sites does create landmarks, but with some known issues:
The landmark structure of this site is created by Google Sites as:
banner [banner]
banner [banner]
navigation [navigation]
main [main]
contentinfo [contentinfo]
contentinfo [contentinfo]
There should be one banner region with the navigation landmark inside it. The main landmark should be all the other content on each page up to the footer. There should only be one contentinfo/footer landmark.
The Main landmark contains only the H1 of the page, whereas it should contain all the content from the banner to the footer. The decision to put the H1 in the focus order is within the range of conformance, but it would be preferable if the convention of having the first interactive item receive focus on the second tab were followed.
Google Sites SHOULD have all the main content contained in the Main landmark. However, the tool only captures the H1 of the page in the main landmark.
The navigation, main, and footer landmarks can be navigated to via a screen reader. Headings are used throughout the site to facilitate additional navigation. As of November 15, 2025, a ticket has not yet been raised with Google regarding this matter.
When adding animated GIFs to a Google Site page, there is no way to add a pause button to the motion, and the animation does not honor a user's preferred reduced motion accessibility settings.
None.
Google Sites does not allow authors to mark logos used in the header as decorative; instead, it forces users to add alternative text to the image. In instances where the logo is presented without additional text, this is conforming. In instances where the logo is presented as visual interest and the adjacent text provides the necessary information, the image should be marked decorative.
In instances where the site uses a logo in the header in addition to text, a short and concise description will be provided that complements the text as best as possible.