Giacomo Petri comments

Results 61 comments of


                                            Giacomo Petri

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

@Jym77, sure, I'm creating a html file containing the entire list of examples for every element that supports alt (img, input type="image" and area) with the combination of title and...

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

Attaching file for reference with all scenarios: [img-inputimg-area-examples.zip](https://github.com/act-rules/act-rules.github.io/files/8928853/img-inputimg-area-examples.zip) note: I've attached a compressed file due to the need of adding valid images to compare with non-loaded images.

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

Request to the HTML AAM group submitted. Once we have an answer with good practices, if still valid I'll ping browser side to understand if they consider highlighted scenarios as...

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

Updates: per HTML AAM https://github.com/w3c/accname/issues/27#issuecomment-802138411 the intent was: > if there's an alt="" that would indicate that the image is meant to be "hidden", and therefore the steps would stop...

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

Updates: In light of @scottaohara clarification at https://github.com/w3c/html-aam/issues/414#issuecomment-1178384158, https://github.com/act-rules/act-rules.github.io/pull/1865#discussion_r916355347 and https://github.com/act-rules/act-rules.github.io/pull/1865#discussion_r916544922 the combination of empty alt attribute and non-empty title attribute gives the input type image a non-empty accessible name...

"Links with identical accessible names and context serve equivalent purpose" [fd3a94]: Definition of context is still not good enough

Thanks Jym for opening the issue. I was thinking about my request, also comparing it with the existing passed and failed examples, and I made some broader considerations: Rule title:...

"Links with identical accessible names and context serve equivalent purpose" [fd3a94]: Definition of context is still not good enough

Failures provided are ambiguous to users in general, in my opinion. Two links with identical accessible name and with the same programmatically determined context, but with different CSS backgrounds (that...

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

Before closing this one, based on https://github.com/w3c/accname/issues/154, do we want to add 2 examples to the existing rule (one passing, one failing) highlighting which is the correct approach for input...

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

\+ I would like to underline few thoughts and I'll do it as they come to my mind, even if they are not strictly related to the ACT-rules activities. ###...

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

@Jym77, I've just mentioned our topic in WCAG. This in an interesting reading for points above (including the original intent of 4.1.1).