E-mail List Archives
Thread: Accessibility of Adobe Experience Manager Content?
Number of posts in this thread: 5 (In chronological order)
From: Robert Fentress
Date: Mon, Aug 25 2014 6:33AM
Subject: Accessibility of Adobe Experience Manager Content?
No previous message | Next message →
Hello, All.
I was so glad to find this list. Thanks, WebAIM for maintaining it!
I was hoping there might be some here who have had experience with the
content management system, Adobe Experience Manager 5.6, in
particular, the content it produces, by default, as opposed to the web
application interface used by content creators and editors. I'd like
to know if things like carousel widgets, media players, tree and
drop-down menus, and other interactive interface elements are keyboard
accessible and if they notify changes in state to individuals using
screen readers. If they are not accessible, how difficult are these
widgets to modify at a system-wide level?
Thanks, in advance, for sharing any experience you've had.
Best,
Rob
--
Robert Fentress
Senior Accessibility Solutions Designer
540.231.1255
Technology-enhanced Learning & Online Strategies
Assistive Technologies
1180 Torgersen Hall
620 Drillfield Drive (0434)
Blacksburg, Virginia 24061
From: Andrew Kirkpatrick
Date: Mon, Aug 25 2014 7:27AM
Subject: Re: Accessibility of Adobe Experience Manager Content?
← Previous message | Next message →
Rob,
We have a best practices document that you may want to take a look at, located at http://docs.adobe.com/docs/en/cq/current/administering/supporting-accessibility.html
If you have questions beyond the content of this document, feel free to contact me, either on this list or individually.
Thanks,
AWK
From: Robert Fentress
Date: Mon, Aug 25 2014 11:48AM
Subject: Re: Accessibility of Adobe Experience Manager Content?
← Previous message | Next message →
Thanks, Andrew. That is helpful.
So it appears from the document you referenced that, by default, the
carousel widget does not include alternative text for images, but that
a system administrator with sufficient knowledge could customize the
widget to do so. Is that correct? Is the default carousel
keyboard-navigable and can it be paused?
Also, am I correct in understanding that there is no native support
for the longdesc attribute on images, but that this could similarly be
added with some custom code by a system administrator?
Finally, it looked like in previous versions of Adobe Experience
Manager (AEM) that the ExtJS framework was used for the default
widgets in the web application interface, such as dialogs, trees and
grids, and that these widgets could be used in the produced websites,
as well. My understanding is ExtJS had very good WAI-ARIA support.
However, AEM now appears to use the Granite UI and I am not familiar
with this. Does this support WAI-ARIA to a similar extent?
Best,
Rob
On Mon, Aug 25, 2014 at 9:27 AM, Andrew Kirkpatrick < = EMAIL ADDRESS REMOVED = > wrote:
> Rob,
> We have a best practices document that you may want to take a look at, located at http://docs.adobe.com/docs/en/cq/current/administering/supporting-accessibility.html
>
> If you have questions beyond the content of this document, feel free to contact me, either on this list or individually.
>
> Thanks,
> AWK
>
>
From: Robert Fentress
Date: Mon, Aug 25 2014 11:55AM
Subject: Re: Accessibility of Adobe Experience Manager Content?
← Previous message | Next message →
Also, the page you referenced made mention of visual CAPTCHAs, but did
not say if CAPTCHA alternatives were supported?
Thanks,
Rob
On Mon, Aug 25, 2014 at 1:48 PM, Robert Fentress < = EMAIL ADDRESS REMOVED = > wrote:
> Thanks, Andrew. That is helpful.
>
> So it appears from the document you referenced that, by default, the
> carousel widget does not include alternative text for images, but that
> a system administrator with sufficient knowledge could customize the
> widget to do so. Is that correct? Is the default carousel
> keyboard-navigable and can it be paused?
>
> Also, am I correct in understanding that there is no native support
> for the longdesc attribute on images, but that this could similarly be
> added with some custom code by a system administrator?
>
> Finally, it looked like in previous versions of Adobe Experience
> Manager (AEM) that the ExtJS framework was used for the default
> widgets in the web application interface, such as dialogs, trees and
> grids, and that these widgets could be used in the produced websites,
> as well. My understanding is ExtJS had very good WAI-ARIA support.
> However, AEM now appears to use the Granite UI and I am not familiar
> with this. Does this support WAI-ARIA to a similar extent?
>
> Best,
> Rob
>
> On Mon, Aug 25, 2014 at 9:27 AM, Andrew Kirkpatrick < = EMAIL ADDRESS REMOVED = > wrote:
>> Rob,
>> We have a best practices document that you may want to take a look at, located at http://docs.adobe.com/docs/en/cq/current/administering/supporting-accessibility.html
>>
>> If you have questions beyond the content of this document, feel free to contact me, either on this list or individually.
>>
>> Thanks,
>> AWK
>>
>>
From: Andrew Kirkpatrick
Date: Mon, Aug 25 2014 12:40PM
Subject: Re: Accessibility of Adobe Experience Manager Content?
← Previous message | No next message
Rob,
GraniteUI is the UI model for the administrative interface. That is built on top of our internal CoralUI framework and we have done (and continue to) work to improve the accessibility of that framework, including utilizing ARIA where appropriate.
Granite isn't used for the widgets that an AEM author might put into a web site. The components for that are built on Sling for 5.6 and we are transitioning to Sightly for 6.0. The Sightly components need some work, which is a current area of focus for the product.
I'm not sure about the keyboard access to the carousel but can inquire.
For longdesc, yes, an admin could modify the UI to provide a way to easily add longdesc. It is also possible for a user to modify the code for an image component in the rich text editor to include the longdesc.
Hope this helps,
AWK