E-mail List Archives
Number of posts in this thread: 3 (In chronological order)
From: Joseph Sherman
Date: Dec 7, 2015 11:01AM
Subject: Microsoft 365 login page
No previous message | Next message →
Anyone had to look at the 365 login page<https://login.microsoftonline.com/>? Is it just me, or for such a simple page it sure has a lot of code: hidden labels, ARIA labels, alt text for form divs, lots of hidden elements, tabindex, a Div with role=button, etc.
Joseph
From: Sundby, Valorie
Date: Dec 7, 2015 11:25AM
Subject: Re: Microsoft 365 login page
← Previous message | Next message →
Joseph,
I see what you mean. This page does not follow the "First rule of ARIA use -
If you can use a native HTML element [HTML5] or attribute with the semantics and behavior you require already built in, instead of re-purposing an element and adding an ARIA role, state or property to make it accessible, then do so." http://www.w3.org/TR/2013/WD-aria-in-html-20131003/#first-rule-of-aria-use
By including ARIA when it is not necessary to do so creates more extensive testing and unnecessary maintenance.
If anyone knows of any benefit to using ARIA when native HTML works just fine, it would be terrific to hear from you.
Valorie
From: Detlev Fischer
Date: Dec 7, 2015 12:30PM
Subject: Re: Microsoft 365 login page
← Previous message | No next message
>
>
> If anyone knows of any benefit to using ARIA when native HTML works just fine, it would be terrific to hear from you.
That's easy - it happens all the time. Designers often dislike the look of native elements (checkboxes, ranges etc.) which varies by browser, and want to customise it to fit the overall design. With proper ARIA mark-up, these elements stand a chance of working OK for screen reader users.
> Valorie
>
>