{"id":755,"date":"2018-05-02T15:53:44","date_gmt":"2018-05-02T15:53:44","guid":{"rendered":"http:\/\/pressbooks.library.ryerson.ca\/dabp\/?post_type=chapter&p=755"},"modified":"2022-12-16T14:52:23","modified_gmt":"2022-12-16T14:52:23","slug":"accessibility-questions-during-product-demonstrations","status":"publish","type":"chapter","link":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/chapter\/accessibility-questions-during-product-demonstrations\/","title":{"raw":"Accessibility Questions During Product Demonstrations","rendered":"Accessibility Questions During Product Demonstrations"},"content":{"raw":"During a product demonstration, specific and technical questions should be asked. It is a good idea to have the responses from the RFP accessibility requirements in hand so they can be clarified.\r\n\r\nIn addition to clarifications in the proposal\u2019s accessibility responses, here are some additional questions that can be asked to assess a vendor\u2019s level of accessibility understanding and their willingness to address accessibility issues in their software to meet your organization's requirements.\r\n
Toolkit: <\/strong>See Accessibility Questions for Product Demonstrations<\/a> for a collection of questions that can be asked while interviewing vendors.<\/div>\r\n
\r\n\r\nHere is the list of 10 possible questions and expected answers:\r\n\r\n1. Which accessibility standards does your product comply with?\u00a0At which Level (if WCAG)?<\/strong>\r\n\r\nDepending on the jurisdiction of the vendor, a local accessibility standard should be mentioned (e.g., Section 508 in the U.S.; AODA in Ontario), or mention WCAG. Added points if the vendor is from a different jurisdiction, and mentions the requirements of your jurisdiction, if different from their own.\r\n\r\nAt a minimum, where WCAG is the vendor\u2019s guideline of choice, Level A should be mentioned, or talk about what remains to be addressed to meet Level A. If Level AA is mentioned, added points could be given. If Level AAA is mentioned, that is a warning sign, since very few if any complex systems will meet Level AAA requirements. Ask what AAA features have been implemented in the system.\r\n\r\n2. Is your product accessible without a mouse? Please demonstrate.<\/strong>\r\n\r\nThe answer should always be \u201cYes.\u201d The vendor should be able to demonstrate by using the Tab key to navigate through the user interface (UI). All functional elements, like menus, links, buttons, and forms, etc., should all be able to receive focus, and users should be able to navigate through menus and open elements using only the keyboard. Watch out for elements that can receive focus, but do not operate with a keypress.\r\n\r\n3. Has your product been tested with assistive technologies?\u00a0If so, with which ones?\u00a0<\/strong>\r\n\r\nShould answer \u201cYes.\u201d\r\n\r\nShould mention a screen reader at a minimum. Should be able to identify which screen readers, such as ChromeVox, JAWS, NDVA, etc. Added points if they also mention Voiceover and\/or Talkback for mobile devices.\r\n\r\n<\/div>\r\n4. Who did the testing?<\/strong>\r\n
\r\n\r\nThe developers of the software should be mentioned. Screen reader testing should be part of the development process. Or, a particular accessibility person within the organization may be the tester. Added points if people with disabilities were used in testing, or a third party accessibility expert. Is the third party tester reputable, if one was used?\r\n\r\n5. What was the testing methodology?\u00a0What were the results?<\/strong>\r\n\r\nShould mention a combination of automated and manual testing strategies, and screen reader testing. Added points if testing with people with disabilities is also part of their testing process.\r\n\r\nIdeally mention the level of conformance reached, as well as acknowledging any issues that may remain, and what they plan to do to address those issues. Answering \u201cfully accessible\u201d is a warning sign. Very few systems will be fully accessible to everyone.\r\n\r\n6. How is accessibility built into your company's quality assurance (QA) process?<\/strong>\r\n\r\nShould talk about the development process at a minimum, and where accessibility design and testing tasks fit into the process. Added points if the vendor goes into detail about the Web accessibility policy implemented at the company.\r\n\r\n7. If you roll out upgrades after we purchase the product, how can you assure us the upgrades will not break accessibility?<\/strong>\r\n\r\nShould refer back to the QA process, local upgrade testing before pushing updates to production environments. Added points if third-party accessibility expert is involved.\r\n\r\n8. Does your product make use of WAI-ARIA? If it does, how so?<\/strong>\r\n\r\nWhere a product has a fairly complex, interactive UI, the answer should be \u201cYes.\u201d This indicates the vendor understands the complex accessibility issues associated with custom-built web interactivity.\r\n\r\nMay mention using ARIA landmarks. Added points if the specific ARIA attributes are mentioned for particular types of interactions, for example, using menu-related ARIA for complex menu, tab panel\u2013related ARIA for tab panel presentations, and so on. Perhaps mention libraries used to implement ARIA, like jQuery or MooTools, or perhaps a custom-made ARIA library created by the vendor.\r\n\r\n9. Does your product adapt responsively to different screen sizes? Please demonstrate.<\/strong>\r\n\r\nShould answer \u201cYes.\u201d Should be able to grab the corner of a browser window and drag it inward to reduce the window size, and the content should adapt cleanly as the window size increases and decreases. Should also be able to demonstrate the product on a mobile device like a smartphone or tablet, and have the UI adapt to the device\u2019s screen size.\r\n\r\n10. Does your product magnify cleanly using just a browser\u2019s zoom feature? Please demonstrate.<\/strong>\r\n\r\nShould answer \u201cYes.\u201d Should be able to use the browser\u2019s zoom function to increase the size of the content to at least 200% without the content flowing off the side of the screen or overlapping with adjacent content. Added points for zoom<\/span>\u00a0sizes greater than 200%. Good zoom adaptation indicates relative measures (em, %) have been used to size elements rather than absolute measures (px, pt), which is also a requirement for good responsive designs.<\/span>\r\n\r\n<\/div>","rendered":"

During a product demonstration, specific and technical questions should be asked. It is a good idea to have the responses from the RFP accessibility requirements in hand so they can be clarified.<\/p>\n

In addition to clarifications in the proposal\u2019s accessibility responses, here are some additional questions that can be asked to assess a vendor\u2019s level of accessibility understanding and their willingness to address accessibility issues in their software to meet your organization’s requirements.<\/p>\n

Toolkit: <\/strong>See Accessibility Questions for Product Demonstrations<\/a> for a collection of questions that can be asked while interviewing vendors.<\/div>\n
\n

Here is the list of 10 possible questions and expected answers:<\/p>\n

1. Which accessibility standards does your product comply with?\u00a0At which Level (if WCAG)?<\/strong><\/p>\n

Depending on the jurisdiction of the vendor, a local accessibility standard should be mentioned (e.g., Section 508 in the U.S.; AODA in Ontario), or mention WCAG. Added points if the vendor is from a different jurisdiction, and mentions the requirements of your jurisdiction, if different from their own.<\/p>\n

At a minimum, where WCAG is the vendor\u2019s guideline of choice, Level A should be mentioned, or talk about what remains to be addressed to meet Level A. If Level AA is mentioned, added points could be given. If Level AAA is mentioned, that is a warning sign, since very few if any complex systems will meet Level AAA requirements. Ask what AAA features have been implemented in the system.<\/p>\n

2. Is your product accessible without a mouse? Please demonstrate.<\/strong><\/p>\n

The answer should always be \u201cYes.\u201d The vendor should be able to demonstrate by using the Tab key to navigate through the user interface (UI). All functional elements, like menus, links, buttons, and forms, etc., should all be able to receive focus, and users should be able to navigate through menus and open elements using only the keyboard. Watch out for elements that can receive focus, but do not operate with a keypress.<\/p>\n

3. Has your product been tested with assistive technologies?\u00a0If so, with which ones?\u00a0<\/strong><\/p>\n

Should answer \u201cYes.\u201d<\/p>\n

Should mention a screen reader at a minimum. Should be able to identify which screen readers, such as ChromeVox, JAWS, NDVA, etc. Added points if they also mention Voiceover and\/or Talkback for mobile devices.<\/p>\n<\/div>\n

4. Who did the testing?<\/strong><\/p>\n

\n

The developers of the software should be mentioned. Screen reader testing should be part of the development process. Or, a particular accessibility person within the organization may be the tester. Added points if people with disabilities were used in testing, or a third party accessibility expert. Is the third party tester reputable, if one was used?<\/p>\n

5. What was the testing methodology?\u00a0What were the results?<\/strong><\/p>\n

Should mention a combination of automated and manual testing strategies, and screen reader testing. Added points if testing with people with disabilities is also part of their testing process.<\/p>\n

Ideally mention the level of conformance reached, as well as acknowledging any issues that may remain, and what they plan to do to address those issues. Answering \u201cfully accessible\u201d is a warning sign. Very few systems will be fully accessible to everyone.<\/p>\n

6. How is accessibility built into your company’s quality assurance (QA) process?<\/strong><\/p>\n

Should talk about the development process at a minimum, and where accessibility design and testing tasks fit into the process. Added points if the vendor goes into detail about the Web accessibility policy implemented at the company.<\/p>\n

7. If you roll out upgrades after we purchase the product, how can you assure us the upgrades will not break accessibility?<\/strong><\/p>\n

Should refer back to the QA process, local upgrade testing before pushing updates to production environments. Added points if third-party accessibility expert is involved.<\/p>\n

8. Does your product make use of WAI-ARIA? If it does, how so?<\/strong><\/p>\n

Where a product has a fairly complex, interactive UI, the answer should be \u201cYes.\u201d This indicates the vendor understands the complex accessibility issues associated with custom-built web interactivity.<\/p>\n

May mention using ARIA landmarks. Added points if the specific ARIA attributes are mentioned for particular types of interactions, for example, using menu-related ARIA for complex menu, tab panel\u2013related ARIA for tab panel presentations, and so on. Perhaps mention libraries used to implement ARIA, like jQuery or MooTools, or perhaps a custom-made ARIA library created by the vendor.<\/p>\n

9. Does your product adapt responsively to different screen sizes? Please demonstrate.<\/strong><\/p>\n

Should answer \u201cYes.\u201d Should be able to grab the corner of a browser window and drag it inward to reduce the window size, and the content should adapt cleanly as the window size increases and decreases. Should also be able to demonstrate the product on a mobile device like a smartphone or tablet, and have the UI adapt to the device\u2019s screen size.<\/p>\n

10. Does your product magnify cleanly using just a browser\u2019s zoom feature? Please demonstrate.<\/strong><\/p>\n

Should answer \u201cYes.\u201d Should be able to use the browser\u2019s zoom function to increase the size of the content to at least 200% without the content flowing off the side of the screen or overlapping with adjacent content. Added points for zoom<\/span>\u00a0sizes greater than 200%. Good zoom adaptation indicates relative measures (em, %) have been used to size elements rather than absolute measures (px, pt), which is also a requirement for good responsive designs.<\/span><\/p>\n<\/div>\n","protected":false},"author":56,"menu_order":11,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-755","chapter","type-chapter","status-publish","hentry"],"part":610,"_links":{"self":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/pressbooks\/v2\/chapters\/755","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/wp\/v2\/users\/56"}],"version-history":[{"count":9,"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/pressbooks\/v2\/chapters\/755\/revisions"}],"predecessor-version":[{"id":1405,"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/pressbooks\/v2\/chapters\/755\/revisions\/1405"}],"part":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/pressbooks\/v2\/parts\/610"}],"metadata":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/pressbooks\/v2\/chapters\/755\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/wp\/v2\/media?parent=755"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/pressbooks\/v2\/chapter-type?post=755"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/wp\/v2\/contributor?post=755"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/wp\/v2\/license?post=755"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}