act-rules.github.io
act-rules.github.io copied to clipboard
act-rules
Accessibility conformance testing rules for HTML
* Fix Failed Example 1 to ensure there actually is a keyboard trap * Add a clarification about forward and backward navigation Closes issue(s): - closes #1885 Need for Call...
Add "logo" to the name of images that are logos, where it make sense. I feel it doesn't make sense in cases like ```html ``` where the image is functional...
There's a mismatch between the rule applicability, the rule example wording and the HTML spec: - Rule applicability allows headers to reference `td` or `th` elements (cells, as defined by...
Added: * failed example 3 * updated "Accessibility Support" section Closes issue: #1861 Need for Call for Review: This will require a 1 week Call for Review Note: Sorry if...
- Rule: Focusable element has no keyboard trap via standard navigation - URL: https://www.w3.org/WAI/standards-guidelines/act/rules/a1b64e/proposed/ - Description: 1. From Expectations: > For each target element, focus can cycle to the browser...
Currently updating only "Line height is not `!important`" to check whether that solution works or not. The second and third condition where about the test target, which is incorrect since...
> Closes issue(s): - closes #XXX (ADD ISSUE NUMBER HERE) Need for Call for Review: > > This can be merged with 1 approval > This will not require a...
Although having treeitems inside a menu doesn't make sense, I don't think this violates the required owned elements conditions in ARIA 1.1 and 1.2 so example 7 shouldn't be a...
For test case examples that use a logo for an image, the accessible name for the image should include that it is a logo. In this [Passed Example 1](https://act-rules.github.io/rules/qt1vmo#passed-example-1) for...
Question about the Expectation for the [rule](https://act-rules.github.io/rules/a1b64e) for no keyboard trap: > For each target element, focus can cycle to the browser UI by using standard keyboard navigation. > Note:...