New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 874384 link

Starred by 1 user
Status: Assigned
Owner:
joanmari...@gmail.com
Cc:
█ krajshree@chromium.org
aboxhall@chromium.org
dmazz...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Forms without accessible names should no longer be mapped as a form

Project Member Reported by joanmari...@gmail.com, Aug 15 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3522.0 Safari/537.36

Steps to reproduce the problem:
1. Load data:text/html,<form action="POST"><input type="submit"></form>
2. Use Accerciser (or the Windows equivalent) to view the accessibility tree

What is the expected behavior?
The form would NOT be exposed with the platform's accessibility "form" role because it lacks an accessible name.

What went wrong?
The form is exposed with the platform's accessibility "form" role.

Did this work before? N/A 

Chrome version: 70.0.3522.0  Channel: n/a
OS Version: 
Flash Version: 

According to the HTML-AAM, forms without an accessible name are no longer mapped as a form (i.e. with ATK_ROLE_FORM in Linux, with IA2_ROLE_FORM in Windows). See https://w3c.github.io/html-aam/#details-id-42 and https://github.com/w3c/html-aam/issues/106

Comment 1 by swarnasree.mukkala@chromium.org, Aug 15

Labels: Needs-Triage-M70

Comment 2 by morlovich@chromium.org, Aug 17

Components: Blink>Accessibility

Comment 3 by krajshree@chromium.org, Aug 30

Cc: krajshree@chromium.org
Labels: Triaged-ET Needs-Feedback
Reporter@ - Thanks for filing the issue...!!

Could you please provide a sample test file/url to test the issue from TE-end.
This will help us in triaging the issue further.

Thanks...!!

Comment 4 by dmazz...@chromium.org, Sep 15

Owner: joanmari...@gmail.com
Status: Assigned (was: Unconfirmed)
Joanie, can I assign it to you? I think I'd prefer to do this in the Linux/Win platform code that maps internal roles to platform roles, not in Blink - because other platforms may prefer to know it's a form.

I'm also curious why this rule? What's the harm in having the form role?

Comment 5 by joanie.d...@gmail.com, Sep 17 

Sure. It was already on my to-do list.

The rationale is that the form element is treated as a landmark by screen readers, but "many frameworks including .NET wrap an entire web page in a FORM element, obviously not very functional as a landmark." See https://github.com/w3c/html-aam/issues/106

I agree that other platforms may prefer to know it's a form. Personally I think that things which Orca should treat as landmarks have ATK_ROLE_LANDMARK, and things which should not have some other role (which might be ATK_ROLE_FORM). But I don't feel strongly enough to argue with nameless forms being treated as if they were divs so I've not pushed back.
►

Sign in to add a comment