Brandcast can be used to create websites that meet Web Content Accessibility guidelines as specified by the W3C. Because Brandcast is a tool that can be used to build any kind of website, much of the responsibility for this will lie in the hands of the designer actually building the site. 

The Brandcast platform gives designers the flexibility to meet all accessibility requirements up to level AA of the Web Content Accessibility Guidelines:

  • Brandcast can support text alternatives (alt-text) for all images and media. It is incumbent on the designer to add the alt-text for whatever media they include in the page.

  • Brandcast supports the use of standard text tags (<p>, <h1>, etc.) that the designer can use to designate page structure, relationships, and section headings. The actual content is of course up to the designer.

  • The color, size, and borders of all elements on the page can be customized by the designer to create the desired contrast ratio.

  • The behavior of all interactive elements (hover states and animations) is fully customizable by the designer in terms of their visual appearance, animation, and timing. The target size of an interactive element can also be determined by the designer.

  • The visual presentation of text (size, color, width, leading, and alignment) can be fully controlled by the designer. Text can be resized by the end user via standard browser-side zoom controls.

  • All Brandcast markup is well-formed: elements have complete start and end tags, elements do not contain duplicate attributes, and any IDs are unique.

  • All Brandcast sites can be designed to be responsive, so they are not locked to a specific display orientation or display size.

  • If audio or video media is added to the page, it’s incumbent on the designer to add captions, sign language interpretation, etc. to those media, outside of the Brandcast platform before the media is uploaded.

  • If the designer uses an embed element to place content in a Brandcast site via a third-party, such as a form, that content’s accessibility will be dependent on the particular third-party used to serve the content. (Brandcast currently does not natively support forms or other kinds of user input elements.)

Did this answer your question?