WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: Software vs Web testing

for

Number of posts in this thread: 6 (In chronological order)

From: Claire Forbes
Date: Thu, Sep 02 2021 9:01AM
Subject: Software vs Web testing
No previous message | Next message →

I continue to encounter push-back from a third party organization who is building courses in Adobe Captivate and then testing them within Adobe Captivate for Section 508 compliance.
I am then provided a web link to test the course for Section 508 compliance and therefore test against Web standards - according to said third party organization this is wrong because they're working in Captivate.

Can someone PLEASE provide some insight or point out something I'm potentially missing here?

Thank you!


Claire Forbes
Project Control Specialist

Victor 12, Inc.
174 West Comstock Avenue Suite 104
​Winter Park, FL. 32789

Tel: 407-612-6011 x119
Fax: 407-985-1980
Web: www.victor12.com

CVE SDVOSB | VOSB | GSA Multiple Award Schedule (MAS) GS‑02F‑087BA
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. ​
​If you have received this message in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

From: Patrick H. Lauke
Date: Thu, Sep 02 2021 9:09AM
Subject: Re: Software vs Web testing
← Previous message | Next message →

On 02/09/2021 16:01, Claire Forbes wrote:
> I continue to encounter push-back from a third party organization who is building courses in Adobe Captivate and then testing them within Adobe Captivate for Section 508 compliance.
> I am then provided a web link to test the course for Section 508 compliance and therefore test against Web standards - according to said third party organization this is wrong because they're working in Captivate.
>
> Can someone PLEASE provide some insight or point out something I'm potentially missing here?

How are the courses accessed in the end by the end users? Also via
Captivate, or will they get to them via the web?

And more fundamentally, there's not really a lot of difference between
testing web vs testing software under 508 Refresh (barring a few WCAG
SCs that have been out-of-scoped for software) ... so what is their
pushback really about? Are you finding issues that they claim are not
issues?

P
--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke

From: Claire Forbes
Date: Thu, Sep 02 2021 9:16AM
Subject: Re: Software vs Web testing
← Previous message | Next message →

End user accesses course via Web.
Yes, pushback because I'm flagging headers not being found via ANDI, but headers do not fall under the scope of software



Claire Forbes
Project Control Specialist

Victor 12, Inc.
174 West Comstock Avenue Suite 104
​Winter Park, FL. 32789

Tel: 407-612-6011 x119
Fax: 407-985-1980
Web: www.victor12.com

CVE SDVOSB | VOSB | GSA Multiple Award Schedule (MAS) GS‑02F‑087BA
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. ​
​If you have received this message in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Patrick H. Lauke
Sent: Thursday, September 2, 2021 11:10 AM
To: = EMAIL ADDRESS REMOVED =
Subject: Re: [WebAIM] Software vs Web testing

On 02/09/2021 16:01, Claire Forbes wrote:
> I continue to encounter push-back from a third party organization who is building courses in Adobe Captivate and then testing them within Adobe Captivate for Section 508 compliance.
> I am then provided a web link to test the course for Section 508 compliance and therefore test against Web standards - according to said third party organization this is wrong because they're working in Captivate.
>
> Can someone PLEASE provide some insight or point out something I'm potentially missing here?

How are the courses accessed in the end by the end users? Also via Captivate, or will they get to them via the web?

And more fundamentally, there's not really a lot of difference between testing web vs testing software under 508 Refresh (barring a few WCAG SCs that have been out-of-scoped for software) ... so what is their pushback really about? Are you finding issues that they claim are not issues?

P
--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke

From: Hayman, Douglass
Date: Thu, Sep 02 2021 9:17AM
Subject: Re: [EXTERNAL] - Software vs Web testing
← Previous message | Next message →

Claire,

It appears from looking at this that the opposite is true, namely that it is not accessible to be examining things within Captivate but that the HTML output could be made accessible, at least for this version though some are odd like not being able to create a title for an html page:

https://www.adobe.com/accessibility/compliance/adobe-captivate-2019-win-acr.html

Many say something along these lines:

Authored Content (HTML): Authors can ensure that content meets this criterion.



Do you have a link to some of that course content that some of us could take a look at or does it require access credentials we don't have?

Doug Hayman
IT Accessibility Coordinator
Information Technology
Olympic College
= EMAIL ADDRESS REMOVED =
(360) 475-7632 (currently working remotely and don't have access to this phone)



-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Claire Forbes
Sent: Thursday, September 2, 2021 8:01 AM
To: = EMAIL ADDRESS REMOVED =
Subject: [EXTERNAL] - [WebAIM] Software vs Web testing

CAUTION: This email came from a non-OC system or external source. Beware of phishing and social engineering!


I continue to encounter push-back from a third party organization who is building courses in Adobe Captivate and then testing them within Adobe Captivate for Section 508 compliance.
I am then provided a web link to test the course for Section 508 compliance and therefore test against Web standards - according to said third party organization this is wrong because they're working in Captivate.

Can someone PLEASE provide some insight or point out something I'm potentially missing here?

Thank you!


Claire Forbes
Project Control Specialist

Victor 12, Inc.
174 West Comstock Avenue Suite 104
​Winter Park, FL. 32789

Tel: 407-612-6011 x119
Fax: 407-985-1980
Web: www.victor12.com

CVE SDVOSB | VOSB | GSA Multiple Award Schedule (MAS) GS‑02F‑087BA This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. ​ ​If you have received this message in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

From: glen walker
Date: Thu, Sep 02 2021 9:40AM
Subject: Re: [EXTERNAL] - Software vs Web testing
← Previous message | Next message →

Sounds like a mix of WCAG and ATAG.

Captivate, itself, falls more under ATAG (authoring tool accessibility
guidelines). ATAG generally isn't as "popular" or as well known as WCAG.
In a nutshell, it essentially says that an authoring tool (something you
use to create web content) must be accessible *and* the content you
generate with the tool must be accessible. You are testing the latter
part. You want to make sure whatever is created by Captivate and accessed
by the students will be accessible. Whether the Captivate tool itself is
accessible isn't really an issue for the students.

If you find accessibility issues in the final product, they're real issues
and should be reported.

From: Patrick H. Lauke
Date: Thu, Sep 02 2021 11:09AM
Subject: Re: Software vs Web testing
← Previous message | No next message

On 02/09/2021 16:16, Claire Forbes wrote:
> End user accesses course via Web.

If the end users will be the actual students accessing these courses,
then it seems that the accessibility of the course should of course be
assessed under the lens of web content accessibility, as they're not
interacting with the software.

P
--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke