[Webkit-unassigned] [Bug 197786] New: AX: elements inheriting display:table announced as data table
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri May 10 10:29:56 PDT 2019
https://bugs.webkit.org/show_bug.cgi?id=197786
Bug ID: 197786
Summary: AX: elements inheriting display:table announced as
data table
Product: WebKit
Version: Safari 12
Hardware: iPhone / iPad
OS: iOS 12
Status: NEW
Severity: Minor
Priority: P2
Component: Accessibility
Assignee: webkit-unassigned at lists.webkit.org
Reporter: rbsmith10291986 at gmail.com
CC: webkit-bug-importer at group.apple.com
This issue is similar to a past issue: https://bugs.webkit.org/show_bug.cgi?id=144804
"A layout table can be coded using a <div> element styled with display:table, and children <div> elements with display:table-cell (plus other table-* rules to define the table’s rows and column).
The expectation is that since the tabular structure is defined with the styling and not with structural markup (e.g. html <table> element or WAI-ARIA role=“table), the content should not be exposed by VO as an actual table. This irrespectively of other style applied to the elements (e.g. borders)."
In this case, we are using display:table-cell for alignment of a label, and VO is announcing "table start" and "table end" when swiping to the control. There is also a CSS-generated ::before class above the control, with display:table. This is a layout table with no table semantics in the html, so it should not be announcing as a table.
Unlike the bug from 2015 above, there are no functional issues entering the "table area" - it's simply a matter of unnecessary/confusing announcement of a table.
This issue is also described here: https://labs.levelaccess.com/index.php/CSS_Display_table_iOS_SamC
"CSS property display:table causes VoiceOver to announce the affected content block as if it were in a table, announcing "table start" and (conditionally) "table end". Whether this issue began only with recent versions of VoiceOver (11+) is unknown without further testing." Based on this description, this may be a regression of the previously fixed issue.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190510/618cdddd/attachment.html>
More information about the webkit-unassigned
mailing list