This release features lots of new features including:
- Support for ARIA 1.2, ARIA DPUB roles, and ARIA Graphics roles
- ShadowDOM support (note: that this is an experimental feature and must be enabled per-scan)
- 12 new automated rules and updates to 7 existing automated rules
- Use CSS selectors, instead of just XPath, for identifying targets
What's Changed
- New: Support for ARIA 1.2
- New: Support for Digital Publishing (DPUB) ARIA roles
- New: Support for Graphics ARIA roles
- New: Support for scanning the Shadow DOM
- New: Event callback added for realtime monitoring of the rule engine
- New: Support CSS selectors identifying targets
- New (automated):
presentationalChildrenNotFocusableidentifies focusable elements found within presentational children - New (automated):
menuitemElementHasLabelidentifies menuitems with no accessible name - New (automated):
objectHasAccessibleNameidentifies<object>with no accessible name - New (automated):
pageXMLLanguageIdenticalchecks thatlangandxml:langattribute values match - New (automated):
wordSpacingIsAdjustablechecks that the style attribute is not used to prevent adjustingword-spacingby using!important, except if it's at least 1.5 times the font size - New (automated):
lineHeightIsAdjustablechecks that the style attribute is not used to prevent adjustingline-heightby using!important, except if it's at least 1.5 times the font size - New (automated):
letterSpacingIsAdjustablechecks that the style attribute is not used to prevent adjustingletter-spacingby using!important, except if it's at least 1.5 times the font size - New (automated):
tableCellHeadersCorrectchecks the references in theheadersattribute exist within current table - New (automated):
tableHeadersMissingCellchecks that each header is associated with a cell in the same table - New (automated):
iframeNegativeTabindexchecks that frames with negative tabindex contain no interactive elements - New (automated):
scrollableElementIsKeyboardAccessiblechecks if a scrollable element is focusable or has a focusable child - New (automated):
cssOrientationIsNotRestrictedchecks if the orientation of the page is not restricted using CSStransformproperty - New (manual):
thirdPartyContentfor identifying third-party applications that are barriers to accessibility - Change (automated):
navigationLinkLabelInNamesupport for non-textual characters - Change (automated):
pageNotRefreshRedirectchecks if refresh value <= 20 hours and if redirect is to itself or another page - Change (automated):
colorContrastDisabled interactive form controls are not tested for contrast - Change (automated):
ariaHiddenUsednow checks all elements in the accessibility tree; previously only non-focusable elements were checked - Change (automated):
zoomingDisablednow only checksmetaelements that includemaximum-scaleoruser-scalable - Change (automated):
inputButtonHasValuerecategorized from an Alert to Best practice - Change (automated):
colorContrastSVGTextonly test the<text>within ansvgelement - Change (manual):
parsingmanual rule is recategorized as a best-practice in WCAG 2.0 and WCAG 2.1 - Change (manual): The default severity value for the manual Custom Widget rules were changed from Medium to High
- Change (manual):
uiComponentsRelationshipsSeverity changed from Critical to High - Change (automated):
ruleduplicateLabelIsUsedminor updates to rule description - Update: Logging from within frames is now more reliable
- Fix: Rules that test attributes with multiple values (e.g.
aria-describedby) now correctly test the individual values - Change:
problematicAltTextis only raised when identified words are lowercase - Update: Use "best-practice" category to explicitly identify best practices
- Change: Elements with 0 width/height are now considered not visible
- Fix: Return topic key, instead of title, on results
- Chore: Update ACT testrunner to use latest test cases
- Docs: Reasons why some ACT test suites and individual testcases are not passing