Re: X-UA-Compatible meta tag and Assistive Technologies

Thank you, Adam and Léonie!

I think it's the IE 11 having issues with Compatibility mode. Some of the
stone-age applications I am working on are set to run in IE 7 mode in the
intranet and using Aria-attributes in them breaks the JQuery and stops the
keyboard interaction as well. I do not have a sample page that I can share
with you. But, I found similar differences in another page to show you an
example:

The page from Ryerson uni's Aria demo page (link follows) works has
keyboard interaction issues in IE 11. The left and right arrow keys does
not move the focus to next tab. But, when it runs in IE 10 compatibility
mode, it works fine.

https://de.ryerson.ca/wa/aria/jquery/tabpanels.html#?1486076256967#goto_tabs

My worry is I can force IE to load the application in the mode that does
not break the application behavior. But, I am also worried if this might
cause any other issues to AT users.

As per Léonie's statement, I also found there are differences in the focus
order due to the unclosed tags. Time to revalidate the code.

Thanks and Regards,
Herin

On Thu, Feb 2, 2017 at 8:35 PM, Léonie Watson <tink@tink.uk> wrote:

> On 02/02/2017 04:10, Herin Hentry wrote:
>
>> I am working on few applications that re-renders in IE Edge in the
>> Emulation mode (IE 5, 7, 8, 9) as they have the X-UA-Compatible meta tags.
>>
>> Has anyone noticed any issues screen readers or other assistive
>> technologies face due to this?
>>
>>   * Visually there are CSS styling differences between Edge and the
>>     older IE versions
>>   * Deprecated HTML tags are adjusted by the IE version.
>>
>
> With the exception of text introduced using the before/after selector [1],
> and focusable content that is reordered using things like FlexBox [2], CSS
> does not tend to affect screen readers.
>
> The use of deprecated HTML tags might be a different story. I think it
> would depend on whether emulation mode changed the way the accessibility
> tree was constructed, as well as how the content was rendered. Do you have
> an example you can point to?
>
>
>> Has there been any research done in this area to refer to about there
>> interaction with ATs?
>>
>
> None that I know of, or could find based on a few minutes searching.
>
> Léonie
> [1] http://tink.uk/accessibility-support-for-css-generated-content/
> [2] http://tink.uk/flexbox-the-keyboard-navigation-disconnect/
>
> --
> @LeonieWatson tink.uk Carpe diem
>