W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2017

Re: ATAG testing

From: Greg Gay <greggay@rogers.com>
Date: Wed, 20 Sep 2017 14:01:25 -0400
To: w3c-wai-ig@w3.org
Message-ID: <45533cbb-63c3-29e3-b9a4-7faef163f9b5@rogers.com>
Turns out JAWS 18 does not work with Edge. Reverting to IE11, JAWS works 
fairly well with TinyMCE in Wordpress 4.8.2.

The next version of JAWS, coming shortly, I'm told will work with Edge.

greg


On 2017-09-20 12:23 PM, Greg Gay wrote:
>
> Hi Sean,
>
> I may have spoke too soon on TinyMCE 4. It's been a while since I've 
> taken a close look at it. Here's some more on V4.0+ accessibility.
>
> https://www.tinymce.com/docs/advanced/accessibility/
>
> With NVDA and Edge there is resonably good access to the TinyMCE UI, 
> though there's room for improvement.† Could not make it work with† my 
> recently upgraded to JAWS 18, though it does not seem to read web 
> content at all using it on a Windows 10 VM from a MAC. I'm guessing 
> I'm missing a setting somewhere. (help, if anyone knows why this might be)
>
> There is also an addon accessibility checker for the subscription 
> (paid) version of TinyMCE. It's a shame they've chosen to make 
> accessibility a paid feature (though only $.40 per user per month).
>
> https://www.tinymce.com/docs/plugins/a11ychecker/
>
> From what I can tell, there are no prompts to warn authors about 
> missing alt text, for instance, which were present in earlier version 
> of the editor.
>
> Bottom line, I think, TinyMCE 4 would not be compliant, but would not 
> be far off. With a little trouble, I was able to create content in 
> Wordpress while using NVDA/Edge. And it is possible to create 
> accessible content, but without prompts, so only if you know what 
> you're doing.
>
> greg
>
>
> On 2017-09-19 8:22 PM, Sean Murphy (seanmmur) wrote:
>>
>> Greg,
>>
>> Thank you for the information on the Wordpress editor as I have just 
>> taken over responsibility of a site. This is good information to know.
>>
>> https://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/08_standard_graphic.png
>>
>>
>>
>> 	
>>
>> *Sean Murphy*
>>
>> ENGINEER.CUSTOMER SUPPORT
>>
>> seanmmur@cisco.com <mailto:seanmmur@cisco.com>
>>
>> Tel: *+61 2 8446 7751*
>>
>>
>>
>> 	
>> 	
>>
>> Cisco Systems, Inc.
>>
>> The Forum 201 Pacific Highway
>>
>> ST LEONARDS
>>
>> 2065
>>
>> Australia
>>
>> cisco.com
>>
>>
>> http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif
>>
>> 	
>> 	
>>
>> Think before you print.
>>
>> This email may contain confidential and privileged material for the 
>> sole use of the intended recipient. Any review, use, distribution or 
>> disclosure by others is strictly prohibited. If you are not the 
>> intended recipient (or authorized to receive for the recipient), 
>> please contact the sender by reply email and delete all copies of 
>> this message.
>>
>> Please click here 
>> <http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html> 
>> for Company Registration Information.
>>
>> 	
>>
>> *From:*Greg Gay [mailto:greggay@rogers.com]
>> *Sent:* Wednesday, 20 September 2017 1:37 AM
>> *To:* w3c-wai-ig@w3.org
>> *Subject:* Re: ATAG testing
>>
>> Hi Sean,
>>
>> We did some work with Moxiecode some years back when ATAG 2 was under 
>> development, to make TinyMCE 3 ATAG 2 compliant. For a while it was 
>> the only open WYSIWYG editor that did comply, being accessible to 
>> screen readers, and helping authors produce accessible content.
>>
>> http://archive.tinymce.com/wiki.php/TinyMCE3x:Accessibility
>>
>> Unfortunately with the introduction of TinyMCE 4, which the current 
>> Wordpress uses, much of the accessibility work done on V3 was lost. 
>> You can no longer use it with a screen reader, or with a keyboard for 
>> that matter.
>>
>> I can't speak for for other CMS, but if they are using a current 
>> version of TinyMCE, they will not be ATAG compliant.
>>
>> Perhaps you, or someone, could remind the TinyMCE folk about that 
>> work with V3. It would not take too much to replicate that with the 
>> current version.
>>
>> greg
>>
>> On 2017-09-19 1:21 AM, Sean Murphy (seanmmur) wrote:
>>
>>     All,
>>
>>     This is a general query and would like to know if any CMS
>>     platform follows the ATAG 2.0 standard? What is the awareness of
>>     this standard in the development world and the general community?
>>     Thus far I donít see much discussion on this standard and havenít
>>     seen many CMS platforms that follow it. Does anyone use the
>>     standard for testing?
>>
>>     https://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/08_standard_graphic.png
>>
>>
>>
>>     	
>>
>>     *Sean Murphy*
>>
>>     ENGINEER.CUSTOMER SUPPORT
>>
>>     seanmmur@cisco.com <mailto:seanmmur@cisco.com>
>>
>>     Tel: *+61 2 8446 7751*
>>
>>
>>
>>     	
>>     	
>>
>>     Cisco Systems, Inc.
>>
>>     The Forum 201 Pacific Highway
>>
>>     ST LEONARDS
>>
>>     2065
>>
>>     Australia
>>
>>     cisco.com
>>
>>
>>     http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif
>>
>>     	
>>     	
>>
>>     Think before you print.
>>
>>     This email may contain confidential and privileged material for
>>     the sole use of the intended recipient. Any review, use,
>>     distribution or disclosure by others is strictly prohibited. If
>>     you are not the intended recipient (or authorized to receive for
>>     the recipient), please contact the sender by reply email and
>>     delete all copies of this message.
>>
>>     Please click here
>>     <http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html>
>>     for Company Registration Information.
>>
>>     	
>>
>
Received on Wednesday, 20 September 2017 18:01:55 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 20 September 2017 18:01:56 UTC