FAQ

FireEyes Extension Compatibility

The tables below outline our support for the various combinations of Operating Systems and Browsers. In the table FireEyes OK shows we have no outstanding issues with FireEyes. Focus rules OK is related to the Focus test available in FireEyes. Certain versions of FireFox do not support this feature.

Windows XP, Vista, 7

Firefox version	Firebug version	FireEyes OK?	Focus rules OK?
< 3.5		no
3.5 – 3.6.*	1.6.*	yes	yes
4.0.*	1.6.* – 1.7.*	yes	no: bug #1252
5.0.* +	1.7.* – 1.9.*	yes	no: bug #1252

Mac OS X 10.5 — 10.6.8

Firefox version	Firebug version	FireEyes OK?	Focus rules OK?
< 3.5		no
3.5 – 3.6.16	1.6.*	yes	yes
3.6.17 & 3.6.18	1.6.*	no: bug #1321
4.0.*	1.6.* – 1.7.*	yes	yes
5.0.* +	1.7.* – 1.9.*	yes	yes

Mac OS X 10.7

Note that OS X 10.7 does NOT ship with Java installed, but will automatically download and install a Java runtime the first time it’s needed. Steps to install:

1. Run a Java app to get Java installed. Simplest procedure: open a Terminal.app window and run the command: ‘java’. Alternate procedure: get started from this web page: http://support.apple.com/kb/DL1421

2. After this is complete, open the Java Preferences app (/Applications/Utilities/)

3. By default, “Enable applet plug-in and Web Start applications” is unchecked – but it must be checked for FireEyes to run!

Firefox version	Firebug version	FireEyes OK?	Focus rules OK?
< 5.0.1		no
5.0.1 +	1.7.* – 1.9.*	yes	yes

Release information

Do I need an account on Worldspace Sync in order to use FireEyes?

Yes. Unlike some of the earlier beta versions, the release version requires you to create a free account on Worldspace Sync and to enter your account information under the “Settings” tab of FireEyes. This is because some content and features of FireEyes are loaded dynamically from Worldspace Sync. Failure to provide this information will cause the product to not work correctly.

Do I need to use Firebug in order to use FireEyes?

Yes. FireEyes runs as a plugin for Firebug (the premier web developer tool for Firefox). Several features of FireEyes integrate with the existing developer tools provided by Firebug, and FireEyes presents itself as an additional tab in the Firebug user interface.

What is the current release status of FireEyes?

FireEyes 1.0.21 is the first production release of the product. Refer to the release notes at the end of this FAQ for details on what is new in this release.

Accessibility of FireEyes

Is FireEyes accessible?

If you’re an AT user, you’ll have to enable the Firebug “accessibility” option in order to use Firebug with your AT. FireEyes contains a setting called “Ensure that Firebug accessibility enhancements are turned on when FireEyes launches.” When this setting is enabled, FireEyes will verify that Firebug’s own accessibility option is also enabled. This setting is enabled by default when you install FireEyes.

The FireEyes user interface is implemented in 100% accessible HTML. However, in the current FireEyes release, JAWS and other ATs do not treat the HTML within an extension the same way they treat the same HTML in the browser. Given this, some components of the user interface may be more difficult to use with AT than without. A future release of FireEyes will address this problem.

What accesskeys are provided by FireEyes?

Firefox does not allow the discovery of accesskeys within the HTML UI of an browser plugin in the same way that it allows the discovery of these within the browser window. The following accesskeys are available, even though they may not be discoverable by AT:

0: ‘Current Document’ tab, switched to and focused
1 through 9: report headings in ‘Current Document’ tab, in reverse chronological order
L: Last tab available, switched to and focused

The accelerator keys used for accesskeys in Worldspace FireEyes do not reflect the user-configurable options that may have been set in the Firefox browser. On Windows computers, the accelerator key will always be the Alt key. On Mac OS computers, the accelerator key will always be the Control key.

What keyboard shortcuts are provided by FireEyes?

One keyboard shortcut is provided:

Alt+F12: toggle Firebug and FireEyes. If Firebug is running attached to the browser window (the default mode), this shortcut will toggle the Firebug panel, and ensure that Worldspace FireEyes is focused whenever Firebug is activated. If Firebug is running in a detached window, this shortcut will bring the Firebug window into the foreground, and ensure that Worldspace FireEyes is focused.

Installation prerequisites

What are the software dependencies for FireEyes?

FireEyes requires:

Firefox (versions 3.5.3 through 10.x),
Firebug (1.5.3 through 1.9.x), and
Java (1.5 or higher, must be installed and enabled in the browser).

Please refer to the extension compatibility tables at the top of this page for specific combinations of Firefox and Firebug that are supported.

If the wrong version of Firebug is installed what will happen?

If the version of Firebug is earlier than 1.5.3, then the FireEyes will be be listed as “additional dependencies required” in the Firefox add-ons pane. The FireEyes user interface will not appear inside Firebug.

If Java is not enabled correctly, what will happen?

If Java is not enabled, or if the wrong version of Java is installed, then FireEyes will load, but will show an error message allowing you to identify when this situation exists. In order to use FireEyes, you will need to install and/or enable a support Java plugin version.

Why is Java disabled?

Mac OS Lion – Updates are disabling Java. Java will not really be enabled unless the user goes to a java applet page. Even if they test java it will not enable unless it’s a java applet.

If the user goes here they will get a popup to cancel or enable and that lets java run

Go to this url to enable java:

http://www.java.com/en/download/testjava.jsp

What happens if I cannot install the correct Java version?

If you cannot install or enable the correct Java version and your IT administrators are not able to do this on your behalf, then you should uninstall FireEyes so that you can continue to use Firebug without encountering the error message.

Is there a version of FireEyes for Internet Explorer, Google Chrome or Safari?

Yes. If you login to Worldspace Sync with Safari, you will be able to install and download the FireEyes lite version for Safari. An Internet Explorer version of the product is currently only available to Worldspace Sync customers.

What operating systems has Worldspace FireEyes been tested on?

Worldspace FireEyes has been tested on Mac OS X (10.5, 10.6, and 10.7) and Windows (Windows XP and Windows 7). It should work on any operating system on which Firefox and Firebug work, and where a Java plugin or runtime environment for Firefox is available. Please report issues that you encounter on other platforms.

Features

Which standards does FireEyes support?

Worldspace FireEyes currently supports WCAG 1 (Priorities 1, 2 and 3), WCAG 2 (levels A and AA), section 508 and some dynamic rules that test for WAI-ARIA compliance.

Does FireEyes support static pages?

Yes. FireEyes can evaluate both static and dynamic web sites and applications.

Automated analysis is done in the background, as you interact with a dynamic site or application. FireEyes monitors all of the browser events including the initial “load” event, and analyzes content as it appears or is changed.

If you want to control the points at which the analysis is done, you can ensure the “Automatic” analysis checkbox is off. Analysis will then occur only when you use the “Now” button to analyze the currently loaded site or page.

Does FireEyes support analyzing multiple pages or a whole site?

Yes. When you have Automatic analysis turned on, then every page you visit will be analyzed and the results will be accumulated in the “Report” tab. The “Current Document” tab will only display the results for the page you are currently viewing in the browser.

Can you export the results of an analysis?

Yes. If you upload the analysis issues to Worldspace Sync, then the issues can be exported in either Excel or Comma Separated Value (CSV) format from the issues report of the project.

Does FireEyes support the remediation of static issues?

Yes. By editing the content of the page using Firebug’s HTML inspector and editing features, you can change the HTML structure. Clicking the “retest” button on an issue in FireEyes will evaluate the HTML to see whether the issue is still present. If the issue has been remediated, the issue will be marked as remediated in the report. When you upload the issue to Worldspace Sync, the modified HTML for the element will be saved along with the issue.

Does FireEyes support the remediation of dynamic issues?

Yes. Using the event recording feature, you can create scripts that can be re-run to reproduce dynamic issues. These scripts can be uploaded to Worldspace Sync and downloaded and re-run at a later point. If “Analyze” is checked in the “Replay” toolbar, analysis will be performed while the script replays — this will validate whether previously discovered issues still exist.

Does FireEyes simulate an AT’s rendering of a web page?

Yes. SimulAT can be used to simulate various AT renderings including a full page transcript, headings, images, links, tables and more. Sighted users who are not familiar with assistive technologies (AT) such as JAWS on NVDA can use this to visually validate what the AT user would hear.

Can scripts be shared with other developers?

Yes. By uploading a script to Worldspace Sync and inviting other users to collaborate with you on the project, you can share scripts and issues with developers, QA engineers, designers, etc.

What does the “Freeze” button do?

The “Freeze” button stops all user events except for the scroll event from being delivered to the browser. The web site or app is then frozen in place, and cannot be change further until it is “Thawed.”

This is useful for exploring interim browser states using Firebug’s HTML inspector in cases where using the inspector would cause the state of the browser to change.

When used in conjunction with script replay, “Freezing” allows you to examine the state of a web app at the point where an error occurred, without triggering mouse move, mouseover and mouseout events or changing the focus of the browser. For example, if FireEyes detects an accessibility issue with an autocompleted drop-down associated with a search form, you might “Freeze” the search in a state where the drop-down is visible.

What are the blue- and green-striped areas that appear in the browser?

The green- and blue-striped areas represent accessibility issues and are toggled on and off by checking or un-checking the “Highlight” checkbox. They are intended only for sighted users and perform two functions: first, they stop the sighted user from interacting with the web page, thereby simulating the usability that a user of AT would have; and second, they allow the sighted user to visually locate the element related to an issue. AT users can get the same information: first, interacting with the web page using the AT, and second, by clicking the “Inspect” button to view the HTML related to the issue in the Firebug HTML inspector.

These highlights also show some summary data. Each highlight is annotated with the element or tag, the number of issues found for that element, and information about issue severity and type. When you mouse over a highlight, an overlay appears in the bottom-left corner of the window showing a summary of the issues associated with the highlighted element. If you click on a highlight, the associated issues will be focused in FireEyes, allowing you to access all of the information related to the issues.

FireEyes is capturing too many changes and events and they are overwhelming me. What can I do?

There are a couple of reasons why FireEyes might capture many events. Firstly, you might have the event recording options, which can be viewed and changed on the “Settings” tab set to record very chatty events such as mouse movements. By turning these off, you can reduce the amount of information captured and displayed by FireEyes; secondly, your web application might be generating lots of changes in the document through the use of JavaScript. You can use the “Filter” button to filter out the changes and events so that they do not appear in the report; thirdly, you can turn off event recording altogether by un-checking the “Record” checkbox.

By default, FireEyes records only a useful subset of events. For example, it will record mouse click events, but not mouse motion events. In order to record and replay all of the events needed to trigger functionality on your site or app, it may be necessary to enable additional event recording options — in which case, many more events will be recorded

What is a project?

Developers often have to work on multiple applications or web sites and different FireEyes settings maybe appropriate for each of these sites. Projects allows you to specify the domains that belong to your project (production, Q.A. and your private sandbox) so that you can have one set of settings for each project. Projects can also be shared with other users allowing you to collaborate on fixing accessibility issues and tracking your progress on fixing them. Finally, projects allow you to record scripts on your sandbox and replay it in your production environment to determine whether the same issues occur in both environments. This can be very useful for QA engineers and developers. Projects are configured in Worldspace Sync, and then loaded into FireEyes.

Why do you have the “Color”, “Order” and “Focus” buttons?

In order to accurately perform color contrast, reading order analysis and focus indicator testing, FireEyes has to send events to the browser and perform DOM manipulations. For example, when performing reading order analysis, FireEyes will disable stylesheets momentarily, to test reading order when CSS is not available or loaded. In order to avoid an infinite loop of analysis when “automatic” analysis is turned on, certain tests have been placed inside a button. Pressing this button will disable the automatic analysis while the analysis is taking place and the re-enable it once completed.

Why does the display sometimes change during reading order analysis?

Worldspace FireEyes does a two-pass analysis on the reading order. The first pass is with CSS enabled and the second pass is with CSS disabled. When the CSS is disabled, the browser will sometimes redraw the document before the analysis begins. This will result in the display of the page changing.

Release notes

Release 1.0.21

New features in release 1.0.21
- FireEyes has a refreshed user interface and improved navigation paths. If you have used any of the previous betas, the overall user interface will be familiar to you — please note that the “Settings” and “Accounts” tabs in earlier betas have been collapsed and simplified into a single “Settings” tab.
- FireEyes integrates with the new Worldspace Sync. This replaces beta 4’s integration with the Worldspace FireEyes server, as well as with the previous version of Worldspace, Worldspace Enterprise.
- FireEyes supports a wider range of Firefox versions (3.5.3 — 10.x) and Firebug versions (1.6 — 19.x).
- Issues are assigned a priority (Critical, Serious, Moderate, or Minor). You may filter issues by priority, making it easier to focus on resolving the most critical accessibility issues first.
- Improved UI for filtering issues and events.
- Improved UI for downloading and uploading issues, events, and projects to and from Worldspace Sync.
- Improved UI for informational, warning, and error messages.
- When highlighting issues, the highlights contain some helpful data (the highlighted tag, # of issues, issue severity, and type of issue). Additionally, when a highlight is moused over, an overlay appears in the bottom-left corner of the document showing a summary of issues associated with that element. (As always, you may click on the highlight to see a detailed presentation of the associated issues inside FireEyes.)
- FireEyes can be configured to spoof user agent strings, making it easier to work on certain types of mobile sites and apps. This can be configured under the “Settings” tab.
- Analysis: updated color contrast analyses.
- Scripting: provide better warning messages when editing scripts in FireEyes that have been saved to, or loaded from, a project on Worldspace Sync.
- Scripting: the scripting “scaling factor” from earlier betas has been renamed to a script replay “speed”, which can be set to slow down replay of certain problematic scripts.
- Scripting: a timeout value, defaulting to 30 seconds, can be configured for scripts. This controls how long the script replay will wait for a newly loaded page to be considered loaded and ready for analysis. This value may need to be adjusted upwards for very slowly loading pages/environments.
- SimulAT: SimulAT has a new feature that allows you to see all structural elements OR all content-related elements for a single page.
- SimulAT: Display of data tables visually shows table captions and headers, and other relational data (such as the relationship between data cells and their corresponding headers).
- SimulAT: when simulating an AT announcement of “invisible” elements, SimulAT will attempt to highlight a parent element instead. (For example, this is very common when navigating drop-down or fly-out navigation menus.)
- Settings: better feedback when configuring or changing Worldspace Sync accounts.
Bug fixes in release 1.0.21
- Analysis: many improvements to the analysis rules used by FireEyes.
- Analysis: reading order and color contrast analyses respect the project’s analysis options.
- Analysis: improve stability and performance of analyses. Ensure that problems with a specific rule do not prevent analysis from continuing.
- Analysis: improve stability of analysis of rules involving checking image dimensions and other metadata.
- Analysis: when creating issues, do not add an “xmlns” attribute to the serialized HTML snippet, unless the attribute has an uncommon value.
- Scripting: when saving a script to Worldspace Sync, provide better feedback for invalid script names and other error conditions.
- Scripting: when replaying a script, certain elements of the FireEyes UI are disabled during replay. These become enabled after script replay has finished or been stopped.
- SimulAT: improved compatibility with a variety of sites and markup elements (including frames and iframes). If a site failed to SimulAT under an earlier beta, please try it once more with the release version.
- Settings: improved normalization of Worldspace Sync URLs; server URLs can be entered with or without a protocol and/or trailing slash (‘/’).
- Performance improvements when launching FireEyes, when displaying and rendering data, and when interacting with Worldspace Sync.
- Stability improvements when interacting with Worldspace Sync over a slow or unreliable network connection.
- Better handling of corrupted FireEyes data in a user’s Firefox profile.
- When viewing the details for an issue, the document is no longer automatically frozen/thawed by FireEyes.
- When adding a new manual issue, the issue has a better default description.
- Improved experience when navigating FireEyes using only a keyboard.
- When the “Highlight” option is on, highlights for issues will automatically update/move to reflect changes in the document.
- Fix a problem where issues would disappear from FireEyes after being uploaded to Worldspace Sync and “Do nothing” was selected as the “After upload” action.
Known issues in release 1.0.21
- When using AT such as JAWS or NVDA to access FireEyes, some elements of the user interface can be difficult to use. In particular, if using JAWS, a user has to manually switch between modes in order to access all of the content inside FireEyes. (#1671 and numerous other bugs)
- If network connectivity is disrupted during upload or download of issues to or from Worldspace Sync, the FireEyes UI can become “stuck”. If you experience this problem, please close the upload or download dialog, verify that you are connected to Worldspace Sync inside FireEyes, and try again. (#836)
- If you are using FireEyes in multiple browser tabs, all in the same project, in certain conditions, duplicate issues can appear in the “Current Document” tab. If you see duplicated issues, simply refreshing the page will resolve the problem. (#889)
- If there are a large number of issues (> 1000) being loaded into FireEyes, FireEyes can become temporarily unresponsive while they are processed. (#1617)
- On OS X, if the document is in the “Frozen” state, command-Q and other Firefox keyboard commands fail to execute. You must first “Thaw” the document. (#1537)
- Depending on the version of Firebug, the “Add New Scope Definition” feature inside the Firebug HTML inspector may not work, or may not be available at all. (#1327)
- Analysis: On Windows and in Firefox 4 and newer, the visual focus indicator test does not work. This is due to an incompatibility in Firefox 4 between Windows and other platforms. If you need this feature, please use another platform like OS X, or use Firefox 3.5 or 3.6 on Windows. (#1252)
- Analysis: reading order analysis can generate false positives on certain sites. (#716)
- Scripting: when recording a script, there is no way to clear an input field before entering other values. You may be able to work around this by recording or creating a “change” event for the field. (#695)
- SimulAT: when inspecting data tables using header markup in addition to rowspan and/or colspan attributes, SimulAT will not take the rowspan or colspan attributes into account and can therefore show misleading related nodes. (#1334)
- SimulAT: on certain sites using complex framesets, SimulAT can fail to generate a report. (#1333)
- Settings: when creating or editing scope definitions, the “Pick Target” feature may yield an incorrect xpath address on certain sites. (#1014)
- Settings: it is possible to create a new scope definition that has no name. (#1395)
- Settings: the “Perform color usage analysis on every single DOM mutation event (SLOW)” and “Ensure that Firebug accessibility enhancements are turned on when FireEyes launches” settings will ALWAYS be set to their default values when FireEyes is launched. The defaults are true and false, respectively; most users will not need to change either setting. If you do need to change the setting, you will have to change it after FireEyes is launched. (#1326)

Beta 4

New Features in Beta 4
- As of 4/9/2011, Firefox 4 is supported by Worldspace FireEyes Beta 4
- The SimulAT feature has been made available to simulate what assistive technology would experience on the page.
- The Focus button has been added to allow FireEyes to automatically detect missing visual focus indicators.
- The ARIA button has been implemented to allow static analysis of ARIA roles and attributes. Additional ARIA rules have been implemented and made available through the analysis settings and through the ARIA button.
- The integration into the Worldspace Enterprise server has been released allowing content encountered during a script replay to be sent to a Worldspace FireEyes collection for analysis and reporting
- Worldspace Enterprise customers can synchronize their FireEyes projects with JIRA allowing a JIRA issue to be created and tracked for each page analyzed.
- The image alternative text rules have been improved to support the Jim Thatcher 11 (JT11) image analysis methodology. This distinguishes between active, informational and formatting images.
- Worldspace Enterprise customers can create custom standards for use with the FireEyes server and extension. These custom standards allow for the inclusion of all existing Deque rules as well as custom rules.
- Worldspace Enterprise customers can create custom rules for use in the FireEyes server and the extension.
- Worldspace Enterprise customers can create weights for the issues generated by Worldspace FireEyes allowing pages and issue categories to be ranked according to importance.
- The synchronization between the server and the extension has been eliminated, this leads to many performance improvements, especially when working with a large number of projects.
- The toolbar has been made collapsible, allowing for users with narrow screens to access all the features in the toolbar using only the mouse.
- Worldspace Enterprise customers can create groups and use these groups to control access to projects.
- Worldspace Enterprise customers can create projects with project administrators as well as project members. Project administrators can control things like project membership, project standard, project policies. Project members can analyze pages, work on issues, scripts, pages etc.
- Worldspace Enterprise customers can create projects that allow the issues to be managed and reported on by page in addition to the issue level functionality available in public projects.
- Scripting and script replay now supports infinite frame nesting
- When exporting issues to Excel from the server, the relevant standards for the issue will also be exported.
- User logins have now been converted to lower case only, avoiding potential duplicate account creation that was common when users were invited to join the service.
- Many performance enhancements were made and memory leaks were fixed, leading to better performance over a long period of time.
- The analysis rules were improved and many conditions that had previously caused the analysis to hang or fail have been fixed.
- Script replay has been made much more robust, in particular where pages are very “chatty”, the script will no longer hang indefinitely although it might take a long time to complete.
- Projects can now be deleted on the server
- Project creation has now been moved to the server
- Projects can now have multiple domains and the domains in the projects no longer have to be unique
- User can now control which project they are working on and can therefore use a particular project’s settings for multiple web sites (although the upload of issues will only store the issues corresponding to the project domains)
Bug Fixes in Beta 4
- When adding multiple synthetic script events, the order is now maintained correctly
- Bugs were fixed that caused the issue download and upload to sometimes fail silently
- Fixed the bug that caused the issue list to sometimes display duplicates of the issues when switching between multiple tabs
Known Issues in Beta 4
- On Windows and in Firefox 4, the visual focus indicator test does not work. This is due to an incompatibility in Firefox 4 between Windows and other platforms. If you need this feature, either use another platform like OS X, or user Firefox 3.5 or 3.6.

Beta 3

New Features in Beta 3
- Server implemented to allow sharing of issues, scripts and templates
- Support for exporting lists of issues in Excel format
- Server projects can be used to store the default settings for a user for a particular project
- Server projects can be shared with other users by inviting them to the project. The invitees will automatically be given the same default settings as the inviter.
- Users can record scripts and share these scripts with all project members by uploading them to the server.
- Users can share generated issues with project members by uploading them to the server.
- Users can create scope definitions to break pages up into the components that different users or groups are repsonsible for and share these scope definitions with all members of the project.
- Users can track the status of shared issues and mark them as fixed or ignored (in the case of false positives). These dispositions are remembered and applied to all future detected instances of an issue.
- Users can assign issues to each other and track the overall progress of issues in the project through the project summary
- Users can attach labels to issues for easy sorting and filtering.
- A powerful filtering interface is available to allow large lists of issues to be managed.
- Users can download issues from the server into the extension for debugging or remediation. They can apply filters such as assignee, status, URL and label to target a particular set of issues.
- Users can capture issues manually and manage these manually captured issues along with the automatically detected issues.
- Issues uploaded to the server are de-duplicated intelligently to minimize the number of issues that needs to be tracked to the unique issues.
- A comprehensive set of help files is now available from within the server UI
- The issue details now contains a list of the standards that apply to the issue as well as the issue status and assignee.
Improvements and Bug Fixes in Beta 3
- The color contrast analyzer is now fully WCAG 2 AA compliant with respect to flicker rates.
- The speed of the automatic analysis has been greatly improved in the case of highly dynamic sites.
- The speed has been improved due to the elimination of memory leaks in the extension’s HTML UI.
- An issue has been fixed with the intermittent display of a Java initialization warning when the Java initialization had in fact completed correctly.
- The color use rules have been improved to generate fewer false positives
- The clear button now allows the user to specify which elements to clear.
- The export functionality has now been moved to the server and supports Excel (see above)
- A multitude of accessibility enhancements have been made including better keyboard navigation through the extension’s issue list and improved announcements when being used with NVDA.
- Added a document level analysis feature to the scope selection to allow for testing of everything except what has been defined in the templates or the selected templates.
- The script replay has been improved to now wait for the page to completely draw and to wait for the prior event’s analyses to complete in addition to waiting at least the time specified in the script prior to firing the next event. This leads to more predictable script replay.
- Scope definition explorer now shows the robust and the non-robust XPaths
- Reading order issues have now been moved to the manual verification severity level from the violation severity level
- about:javascript and about:blank addresses are now no longer considered valid issue addresses
- On pages with single quotes inside JavaScript code, the analysis sometimes failed to generate any issues. This has been fixed.
- An option has been added to allow the user to reset to the settings stored for them on the server in addition to the existing option of restoring their settings to the FireEyes defaults.
- The script timeout settings for Firefox are now automatically set to values that work well with FireEyes – eliminating the annoying popup warnings for long running scripts.
- The download mechanism for the extension has been improved to now be correctly interpreted by Firefox, leading to an improved download experience.
- We have used ARIA live-regions to announce the status and updates for background tasks to the AT
- We have fixed a bug where the button controls became unresponsive after a tab was opened for a web site Firebug is disabled
- We have fixed many memory leaks that caused the Firefox process to consume a large amount of memory and eventually become unresponsive over the course of a day of using FireEyes.
- When exporting issues to Excel or .csv, the mapping to the issues relevant Section 508 paragraph, WCAG 1 technique and/or WCAG 2 success criteria is also exported
- We fixed an issue where dynamic issues being uploaded to the server would cause the dialog to display until dismissed and also failed to upload the issues to the server
- We fixed some confusing focus changes when issues are deleted from the issues list using the keyboard
- The server now supports the storage of UTF8 content allowing issues from multilingual sites to be stored and retrieved correctly
- Fixed the color contrast and reading order analysis buttons to only replace the issues from the current document instead of replacing all the color contrast or reading order issues in the issues list
Known Issues In Beta 3
- Sometimes, code can fail silently when the network connection is temporarily interrupted
- Firefox 4.0 is not supported due to an issue with Java support in Firefox 4.
- The spoken text in the combo-boxes for capturing manual issues in the extension is not understandable by some AT (in particular NVDA)
- Some DOM changes do not trigger automatic analysis. In particular changes that affect only the text of a node will sometimes not be picked up.