We made some changes to keep the rules engine running smoothly.
- New (manual):
bestPracticeEaacovers best practices specific to EN 301 549. - Fix:
iframeelements now have access to the accessibility tree context for where they occur in the DOM and can utilize this information during a scan. - Fix:
ARIAAttributeNotAllowedincorrectly flaggedheaderandfooterelements that included a validaria-labelattribute. - Fix:
buttonElementHasLabelnow correctly ignores buttons that are not in the accessibility tree. - Fix:
DataCloneError: Failed to execute 'postMessage' on 'Window': HTMLElement object could not be cloned. - Change:
navigationUnfocusableLinkPurposenow ignoresaelements with atabindex="-1"and a validhrefas they are considered implementations of the roving tabindex technique.
Note: Some users may see a decrease in their results if they have been properly utilizing the roving tabindex technique.
- Change: Elements that are hidden by their parent are now tested first so that individual child states do not override the parent hidden state.
Note: Some users may see a fluctuation in the their7 results due to this change as it involved an update to the order of operations for determining whether an element is visible in the accessibility tree based on its position within the DOM.
- Change: The response from the engine now returns additional information needed by the ARC Platform including: detailed information about the page and its metadata and additional metadata for each node returned including attributes and styles.