Smartdesigner™
Accessability Statement
Smartdesigner Voluntary Product Accessibility Template (VPAT)
This Voluntary Product Accessibility Template, or VPAT, is a tool that administrators and decision-makers can use to evaluate Smartdesigner conformance with the accessibility standards under US GCA's Section 508 of the Rehabilitation Act and WCAG 2.2. As well, Smartdesigner is conformant with the Directive (EU) 2016/2102 of the European Parliament and of the Council.WCAG 2.2 A & AA Conformance Report
This table below documents the conformance of Smartdesigner (including web content, electronic documents, software components, and authoring systems) with WCAG 2.2.Definitions
Content referrs to content created with Smartdesigner.Checker referrs to the in Smartdesigner built-in proactive WCAG 2.2 AA accessibility checking tool.
User referrs to the the end-user consuming the contentent created.
Principle 1: Perceivable. | ||
| Criteria | Conformance | Level Remarks & Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supported | Non-text content that is presented to the user has a text alternative that serves the equivalent purpose. Should non-text content lack alternative the checker will display a warning that the content is non-compliant, before publishing to the users. |
| 1.2.1 Prerecorded Audio-only and Video-only | Not Applicable | Prerecorded audio or video are neither provided by nor can such be authored in Smartdesigner. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | Prerecorded audio or video are neither provided by nor can such be authored in Smartdesigner. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | Prerecorded audio or video are neither provided by nor can such be authored in Smartdesigner. |
| 1.2.4 Captions (Live) | Not Applicable | Prerecorded audio or video are neither provided by nor can such be authored in Smartdesigner. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | Prerecorded audio or video are neither provided by nor can such be authored in Smartdesigner. |
| 1.3.1 Info and Relationships | Supported | Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. Should information be structurally inconsistent the checker will display a warning that the content is non-compliant, before publishing to the users. |
| 1.3.2 Meaningful Sequence | Supported | When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. |
| 1.3.3 Sensory Characteristics | Supported | Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound. |
| 1.3.4 Orientation | Supported | Content does not restrict its view and operation to a single display orientation, such as portrait or landscape. |
| 1.3.5 Identify Input Purpose | Supported | The purpose of each input field collecting information about the user can be programmatically determined. |
| 1.4.1 Use of Color | Supported | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. |
| 1.4.2 Audio Control | Not Applicable | Prerecorded audio or video are neither provided by nor can such be authored in Smartdesigner. |
| 1.4.3 Contrast (Minimum) | Supported | The visual presentation of text and images of text has a contrast ratio of at least 4.5:1. |
| 1.4.4 Resize text | Supported | Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. |
| 1.4.5 Images of Text | Not Applicable | Images of text are not provided by Smartdesigner. Users are responsible for accessibility of content they upload. |
| 1.4.10 Reflow | Supported | Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions. Content can be presented at 320x256 resolution without loss of information or functionality. |
| 1.4.11 Non-text Contrast | Supported | The visual presentation of graphical objects and user interface elements have a contrast ratio of at least 3:1 against adjacent color(s). |
| 1.4.12 Text Spacing | Supported | Smartdesigner users can change text style properties without loss of content or functionality. |
| 1.4.13 Content on Hover or Focus | Not Applicble | Additional content does not appear on keyboard focus or pointer hover. |
Principle 2: Operable. | ||
| Criteria | Conformance | Level Remarks & Explanations |
|---|---|---|
| 2.1.1 Keyboard | Supported | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes |
| 2.1.2 No Keyboard Trap | Supported | Focus can be moved to a component of the content page using a keyboard interface and focus can be moved away from that component using only a keyboard interface. |
| 2.1.4 Character Key Shortcuts | Not Applicable | No Keyboard Shortcuts exist when consuming content. |
| 2.2.1 Timing Adjustable | Not Applicable | Content does not time-out interface elements or content. |
| 2.2.2 Pause, Stop, Hide | Not Applicable | Content does not contain moving, blinking, scrolling, or auto-updating content that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content. |
| 2.3.1 Three Flashes or Below Threshold | Not Applicable | Content does not contain any blinking content. |
| 2.4.1 Bypass Blocks | Not Applicable | Content does not contain content that is repeated on multiple Web pages. |
| 2.4.2 Page Titled | Not Applicable | Content does not contain web pages with titles. |
| 2.4.3 Focus Order | Supported | Content can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. |
| 2.4.4 Link Purpose (In Context) | Supported | The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. |
| 2.4.5 Multiple Ways | Not Applicable | Content does not contain multiple pages. |
| 2.4.6 Headings and Labels | Supported | Headings and labels describe topic or purpose. |
| 2.4.7 Focus Visible | Supported | Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible when consuming the content. |
| 2.5.1 Pointer Gestures | Not Applicable | Content does not contain navigation by multipoint or path-based gestures. |
| 2.5.2 Pointer Cancellation | Supported | No actions in the content complete on mouse-down, and thus can be aborted by moving the mouse away from the button or target area before mouse-up. |
| 2.5.3 Label in Name | Supported | For user contant and interface components with labels that include text or images of text, the name contains the text that is presented visually. |
| 2.5.4 Motion Actuation | Not Applicable | Content does not contain any motion operations. |
Principle 3: Understandable. | ||
| Criteria | Conformance | Level Remarks & Explanations |
|---|---|---|
| 3.1.1 Language of Page | Supported | The default human language of each Web page can be programmatically determined. (English or Swedish). |
| 3.1.2 Language of Parts | Not Applicable | Multi-language content is not provided. |
| 3.2.1 On Focus | Supported | When any user interface component receives focus, it does not initiate a change of context. |
| 3.2.2 On Input | Supported | Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. |
| 3.2.3 Consistent Navigation | Not Applicable | Content does not contain navigational mechanisms that are repeated on multiple Web pages. |
| 3.2.4 Consistent Identification | Supported | Components that have the same functionality are identified consistently. |
| 3.3.1 Error Identification | Supported | If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. |
| 3.3.2 Labels or Instructions | Supported | Labels or instructions are provided when content requires user input. |
| 3.3.3 Error Suggestion | Not Applicable | Content does not allow user input. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Not Applicable | No legal or financial data is stored. |
Principle 4: Robust. | ||
| Criteria | Conformance | Level Remarks & Explanations |
|---|---|---|
| 4.1.1 Parsing | Supported | In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. |
| 4.1.2 Name, Role, Value | Supported | For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. |
| 4.1.3 Status Messages | Not Applicable | Status messages are not used. |
Functional Performance Criteria (FPC) | ||
| Criteria | Conformance | Level Remarks & Explanations |
|---|---|---|
| Without Vision | Supported | Content works well with screen readers. |
| With Limited Vision | Supported | Content supports screen magnification and browser-provided zoom functionality. |
| Without Perception of Color | Supported | Content does not require color perception for operation. |
| Without Hearing | Not Applicable | Content does not use any audio for its default operation. |
| With Limited Hearing | Not Applicable | Content does not use any audio for its default operation. |
| Without Speech | Not Applicable | Content does not require speech for operation. |
| With Limited Manipulation | Supported | Content does not require fine motor control or simultaneous actions. It is accessible via keyboard and touch devices. |
| With Limited Reach and Strength | Supported | Content does not require fine motor control or simultaneous actions. It is accessible via keyboard and touch devices. |
| With Limited Language, Cognitive, and Learning Abilities | Supported | Content provides an easy-to-use interface for users with cognitive or learning disabilities. |
