Set "Enable Accessibility Optimization" programmatically

Having trouble deploying Oxygen XML Web Author? Got a bug to report? Post it all here.
david.badger
Posts: 29
Joined: Tue Feb 25, 2014 12:14 am

Set "Enable Accessibility Optimization" programmatically

Post by david.badger »

Hello,

We are using Web Author v. 22.1.

Is there any way to enable accessibility optimization automatically? We don't want users to have to manually enable it. I've looked through all the loading options and can't find this exposed.

Thank you!
cristi_talau
Posts: 517
Joined: Thu Sep 04, 2014 4:22 pm

Re: Set "Enable Accessibility Optimization" programmatically

Post by cristi_talau »

Hello,

Accessibility optimization comes with some performance and aesthetics implications. What it improves is mainly support for screen readers and other assistive technologies. That's why we considered a good idea to turn it off by default.

I can add a feature request to be able to enable it programmatically. Some more details would help us properly prioritize the issue:
  • Do you want to just change the default, and leave the user control the option? Or enforce the accessibility mode without giving the user an option to turn it off.
  • Can you provide some details about your use-case? Do you have a majority of users that use screen readers? Or is it a compliance requirement?
Best,
Cristian
david.badger
Posts: 29
Joined: Tue Feb 25, 2014 12:14 am

Re: Set "Enable Accessibility Optimization" programmatically

Post by david.badger »

Thanks Cristian.

I think we're OK with being able to change the default programmatically (not necessarily force it).

The use-case is the custom CMS we're integrating with stores user information and preferences. We'd like to be able to read those preferences (including preference for accessibility optimization on/off) and reflect them during the editor session.
cristi_talau
Posts: 517
Joined: Thu Sep 04, 2014 4:22 pm

Re: Set "Enable Accessibility Optimization" programmatically

Post by cristi_talau »

Hello,

I registered your feedback as a feature request for a future version and I will update this forum thread when it will be implemented.

In the scenario that you described, if there is an "Accessibility Mode" in the CMS, I think that the best user experience would be that when the user enables that mode, to enable it in Web Author as well and do not let the user alter the option. If they are altering the option only for Web Author then the CMS-level and Web Autor-level options would diverge.

Best,
Cristian
Post Reply