Giacomo Petri

Related Documents links - Insufficient contrast ratio

1

- **URL**: https://www.w3.org/WAI/ARIA/apg/example-index/landmarks/index.html - **Accessibility failure**: contrast ratio between related documents links text color and background is not sufficient (#337ab7 foreground color and #f4f4f4 background color, with a contrast ratio...

Order of headings - Note regions

1

- **URL**: https://www.w3.org/WAI/ARIA/apg/patterns/dialogmodal/ (or any page containing a NOTE section) - **Accessibility failure (not following best practices)**: every NOTE section starts with an H5. Even though the NOTE content is...

Update autocomplete-valid-value-73f2c2.md

1

Updates: - updated **fixed values** list item in Applicability section adding necessary type values to reflect html specs; - removed "hidden" type from that list; - added background note both...

Text has enhanced contrast - Passed example 7 + clarification

2

While reviewing pull request [#1904](https://github.com/act-rules/act-rules.github.io/pull/1904/) I noticed passed example 7: > This text has the default browser text color on the default browser background color. By default this is black...

Update image-button-non-empty-accessible-name-59796f.md

2

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...

Focusable element has no keyboard trap via standard navigation - Expectation + add clarification

2

- 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...

Autocomplete attribute has valid value - Input type image [73f2c2]

2

- Rule: Autocomplete attribute has valid value - URL: https://www.w3.org/WAI/standards-guidelines/act/rules/73f2c2/#attribute-value - Reference: https://html.spec.whatwg.org/#image-button-state-(type=image) > The following content attributes must not be specified and [do not apply](https://html.spec.whatwg.org/#do-not-apply) to the element: [accept](https://html.spec.whatwg.org/#attr-input-accept),...

Heading has non-empty accessible name - Failed Example 8

1

In [Heading has non-empty accessible name](https://www.w3.org/WAI/standards-guidelines/act/rules/ffd0e9/proposed/), [Failed Example 8](https://w3.org/WAI/content-assets/wcag-act-rules/testcases/ffd0e9/0bf7d49ddf99066b816fe42e5cd827a15c7ad24d.html) > This h1 element has an [explicit role](https://www.w3.org/WAI/standards-guidelines/act/rules/ffd0e9/proposed/#explicit-role) of none. However, the [global](https://www.w3.org/TR/wai-aria-1.1/#global_states) [property](https://www.w3.org/TR/wai-aria/#dfn-property) aria-label is specified. Per [ARIA 1.3 -...

Form field has non-empty accessible name - Input nested into a label with for attribute pointing to a non-existing element

8

Hello, I’ve a question about a specific scenario, referring to [Form field has non-empty accessible name](https://www.w3.org/WAI/standards-guidelines/act/rules/e086e5/) ### Example: ``` First name ``` ### Properties: - label containing input (sufficient technique)...

"Image button has non-empty accessible name" [59796f] - clarification about input type image with empty alt but non-empty title

11

- **Starting URL**: https://www.w3.org/WAI/standards-guidelines/act/rules/59796f/ - **Highlighted element**: input type image, empty alt attribute and non-empty title attribute `` - **Description**: should we add an example for input type image with...