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

Issue 702445 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

IAccessible2 tag object attribute no longer exposed

Project Member Reported by ja...@nvaccess.org, Mar 17 2017

Issue description

Chrome Version: 59.0.3043.0 (Official Build) canary(64-bit)
OS: Windows 10 64 bit

STR (with the NVDA screen reader):
1. Open this URL in Chrome: data:text/html,Before<blockquote>Inside</blockquote>
2. Press control+home to ensure you're at the top of the document.
3. Press down arrow.
Expected: NVDA should say "block quote  Inside"
Actual: It just says "Inside"

The IAccessible2 "tag" object attribute is no longer being exposed (via IAccessible2::attributes). This is necessary in order for IAccessible2 clients to detect block quotes. It's also extremely useful for debugging.

On the above blockquote accessible, we get only the following attributes:
display:block;
We would ideally get something like this:
display:block;tag:blockquote;

This is a regression, but I'm not sure when it happened. I know it worked in 40.0.2201.2 canary, since I confirmed that  issue 347854  related to block quotes was fixed in that version. It's broken in 57.0.2987.110. That's a pretty massive regression window, though. :(
 
Labels: NewComponent-Accessibility NewComponent-Accessibility-Compatibility
Components: UI>Accessibility>Compatibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility
Owner: aleventhal@chromium.org
Status: Assigned (was: Untriaged)
Jamie, the IA2 tree looks correct. Maybe it was fixed since you file the issue. Will you try again? I'm adding a test.

Comment 7 by ja...@nvaccess.org, Jun 11 2017

Status: Verified (was: Assigned)
Yes, it's now fixed. Nektarios noted that it was fixed in an email to me dated 22 March, but this issue didn't get closed. I don't know what commit fixed it, though.

Sign in to add a comment