3 ms·

It's not that you are against a website's being tested with edbrowse; it just that you don't want that to be a substitute for testing using a screen reader and

• jscholes 6y ago
  > it just that you don't want that to be a substitute for testing using a screen reader and a mainstream browser. Do I have that right? For sure. If your website does work in edbrowse, it may imply that you have a decent chance of making it accessible because it doesn't use a ton of dynamic interactions or page updates etc. But it doesn't guarantee it. You could still have issues with heading hierarchy, communication of control state and other factors. In some cases, edbrowse may even lull someone into a false sense of security, because it simply can't present certain aspects of your page. But when displayed in a mainstream browser, they may be inaccessible. In a nutshell, it's unlikely that you can draw any meaningful conclusions after testing with edbrowse, be they about the accessibility of the page or the typical experience of a blind user on the web.
  • deleted 6y ago
    [deleted]