E-mail List Archives

Search E-mail List Archives for

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

From: Graham Armfield
Date: Tue, Jul 14 2015 5:02AM
Subject: Interactive Elements on Older Technologies - ARIA vs Screen Reader Text
No previous message | Next message →

I'm working with a client at the moment on a website that contains
interactivity like modals, accordions, tab panels, etc. And I'm familiar
with all the necessary ARIA attributes that would be required to help site
visitors with AT work with these interactive elements.

However, there is a requirement to support some older browsers and site
visitors on earlier Android platforms - some with little or no ARIA support.

I'm thinking that judicious deployment of some screen reader text to
explain what elements are for and whether they are selected/expanded would
help the users on the older technologies.

But my question is, should I deploy those alongside the full ARIA solution
too? I'm thinking yes, as I'd rather not degrade the experience for those
on more modern technologies that do support ARIA. However I am concerned
that doing so may create a lot of extra noise for those on ARIA supporting
technologies.

What are your views on a sensible way forward here?


​Thank
s
Graham Armfield



coolfields.co.uk <http://www.coolfields.co.uk/>;
M:07905 590026
T: 01483 856613
@coolfields <https://twitter.com/coolfields>

From: Lynn Holdsworth
Date: Fri, Jul 17 2015 11:11AM
Subject: Re: Interactive Elements on Older Technologies - ARIA vs Screen Reader Text
← Previous message | Next message →

Hi Graham,

If you know the older browsers and Android versions that your users
will be browsing with, how feasible would it be to sniff these out and
serve them up a fallback version of the markup?

KR, Lynn

On 14/07/2015, Graham Armfield < = EMAIL ADDRESS REMOVED = > wrote:
> I'm working with a client at the moment on a website that contains
> interactivity like modals, accordions, tab panels, etc. And I'm familiar
> with all the necessary ARIA attributes that would be required to help site
> visitors with AT work with these interactive elements.
>
> However, there is a requirement to support some older browsers and site
> visitors on earlier Android platforms - some with little or no ARIA support.
>
> I'm thinking that judicious deployment of some screen reader text to
> explain what elements are for and whether they are selected/expanded would
> help the users on the older technologies.
>
> But my question is, should I deploy those alongside the full ARIA solution
> too? I'm thinking yes, as I'd rather not degrade the experience for those
> on more modern technologies that do support ARIA. However I am concerned
> that doing so may create a lot of extra noise for those on ARIA supporting
> technologies.
>
> What are your views on a sensible way forward here?
>
>
> ​Thank
> s
> Graham Armfield
>
>
>
> coolfields.co.uk <http://www.coolfields.co.uk/>;
> M:07905 590026
> T: 01483 856613
> @coolfields <https://twitter.com/coolfields>
> > > > >

From: Graham Armfield
Date: Fri, Jul 17 2015 12:23PM
Subject: Re: Interactive Elements on Older Technologies - ARIA vs Screen Reader Text
← Previous message | No next message

Is it feasible to sniff for particular aria attribute support?

I don't think any browser or AT has total ARIA support at this stage, so
you'd need to test at the attribute level.

Regards
Graham
On 17 Jul 2015 18:11, "Lynn Holdsworth" < = EMAIL ADDRESS REMOVED = > wrote:

> Hi Graham,
>
> If you know the older browsers and Android versions that your users
> will be browsing with, how feasible would it be to sniff these out and
> serve them up a fallback version of the markup?
>
> KR, Lynn
>
> On 14/07/2015, Graham Armfield < = EMAIL ADDRESS REMOVED = > wrote:
> > I'm working with a client at the moment on a website that contains
> > interactivity like modals, accordions, tab panels, etc. And I'm familiar
> > with all the necessary ARIA attributes that would be required to help
> site
> > visitors with AT work with these interactive elements.
> >
> > However, there is a requirement to support some older browsers and site
> > visitors on earlier Android platforms - some with little or no ARIA
> support.
> >
> > I'm thinking that judicious deployment of some screen reader text to
> > explain what elements are for and whether they are selected/expanded
> would
> > help the users on the older technologies.
> >
> > But my question is, should I deploy those alongside the full ARIA
> solution
> > too? I'm thinking yes, as I'd rather not degrade the experience for those
> > on more modern technologies that do support ARIA. However I am concerned
> > that doing so may create a lot of extra noise for those on ARIA
> supporting
> > technologies.
> >
> > What are your views on a sensible way forward here?
> >
> >
> > ​Thank
> > s
> > Graham Armfield
> >
> >
> >
> > coolfields.co.uk <http://www.coolfields.co.uk/>;
> > M:07905 590026
> > T: 01483 856613
> > @coolfields <https://twitter.com/coolfields>
> > > > > > > > > >
> > > > >