We use cookies to ensure that we give you the best experience on our website. By continuing to use this site, you agree to our use of cookies in accordance with our Privacy Policy.
Privacy Overview
Login
Your Role
Challenges You Face
results
Learn
Resources
Company
Accessibility
Accessibility
Voluntary Product Accessibility Template (VPAT) outlining §508 accessibility information for MarketSmart Dashboard.
VPAT ® Version 2.1 – March 2020
Name of Product/Version: MarketSmart 3.0
Product Description: Web application for reviewing donor data and organizing prospective donors
Date: May 2020
Contact information: dev@imarketsmart.com
Table 1: Success Criteria, Level A
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
1.1.1 Non-text Content (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product uses standard HTML techniques for providing text equivalents of non-text elements. This includes the use of “alt” attributes for images and the use of “aria-label” or “aria-describedby” attributes for other visual elements.
Some purely decorative elements that have no functional or informational purpose may not provide a text alternative. |
|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Not Applicable |
The MarketSmart product does not include audio or video content. |
|
1.2.2 Captions (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Not Applicable |
The MarketSmart product does not include audio or video content. MarketSmart does not provide capabilities for captioning or defining audio descriptions of designer-specified video content. |
|
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Not Applicable |
The MarketSmart product does not use synchronized media. |
|
1.3.1 Info and Relationships (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product uses semantically-correct markup so that information, structure, and relationships can be understood independent of presentation. |
|
1.3.2 Meaningful Sequence (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product generates semantically-correct markup to allow assistive technologies to interpret the meaning of content and controls. |
|
1.3.3 Sensory Characteristics (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product does not depend solely on sensory characteristics such as shape, size, visual location, orientation, or sound to understand content. |
|
1.4.1 Use of Color (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Color is only used as a decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information. |
|
1.4.2 Audio Control (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Not Applicable |
The MarketSmart product does not include audio or video content. |
|
2.1.1 Keyboard (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product is a web-based application that supports standard keyboard navigation and input functions (such as pressing [Tab] to move between input fields, pressing the arrow keys to move between list items, and pressing [Space] or [Enter] to make selections). |
|
2.1.2 No Keyboard Trap (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product is a web-based application that supports standard keyboard navigation and ensures that keyboard users cannot be trapped in a subset of content. |
|
2.2.1 Timing Adjustable (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Web: Electronic Docs: Software: Authoring Tool: |
Web: Electronic Docs: Software: Authoring Tool: |
|
2.2.2 Pause, Stop, Hide (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product has a mechanism for the user to hide content that appears automatically. There is no auto-updating content. |
|
2.3.1 Three Flashes or Below Threshold (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Not Applicable |
The MarketSmart product does not use flashing interface elements. |
|
2.4.1 Bypass Blocks (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Not Applicable |
The MarketSmart product does not include sections of content that a repeated on multiple web pages within the web application. |
|
2.4.2 Page Titled (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Web pages within the MarketSmart product have descriptive titles that indicate the topic or purpose of each page. |
|
2.4.3 Focus Order (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product uses a logical tab order through interactive elements such as links and form controls.
MarketSmart also uses semantically correct markup, ensuring that the markup matches the visual presentation of content on the page. |
|
2.4.4 Link Purpose (In Context) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product uses descriptive text or WAI-ARIA techniques, such as adding an “aria-label” attribute to table paging control icons, to identify the purpose of links. |
|
3.1.1 Language of Page (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product uses the language attribute on the HTML element to specify the default language of a page |
|
3.2.1 On Focus (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
When a component in an MarketSmart user interface receives focus, it does not initiate a change of context. |
|
3.2.2 On Input (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Changing the setting of a component in an MarketSmart user interface does not initiate a change of context. |
|
3.3.1 Error Identification (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product uses “aria-invalid” to flag inputs with errors and relay this information to Assistive Technologies. |
|
3.3.2 Labels or Instructions (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product uses standard HTML and WAI-ARIA attributes to associate labels and instructions to user interface elements. This includes the use of “aria-labelledby” and “aria-describedby” to describe relationships to Assistive Technologies. |
|
4.1.1 Parsing (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product uses semantically-correct markup for all interface elements. The markup is programmatically generated to prevent parsing errors. |
|
4.1.2 Name, Role, Value (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies. |
Table 2: Success Criteria, Level AA
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
1.2.4 Captions (Live) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Not Applicable |
The MarketSmart product does not use synchronized media. |
|
1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Not Applicable |
The MarketSmart product does not use synchronized media. |
|
1.4.3 Contrast (Minimum) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The visual presentation of text in the MarketSmart product provides sufficient contrast. |
|
1.4.4 Resize text (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
MarketSmart product user interfaces support standard zoom capabilities built into modern web browsers and operating systems. |
|
1.4.5 Images of Text (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product does not use images of text. |
|
2.4.5 Multiple Ways (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product contains top-level navigation to access page content. |
|
2.4.6 Headings and Labels (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product uses semantically-correct markup for all interface elements, including headings and labels. |
|
2.4.7 Focus Visible (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product uses visual changes to elements to indicate the current position of focus. |
|
3.1.2 Language of Parts (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Does Not Support |
In the MarketSmart product, the language of a page can be programmatically determined. However, there is no mechanism to specify different languages for subsets of a page. |
|
3.2.3 Consistent Navigation (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product uses the same navigation mechanisms across pages. |
|
3.2.4 Consistent Identification (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product maintains the same functionality for components across pages. |
|
3.3.3 Error Suggestion (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The MarketSmart product provides suggestions for correcting errors such as identifying required fields using the “aria-required” attribute. |
|
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Not Applicable |
The MarketSmart product does not contain any legal or financial decisions for the end user to make. |
Table 3: Success Criteria, Level AAA
Notes: The MarketSmart product has not been evaluated for WCAG 2.0 Level AAA conformance.
2017 Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
302.1 Without Vision |
Supports |
The MarketSmart product uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies. |
|
302.2 With Limited Vision |
Supports |
The MarketSmart product supports standard browser magnification and contrast adjustments. |
|
302.3 Without Perception of Color |
Supports |
Color is only used as a decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information. |
|
302.4 Without Hearing |
Not Applicable |
The MarketSmart product does not include audio-only features that require hearing to be used. |
|
302.5 With Limited Hearing |
Not Applicable |
The MarketSmart product does not include audio-only features that require hearing to be used. |
|
302.6 Without Speech |
Not Applicable |
The MarketSmart product does not require speech input. |
|
302.7 With Limited Manipulation |
Supports |
The MarketSmart product supports standard input mechanisms such as user-provided keyboards and pointing devices. Usage of the product does not require fine motor controls nor simultaneous actions. |
|
302.8 With Limited Reach and Strength |
Not Applicable |
|
|
302.9 With Limited Language, Cognitive, and Learning Abilities |
Supports |
|
Chapter 4: Hardware
Notes: The MarketSmart product is a web software application and is not subject to the requirements of this section.
Chapter 5: Software
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
501.1 Scope – Incorporation of WCAG 2.0 AA |
See WCAG 2.0 section |
See information in WCAG section |
|
502 Interoperability with Assistive Technology |
Heading cell – no response required |
Heading cell – no response required |
|
502.2.1 User Control of Accessibility Features |
Not Applicable |
MarketSmart is not considered platform software as defined by Section 508. |
|
502.2.2 No Disruption of Accessibility Features |
Supports |
MarketSmart is compatible with operating system and browser accessibility features configured by the user. |
|
502.3 Accessibility Services |
Heading cell – no response required |
Heading cell – no response required |
|
502.3.1 Object Information |
Supports |
The MarketSmart product uses WAI-ARIA attributes to describe the role, state, and description of user interface elements to Assistive Technologies. The includes the use of “role”, “aria-invalid”, and “aria-required” attributes. |
|
502.3.2 Modification of Object Information |
Supports |
The MarketSmart product uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies. |
|
502.3.3 Row, Column, and Headers |
Supports |
The MarketSmart product uses standard HTML attributes to define table structure and relationships, including column headers, to Assistive Technologies. |
|
502.3.4 Values |
Supports |
The MarketSmart product uses standard HTML or and ARIA object attributes for maximum compatibility with assistive technologies. |
|
502.3.5 Modification of Values |
Supports |
The MarketSmart product uses standard HTML or and ARIA object attributes for maximum compatibility with assistive technologies. |
|
502.3.6 Label Relationships |
Supports |
The MarketSmart product uses standard HTML and WAI-ARIA attributes to describe label relationships of user interface elements to Assistive Technologies. This includes the use of “<label>” and “aria-labelledby” attributes. |
|
502.3.7 Hierarchical Relationships |
Supports |
The MarketSmart product uses standard HTML markup to express hierarchical relationships. |
|
502.3.8 Text |
Supports |
The MarketSmart product renders strings as plain text values in HTML for maximum compatibility with assistive technologies. |
|
502.3.9 Modification of Text |
Supports |
The MarketSmart product renders strings as plain text values in HTML for maximum compatibility with assistive technologies. |
|
502.3.10 List of Actions |
Supports |
The MarketSmart product uses standard HTML or and ARIA object attributes for maximum compatibility with assistive technologies. |
|
502.3.11 Actions on Objects |
Supports |
The MarketSmart product uses standard HTML or and ARIA object attributes for maximum compatibility with assistive technologies. |
|
502.3.12 Focus Cursor |
Supports |
The MarketSmart product uses visual changes to elements to indicate the current position of focus. |
|
502.3.13 Modification of Focus Cursor |
Supports |
The MarketSmart product uses standard HTML elements with standard cursor controls for user input. |
|
502.3.14 Event Notification |
Supports with Exceptions |
The MarketSmart product has a session timeout alert to notify users when a session is about to end. Assistive technologies do not announce this message as an alert, although users may navigate via mouse or keyboard to read the message and choose to extend their session. |
|
502.4 Platform Accessibility Features |
Not Applicable |
MarketSmart is not considered platform software as defined by Section 508. |
|
503 Applications |
Heading cell – no response required |
Heading cell – no response required |
|
503.2 User Preferences |
Supports |
The MarketSmart product respects user preferences from platform or OS settings. For example, if a user enables high contrast mode, MarketSmart user interfaces will display with high contrast. |
|
503.3 Alternative User Interfaces |
Not Applicable |
MarketSmart does not provide any alternative user interfaces that function as assistive technology. |
|
503.4 User Controls for Captions and Audio Description |
Heading cell – no response required |
Heading cell – no response required |
|
503.4.1 Caption Controls |
Not Applicable |
MarketSmart product does not contain audio or video content. |
|
503.4.2 Audio Description Controls |
Not Applicable |
MarketSmart product does not contain audio or video content. |
|
504 Authoring Tools |
Heading cell – no response required |
Heading cell – no response required |
|
504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) |
See WCAG 2.0 section |
See information in WCAG section |
|
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Not Applicable |
|
|
504.2.2 PDF Export |
Not Applicable |
|
|
504.3 Prompts |
Not Applicable |
|
|
504.4 Templates |
Not Applicable |
|
Chapter 6: Support Documentation and Services
Notes: This report covers accessibility conformance for the MarketSmart product and does not discuss Documentation or Support Services.
EN 301 549 Report
Chapter 4: 4.2 Functional Performance Statements (FPS)
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
4.2.1 Usage without vision |
Supports |
The MarketSmart product uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies |
|
4.2.2 Usage with limited vision |
Supports |
The MarketSmart product supports standard browser magnification and contrast adjustments |
|
4.2.3 Usage without perception of colour |
Supports |
Color is only used as a decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information. |
|
4.2.4 Usage without hearing |
Not Applicable |
The MarketSmart product does not include audio-only features that require hearing to be used |
|
4.2.5 Usage with limited hearing |
Not Applicable |
The MarketSmart product does not include audio-only features that require hearing to be used |
|
4.2.6 Usage without vocal capability |
Not Applicable |
The MarketSmart product does not require speech input |
|
4.2.7 Usage with limited manipulation or strength |
Supports |
The MarketSmart product supports standard input mechanisms such as user-provided keyboards and pointing devices |
|
4.2.8 Usage with limited reach |
Not Applicable |
|
|
4.2.9 Minimize photosensitive seizure triggers |
Supports |
The MarketSmart product does not include visual features with flashing that could trigger seizures |
|
4.2.10 Usage with limited cognition |
Supports |
MarketSmart uses a logical focus order, and provides capabilities for specifying error text for user interface components configured by application designers |
|
4.2.11 Privacy |
Supports |
The MarketSmart product does not impede usage of standard privacy controls alongside assistive technologies. |
Chapter 5: Generic Requirements
Notes: The MarketSmart product supports standard assistive technologies and is therefore not subject to the Closed Functionality criteria described in this Chapter.
Chapter 6: ICT with Two-Way Voice Communication
Notes: The MarketSmart product does not offer two-way voice communication and is therefore not subject to the requirements of this section
Chapter 7: ICT with Video Capabilities
Notes: The MarketSmart product does not include video content
Chapter 8: Hardware
Notes: The MarketSmart product is a web software application and is not subject to the requirements of this section.
Chapter 9: Web (see WCAG 2.0 section)
Chapter 10: Non-web Documents
Notes: The MarketSmart product does not include non-web documents and is therefore not subject to the requirements of this section
Chapter 11: Software
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
11.2.1 Software success criteria (excluding closed functionality) |
See WCAG 2.0 section |
See information in WCAG section |
|
11.2.2 Software success criteria (closed functionality) |
See WCAG 2.0 section |
See information in WCAG section |
|
11.3 Interoperability with assistive technology |
Heading cell – no response required |
Heading cell – no response required |
|
11.3.1 Closed functionality (informative) |
Heading cell – no response required |
Heading cell – no response required |
|
11.3.2 Accessibility services |
Heading cell – no response required |
Heading cell – no response required |
|
11.3.2.1 Platform accessibility service support for software that provides a user interface |
See 11.3.2.5 through 11.3.2.17 |
See information in 11.3.2.5 through 11.3.2.17 |
|
11.3.2.2 Platform accessibility service support for assistive technologies |
See 11.3.2.5 through 11.3.2.17 |
See information in 11.3.2.5 through 11.3.2.17 |
|
11.3.2.3 Use of accessibility services |
Supports |
MarketSmart uses standard platform accessibility services. |
|
11.3.2.4 Assistive technology |
Not Applicable |
The MarketSmart product is not itself an assistive technology. |
|
11.3.2.5 Object information |
Supports |
The MarketSmart product uses WAI-ARIA attributes to describe the role, state, and description of user interface elements to Assistive Technologies. The includes the use of “role”, “aria-invalid”, and “aria-required” attributes. |
|
11.3.2.6 Row, column, and headers |
Supports |
The MarketSmart product uses standard HTML attributes to define table structure and relationships, including column headers, to Assistive Technologies. |
|
11.3.2.7 Values |
Supports |
|
|
11.3.2.8 Label relationships |
Supports |
The MarketSmart product uses standard HTML and WAI-ARIA attributes to describe label relationships of user interface elements to Assistive Technologies. This includes the use of “<label>” and “aria-labelledby” attributes. |
|
11.3.2.9 Parent-child relationships |
Supports |
|
|
11.3.2.10 Text |
Supports |
|
|
11.3.2.11 List of available actions |
Supports |
|
|
11.3.2.12 Execution of available actions |
Supports |
|
|
11.3.2.13 Tracking of focus and selection attributes |
Supports |
|
|
11.3.2.14 Modification of focus and selection attributes |
Supports |
|
|
11.3.2.15 Change notification |
Supports |
|
|
11.3.2.16 Modifications of states and properties |
Supports |
|
|
11.3.2.17 Modifications of values and text |
Supports |
|
|
11.4 Documented accessibility usage |
Heading cell – no response required |
Heading cell – no response required |
|
11.4.1 User control of accessibility features |
Not Applicable |
MarketSmart is not considered platform software as defined by EN 301 549. |
|
11.4.2 No disruption of accessibility features |
Supports |
|
|
11.5 User preferences |
Supports |
The MarketSmart product respects user preferences from platform or OS settings. For example, if a user enables high contrast mode, MarketSmart user interfaces will display with high contrast. |
|
11.6 Authoring tools |
Heading cell – no response required |
Heading cell – no response required |
|
11.6.1 Content technology |
Heading cell – no response required |
Heading cell – no response required |
|
11.6.2 Accessible content creation (if not authoring tool, enter “not applicable”) |
See WCAG 2.0 section |
See information in WCAG section |
|
11.6.3 Preservation of accessibility information in transformations |
Not Applicable |
|
|
11.6.4 Repair assistance |
Not Applicable |
|
|
11.6.5 Templates |
Not Applicable |
|
Get the book!
Feeling like your job is getting harder because donor expectations have changed and competition for the charitable dollar is growing?
Finding that the old orthodoxies and conventions espoused by so-called experts in online echo-chambers and at conferences don’t work anymore?
Want to help more people make impact by facilitating their acts of philanthropy but feel like too many obstacles keep getting in your way?
Then this book is for you.
Engagement Fundraising was developed from the perspective of a donor who discovered firsthand that the impersonal, spray-and-pray approaches of his beloved charity were not only offensive but also wasteful and ineffective. So he took action. And now, you can too.
Get smarter with the SmartIdeas blog
Subscribe to our blog today and get actionable fundraising ideas delivered straight to your inbox!