E-mail List Archives

Search E-mail List Archives for

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

From: Nahidi, Jinkuk
Date: Wed, May 14 2014 10:17AM
Subject: Disclaimer accessibility and widget accessibility on assets.cms.gov
No previous message | Next message →

Hi all,

Question 1:

For disclaimer content that is superscripted, I've seen one approach but I really don't feel is ideal where the superscripted disclaimer (1) is a link to the disclaimer/legal text at the end of the site. If we don't link it does it not make it accessible? Or is there another way? I personally could not figure out an elegant approach. I thought about maybe describedby but its not interactable/focusable so that was a no go.

The experience of a person going to the disclaimer through an anchor/focus would also not be ideal because of the going back and just really effects the users flow. Ideally just having some sort of aria tag that says hey this is the disclaimer text for this paragraph or that there is a disclaimer text somewhere at the end callout as the person reads that paragraph. Just wondering if something like that exists currently.

Question 2/Comment about assets.cms.gov:

This asset below isn't accessible or is it?

I can not interact with it via keyboard to navigate the slider and thus it isn't accessible? Would adding just a tab index element which I tried in my browser deep it accessible then? It did work for me when I just edited the html in my browser and verified the functionality of the slider.

I just want to make sure there isn't some sort of magic happening here that makes it accessible and if there is I'd like to know what it is. :)

http://assets.cms.gov/resources/framework/2.0/Pages/demo-slider.html

Thanks,

Jinkuk Nahidi

From: Petri, Kenneth
Date: Thu, May 15 2014 1:38PM
Subject: Re: Disclaimer accessibility and widget accessibility onassets.cms.gov
← Previous message | Next message →

Re: Question 2: It's broken. No keyboard interactivity, though the screen reader still reports it as a slider and reads the value properly.

From: Birkir R. Gunnarsson
Date: Sat, May 17 2014 5:13PM
Subject: Re: Disclaimer accessibility and widget accessibility on assets.cms.gov
← Previous message | No next message

In terms of accessible foot notes.
This is where the ARIA floto-flowfrom properties would come in handy dandy.
Unfortunately assistive technology support for these is still near
completely missing (Jaws has some support with Firefox only).
You may want to implement foot notes as links (to foot notes, and a
link from the foot note back to the paragraph that references it),
with aria-flowto as an experimental addition.
In other words, the links would have to be an accessible fallback to
using the aria-flowto/flowfrom set of properties.



On 5/15/14, Petri, Kenneth < = EMAIL ADDRESS REMOVED = > wrote:
> Re: Question 2: It's broken. No keyboard interactivity, though the screen
> reader still reports it as a slider and reads the value properly.
>
>
>
>