WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Indicating primar and secondary action links to screen readers

for

From: Birkir R. Gunnarsson
Date: Sep 7, 2016 11:11AM

Yeap, I err on the side of Sailesh's post here.
I don't think screen readers need the visual emphasis that helps other
users, such as people with cognitive impairment, identify the primary
action item on a page.
My gut instinct is to recommend removing the screen reader only text
indicating this styling, because I don't quite see that it helps the
uesrs any, it just adds to verbosity.
Cheers and thanks guys


On 9/7/16, Sailesh Panchang < <EMAIL REMOVED> > wrote:
> A very strong vote for not using markup / structure that developers
> don't have to invent and browsers / At do not support (uniformly) ...
> like aria-roledescription
> Proper heading structure will provide suitable context.
> A user can discover primary purpose or topic of a page from page title
> / h1 markup and review content that follows for primary action.
> Is it clear explicitly that The intent for styling 'Register'
> distinctly is to highlight difference between primary vs secondary
> only? Do users realize this or only the author?
> Also, as already stated, if it resembles a button, maybe it should be a
> button.
> Surely the 'Register' element can be styled distinctively so it grabs
> visual attention but no additional markup to aid accessibility is
> needed. ... Just like Submit and Cancel buttons can have different
> colors for visual identification as long as their purpose is clear
> via text.
> Regards,
> Sailesh Panchang
>
>
> On 9/7/16, Jeevan Reddy < <EMAIL REMOVED> > wrote:
>> the better way to communicating the primary and secondary actions is
>> to use button semantics to the primary action and link semantics for
>> the secondary action.. if the native button semantics can't permit you
>> then use 'aria button role'.
>> Cheers
>> Jeevan Reddy
>>
>> On 9/7/16, Jim Homme < <EMAIL REMOVED> > wrote:
>>> Hi,
>>> If I understand what you are saing, then this might lend itself to
>>> headings
>>> and sub-headings, as in h2 and h3, lists and nested lists, or some other
>>> autoatically-speaking structure that developers don't have to invent.
>>>
>>> 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 Birkir R. Gunnarsson
>>> Sent: Tuesday, September 06, 2016 4:48 PM
>>> To: WebAIM Discussion List < <EMAIL REMOVED> >
>>> Subject: Re: [WebAIM] Indicating primar and secondary action links to
>>> screen
>>> readers
>>>
>>> Imagine you have a page where users can read about an email offer list.
>>> The
>>> page includes a couple of links and some text, but the "register for our
>>> mailing list" link is visually formatted to stand out as the primary
>>> action.
>>> It is assigned a CSS class such as "primary action" or similar that makes
>>> it
>>> look box like (almost button like).
>>> Traditionally I haven't even thought of communicating this info in any
>>> way,
>>> if the link has accessible text and is in a content location that makes
>>> sense, and I don't think my stance on this has necessary changed.
>>> But when visual styling is used to assign priority to links on a page,
>>> well,
>>> it is tricky to figure out if that info is important enough to look for a
>>> text alterantive.
>>> Cheers
>>>
>>>
>>>
>>> On 9/6/16, Jim Homme < <EMAIL REMOVED> > wrote:
>>>> Hi Birkir,
>>>> We try to advocate for as little off-screen content as possible here.
>>>> Our view is that any site should try to make an equivalent experience
>>>> for as wide as possible audience of people with disabilities. If you
>>>> create off-screen controls, for example, people with motor
>>>> disabilities who have site might tab onto them and get confused when
>>>> focus disappears, and the same for people with inteellectual
>>>> disabilities.
>>>>
>>>> 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-techno
>>>> logy-solutions
>>>> E+R=O
>>>>
>>>> -----Original Message-----
>>>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
>>>> Behalf Of Birkir R. Gunnarsson
>>>> Sent: Tuesday, September 06, 2016 4:02 PM
>>>> To: WebAIM Discussion List < <EMAIL REMOVED> >
>>>> Subject: [WebAIM] Indicating primar and secondary action links to
>>>> screen readers
>>>>
>>>> Hi gang
>>>>
>>>> I am contemplating a curious question from my team.
>>>>
>>>> They are wondering if they should use visually hidden texton links and
>>>> buttons that are visually indicated as the primary and secondary
>>>> actions on webpages.
>>>> Basically primary action (or call to action) links or buttons
>>>> (normally one per webpage) get unique visual emphasis via CSS, ditto
>>>> with secondary actions.
>>>> There is no HTML element or ARIA attribute to provide equivalent
>>>> functionality programmatically (perhaps the aria-roledescription could
>>>> be used for this purpose).
>>>> Bottomline:
>>>> 1. Is this information important enough so that it should be provided
>>>> textually or programmatically? I have never made such a call in my
>>>> findings, and I have never seen it done on websites I have audited,
>>>> but it is a fact that this info could be important or at least useful on
>>>> some pages.
>>>> 2. If it is provided, is there a technique better than good old screen
>>>> reader text to do so?
>>>> I am not a fan of using heading tags to do this, I think it is not
>>>> correct use of headings.
>>>>
>>>> Cheers
>>>> -B
>>>>
>>>> --
>>>> Work hard. Have fun. Make history.
>>>> >>>> >>>> archives at http://webaim.org/discussion/archives
>>>> >>>> >>>> >>>> archives at http://webaim.org/discussion/archives
>>>> >>>>
>>>
>>>
>>> --
>>> Work hard. Have fun. Make history.
>>> >>> >>> at
>>> http://webaim.org/discussion/archives
>>> >>> >>> >>> >>> >>>
>>
>>
>> --
>> Best Regards,
>> Jeevan Reddy,
>> Accessibility Consultant,
>> Infosys Ltd,
>> Bangalore, India.
>> >> >> >> >>
> > > > >


--
Work hard. Have fun. Make history.