One customer wanting their website to be WCAG 2.0 AA level compliance is asking the website to be tested using JAWS, Talkback and Voiceover. The compliance needs to be tested for IE, MS Edge, Chrome , Firefox and Safari (in Mac OS, Windows 7, iOS & Android)
We already have NVDA in our approved to use product list.
Can't NVDA alone be used to test our website and certify it for WCAG 2.0 AA level compliance?
The Web Content Accessibility Guidelines (WCAG) require that web content conforms to a set of success criteria; they do not explicit require tests with specific browsers and assistive technologies. For example, when you look at the Techniques for WCAG 2.0, each technique and failure has a test procedure that is independent of specific products (except for "technologies" that are proprietary, such as Silverlight, where they suggest the use of UIAVerify or Silverlight Spy).
So the question is actually about defining what user agent support means for your client's site. While NVDA is fairly popular, it works only on Microsoft Windows and it does not always interact in the same way with certain browsers as other screen readers (e.g. Firefox support versus Chrome support). Unless your client's site is a fairly simple site with just static HTML, I would not recommend testing it only with NVDA. On Windows, the combination of JAWS and IE (including Edge) should not be ignored. Mobile is a different experience than desktop or laptop.
Conclusion: If you are evaluating a non-trivial website, do not test with NVDA alone.
Related
If I have website functionality that works in Chrome and Firefox but not in IE11, (basically a keyboard trap in a form). Does that still fail compliance? Or is the end user responsible for choosing browsers that work better?
Yes it would fail compliance. WCAG is browser agnostic and the guidelines are to be followed for all browsers. A significant number of people use JAWS as a screenreader, which is most widely used by Internet Explorer. This would be rendering the page useless for a significant number of users and would be a violation of
Guideline 2.1.
If I have website functionality that works in Chrome and Firefox but not in IE11, (basically a keyboard trap in a form). Does that still fail compliance?
You have to read Understanding Conformance to understand that this is a very complex questions
You can perfectly claim conformance based on tests done on some selected browsers, for instance those used by a company when talking about an intranet application ("Web technologies may only need to be supported by those specific user agents and assistive technologies deployed at a company."). But this will give you a conformance for those browsers, and not for the other one.
So yes, this will be conform using Chrome, and not using IE11. This does not help.
Or is the end user responsible for chosing browsers that work better?
You define your end user. If you can choose the browser used by your visitors (company intranet, touch screen kiosk, ...), then you are responsible for chosing and can set the required environment.
In any other case, if you can't choose the browser used by your visitors you have to give them a conforming version or an alternate conforming version.
You can claim conformance for a set of browsers, but as long as your website is not compatible with IE11, it will not be accessible for those users, and you can't ask them to use another browser (as they sometimes have no choice to)
I have problem with edge accessibility on window 10.
I see that microsoft edge supported accessibility technology as narrator. It can access and read controls on window 10. I try and see that it works normally.
However, AccExplore32 tool can not access web element in Edge although it still works with IE.
I use accessibility technology like AccTool. Therefore, I can not access control in Edge page.
Chrome has a setting that force chrome enable accessiblity by "--force-renderer-accessibility"
Does Edge have it ?
You can view the accessibility tree of Microsoft Edge using Inspect.exe from the Windows 10 SDK. You'll get the most accurate representation if you choose "UI Automation Mode" and "Control View" from the Options menu in Inspect.
Please see this blog post for more information on accessibility in Edge: Accessibility: Towards a more inclusive web with Microsoft Edge and Windows 10.
Currently (November 19th, 2015) Microsoft still doesn't provide fair accessibility in ApplicationFrame.dll which powers Edge, Calendar, the built-in mail client and some other Windows 10 apps. They actually broke the UIA (User Interface Automation) for assistive technologies.
This exactly is the reason why JAWS for Windows and other great assistive technology players lack support for Edge and other apps based on this library.
I want to create an ASP.NET web site. I have not been using ASP.NET for quite a while and I need help. As you know already there is an IE9 mobile browser for Windows phone, I have these questions:
1) Which version of ASP.NET is supported by the IE 9 mobile browser in Windows phone? I means all the output of html is ok.
2) Can all controls in all versions of ASP.NET be used for the IE9 mobile browser?
3) What di I need to set in the Declaration part < !Doctype.......> in my ASP.NET pages ? Will ASP.NET output it according for IE9 MObile Browser?
4) Does the Div control work ? Will this work Div.html = "........html ...."
5) What should not be used from ASP.NET for the IE 9 mobile browser?
6) How do I make the fontsize bigger or which fontsize is best for Wp screen?
------- Update
I have ASP.NET V1.1 with JQuery ( not the latest) , My Windows phone 7 HD7 can not work with the JQuery? Does JQuery have diff version for mobile than ASP.NET?
Any info on what version of Html spit out by ASP.NET V1.1,2.0, to the ASP.NET 4.0??
Using Plain HTML wont help much on the server for many server tasks.
Any resource link on how to build aspnet for windows phone 7 would be appreciated.
See the Web Development for Windows Phone details on MSDN as it provides specific guidance on developing for the phone and details of what is not supported on the phone (but is in the full version of IE9).
The phone uses the same code base for the rendering and javascript engine as the desktop version of IE9 does so most things should work.
If you're build a site specifically targetting the phone you will probably see better results if using jQueryMobile rather than the full version but be sure to test fully.
I'd recommend building a HTML 5 site rather than any (X)HTML 4 variation. The browser supports a lot of the newer functionality and you'll get a cleaner layout as well as backwards compatibility for other devices.
You'll also find lots of useful relevant articles at http://blogs.msdn.com/b/iemobile/ and http://windowsteamblog.com/windows_phone/b/wpdev/archive/tags/ie9/
ASP.NET is a server side technology so it is not related or constrained by the client devices which access to it, you can use Windows based computers, ITab, Max, Linux, Android, Windows Phone 7, Blackberry phones... to connect to the web site and in any case all the server side processing is performed on the web server (or other back end app servers depending on configuration), on the clients will only arrive html to be rendered and this could contain javascript to be executed locally.
in general modern mobile browsers are very good, I had the best experience with Android devices on mobile devices, which run some kind of Chrome compatible browser, iPhones and iPads run safari, also available for PC and Mac.
if you test your application from a PC with multiple browsers like Chrome, Safari and IE and everything works fine, it will most likely work fine, in general JavaScript abstraction libraries are used to write fully cross browser and cross platform javascript, one of the most popular is JQuery.
I am convinced that the version of IE9 (or similar one, it's not 100% the same IE9 of desktops) included in Windows Phone is probably advanced enough to support all HTML 4 tags and probably has a very advanced Javascript engine as well.
To detect from the server which user agent (device, browser) is connected and render different content or format layout with specific style sheets, check this question here in SO:
how to detect a mobile phone in a web application
I am creating mobile application in asp.net webform targeting IPhone, Android and blackberry. I am using JQuery-Mobile for the same.
Below is my first page I have developed with jquery-mobile.
I don't have iphone, android and blackberry. So my questions are:
Best Simulator I can use on windows XP/ Windows Server 2008 for Iphone, Andriod and Blackberry
Also, when I am running the application on the browser it is looking wierd. I mean textbox size, buttons. Is this the way it looks on normal webpage or it's my faulty design?
As I am developing application in asp.net, do I need to install latest browser which support HTML5 and CSS3 because below browser is IE7.
An old IE is not the best choice to test the capabilities of a HTML5+javascript framework...
For daily basis it's quite ok to use Firefox or any WebKit based browser (chrome, safari ...)
Emulators are very helpful, but to be sure your product works well you will probably need to give it a try on an actual device. I have already seen some reports of problems that show up only when working with the real device.
A team that I do some JQM stuff for has bought a cheap old ipod touch for testing. It's the most demanding apple product you can get. It has the oldest browser, causes most problems and is the slowest. Best choice! :)
Emulator for Android
Simulators for Blackberry
I'm sure Apple has one too - but I think you need to register as a iOS developer before you can get your hands on it. I believe using third-party iOS emulators is against Apple's policy.
Is WML and WMLScripts are used anymore ? I remember writing WML apps with classic-asp on server-side and we used interact with phone functionality from client using WMLScript and WTAI and do some cool things like, adding phone numbers to address book, trigger a call from WMLScript and much more. I still miss those things. I really want to know if modern web-browsers on phone have replaced WML with rich HTML support.
I also found that one of the most active WML and WAP forum Openwave Developers of our time is now discontinued which is no less than a shock to me. The forum also provided a nice WAP development SDK for testing WAP gateway simulation and WAP-pages on openwave browser simulator. All of these is now not seem to be available.
BEFORE DOWN VOTING EXPLAIN WHY, IF IS JUST BECAUSE OF IGNORANCE THEN STAY AWAY.
It is not dead yet.
It is used by some POS systems such as POSWEB, I have been developing on it for years in conjunction to ASP.NET to generate dynamic WML cards or downloadable catalogs, receipts, etc.
APPI Tecnologia's POSWEB Solution
Also another similar platforms do exist such as VERIWEB which are intended for the same purpose. Also I heard about similar ported WML/WMLScript being used in compact network enabled devices such as food / groceries dispensers, traveling card machines, etc.
This implementations supports mostly of the WML/WMLScript standard however it usually integrates additional functionality (depending on the target device), such as Smart Card processing, Simetric and assimetric cryptography, flat and indexed files creation and so on.
WML is still alive and in use many modern browsers doses not supporting WML for example andoid browsers like Firefox, Chrome but Opera still support WML for mobile and for web browsers also.
WML is more friendly to old phones but xHTML MP is the future in mobile WAP sites.
I would say, it's becoming less and less common out there in the wild.
You might find the odd device coming through that only does WML, but the effort to support those few might not be your goal in which case starting at html should be OK.
The users of those older phones typically already accept that their phone isn't the best and can't do as much as other phones.
Check out 0.facebook.com! There's been some resurgence of WML interest among some companies, mine included after Facebook Zero. The idea is that much of the technology still used in the developing world utilizes old technologies like WML, and coding up modern pages in WML will increase access in the developing world.