WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessibility of Adobe Experience Manager Content?

for

From: Robert Fentress
Date: Aug 25, 2014 11:48AM


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 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
>
> -----Original Message-----
> From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Robert Fentress
> Sent: Monday, August 25, 2014 8:34 AM
> To: WebAIM Discussion List
> Subject: [WebAIM] Accessibility of Adobe Experience Manager Content?
>
> 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
> > > > > --
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