E-mail List Archives
WCAG 2.0 level AA and the combination between screen readers and browsers compatibility
From: Eilana Benish
Date: Jun 3, 2019 10:08AM
- Next message: Michael Ausbun: "Accessible automated tools"
- Previous message: Michael Ausbun: "Re: MathML and simple math content"
- Next message in Thread: Birkir R. Gunnarsson: "Re: WCAG 2.0 level AA and the combination between screen readers and browsers compatibility"
- Previous message in Thread: None
- View all messages in this Thread
Hi all,
is there any document from the WCAG which specifies how many screen readers
and browser combinations should be compatible to the WCAG 2 level AA?
from my experience, it is impossible to meet all the combinations with all
screen readers and browsers when websites implement ARIA and HTML5
Here in Israel, we must comply to the Israeli 5568 standard which based on
the WCAG 2.0 Level AA and the modification maid so the 2.4.10 Section
Headings level AAA
<https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-headings.html>
criteria will be also included in the Israeli 5568 standard (I insisted for
that downgrade back then …).
HTML 5 and ARIA are commonly used, many times incorrectly and when not
needed… and then the fixing issues starts.
I know the common combinations for screen reader and browsers
· NVDA + FF
· JAWS + Google chrome and IE
· IOS + safari
· Talkback + android
I`m testing in the latest versions …
But sometimes the developer develops the sites with JAWS for chrome and IE
and leaves the rest behind. And then I have to ask to repair… and then they
start to argue
And at the end, the client wonts to be sure that his website is WCAG and
the regulations compliant. And in Israel, I am authorized
accessibility consulted
â and my signature required
So, I need to know what the WCAG have to say about the compliant issue.
I hope someone can help me with that
Thanks in advance.
Eilana Benish
*×××××× ×¨×, ×××× × ×× ×ש, *
*×××¨×©× × ××ש×ת ש×ר×ת (2200)*
*××××× ×× ×××× ×¤×¨××ק×××: **× ××ש×ת ×ש××ש×ת ××× ××¨× × ×××× ××××××ת ××××¢*
<https://adn-accesstime.com/2018/10/20/×פ××קצ××ת-ת×××ר×ת-×תק××ת-reminder-reminders-with-×-ios/>
*××פ×× 050-7100367 ×××"× ** <EMAIL REMOVED> *
< <EMAIL REMOVED> >
*××פ××קצ×× â **IOS*
<https://itunes.apple.com/app/id1438649378?fbclid=IwAR2xQt2j9TXnIBdOVz1oY3T0oBPTepgWndQIlruALWr4q7T4gTZ1mUJAmCQ>*
â **×× ×ר××××*
<https://play.google.com/store/apps/details?id=com.adn_accesstime.presspadnews&fbclid=IwAR2KslNcOzRqC8zD_Dpr9qI5EvHFjKAQK2-lCwFoMLVgVHw-M34OZIuUTDo>
- Next message: Michael Ausbun: "Accessible automated tools"
- Previous message: Michael Ausbun: "Re: MathML and simple math content"
- Next message in Thread: Birkir R. Gunnarsson: "Re: WCAG 2.0 level AA and the combination between screen readers and browsers compatibility"
- Previous message in Thread: None
- View all messages in this Thread