WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Keyboard accessibility of abbreviations

for

From: Scott González
Date: Apr 16, 2015 11:45AM

Regarding <ins> and <del>, I've seen this CSS recommendation before:

@media braille, embossed, speech {
del:before { content: "Deleted: "; }
del:after { content: " (End of deletion.) "; }
}
del:hover { text-decoration: none; }
ins { text-decoration: none; border-bottom: dashed green 2px; }


On Thu, Apr 16, 2015 at 12:51 PM, Moore,Michael (DARS) <
<EMAIL REMOVED> > wrote:

> And while we are at it can we get more bug fixes reported to the screen
> reader folks to recognize and indicate content inside of <ins> and </del>.
> I have reported this for years to no effect.
>
> Mike Moore
> Accessibility Coordinator,
> Texas Department of Assistive and Rehabilitative Services
> (512) 424-4159 (Office)
> (512) 574-0091 (Cell)
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of Jim Allan
> Sent: Thursday, April 16, 2015 10:26 AM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] Keyboard accessibility of abbreviations
>
> I would also file a bug on all of the browsers. keyboard access to
> abbreviations and such should be a browser function. There should not be a
> need for thousands of authors to code some stuff that should be a function
> of the browser.
> Jim
>
> On Thu, Apr 16, 2015 at 5:29 AM, < <EMAIL REMOVED> > wrote:
>
> > Hi List,
> >
> > I'm currently trying to improve the keyboard accessibility of our
> > website and recently decided to tackle abbreviations. According to the
> > German accessibility regulations (and I'm sure there are equivalent
> > success criteria in the WCAG) all functionality must be accessible by
> > keyboard, and the expanded form of all abbreviations must be accessible
> to all users.
> >
> > To achieve this, we set up this javascript solution:
> > https://jsfiddle.net/saenas/un40y5ey/
> >
> > But while it should fulfill the SC, we're not sure how good it is from
> > a usability viewpoint. Since we provide medical information, there are
> > a lot of abbreviations on our website, and implementing this solution
> > (or any like it, really) forces keyboard users to tab a lot more.
> > Additionally, while it is supposed to only expand the first instance
> > of each abbreviation per page, this mechanism doesn't work for the
> > navigation and the sidebar - so an abbreviation that is present in
> > each element would be expanded three times.
> > For reference, here is a link to one of our pages that contains LOTS
> > of
> > abbreviations: http://www.dimdi.de/static/de/klassi/index.htm
> >
> > That's why I'd like to ask keyboard users here: what do you think of
> > such a solution? Do you think it would improve your experience or make
> it worse?
> > Does anyone have suggestions for improvement?
> >
> > Thank you for your feedback!
> > > > > > archives at http://webaim.org/discussion/archives
> > > >
>
>
>
> --
> [image: http://www.tsbvi.edu] <http://www.tsbvi.edu>;Jim Allan,
> Accessibility Coordinator & Webmaster Texas School for the Blind and
> Visually Impaired
> 1100 W. 45th St., Austin, Texas 78756
> voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/
> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
> > > at http://webaim.org/discussion/archives
> > > > > >