WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Edge Chromium vs Chrome - accessibility differences?

for

From: Vaibhav Saraf
Date: Nov 25, 2020 11:54PM

Hi Mallory,

To my bad luck the website has done some corrections today it seems.
Yesterday there was no 'href' attribute for the <a> element in the dev
tools but today I can see one. I would have thought that I was dreaming but
I had shared this to a teammate and she observed the same.

Today the code looks like this:

<a href="
https://courses.edx.org/register?course_id=course-v1%3AUPValenciaX%2BHIENGLISH201.4x%2B1T2020&amp;enrollment_action=enroll&amp;email_opt_in=false"
class="btn-brand enroll-btn legacy w-100"><div
class="text-center"><span>Enroll <div><small>Starts Nov
25</small></div></span></div></a>

Thanks,
Vaibhav





On Thu, 26 Nov 2020 at 02:32, Mallory < <EMAIL REMOVED> > wrote:

> Hi Vaibhav,
> I'd be interested in seeing the code snippet for that button, or the
> website. I would not expect either browser to call the link a button!
>
> cheers,
> _mallory
>
> On Wed, Nov 25, 2020, at 5:56 PM, Vaibhav Saraf wrote:
> > Hi Mark,
> >
> > Today I had opened an educational website on Edge and Chrome. I was
> > surprised to see that the 'Course Enrollment' button was spoken as button
> > on Chrome and as a link on Edge.
> >
> > It was built with <a> anchor element with the a button class from some
> > framework.
> >
> > Also I was using the latest versions of both the browsers with NVDA
> 2020.3.
> > That can give a hint to your initial questions, very curious why this is
> > the case.
> >
> > Thanks,
> > Vaibhav
> >
> >
> > On Wed, 25 Nov 2020 at 17:36, Mark Magennis < <EMAIL REMOVED>
> >
> > wrote:
> >
> > > Now that Edge is using Chromium, I'm wondering what this will mean
> > > regarding accessibility. In what ways will the experience of using a
> > > website in Edge 2 differ from using it in Chrome. Some questions that
> come
> > > to mind are:
> > >
> > >
> > > * Will the accessibility tree in Edge be the same as the
> accessibility
> > > tree in Chrome?
> > > * Will Edge's support for ARIA be the same as Chrome's?
> > > * Might any of the heuristics that screen readers use beyond
> accessing
> > > the accessibility tree lead to different experiences?
> > > * Will the two browsers display colours in the same way?
> > > * Are there specific accessibility tests that need to be done in
> both
> > > browsers and others where testing in one will cover the other as well?
> > >
> > > I don't know whether these are the right questions to ask, but I'm
> looking
> > > forward to getting any knowledge and insight that's available about the
> > > impact of the switch.
> > >
> > > Thanks,
> > > Mark
> > >
> > > Mark Magennis
> > > Senior Accessibility Specialist
> > > Skillsoft | mobile: +353 87 60 60 162
> > > www.skillsoft.com<;http://www.skillsoft.com/>;
> > >
> > > [Skillsoft / Sumtotal]
> > >
> > > > > > > > > > > > > > >
> > > > > > > > > >
> > > > >