WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Hidden text and mobile devices

for

From: Birkir R. Gunnarsson
Date: Aug 24, 2016 1:00PM

I see (and have recommended) one use case for screen reader specific
text in datepicker/calendar grids, where the sighted user get the
month and day of week from caption/column header. Screen readers read
tables (let alone grids) so differently, that sometimes the only way
to ensure a consistent experience is to create screen reader only text
for the individual date buttons.

That is about the only use case I can think of, in general I totally agree.
Since the question to this list came from somebody in the airline
industry, I would not be super surprised if the scenario is a
datepicker.


On 8/24/16, Jim Homme < <EMAIL REMOVED> > wrote:
> Hi Jared,
> Your last statement is correct. Furthermore, NVDA does not have a setting to
> change how it handles the abbrev and acronym tags, and I do not remember
> intentionally testing that tag with NVDA. JAWS has the setting that expands
> these tags off by default. I don't have Window-eyes installed right now, and
> don't know how it treats the tags. I would also need to intentionally test
> this with VoiceOver. I have an iPhone.
>
> Thanks.
>
> Jim
>
>
> =========> Jim Homme,
> Accessibility Consultant,
> Bender HighTest Accessibility Team
> Bender Consulting Services, Inc.,
> 412-787-8567,
> <EMAIL REMOVED>
> http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
> E+R=O
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf
> Of Jared Smith
> Sent: Wednesday, August 24, 2016 9:30 AM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Hidden text and mobile devices
>
>> To give a concrete example: when we display a date in short format
>> (Mon 26 Oct), we hide this element with aria-hidden, and add a sr-only
>> text (Monday 26 October) for screen readers.
>
> Why would "Mon 26 Oct" be any more confusing to a screen reader user than to
> a sighted user? If this text is not understandable as is, it should be
> expanded and made more useful for everyone. If it's not confusing visually,
> providing much more verbose and lengthy text just for screen reader users
> isn't creating an equitable experience.
>
> Most screen readers have a setting for reading the expansion (title
> attribute) for acronyms and abbreviations. I believe the default is to not
> read these on Windows screen readers.
>
> Jared
> > > http://webaim.org/discussion/archives
> > > > > >


--
Work hard. Have fun. Make history.