WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Indicating primar and secondary action links to screen readers

for

From: Sailesh Panchang
Date: Sep 7, 2016 8:54AM

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
>>
>>