The IntelligenceBank platform is a web-based service with dynamic content. It is regularly audited against key accessibility standards, as defined by the Web Content Accessibility Guidelines (versions 2.0 and 2.1).
IntelligenceBank is committed to optimizing its platform to ensure that it meets Level A and Level AA guidelines whenever possible, noting that in some cases, full compliance may be dependent on the content created or uploaded by the Client.
Core Development Principles
The following code guidelines are at the heart of the IntelligenceBank product and drive all our development practices:
- All elements can be accessed via keyboard navigation (tab).
- There are no time-based limitations.
- Tabbing follows a logical order.
- Interactive controls are keyboard focusable.
- User focus and keyboard navigation cannot be trapped in a region.
- Page areas are clearly delimited and can be jumped to via shortcuts (e.g. Navigation menu). Use semantic html, skip shortcuts, and HTML5 landmark elements.
- All non-text content such as images or icons have meaningful alternative text.
- Headers are used in a hierarchical manner and reflect the page structure and its key areas.
- All form fields have a label clearly associated with the input.
- All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies.
- Interactive elements indicate their purpose and state.
- Native HTML should be used whenever possible as these elements can have functions in-built for supporting accessibility. When native HTML cannot be used, ARIA features should be used.
- <frame> and <iframe> elements should have a Title.
- Links should have a discernible name.
- Background and foreground colors should have sufficient control ratio. Add tool here.
- Zooming should not be disabled
- Visual order on the page follows DOM order.
- Offscreen content is hidden from assistive technology.
- Developers should use ARIA states to indicate the state of UI widget elements and use CSS attribute selectors to alter the visual appearance based on the state changes (rather than using script to change a class name on the element).
Accessibility compliance testing is part of any new development and is conducted via a variety of tools, which include: